|
|
Post by stringsibanez on Nov 30, 2016 14:14:05 GMT -8
Hi,
I bought myself an MTi2 a couple of days ago, and after watching the intro video and trying to search my way through the .pdf manual (as well as using the search function on this forum) I decided it might be easier to post my any questions I encounter in a consolidated thread. So here are my first questions:
1) I've created some Window Configurations (ProTools 12) for myself and put them in custom BC buttons so that I can easily switch between different Mix / Edit / Midi views etc. I was wondering if it is possible to use BC code to simultaneously switch to a different saved Raven layout? (So that I push the batch command for my Edit configuration and it automatically switches my to layout 2 on my Raven display thing..?)
2) Is it possible to create a blank BC panel from nothing somehow?
3) Is there a way, using the Raven, to get the equivalent functionality of option clicking a pan knob or fader in PT such that it snaps back to 'default' / 0 / centre / etc?
Also, over the years I have found that keeping my ProTools solo mode in X-OR is most convenient. I simply hold 'shift' as I click solo buttons to solo multiple things and un-soloing everything is as simple as clicking any solo button twice. I have found, however, that this mode does not appear to work with the Raven as the 'shift' button does not seem to have any impact on Raven touches.
4) Is there a way to use BC code to show/hide the Raven Mixer, switch between Mix 22/24, set banked position, + or - Racks... or additionally switch between internal and external mixers within a Batch Command?
5) It doesn't seem as though the shuffle/slip/grid/etc buttons are capable of getting ProTools edit windows into the Slip-Grid combination mode?
6) Is it possible to un-link banking so that when I bank by 24 on the mixer the edit-window doesn't change (visible on another display)?
7) I frequently notice that automation moves (regardless of the specific control surface) are written late by approximately the same amount as the "System Delay" as reported by Pro Tools. Is it possible to make a batch command that would nudge a selection (manually selected) by an specific amount so that I don't have to manually move automation moves into place?
Thanks in advance for any help, and I'll post any additional questions (should they arise) in this thread as well.
-Steve
|
|
|
|
Post by jameyz on Dec 1, 2016 10:56:49 GMT -8
1) I've created some Window Configurations (ProTools 12) for myself and put them in custom BC buttons so that I can easily switch between different Mix / Edit / Midi views etc. I was wondering if it is possible to use BC code to simultaneously switch to a different saved Raven layout? (So that I push the batch command for my Edit configuration and it automatically switches my to layout 2 on my Raven display thing..?) That is not possible yet, some users had a similar idea for Cubase so I think it could be cool. 2) Is it possible to create a blank BC panel from nothing somehow? There are the max numbers of panel on each layout. You will have to push and hold a panel and that hit clear all" to get a blank one. 3) Is there a way, using the Raven, to get the equivalent functionality of option clicking a pan knob or fader in PT such that it snaps back to 'default' / 0 / centre / etc? Also, over the years I have found that keeping my ProTools solo mode in X-OR is most convenient. I simply hold 'shift' as I click solo buttons to solo multiple things and un-soloing everything is as simple as clicking any solo button twice. I have found, however, that this mode does not appear to work with the Raven as the 'shift' button does not seem to have any impact on Raven touches. The Raven modifiers will be fixed for MTi2 users in the next update coming in a couple weeks. 4) Is there a way to use BC code to show/hide the Raven Mixer, switch between Mix 22/24, set banked position, + or - Racks... or additionally switch between internal and external mixers within a Batch Command? Unfortunately Pro tools doesn't have a menu item or key command for this Tracks list window. Also, BCs can't really trigger GUI items. Those only respond to touch. 5) It doesn't seem as though the shuffle/slip/grid/etc buttons are capable of getting ProTools edit windows into the Slip-Grid combination mode? That would need to be programmed into a BC. 6) Is it possible to un-link banking so that when I bank by 24 on the mixer the edit-window doesn't change (visible on another display)? Yes this is a setting in the mixing tab or PT Prefs. Edit window follows banking. 7) I frequently notice that automation moves (regardless of the specific control surface) are written late by approximately the same amount as the "System Delay" as reported by Pro Tools. Is it possible to make a batch command that would nudge a selection (manually selected) by an specific amount so that I don't have to manually move automation moves into place? I think that one Pro Tools needs to fix this asap. I have been begging for years. There would be no way for Raven to know how many samples your delay comp was. But there is a way to copy paste automation with some BCS. |
|
|
|
Post by stringsibanez on Dec 1, 2016 15:44:38 GMT -8
Thanks for answering my plethora of questions  . Adapting to the difference in workflow (or creating a new one, depending on how one looks at it) stands to take a bit of time / have a bit of a learning curve, but I can already see where the payoff will be and everything seems simple enough to do.. There's just the odd thing that isn't immediately obvious or stated explicitly in the instructional materials. 1) I've created some Window Configurations (ProTools 12) for myself and put them in custom BC buttons so that I can easily switch between different Mix / Edit / Midi views etc. I was wondering if it is possible to use BC code to simultaneously switch to a different saved Raven layout? (So that I push the batch command for my Edit configuration and it automatically switches me to layout 2 on my Raven display thing..?) That is not possible yet, some users had a similar idea for Cubase so I think it could be cool. I could certainly see this being a useful feature addition (on top of some other good suggestions I've read around the forum). 2) Is it possible to create a blank BC panel from nothing somehow? There are the max numbers of panel on each layout. You will have to push and hold a panel and that hit clear all" to get a blank one. Fair enough... and it really isn't that much of an inconvenience to have the limits in place. I just wasn't initially sure if clearing an existing panel would take away my ability to reference it later (as a kind of tutorial), but as I've been putting together a workflow for myself I haven't found a whole lot of the pre-existing panels to be what I'm looking for anyway. 3) Is there a way, using the Raven, to get the equivalent functionality of option clicking a pan knob or fader in PT such that it snaps back to 'default' / 0 / centre / etc? Also, over the years I have found that keeping my ProTools solo mode in X-OR is most convenient. I simply hold 'shift' as I click solo buttons to solo multiple things and un-soloing everything is as simple as clicking any solo button twice. I have found, however, that this mode does not appear to work with the Raven as the 'shift' button does not seem to have any impact on Raven touches. The Raven modifiers will be fixed for MTi2 users in the next update coming in a couple weeks. This I am definitely glad to hear. There are just a handful of things I've run across where the mouse and keyboard can still do the job just a little easier and this should close a good amount of that gap. 4) Is there a way to use BC code to show/hide the Raven Mixer, switch between Mix 22/24, set banked position, + or - Racks... or additionally switch between internal and external mixers within a Batch Command? Unfortunately Pro tools doesn't have a menu item or key command for this Tracks list window. Also, BCs can't really trigger GUI items. Those only respond to touch. I suppose I can manage without this functionality at this point since it's generally just a few extra clicks. I would consider, however, maybe making the suggestion to the Raven/ BC team that it could be useful if the functions provided by the existing Raven buttons could also be called by Batch Command scripts so that functions that users tend to repeat together can be stacked in a single button push. (One example would be when I use the buttons I created for switching between mix/edit/midi layouts (PT Window Configurations) which distribute different things across my 3 displays. It would save some extra clicks if I could also just call the Raven functions to toggle Mixer 22/24 (which fixes any alignment mismatching) or switch to Layout 1/2/3/4 all within that same BC script. 5) It doesn't seem as though the shuffle/slip/grid/etc buttons are capable of getting ProTools edit windows into the Slip-Grid combination mode? That would need to be programmed into a BC. Yeah, I wondered about that. Easy enough I guess to simply BC an F2+F4 button or whatever I would need. 6) Is it possible to un-link banking so that when I bank by 24 on the mixer the edit-window doesn't change (visible on another display)? Yes this is a setting in the mixing tab or PT Prefs. Edit window follows banking. Awesome! That got it instantly working to my liking. Thanks! Somehow I managed to miss this setting when I'd glanced over the preferences before posting. Chalk that up to a combination of everything new I'm learning at once. Also, it seems to me that I never really encountered (or maybe just didn't take note of) this behaviour with previous control surfaces, but that could have been due to smaller banking vales of 8 or 1. I could see it being useful if the "Customize Toolbar" thing provided other optional button sets so a user could choose between Bank Left 24/Bank Right 24, Bank Left 8/Bank Right 8, Bank Left 1/ Bank Right 1 or something like that. 7) I frequently notice that automation moves (regardless of the specific control surface) are written late by approximately the same amount as the "System Delay" as reported by Pro Tools. Is it possible to make a batch command that would nudge a selection (manually selected) by an specific amount so that I don't have to manually move automation moves into place? I think that one Pro Tools needs to fix this asap. I have been begging for years. There would be no way for Raven to know how many samples your delay comp was. But there is a way to copy paste automation with some BCS. Absolutely, this is definitely something Avid should have addressed years ago. Honestly though, I would settle for simply highlighting the automation I just recorded (manually) and then making up a BC button I could push and it would nudge my selection back/left by the system delay (which I could edit into the script in each instance).. It would save a lot of counting out pushes of my 'nudge' command keys. I could also see it as useful if the sensitivity of Fine Faders Mode was adjustable somewhere so that it could be even more subtle in some instances. |
|
|
|
Post by stringsibanez on Dec 1, 2016 20:27:25 GMT -8
Update: Apparently getting into Slip-Grid mode using a BC is either impossible or less than obvious... the 'key command' entry field in a Batch Command won't allow both F2 and F4 to be entered as a combination.. only one or the other.
|
|
|
|
Post by jameyz on Dec 1, 2016 20:31:02 GMT -8
Update: Apparently getting into Slip-Grid mode using a BC is either impossible or less than obvious... the 'key command' entry field in a Batch Command won't allow both F2 and F4 to be entered as a combination.. only one or the other. Can use a 2 different key commands inputs so they launch right after each other. Also seem you have to use SHIFT F to get it to latch.  |
|
|
|
Post by stringsibanez on Dec 1, 2016 20:53:05 GMT -8
Update: Apparently getting into Slip-Grid mode using a BC is either impossible or less than obvious... the 'key command' entry field in a Batch Command won't allow both F2 and F4 to be entered as a combination.. only one or the other. Can use a 2 different key commands inputs so they launch right after each other. Also seem you have to use SHIFT F to get it to latch. Awesome! That works like a charm.. I didn't even know there were alternate ways to switch between those modes as I've gotten so used to using the 'F#' keys. |
|
|
|
Post by stringsibanez on Dec 19, 2016 17:54:35 GMT -8
So this is unrelated to my previous inquiries, but I noticed two things I was curious about: 1) In "fine faders" mode, I still can't get levels to adjust by only 0.1dB the way I can with cmd+mouse. Is this limitation standard, or is there a way to adjust sensitivity? 2) if I flip between the Raven overlay and the protools mixer, the stated levels/values are sometimes/often different. This seems to present itself more readily on lower fader values (below ~-16 or -17db it seems to more consistently show different values). For example: grabbing a random Raven fader and lowering it to -17.1dB -> flip to the ProTools mixer and it says the level is -17.2dB?? Any thoughts on this behaviour? Thanks, -Steve |
|
|
|
Post by jameyz on Dec 20, 2016 6:33:40 GMT -8
1. Push and Hold the Fine faders button to adjust the resolution.
2. I think what you are just seeing the limitations of HUI resolution at low dB values and the floating point integers not translating correctly due to the old protocol.
|
|
|
|
Post by stringsibanez on Dec 24, 2016 11:29:39 GMT -8
1. Push and Hold the Fine faders button to adjust the resolution. Awesome! I had been hoping there was a way to do this.. this makes the Raven even better. 2. I think what you are just seeing the limitations of HUI resolution at low dB values and the floating point integers not translating correctly due to the old protocol. Ok, that makes sense.. and also explains why the discrepancy only seems to present itself at lower fader values. |
|
|
|
Post by stringsibanez on Feb 21, 2017 21:22:26 GMT -8
Hey, So I'm not sure what the cause is since, as far as I can tell, nothing with my system has changed but: All of a sudden, the Raven software is no longer communicating with ProTools. I can launch the Raven software and the overlay will load and align itself with the session (provided it had been used with that session before close), but the bank buttons / transport controls / faders / etc aren't functioning or controlling the DAW. My batch command buttons for switching between PT workspaces seem to work fine. Note: V-Control appears to be working fine until Raven finishes launching.. at which point hovering over the "V" icon at the top of the screen in OSX produces the spinning wheel. I have so far tried: -Restarting everything (DAW, V-Control, Raven, Computer, etc) in various combinations. -Re-Running the Raven Installer software. -Trashing the V-Control Preferences. -Removing and then re-adding the HUI and Midi settings related to Raven/V-Control withing PT. No luck so far. Any thoughts? |
|
|
|
Post by jameyz on Feb 22, 2017 6:51:01 GMT -8
Hey, So I'm not sure what the cause is since, as far as I can tell, nothing with my system has changed but: All of a sudden, the Raven software is no longer communicating with ProTools. I can launch the Raven software and the overlay will load and align itself with the session (provided it had been used with that session before close), but the bank buttons / transport controls / faders / etc aren't functioning or controlling the DAW. My batch command buttons for switching between PT workspaces seem to work fine. Note: V-Control appears to be working fine until Raven finishes launching.. at which point hovering over the "V" icon at the top of the screen in OSX produces the spinning wheel. I have so far tried: -Restarting everything (DAW, V-Control, Raven, Computer, etc) in various combinations. -Re-Running the Raven Installer software. -Trashing the V-Control Preferences. -Removing and then re-adding the HUI and Midi settings related to Raven/V-Control withing PT. No luck so far. Any thoughts? Hi, Which OS are you on?? Do you have touch on the Raven buttons, they just don't trigger PT??? Is V-control added in accessibility??? Can you try the latest v-control update? neyrinck.com |
|
|
|
Post by stringsibanez on Feb 22, 2017 18:55:20 GMT -8
Hey, So I'm not sure what the cause is since, as far as I can tell, nothing with my system has changed but: All of a sudden, the Raven software is no longer communicating with ProTools. I can launch the Raven software and the overlay will load and align itself with the session (provided it had been used with that session before close), but the bank buttons / transport controls / faders / etc aren't functioning or controlling the DAW. My batch command buttons for switching between PT workspaces seem to work fine. Note: V-Control appears to be working fine until Raven finishes launching.. at which point hovering over the "V" icon at the top of the screen in OSX produces the spinning wheel. I have so far tried: -Restarting everything (DAW, V-Control, Raven, Computer, etc) in various combinations. -Re-Running the Raven Installer software. -Trashing the V-Control Preferences. -Removing and then re-adding the HUI and Midi settings related to Raven/V-Control withing PT. No luck so far. Any thoughts? Hi, Which OS are you on?? Do you have touch on the Raven buttons, they just don't trigger PT??? Is V-control added in accessibility??? Can you try the latest v-control update? neyrinck.comI am running OS X 10.8.5 The Raven software itself responds to touch as expected; ProTools just isn't receiving the input. I did everything in the initial setup of the MTi2.. everything was working fine until a few days ago. (Nothing with the system itself has changed). So far the best I've managed to come up with is a "ProTools is unable to communicate with HUI..." error. Which is essentially what I was imagining to be the case. This still doesn't explain V-Control pinwheeling forever once Raven is launched. |
|
|
|
Post by jameyz on Feb 23, 2017 7:42:51 GMT -8
Hi, Which OS are you on?? Do you have touch on the Raven buttons, they just don't trigger PT??? Is V-control added in accessibility??? Can you try the latest v-control update? neyrinck.comI am running OS X 10.8.5 The Raven software itself responds to touch as expected; ProTools just isn't receiving the input. I did everything in the initial setup of the MTi2.. everything was working fine until a few days ago. (Nothing with the system itself has changed). So far the best I've managed to come up with is a "ProTools is unable to communicate with HUI..." error. Which is essentially what I was imagining to be the case. This still doesn't explain V-Control pinwheeling forever once Raven is launched. Did you install the latest V-control?? Here is the link to start a support ticket for the Raven.. |
|
|
|
Post by stringsibanez on Feb 23, 2017 14:15:02 GMT -8
I am running OS X 10.8.5 The Raven software itself responds to touch as expected; ProTools just isn't receiving the input. I did everything in the initial setup of the MTi2.. everything was working fine until a few days ago. (Nothing with the system itself has changed). So far the best I've managed to come up with is a "ProTools is unable to communicate with HUI..." error. Which is essentially what I was imagining to be the case. This still doesn't explain V-Control pinwheeling forever once Raven is launched. Did you install the latest V-control?? Here is the link to start a support ticket for the Raven.. I only have the version of V-control that came with my initial Raven install. If I don't have it, I should probably try the latest Raven installer as well.I am currently downloading the V-Control 2.2.5.4 installer from the neyrinck site... I'll post back with results shortly. Edit: installing the latest version of V-Control has no effect on the issue... just getting a "ProTools is unable to communicate with HUI..." pop-up. |
|
|
|
Post by jameyz on Feb 24, 2017 10:06:34 GMT -8
Did you install the latest V-control?? Here is the link to start a support ticket for the Raven.. just getting a "ProTools is unable to communicate with HUI..." pop-up. Just check the box for "don't show this again" That pop up is normal. |
|
|
|
Post by stringsibanez on Feb 26, 2017 18:27:25 GMT -8
just getting a "ProTools is unable to communicate with HUI..." pop-up. Just check the box for "don't show this again" That pop up is normal. Yea, that stopped the pop-up, but v-control is still pin-wheeling forever and my Raven doesn't work. I have gone through this process: slatemt.zendesk.com/hc/en-us/articles/216707757-Complete-Clean-Uninstall-of-V-Control-Preferences a few times and re-installed with no luck. Trashed Pro-Tools preferences and repeated the setup processes. The only things I can think of are that my iLoks might have changed USB ports as I've taken them on some jobs.. but I'd have no way to know how they started. ..and at one point (during the last 2 or 3 weeks or so) I swapped out my Hackintosh's system definition file (smbios.plist) so that I could download the Sierra installer from the App Store, and then switched it back afterword. Neither of these things would explain to me though why V-Control would work perfectly fine until the Raven app attempts to connect to it.. at which point it stops working. |
|
.