How can we save our ccr assignments in 3x
in V.2 there was a save device option on the preset window ?
topaz.
save device settings/ccr's in 3x
Try it
I need to too - looks like topaz tried this and it didn't work - I did do this on something and the CC's stuck, but might have fallen for the same thing marcuspocus did, and the CCs were actually saved in the project? So I'll need to double check. But if it doesn't work that way it really should!! 
<font size=-1>[ This Message was edited by: subhuman on 2002-01-18 10:33 ]</font>


<font size=-1>[ This Message was edited by: subhuman on 2002-01-18 10:33 ]</font>
On 2002-01-18 10:24, subhuman wrote:
Try itI need to too - looks like topaz tried this and it didn't work - I did do this on something and the CC's stuck, but might have fallen for the same thing marcuspocus did, and the CCs were actually saved in the project? So I'll need to double check. But if it doesn't work that way it really should!!
<font size=-1>[ This Message was edited by: subhuman on 2002-01-18 10:33 ]</font>
Sure, I know you have to try that too, but if you say it works I suppose you're experienced w that.
I know one thing that's always worked in all Pulsar OS: save the project, and the CC# are saved along. And devices up to 2.04, not the OS, include a 'device save' option in the preset list.
I have +/- 15 2.04 devices saved like that, every channel's filled with my favorites. They all include midi remote CC#, most of them have presets saved into them which are bank and program change assigned.
For me in 3.01, following actually works:
-2.04 devices remote can still be saved, including the presets.
-3.x devices' remote can be saved in the project.
This means that I need so many template projects. For all different devices, and what if I wanted to add a 3.01 device on the fly? Down goes creativity and intuitive use on this marveleous DSP platform.
I'm testing XTC now. But I think 3.01 rules will count and that you'll need ie. CubaseXTC.all for every bloody midi implementation.
Ok some XTC midi remote test results:
->Fx can be automated as any VST plugin, press 'Write' on Cubase's ChannelMixer.
->I can't get midi to synths. The Synth Midi In LED doesn't light up.
Hope's in a next version, Pulsar OS 3.1, but in the mean time this oh so flexible tool keeps changing too fast for my one-man studio. And these midi assignments are a time consuming work!
atomic.
ps - Any feedback on this topic would be greatly appreciated. You can check Prestes and Tools for Presets I uploaded to control Pulsar with a Peavey Pc1600x.
<font size=-1>[ This Message was edited by: atomic on 2002-02-01 12:34 ]</font>
so have creamware removed this function, surely not, we cant be expected to say
"hey man just wait an hour while I sort out all the midi learns" LOL
confirmation is needed, also on the poss bug subject can someone try the delay plugins and see if time divisions can be entered
IE, 1/6 1/4 etc.. doesnt work here.
topaz.
"hey man just wait an hour while I sort out all the midi learns" LOL
confirmation is needed, also on the poss bug subject can someone try the delay plugins and see if time divisions can be entered
IE, 1/6 1/4 etc.. doesnt work here.
topaz.
On 2002-01-18 10:24, subhuman wrote:
Try itI need to too - looks like topaz tried this and it didn't work - I did do this on something and the CC's stuck, but might have fallen for the same thing marcuspocus did, and the CCs were actually saved in the project? So I'll need to double check. But if it doesn't work that way it really should!!
<font size=-1>[ This Message was edited by: subhuman on 2002-01-18 10:33 ]</font>