|
|
Post by jameyz on Apr 9, 2016 10:54:59 GMT -8
Hey Raven Users, When I get a huge session in Cubase I like to spend a couple minutes getting my visibility configurations together so I can easily focus on the tracks I want to mix, instead of banking around trying to find the tracks. Here are the BCs to import if you don't want to program them yourself, or if you don't have a numpad on your laptop.. Cubase Fader Focus.zip (6.79 KB) you can also drag the ravpan into your user ravpan folder. /Users/name/Library/Application Support/Slate Media Technology/Raven MTi/Panel/Cubase/8. This way you can just import the whole raven panel instead of a single BC at a time. |
|
dk
New Member
Posts: 43 
|
Post by dk on Jun 2, 2016 10:55:19 GMT -8
I wonder if you'd be able to help me with this...
I'm hoping to switch from PT to Cubase but the one thing holding me back is this channel visibility setup. There are a few issues with it for me.
1. Currently with Cubase if you have your visibility groups all setup, once you add a new track to the session it starts appearing in ALL visibility groups. You would need to go through and update all the groups again without this one channel. Total no deal!
2. It is possible to link the visibility configs in the Mix Console and the Project window, but it seems to be that the Mix Console is the master and the Project is the slave in this case. Are there any work arounds to flip this around and make the project the master?
The Project Logical Editor is the greatest thing out there, I can make very detailed visibility configurations that show/hide folders with certain names or track types etc. I can get the Project Window acting 100% as I'd like it, but as soon as I try and use the Mix Console all my work is gone! The Project Logical Editor can't even be opened while the Mix Console is active.
Any tips would be greatly appreciated!
|
|
|
|
Post by jameyz on Jun 2, 2016 18:41:13 GMT -8
If you add a new track to the configuration it is easy to just hit the key command or Batch Command for "update Visibility Configuration" so this shouldn't be a problem.
The mix console and project window have different vis configs so this is a pain with CU, but probably easy enough to setup.
You are right about the Project Logic editor, but maybe if you stick more with the External and floating mixers this will be easier to setup.
|
|
|
|
Post by waxman on Jun 2, 2016 22:31:43 GMT -8
If you add a new track to the configuration it is easy to just hit the key command or Batch Command for "update Visibility Configuration" so this shouldn't be a problem. The mix console and project window have different vis configs so this is a pain with CU, but probably easy enough to setup. You are right about the Project Logic editor, but maybe if you stick more with the External and floating mixers this will be easier to setup. JZ... Could this work in DP? |
|
dk
New Member
Posts: 43
|
Post by dk on Jun 3, 2016 2:29:20 GMT -8
I posted this on the steinberg forum where I'm having the same discussion: ------------------------------------------------------------------------------------- I just came up with a pretty decent solution. At least it seems that way now but I'll be interested to see how it plays out. It's a kind of VCA Spill. Maybe someone on here has already figured this out too. I like to mix with VCAs, so all tracks are part of one VCA group. If you make one vis config that shows just the VCAs, you have all your subgroups essentially. Then if you select one particular VCA, you can use the command 'show channels connected to the first selected channel' (I think that's the command). This will 'spill' that particular VCA onto the faders. Then you can just recall the VCA vis config before spilling another group. With key commands and/or Slate Raven (what I am trying to setup) this will be pretty good I think! If I am adding new tracks to a session at mix time, I am more than likely duplicating tracks which should place them into the existing VCA group (I hope), so there theoretically shouldn't be any problems with tracks showing up in all configs. The only one I may need to update when I add new tracks is the VCA vis config. Keen to hear people's thoughts on this  |
|
|
|
Post by jameyz on Jun 3, 2016 7:57:55 GMT -8
DK Sounds like a great idea, I will have to give this a try also.
Edit: I just gave it a try and it works great. Basically a VCA spill for Cubase.
The key command for "Show Channels Connected" was not setup in the Raven Keys, so I added it to them and made a BC for it "SHIFT CMND OPT V". Will add this in the update coming next week.
Also, I found the option to sync visibility between Mix and Project. So that is very helpful.
|
|
|
|
Post by jameyz on Jun 3, 2016 7:59:04 GMT -8
Waxman, I don't think DP has any way to setup fader groups or show/hide status.
But it you know of a way then setting up groups with track show/hide info would make mixing large sessions much easier.
|
|
|
|
Post by waxman on Jun 3, 2016 8:04:16 GMT -8
Waxman, I don't think DP has any way to setup fader groups or show/hide status. But it you know of a way then setting up groups with track show/hide info would make mixing large sessions much easier. Yes MOTU just added it in the tracks window to hide tracks on the newest version. They always had folders I'll check and see if the new hide tracks translates to the mixer section. |
|
dk
New Member
Posts: 43
|
Post by dk on Jun 6, 2016 6:03:42 GMT -8
Jameyz, looking forward to seeing this in the next update. Really happy with how this works!!
|
|
