oh the joys of q-link>cchange

hi,
im well into recording my changes using the sliders at the moment, using certain changes to mod filters on my NordG2 Engine.....
but i hit a critical point last nite where i decided it would be better to hane cc#31 in the sequence instead of cc#29, just 'cos i wanted to re-assing the knob functions on the synth. but then i got swamped by having to dial the new value into every single event in step edit, it vuggin killed me (and my down cursor).....

anyone using this behaviour, and have any better ways of changing control change numbers?

so ive asked JJ - how about a mode+step edit addition, the usual F3=edit - with a new F1=re-assign function where any event number or type can be re-assigned to another (with compatible type to type assignments only obviously)

arebee wrote:hi,
im well into recording my changes using the sliders at the moment, using certain changes to mod filters on my NordG2 Engine.....
but i hit a critical point last nite where i decided it would be better to hane cc#31 in the sequence instead of cc#29, just 'cos i wanted to re-assing the knob functions on the synth. but then i got swamped by having to dial the new value into every single event in step edit, it vuggin killed me (and my down cursor).....

anyone using this behaviour, and have any better ways of changing control change numbers?

so ive asked JJ - how about a mode+step edit addition, the usual F3=edit - with a new F1=re-assign function where any event number or type can be re-assigned to another (with compatible type to type assignments only obviously)

no offense but I feel that's a waste of code

i dont think so, i mean , if a lot of events could be re-assigned - not just cc's, it would help loads...... but i can imagine from your point of view - and im sure you'll correct me if im mistaken,that u anit using these concentrations of high density events in yer mpc work.

from my perspective - JJ's put these midi/cc/slider attributes into the code for a good reason, and in some respects JJ hasn't backed this up with the relevant tools to deal with the consequences. (eg qlink/cc event thin/quantise, replace events) tools which i feel are indeed necessary to cope with the inclusion of such powerfull additions like these.

i agree with both posters

added transposition would be nice, convert either qlink or cc data to a different value, but at the same time i feel that it would take just as long as manually recording it in

remember, you CAN copy and paste qlink//cc data of its own type within a sequence, so say you're drawing a standalone sine LFO with a filter qreal - you could just draw one waveform of the sine and then select it/copy it to however long it needs to be.

i find working with the qlink/cc recording graph very quick and easy even without the bonus of the code that arebee was talking about.

to me, this seems something that belongs in sequence edit!

no i want the same cc values (and its very complex - nothing i could recreate manually, as it was a one off live take! but cc# switched to a diff cc#, ie: 29 to 31, just house keeping stuff, but cant do it anywhere else except Digital performer's ''reassign continuous data''

pce
rB/

[quote="Antonym"
i find working with the qlink/cc recording graph very quick and easy even without the bonus of the code that arebee was talking about.[/quote]

what is the qlink/cc recording graph? is it some utility that generates cc events without actually moving the sliders? did I miss something here?

nah i'm just talking about qreal edit

ahhhh, thx...

Did you try expoting as midi, changing the cc in a midi editor and transfer it back to the mpc? Not sure that works as i dont use the midi export but might be worth a shot.

yeah i tried, i saved as a .mid file, imported to DP, reassigned the cc# in there then imported it back to the mpc, but my problem was that as a .mid file, ALL the mpc specific stuff gets lost, ie: program allocations to tracks and any note on event stuff gets stripped out if u dont export as 'seq' kind.

so it shafted the rest of the patterns, so i gave up. mbe tmoro i'll export and do it all again but this time just import to a separate seq, and copy the data from one seq to the other..
see what happens.

couldnt you change the assignment on the nord? ...i.e. have the nord respond on 'x' instead of 'y' channel to the parameters you have on the mpc, therefore controlling the same mod on a different channel?

I don't own a nord, so I don't know if it has fixed parameters

Did you try expoting as midi, changing the cc in a midi editor and transfer it back to the mpc? Not sure that works as i dont use the midi export but might be worth a shot.

my thoughts exactly. I do that kinda thing with cubase, works perfectly.
or maybe try running the midi through a midi filter (like in cubase), which can change assignments , and re record the corrected info

The Grublet wrote:couldnt you change the assignment on the nord? ...i.e. have the nord respond on 'x' instead of 'y' channel to the parameters you have on the mpc, therefore controlling the same mod on a different channel?

I don't own a nord, so I don't know if it has fixed parameters

yeah that was the easy part, but because im doing lots of patches i wanted them to share common traits, like all having filter on cc# XX or etc,
and in this case i wanted to switch back the cc#number in the moc seq, and then found it almost impossible, its my own fault, not dissin JJ just hoped that anything like this 'swap' procedure could be implemented....and therefore be well powerfull for swapping data around in there.