Closed GoogleCodeExporter closed 9 years ago
Original comment by nickdowell
on 31 May 2011 at 8:30
Agreed, the DSSI version does need a lot of work.
Which DSSI host are you using? Is it possible to have amsynth load a preset
file without a GUI custom to control that?
Original comment by nickdowell
on 31 May 2011 at 8:32
I'm using Qtractor. Qtractor doesn't need a GUI to load presets/banks, for
example with the ZynAddSubFX DSSI plug-in you can select banks and then
instruments from the plug-in properties window.
Best,
Jeremy
Original comment by autosta...@gmail.com
on 31 May 2011 at 9:28
Hi Jeremy!
I've implemented basic preset selection from the dssi host (r431)
The amsynth dssi plug-in will automatically load your default bank file
(~/.amSynth.presets - run the stand-alone version to create it if it doesn't
exist)
So far I've tested it under Qtractor; there presets can be selected from the
track properties dialog (but not from the parameter editor window...)
Original comment by nickdowell
on 1 Jun 2011 at 7:43
Hello Nick,
That's great, thanks a lot! I did have to remove the ifdef DEBUG statement from
dssi.cpp, after that it compiled well and it works like a charm! So thanks
again! And yes, you have to set the right bank and program in the track
properties dialog, the parameter editor window settings are stored in
Qtractor's own config file.
I've added the tiny dssi.cpp patch. Also, for the plug-in to compile on 64bit
machines I've found I had to add some -fPIC options here and there. I mostly
build deb packages right away so I added CFLAGS and CXXFLAGS lines to my rules
file and also modified the Makefile-dssi file. I've also added that patch.
Best,
Jeremy
Original comment by autosta...@gmail.com
on 1 Jun 2011 at 9:23
Attachments:
And sorry about the confusing plug-in properties window thing, of course I
meant the track properties dialog :)
Jeremy
Original comment by autosta...@gmail.com
on 1 Jun 2011 at 9:30
Thanks for the patches, Jeremy!
I've committed the fixes now (r432) albeit slightly modified because I wanted
to disable all the log messages for non-developer builds. Hope I haven't messed
anything else up :)
Nick
Original comment by nickdowell
on 1 Jun 2011 at 9:47
Hello Nick,
Afaics nothing got messed up, packages build cleanly now without any need for
patching the source tree which is great! So thanks a lot again!
Best,
Jeremy
Original comment by autosta...@gmail.com
on 2 Jun 2011 at 7:57
Please try out the latest source from the amsynth git repository
- DSSI plugin is now built and installer by normal make & make install process
- DSSI plugin now has a GUI
Original comment by nickdowell
on 8 Jan 2012 at 11:31
Hello Nick,
Trying it out right now!
http://downloads.autostatic.com/temp/qtractor-amsynth-dssi.png
How awesome is this, thanks! One thing though, apparently the plug-in listens
on all MIDI channels despite the fact I've set it to listen to MIDI channel 1
only in Qtractor (see the screenshot above). This isn't a big issue as I use
separate MIDI buses for each softsynth plug-in anyway.
Thanks again!
Jeremy
Original comment by autosta...@gmail.com
on 11 Jan 2012 at 8:44
Sorry for the noise, the plug-in only listens on the assigned MIDI channel in
Qtractor. Another thing though, the DSSI GUI doesn't get updated when I change
settings.
Jeremy
Original comment by autosta...@gmail.com
on 18 Jan 2012 at 2:12
Hey I'm trying to compile amsynth from git to get the dssi plugin, but I'm
getting an error regarding -fPIC when running make: http://pastebin.com/ZXfuZeYN
This is a 64-bit system. I notice you mentioned about adding -fPIC flags in an
earlier post but A: you said this was fixed? and B: I don't know where to add
the flag as I do not see Makefile-dssi anywhere.
Thanks,
Tim.
Original comment by TimCape...@gmail.com
on 26 Jan 2012 at 11:31
So I poked around a bit and figured this out. I don't know if this is the right
thing to do, but it built and works great now. BTW I used checkinstall which
worked happily. I am now using amsynth as a dssi in renoise ::joy::
fix here:
http://pastebin.com/WDjV5wZB
and attached here:
Original comment by TimCape...@gmail.com
on 27 Jan 2012 at 1:21
Attachments:
Thanks for reporting that problem and the patch.
I've implemented a slightly different fix because CFLAGS is supposed to be a
user-overridable setting, and I'd rather not set the -fPIC flag for the
standalone targets.
#95dac42b065f
Original comment by nickdowell
on 28 Jan 2012 at 12:55
Should have resolved this ticket a while back, since the DSSI plug-in received
more love :)
Original comment by nickdowell
on 27 Jun 2013 at 7:41
Original issue reported on code.google.com by
autosta...@gmail.com
on 31 May 2011 at 8:05