Re: [Bluemusic-users] change presets
Brought to you by:
kunstmusik
From: Steven Yi <ste...@gm...> - 2016-09-20 13:09:00
|
If I understand correctly, I'm not sure a PresetObject would be the simplest path. In my mind, the underlying problem might be better addressed if: 1. the presets that are currently within Blue are exposed within Csound code 2. a preset instrument is made available that could be triggered by event opcodes or score text However, now I am wondering, if you are sequencing the changes of instrument settings, would it maybe be more logically consistent to use the new Sound SoundObject features introduced in 2.6.1 to put XLooper directly on the timeline? You could then make different instances of each Xlooper on the timeline. Each would have its own settings and you wouldn't have to worry about changing parameters. In my mind, this is a different way of working than typical MIDI-based systems and might be a good use case for Sound. (While I haven't used a Kyma system, I imagine this is how one might go about this problem using something like that.) The one issue here though is if you are using parameter automation, as Sound does not expose those for automation currently. If the idea works, but that limitation is a problem, then I could work on developing the user interface, either within the timeline or within Sound's editor, to allow for drawing curves and having them associated with just that object. I think that's a pretty powerful option to have and would gladly look at developing it for 2.7.0. On Thu, Sep 15, 2016 at 8:17 AM, Menno Knevel <mag...@gm...> wrote: > Feature is requested, and i was thinking a bit on the subject some more. I > hope it makes sense. > > At the time i was working a lot with Cubase and midi (AtariST - still got > it!). It takes a little while to transmit all the initialization data to the > hardware/software synth - this i did using sysex midi data or simply a > Program Change. > A Program Change was a quicker way because one only changes instruments with > their preset parameters already set. > > When i tried to send over this long list of sysex data to change ALL of the > parameters of the synth (so that the sound was more or less changing live), > then, while playing, the synth would choke and hang and i had to manually > reset the synth :) > > To make sure that the synth and all its settings was available just BEFORE > playing, i put on the timeline a Part containing only the Program Change or > SysEx data. It takes a few milliseconds to load, just as expect a ftable > containing init data for the BSB will take. > > This leads me to the idea that perhaps a seprerate Object (PresetObject) > could be created and be used to insert right before the actual notes start > playing. > Another advantage would be that the user can move the PresetObject around at > a later time, copy it etc. > > The ftable (= PresetObject) gets its time from the timeline. It would all be > csd compatible :) > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/change-presets-tp5751605p5751665.html > Sent from the Csound - Blue - User mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users |