Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
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-14 14:18
chatGPZ

Registered: Dec 2001
Posts: 11391
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?
2020-08-14 14:29
Stone

Registered: Oct 2006
Posts: 172
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.
2020-08-14 14:36
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*.
2020-08-14 15:44
chatGPZ

Registered: Dec 2001
Posts: 11391
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 :)
2020-08-14 16:12
Compyx

Registered: Jan 2005
Posts: 631
Yeah, a public source repo would help a lot.
2020-08-15 10:26
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.
2020-08-15 10:42
Krill

Registered: Apr 2002
Posts: 2982
Why not put the repository on chordian.net? Full control. \=D/

(I don't trust github et al. either.)
2020-08-15 10:50
spider-j

Registered: Oct 2004
Posts: 502
Quoting Laxity
It 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.
2020-08-15 11:18
Krill

Registered: Apr 2002
Posts: 2982
Quoting spider-j
Of course – as Krill pointed out – self-hosting is an option to have full control if you're really concerned about that.
And it may even be read-only for anyone but the admin. If someone requests merging in a patch, they'd just send a diff with the latest repository version.

Worst that can happen is that they decide to fork the project and put it on github et al. themselves, but that's how it is with free and open source. :)
2020-08-15 12:10
chatGPZ

Registered: Dec 2001
Posts: 11391
First of all i wouldnt bother hiding a "development branch" - that only creates more work (someone contributes a fix - and then you cant just apply it, but have to merge it into your development branch). There will be very few ppl actually looking at the code anyway - and those who do should better see the current version, and not something from the last release.

I dont recommend self hosting either if you have no experience with that - again, it only creates more work with very little gain.

If you create a github project, you should get everything you want. You can just not grant anyone write access, so you have full control over whats in the repo. And everyone who wants to contribute fixes can clone the repo and send you a pull request, which is then very easy to merge (with a single click).

I dont like github all that much myself, but thats because i had many years of exposure to subversion before, and i am just too used to it (and it does all i need/want). If you dont know either, starting with git is probably the much better idea :) (warning: it can be very WTF at times)
Previous - 1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Fred/Channel 4
Guests online: 103
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Coma Light 13  (9.6)
4 Edge of Disgrace  (9.6)
5 Mojo  (9.6)
6 Uncensored  (9.6)
7 The Demo Coder  (9.6)
8 Comaland 100%  (9.6)
9 What Is The Matrix 2  (9.6)
10 Unboxed  (9.6)
Top onefile Demos
1 Layers  (9.7)
2 Cubic Dream  (9.6)
3 Party Elk 2  (9.6)
4 Copper Booze  (9.6)
5 Dawnfall V1.1  (9.5)
6 Rainbow Connection  (9.5)
7 Morph  (9.5)
8 Libertongo  (9.5)
9 Onscreen 5k  (9.5)
10 It's More Fun to Com..  (9.5)
Top Groups
1 Booze Design  (9.3)
2 Oxyron  (9.3)
3 Performers  (9.3)
4 Triad  (9.3)
5 Censor Design  (9.3)
Top Coders
1 Axis  (9.8)
2 Sailor  (9.8)
3 Graham  (9.8)
4 Crossbow  (9.8)
5 Lft  (9.8)

Home - Disclaimer
Copyright © No Name 2001-2025
Page generated in: 0.259 sec.