[CSDb] - User Forums - SID Factory II

You are not logged in - nap

CSDb User Forums

Forums > C64 Composing > SID Factory II

2020-06-05 15:41

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....

2020-08-13 14:47

chatGPZ

Registered: Dec 2001
Posts: 11386

@Laxity: Thumbs up! I can understand your reservations against showing the premature source - but really, this is not a problem in practise. Anyone looking at it knows that feeling :) "release early, release often" is the common way to do it :)

That said, there are a few things to consider regarding GPL

- you have put a GPL v3 license in the source package. you should *really* make sure this is actually what you want, and what the implications are (its quite different to the v2 in some regards). i can't explain this in a few words, but you should find more than enough info about GPL v2 vs GPL v3 on the net. (VICE and ReSID use v2 for that matter, with the "or later version" option)

- If you dont intend to change ReSID yourself, you should at least put a GPL v2 into the resid directories (actually, put the respective licenses into all the libs you are using). This avoids complications in the future.

- The source seems a bit "naked" to me. Depending on which GPL version you choose, you will have to provide everything required to build from source (that includes project files etc). also binary blobs like the driver .prg files can be a problem, those may require source too (with v3 i think this is a must, but it would be really nice in any case).

- Last not least, please add the license and contact info to your binary releases. That was actually one of the major reasons for me to even bring up the topic - when those things are missing, its usually a sign of someone trying to hide the fact he is using GPLd software.

I'd also suggest putting the source into a public repository, because that makes some things much easier. Totally your own choice, of course.

So - is anyone already looking into creating makefiles for linux? If noone else does, i will look into that, perhaps this weekend.

2020-08-13 15:30

Laxity

Registered: Aug 2005
Posts: 459

Thanks :)

I guess I can change it to v2 still, right?

What I did was look at what Cadaver provided with Goat, so I thought that was good enough for Jazz (except I got the license text from the interwebs). Contact info in form of physical address or email sufficient?

Driver sources aren’t required to run the software, and is more like a plugin. Drivers will be included later too. I guess from the next build we might have it where it makes sense. I would be surprised if that is a requirement, but hey - I know nothing about this stuff.

Would be great if you tried building for Linux. If you need any assistance, please let me know.

Thanks for the help so far.

2020-08-13 15:47

chatGPZ

Registered: Dec 2001
Posts: 11386

Quote:

I guess I can change it to v2 still, right?

If you want to get really anal about it... technically the one you released is now GPL v3 licensed. BUT - since you are the only author, you can always re-license it (This becomes a lot more difficult once you accept contributions from other ppl). So yes, you can do it :)

Quote:

Contact info in form of physical address or email sufficient?

email, or even a website with a contact form, is fine.

Quote:

Driver sources aren’t required to run the software, and is more like a plugin. Drivers will be included later too. I guess from the next build we might have it where it makes sense. I would be surprised if that is a requirement, but hey - I know nothing about this stuff.

This topic can become *really* difficult, i have usually solved it in the past by simply providing all source :) This "plugin" debate is something ppl in the community have been arguing about quite a bit in the past - the general consensus seems to be that: when your host program and the plugins are the only existing combination (the plugins can be used in exactly one host programs), this is no different to linking them into the binary, with all implications (ie GPL "infection"). But i'm not a lawyer.... it's something to consider however. This restriction exists so you cant "break" GPL by just compiling all GPL code into "plugins" and load it dynamically into your program.

2020-08-13 15:51

iAN CooG

Registered: May 2002
Posts: 3193

> I feel a bit like I've put out my dirty underwear for show.

Oh don't worry, there is a niche market for that kind of fetish too. :D

2020-08-13 16:16

tlr

Registered: Sep 2003
Posts: 1790

Quoting Groepaz

- The source seems a bit "naked" to me. Depending on which GPL version you choose, you will have to provide everything required to build from source (that includes project files etc). also binary blobs like the driver .prg files can be a problem, those may require source too (with v3 i think this is a must, but it would be really nice in any case).

The .prg binaries are in a grey area IMO. Is there really always source for included firmware? e.g microcode, CPU management engine, WIFI chipset code, etc...
That said, it would be really nice to have source for that as well. :)

Quoting Groepaz

So - is anyone already looking into creating makefiles for linux? If noone else does, i will look into that, perhaps this weekend.

Please do! :)

2020-08-13 16:33

Laxity

Registered: Aug 2005
Posts: 459

Quote: Quoting Groepaz
- The source seems a bit "naked" to me. Depending on which GPL version you choose, you will have to provide everything required to build from source (that includes project files etc). also binary blobs like the driver .prg files can be a problem, those may require source too (with v3 i think this is a must, but it would be really nice in any case).

The .prg binaries are in a grey area IMO. Is there really always source for included firmware? e.g microcode, CPU management engine, WIFI chipset code, etc...
That said, it would be really nice to have source for that as well. :)

Quoting Groepaz
So - is anyone already looking into creating makefiles for linux? If noone else does, i will look into that, perhaps this weekend.

Please do! :)

A shit. It tried to reply on the underwear comment. :)

Those are prgs that you can load on any c64, emulator and now also sid factory. Those files just provide at chunk of meta-data the editor can interpret.

2020-08-13 18:53

JCH

Registered: Aug 2008
Posts: 200

I have now replaced GPL v3 with v2 in all SF2 archives at the blog, including the one with source codes.

The file included is the plain text version I found here.

2020-08-13 18:55

Laxity

Registered: Aug 2005
Posts: 459

Awesome, buddy. :)

2020-08-13 19:19

chatGPZ

Registered: Dec 2001
Posts: 11386

I couldnt resist... i have it running natively. I had to add a couple missing includes here and there, and provide a platform file. Will fix the mess i made a bit and then post a link, stay tuned :)

2020-08-13 20:06

chatGPZ

Registered: Dec 2001
Posts: 11386

So yay, here it is.... Linux binaries (NOT statically linked with SDL2): http://hitmen.c02.at/temp/SIDFactoryII_Linux_20200718.zip

Source with Makefiles and additions required to compile on Linux:
http://hitmen.c02.at/temp/SIDFactoryII_Source_20200718_Makefile..

Included is a really quick and dirty makefile (and completely untested variants of it for msys and macos), and a .patch file which has all the changes in it, so you can review and copy/change those files in your sourcetree (or just copy over the changed files. i only added a few missing includes, plus added platform files for linux)

If you merge all those things, in the future the only eventually still needed changes for linux will touch the makefile or the platform files.

cheers :)