Re: [Freecycle-users] midi export and libinstpatch bug fixes

[Predrag Viceic]

Hi Brandon !

 

Sorry for not responding faster, I monitor this list only from time to time.. :(

 

Well, as you guys have probably understood it, I'm not working actively on Freecycle anymore :( There is an embryo of implementation for Qt4, but there is lot of work to be done, and I'm turning 40 in few months, so job, family and all that stuff take quite a lot of time :)

 

That being said, I'll gladly help anyone take this project under his/hers wing !

 

If you Brandon, ore someone other is interested, you can checkout the last sources, import those to a GitHub account and who knows !

 

Best !

Predrag

 

 

 

Le mardi, 7 octobre 2014, 23.41:21 Brandon Smith a écrit :

> Hi All,

>

> I've created a pair of patches for freecycle that fix a couple of critical

> bugs, and now I'm happily chopping breaks in linux in 2014 :) The

> 'libinst1' patch updates the code to use the libinstpatch 1.0 api, which is

> the most recent version in modern repos, allowing sf2 export. This bug was

> mentioned here:

> https://lists.nongnu.org/archive/html/freecycle-users/2011-05/msg00000.html

> The 'midioutput' patch fixes the corrupt output of midi files, which was

> identified here:

> https://lists.nongnu.org/archive/html/freecycle-users/2009-06/msg00001.htm

> and here:

> https://lists.nongnu.org/archive/html/freecycle-users/2008-02/msg00000.html

> Now that these two bugs are fixed, I can import the midi file into my daw

> and play the chunks in fluidsynth.

>

> I also needed to make a lot of customizations to my development environment

> in order to build freecycle in Debian 7. I've attached a bash script of my

> build process, including apt dependencies and building qt3

> (installqt3fc.bash). Please note that there are required patches for both

> qt3 and freecycle, which I have also attached. It's pretty obvious that the

> qt4 port is the most important thing to get done, since qt3 is so out of

> date and needs to be patched to even work. If freecycle could be built

> against qt4, it could probably get included back in some repos as well. I'd

> be happy to put in some effort towards this, although I'm not too familiar

> with qt. Let me know if anything doesn't work or any other feedback on

> these patches & build instructions, thanks!

>

> -Brandon