| |
JCH
Registered: Aug 2008
Posts: 193 |
SID Factory II
Laxity and I have decided to go BETA with SID Factory II to let all curious SID composers also have a go at this cross-platform SID editor.
We have a Facebook group that you are welcome to join. There's also a nifty user manual there. If you're not on Facebook, this thread should serve as another place where we can share questions, ideas, music, bugs, new builds, additional files, etc.
Please note that although SID Factory II is quite stable and more than capable of editing SID tunes at this point, it is still missing a few essential things such as e.g. sub tunes. We have a solid ToDo and will post new builds here as they become available.
The first official BETA build: SIDFactoryII_20200604.zip |
|
... 144 posts hidden. Click here to view all posts....
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11089 |
BTW, i have no clue at all on how to build a .deb - so if anyone wants to do that now, go ahead :) |
| |
Stone
Registered: Oct 2006
Posts: 168 |
I have started using cmake for all my multi platform hobby projects. It saves me from all the hassle of maintaining multiple build systems. Even selecting clang as the compiler for Visual Studio is dead easy. I highly recommend clang btw, it produces very sensible warnings and does a better job of optimizing than the Microsoft compiler. Resid-fp without floating point optimizations is extremely heavy on the CPU... |
| |
chatGPZ
Registered: Dec 2001
Posts: 11089 |
cmake for something like this is super overkill. the makefile contains like 1 command :) but i should indeed have not explicitly used g++ in it. oh well. does it matter really? |
| |
Stone
Registered: Oct 2006
Posts: 168 |
To each their own, but when I'm compiling for Windows, Linux and MacOS I don't think it's overkill at all, not even for the smallest of projects. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
It does, use $(CXX) so the user's default compiler can be used (and changed on the commandline).
And, as tlr mentioned it needs more -W*. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11089 |
yeah will do that kind of detail fixes once the other stuff is merged.
that said, i still recommend a public repo... it would be a lot less tedious to provide this kind of stuff :) |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Yeah, a public source repo would help a lot. |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
We’re considering the option of putting it on GitHub. I have 0 experience with this, so a factor is that we’d like to retain control of the project at the time being. I’m not quite sure how that really works on GitHub. It would be excellent if one can have a private development branch and a public ditto. There’s a bit to learn. :) Also, I can't imagine that SID factory II is much of a target for modifications yet, or might even ever be.
Anyway, I appreciate all the input from you guys. Thanks for taking the time to look at it. |
| |
Krill
Registered: Apr 2002
Posts: 2821 |
Why not put the repository on chordian.net? Full control. \=D/
(I don't trust github et al. either.) |
| |
spider-j
Registered: Oct 2004
Posts: 443 |
Quoting LaxityIt would be excellent if one can have a private development branch and a public ditto.
I'd guess that actually noone cares about dev branches unless you have a bug in master. In both cases: it's really no problem to also have dev public.
I don't think many people have the hobby to check dev branches and making fun of the ugly code they find there ;-)
Of course – as Krill pointed out – self-hosting is an option to have full control if you're really concerned about that. |
| Previous - 1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 - Next |
