| |
JCH
Registered: Aug 2008
Posts: 200 |
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 |
|
... 145 posts hidden. Click here to view all posts....
|
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Wow.. that was quick. Thank you! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
There are still some flaws with those Makefiles... first obvious one reported by Mr.Ammo: if you compile on macos and it gives you a ton of errors, add -std=c++17 to FLAGS :) The same might be required on Linux, depending on your version of GCC |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Yeah, needs c++17 for sure. We've got the macOS version already. Not that I know much about the mac really, but I did have to do a lot of changes to the code for Clang to agree with it, because it was written in Visual Studio, and the MS compiler is not following the standards fully and allowing thing that Clang will get really upset about :)
Looked over the diff. Looks like you only had to implement a copy of the macos platform for linux and add a few includes for making memset available. Nice.
I'll make sure to bring those over to the current work and extend it to support the new features.
I noticed the builds were crazy HUGE.:) |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quoting GroepazThere are still some flaws with those Makefiles... first obvious one reported by Mr.Ammo: if you compile on macos and it gives you a ton of errors, add -std=c++17 to FLAGS :) The same might be required on Linux, depending on your version of GCC
Compiles on Ubuntu 20.04LTS, gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0, though with quite a few warnings (here: sf2-20200718_warnings.txt).
It seems to run fine, but I only loaded and played a demo song.
A rather weird anomaly is that selecting '..' in the file selector gives a modal warning about invalid file, but pressing enter there clears it and still goes to the parent directory. |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quoting LaxityI noticed the builds were crazy HUGE.:)
tlr@sakura$ ls -l sf2
-rwxrwxr-x 1 tlr tlr 28679328 Aug 13 21:07 sf2
tlr@sakura$ strip -s sf2
tlr@sakura$ ls -l sf2
-rwxrwxr-x 1 tlr tlr 992208 Aug 13 21:16 sf2
tlr@sakura$
Better? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Quote:We've got the macOS version already.
yes, sure. but some ppl prefer compiling on the commandline :)
it might actually be possible to remove the need to define this _SF2_whatever symbol, and use system specific symbols instead... so a single makefile will work for all of them. a good start would be to require _SF2_MACOS for macos, and not put the macos stuff in the "else" branches (instead put an #error there). In another step you can then replace those by system specific (defined by your compiler, or IDE) defines, like _WIN32 for windows. Oh well. it works either way for now :=)
edit: oh yeah, perhaps remove the -g from FLAGS (that will add debug symbols) |
| |
JCH
Registered: Aug 2008
Posts: 200 |
The ".." file thing is a bug that we've fixed in the next build to come. You can use Backspace instead in Windows, hope that works in Linux too. |
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Quote: The ".." file thing is a bug that we've fixed in the next build to come. You can use Backspace instead in Windows, hope that works in Linux too.
Backspace works in linux too, thanks! |
| |
Laxity
Registered: Aug 2005
Posts: 459 |
Quote: Quoting GroepazThere are still some flaws with those Makefiles... first obvious one reported by Mr.Ammo: if you compile on macos and it gives you a ton of errors, add -std=c++17 to FLAGS :) The same might be required on Linux, depending on your version of GCC
Compiles on Ubuntu 20.04LTS, gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0, though with quite a few warnings (here: sf2-20200718_warnings.txt).
It seems to run fine, but I only loaded and played a demo song.
A rather weird anomaly is that selecting '..' in the file selector gives a modal warning about invalid file, but pressing enter there clears it and still goes to the parent directory.
Yeah, ok. I havn’t had initialization order warnings since coding for PS3, it’s not a standard level of warnings In Visual Studio, nor XCode. I guess you can win some speed on the cachelines, but for the purpose of this application, that seems like a waste of time.
I have some warning using clang, which sre all in reSID, else nothing.
The “..” bug is fixed. I actually thought it was in released source also. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
i added -Wall in the makefile, which is what i always do... they are always worth fixing, IMHO, cleaner code does never hurt :) (i even use -Wextra -W for my own stuff) |
| Previous - 1 | ... | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | ... | 16 - Next |
