|
|
Post by toodamnhip on Dec 5, 2016 21:49:33 GMT -8
There is quite a disconnect if the programming/features, between fader mode and aux fader mode. I am hoping this discontinuity of features can somehow be improved: ***No level meters anywhere in aux fader mode, either for the main out or for the send level. (I’d love to see a send level separate from the main level) ***No one or two finger swipe available to move through fader banks. *** No send mute or send pan ***Only 4 aux sends available ***And a big issue in all areas of Raven, and this is THE ISSUE that slows me down the most with Raven.... *******no automation status buttons or ability to change automation status anywhere in Raven.**************** I call this a “disconnect" because many features connected to the main fader screen just stop when going to Aux mode. Seems like programmers may have had to make a choice as to releasing Raven so as to start making money or delay release to build aux mode better. I understand if this is the case but hope, now that some catch up time has gone by, that raven catches up so there is a sense of feature continuity when moving into aux fader mode. And if you tell me that what I ask for is NOT supported by some Mackie/MIDI communication protocol frozen in time...... I’m a gonna cry.....lol Sorry to be a squeaky wheel, but I hit these issues every day and the remedy of these issues would make my mixing life much easier....  |
|
|
|
Post by jameyz on Dec 6, 2016 8:21:44 GMT -8
good ideas. I will bring it up to the dev team.
|
|
|
|
Post by waxman on Dec 6, 2016 13:46:02 GMT -8
TDH It's a lot about organization right? Those are the many issues I had to find work arounds for the first month I got my Raven MTi2 one year ago. I've had 3 major reorganization work flows on the Raven since I got it. It's because DP is the odd man out when it comes to Raven design. No templates and dynamic layout of DP is a bit tricky and I think has more to do with the Ravens design then the HUI/Mackie protocol.
I have not found a better the work around then to have a channel strip top left hand corner for automation and its is about as good as it gets. Let me know if you figure something else out. I think if DP would disconnect the automation from the R/S/M/I section it and make it the same size as the Raven strip that would be a big advance. Or if Raven was the same size as DP strip aka "skinny mixer" we would be good. But JZ mention 24 fader protocol in Mackie. Probably I would opt for a wider DP automation strip that would float. Or a wider DP mixer now that all those issues are exposed. I don't see much advantage in 32 channels at a time the 24 especially since touch is a factor. The current DP automation box is already big enough to be activated by touch but it's tight. Keeping the insert and send busses always available in DP mixer above the floating mixer was about as good as I could get until they do some major fixes by either company. I would pay $200 for a RAVEN friendly version of DP...
Overall there is plenty of room for automation, pan, and a assignable send all on the big raven mixer but that dump blank panel just stares back at us. A rework of the floating mixer would accomplish the same thing. I also think the batch commander is 25 % over sized. It's nice for the names but smaller letters would work and you just don't need that big a buttons to accomplish the touch protocol.
What is MOST needed is vertical real estate. The Jamey Z method of having different setups on each batch command strip is probably best using 1-6 buttons as opposed to 2 racks of BCs open. But I usually use 2 since I've gotten use to it. However I did set up a strip with just VI's which I store on #4 so I am breaking out. I got used to using 2 BC racks before I saw a post by JZ how he organized so I am resisting change.
I've found I can keep the DP mixer open with enough sends and returns for most sessions but it requires a mouse to adjust send levels. Still I favor that over the aux mixer. Going to the AUX mixer is like another world and takes a second to get reoriented. So basically for me the Raven is the joy of using Faders and BCs. Which don't get me wrong I LOVE the way I work on the Raven. But it's about 50% of how cool it could be. Hopefully there will be redesign someday but don't hold your breath. The Raven team seem to have a lot to get to with windows and other DAW's. In the meantime I hope you are enjoying the RAVEN... The alternative is unthinkable IMO. Maybe we should get the DP Raven users to LOBBY MOTU for some redesign? Just decoupling the Automation and resizing the mixer would be amazing.
|
|
|
|
Post by toodamnhip on Dec 9, 2016 5:29:19 GMT -8
I can 100% report that on my system, when mixing in DP 8.07, I cannot go through any session without Aux mixing using the aux fader in Raven, eventually disconnecting in multiple strange ways. As stated before, : **The aux Raven fader will at some point get confused and start working the main faders in DP **The main fader in Raven will at that point be controlling the PAN of DP. Crazy man. Sometimes I can jog things back not place by switching between 1-2-3-4 in the aux screen , going back to the Main Ravne fader screen, and back again to the aux screen. Sometimes nothing works and, being in a hurry, I just keep mixing using the Raven aux sends to control DPs main faders. This is made all the more difficult because there are NO levels showing to know what your levels are when in the Raven aux fader window. And since I cant swipe to a new fader bank, I have to switch to the main fader window , then swipe to go where I want, and then go back to aux faders to continue mixing. When this all starts to just suck too much, I have to re start the computer and re boot everything. Only to have it happen again at any random moment I go to aux faders after the re boot. Are we having fun yet? |
|
|
|
Post by jameyz on Dec 9, 2016 8:06:45 GMT -8
Be sure to toggle back to Channel mode after using the sends, I think this happens when exiting the Raven mixer while sends are open, then toggling back to channel..
|
|
