mod wheel sending odd continuos controller
mod wheel sending odd continuos controller
I am seeing someting wierd while recording MIDI from the voyager to Digital Performer 4.52.
When I use the mod wheel DP records the note, modulation controler and CC 33.
This is very odd to me. I can't figure out why that CC is being sent out or how it's assigned to the mod wheel.
How can I figure out what paramete in the voyager is responsible for sending these messages?
Does anyone have a more complete source on how CC's are assigned in the voyager? I can't find anything in any of the manuals or addendums.
thanks!
- chris walcott
When I use the mod wheel DP records the note, modulation controler and CC 33.
This is very odd to me. I can't figure out why that CC is being sent out or how it's assigned to the mod wheel.
How can I figure out what paramete in the voyager is responsible for sending these messages?
Does anyone have a more complete source on how CC's are assigned in the voyager? I can't find anything in any of the manuals or addendums.
thanks!
- chris walcott
Voyager's Mod Wheel (and most other Voyager controls) sends two bytes of Continuous Controller (CC) data, not one. This is done to provide finer resolution and control then can be specified in a single byte. The Mod Wheel assignment is CC 1 (MSB), and CC 33 (LSB). It is not programmable, and cannot be changed.
The Voyager's CC assignments were listed in the v2.0 (and 2.1) Update User Instructions. These assignments are unchanged in v2.5.
The Voyager's CC assignments were listed in the v2.0 (and 2.1) Update User Instructions. These assignments are unchanged in v2.5.
Thanks
I will attempt to deal!
Next question when I move the mod wheel all the way down to off, the value on the offset page alternates between 0 & 3. If I hold it all the way down it stays at 0. Is this normal?
Do I need to trim it out?
Can I ?
dave
Next question when I move the mod wheel all the way down to off, the value on the offset page alternates between 0 & 3. If I hold it all the way down it stays at 0. Is this normal?
Do I need to trim it out?
Can I ?
dave
-
- Posts: 684
- Joined: Sun Aug 03, 2003 12:16 am
- Location: Oxford, UK
Follow up.
I went ahead and adjusted the Mod trim to 0 but I no longer could hit 255 at full throw. Is there a scaling control? If not I think the pot is bad. Since it can be forced to 0.
dave
dave
- RL
- Posts: 770
- Joined: Wed May 19, 2004 4:17 am
- Location: http://www.moogmusic.de/
- Contact:
Hello Dave,
RL = Rudi Linhard
He does all the software inside the Voyager.
He answered your mail and asked a question.
So there is a Moog tech listening to you.
But you didn't answered his question.
RL = Rudi Linhard
He does all the software inside the Voyager.
He answered your mail and asked a question.
So there is a Moog tech listening to you.
But you didn't answered his question.
keep on turning these Moog knobs
Till "Qwave" Kopper
[url=http://launch.groups.yahoo.com/group/Squarewave/]Squarewave Group[/url] member "waldorfian_qwave"
Till "Qwave" Kopper
[url=http://launch.groups.yahoo.com/group/Squarewave/]Squarewave Group[/url] member "waldorfian_qwave"
Ok I am a dork! Sorry I missed this most obvious post.
The highest value it got to was 239 or so. After I trimmed to zero there appeared to be a fair amount of range at that zero point so I could move it around at the high end but never get zero to 255 without the bounce at the low end.
Thanks again.
dave
The highest value it got to was 239 or so. After I trimmed to zero there appeared to be a fair amount of range at that zero point so I could move it around at the high end but never get zero to 255 without the bounce at the low end.
Thanks again.
dave