Automating Mixers

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
User avatar
nightscope
Posts: 686
Joined: Tue Aug 21, 2007 4:24 pm
Location: UK

Automating Mixers

Post by nightscope »

Scope-ites,

I'm just trying to get the Scope mixers hooked up to my Bitstream 3X controller. The 4896 is working OK with shifting the faders when I tweak the 3X. And when I tweak the 4896 onscreen I get cc's going out of the mixer midi out. But I can't seem to get the mixer midi out sending the 4896 fader position when I tweak the hardware fader.

Do the Scope mixers send fader feedback for hardware controllers back to the hardware? So I tweak the hardware and the Scope mixer sends the new fader position back to the hardware and updates it?

I've read this here and I read they do. http://www.planetz.com/forums/viewtopic ... r+feedback

Puzzling.

ns
User avatar
valis
Posts: 7680
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Post by valis »

If the scope mixer sent midi back to the bitstream at the same time the bitstream was sending data to the mixer, that would be considered a midi loop, no?
User avatar
nightscope
Posts: 686
Joined: Tue Aug 21, 2007 4:24 pm
Location: UK

Post by nightscope »

valis wrote:If the scope mixer sent midi back to the bitstream at the same time the bitstream was sending data to the mixer, that would be considered a midi loop, no?
I don't know. This Bitstream controller has a feature called "hook". It's a substitute fo motorized faders. I figured the hardware has to monitor the 4896 somehow so's it knows where the faders are. Only way to do that is to get messages back from the mixer on mixer's midi out to hardware midi in.

How to get it working is another matter.

I'll rephrase my question. Does anyone know what is passed from 4896 mixer midi out under what conditions. I know it's cc's.

ns
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

sure, it's a stream of cc data, but only if that knob is assigned to a cc number. you can use a midi monitor(it's in the menu named "midi"), to verify that you're sending data.

that function does work, however(knob automation). i've used it before.
User avatar
nightscope
Posts: 686
Joined: Tue Aug 21, 2007 4:24 pm
Location: UK

Post by nightscope »

garyb wrote:sure, it's a stream of cc data, but only if that knob is assigned to a cc number. you can use a midi monitor(it's in the menu named "midi"), to verify that you're sending data.

that function does work, however(knob automation). i've used it before.
Thanks, gary. I've already got the 4896 assigned controlling faders on cc#40. Move hardware fader, scope fader moves. So the Bitstream works contolling scope faders fine. I got a midi monitor on 4896 midi out but nothing is back passed out when I use the Bitstream. when I tweak the 4896 onscreen it passes out data OK.

I know the knob automation works fine. It's just the feedback to the Bitstream "hook" feature. Do scope mixers support this?

ns
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

when midi goes in the scope fader moves, so the scope fader is immedialtely where the bitstream fader is. when the scope fader moves, it sends out data so that if the scope fader moves, the motorized fader will move.

as i understand the bitstream's hook mode, when you change patches in the bitstream, it won't update fader position on the controlled device until you move the bitstream fader.

from the bitstream's manual:
Hook mode allows the user to avoid any undesirable jump in values: After any group change, if the physical position of the analog control doesn’t correspond to the value of the same control in the newly selected group, the MIDI data is not sent while the physical position and the value are different. Thus, no jump in value is obtained. The LCD screen of the Bitstream 3X indicates the direction to move the control to finally generate the MIDI.

so, it seems everything is working like it should.....
User avatar
nightscope
Posts: 686
Joined: Tue Aug 21, 2007 4:24 pm
Location: UK

Post by nightscope »

garyb wrote:when midi goes in the scope fader moves, so the scope fader is immedialtely where the bitstream fader is. when the scope fader moves, it sends out data so that if the scope fader moves, the motorized fader will move.
Yes, thanks, you got it exactly right and I understand what supposed to be happening. Only thing is when I move a Bitstream fader the Scope fader moves but no data is sent out of the Scope mixer midi out. I have the mixer midi out connected back to the Bitstream and to a midi monitor.

Losing the will to live!!

ns

PS (5 minutes later!!) OK I think I got it. Thanks for the tips!!
Post Reply