Extra control data incomming when recording cutoff and mod
-
- Posts: 9
- Joined: Fri Feb 22, 2008 7:14 am
Extra control data incomming when recording cutoff and mod
Hi All,
I noticed that my TE phatty outputs addition ctrl data incomming when rec. mod and cutoff freq. data
as follows
mod wheel
mod 1 => cc 33
and...
cutoff
cc 19 => cc 51
I could not find these cc (33 and 51) mentioned in the midi spec of the manual.
i checked the contents of these addtional channels and it does not obviously correspond to the associated channel in fact it look almost noisey and random.
This would not present a problem otherwise, but I use a hardware sequencer that records on cc per track autosensing the data and the result is the cutoff slope cc19 is messed up by the additional cc51 data.
Is this for higher precision 14 bit? whats are the other channels and is it possible to switch off.
Any ideas i'd be greatful.
Cheers,
Wilson
I noticed that my TE phatty outputs addition ctrl data incomming when rec. mod and cutoff freq. data
as follows
mod wheel
mod 1 => cc 33
and...
cutoff
cc 19 => cc 51
I could not find these cc (33 and 51) mentioned in the midi spec of the manual.
i checked the contents of these addtional channels and it does not obviously correspond to the associated channel in fact it look almost noisey and random.
This would not present a problem otherwise, but I use a hardware sequencer that records on cc per track autosensing the data and the result is the cutoff slope cc19 is messed up by the additional cc51 data.
Is this for higher precision 14 bit? whats are the other channels and is it possible to switch off.
Any ideas i'd be greatful.
Cheers,
Wilson
Yes that is 14-bit CC data, which is implemented for both filter cutoff and pitch bend, to get smoother control. Notice that each pair of numbers is 32 apart; this is intentional. It's the standard MIDI spec for paired 14-bit controllers.
We're planning a master menu option to enable/disable 14-bit MIDI, for compatibility with gear that doesn't like the extra info. For now, you'd have to filter out the MIDI data yourself. There are various hardware and software MIDI filters that could do this; perhaps you can set up a MIDI filter right within your sequencer.
We're planning a master menu option to enable/disable 14-bit MIDI, for compatibility with gear that doesn't like the extra info. For now, you'd have to filter out the MIDI data yourself. There are various hardware and software MIDI filters that could do this; perhaps you can set up a MIDI filter right within your sequencer.
any updates to this? I have SONAR 7 and a M-Audio Midisport 8x8 and when trying to record a performance with heavy use of the mod wheel, I crash almost every time. Any idea when the override for 14-bit data will be implemented and if not, can you point to a good inline filter?
Thanks!
chvad
Thanks!
chvad
http://www.chvad.com
http://www.totsland.net
http://www.thequalia.com
http://www.wtiirecords.com
http://www.darksonus.com
http://www.totsland.net
http://www.thequalia.com
http://www.wtiirecords.com
http://www.darksonus.com
oh hey if you are using a PC (I am assuming sonar = PC) then there is a free software inline filter... get MidiOx + MidiYoke from http://www.midiOx.com , read the helpfiles on installing MidiYoke, it's like a bunch of virtual MIDI ports inside your computer. The idea is, you have MidiOx running, it takes incoming MIDI and you can precisely filter out any specific CCs you want (in this case, CC 33 and 51), then pass the filtered midi to a channel of MidiYoke... then tell your sequencer to monitor this same MidiYoke channel for its MIDI input; the sequencer will see only filtered MIDI.
Try this; hope it works well enough until the firmware update.
Cheers,
A
Try this; hope it works well enough until the firmware update.
Cheers,
A