|
|
Post by machinesworking on Oct 14, 2016 14:39:54 GMT -8
So the preference window for UPDD Gesture Settings keeps popping up every time I start up the computer.
Since I assume it's best to leave it at factory default how do I get this pop up window to not pop up?
A couple other things:
Bach commands, it's cool you can make your own and that they show up across the .ravelay(s) you may have, but there's a HUGE trade off right now. .
You either use one ravelay, and get to have your configured commands in sets of 4,6,8 available to you when you hit "customize toolbar", but have to configure custom icons in the Raven mixer for each song you want to work on, or you use multiple ravelays that each have their own custom icons for tracks in the Raven Mixer, yet you must configure 4,6,8 blocks of Batch Commands in each Ravelay as you add in new commands, which is a mess. Especially considering that the way custom Batch Commands are stored is without their name, so each time you must rename a command like "Jump to next Marker" in the command box in the batch block. It's not impossible to have Batch command blocks of 4,6,8 commands etc. be a system wide preference, this would be the best solution. As it stands you either have to manually recreate each block of Batch Commands for each ravelay, or you have to re instantiate custom icons in each track for each song you open, each time you open that song, in order to preserve the "master" ravelay.
Is there any way to use only one rack in the Raven? DP is the only DAW that for some reason Slate decided to have as default two racks open. I'm fine with scrolling a little for commands I don't use all the time, and could easily see a "compose" set and "mixdown" set. I haven't seen any way in preferences to change it to start up with one rack open.
Thanks, I was told to forward any suggestions to your team, but the forum is a good start I think.
|
|
|
|
Post by jameyz on Oct 14, 2016 16:27:12 GMT -8
Hi,
You can save the Ravlay with just one Rack down, be sure to hit "Save layout" and overwrite the current layout.
I prefer to only use 1 ravlay for all of my sessions. Then I use the layouts for different task. Also, as long as you name the Tracks the same the custom icons should come up. The ravlay can store plenty of icon info so you shouldn't need to open for every song just for icons.
layout 1 Recording
Layout 2 Editing
Layout 3 Mixing
Layout 4 Bouncing
Layout 5 MIDI
|
|
|
|
Post by machinesworking on Oct 16, 2016 14:11:53 GMT -8
Jameyz,
I cannot save a Ravlay as a single rack, it always reverts to two racks when opening the ravlay.
having layouts for different tasks is a solution if, and only if you work in a similar fashion every time.
I use various VSTi's for different songs, there is no standard setup for me, save maybe at this point Maschine and Kontakt.
So, a generic set up will not do, that's why I prefer saving a ravlay with a song in DP.
It's a setup Slate seems to think is valid so it would be nice if I could move Batch commands already grouped in 4,6,8 windows between ravlays.
I have no idea what you mean by "Also, as long as you name the Tracks the same the custom icons should come up."?
Could you elaborate? I haven't seen this behavior.
|
|
|
|
Post by jameyz on Oct 18, 2016 13:21:08 GMT -8
Jameyz, I cannot save a Ravlay as a single rack, it always reverts to two racks when opening the ravlay. having layouts for different tasks is a solution if, and only if you work in a similar fashion every time. I use various VSTi's for different songs, there is no standard setup for me, save maybe at this point Maschine and Kontakt. So, a generic set up will not do, that's why I prefer saving a ravlay with a song in DP. It's a setup Slate seems to think is valid so it would be nice if I could move Batch commands already grouped in 4,6,8 windows between ravlays. I have no idea what you mean by "Also, as long as you name the Tracks the same the custom icons should come up."? Could you elaborate? I haven't seen this behavior. You really should be able to save the layout with 1 rack. Be sure to press "save layout" and overwrite the current layout after hiding the Rack. Once an icon is added to a fader in Raven the Ravlay saves the name of the track and the icon to put on that track name. So if another track appears with a similar name, it will add that icon to it. |
|
|
|
Post by machinesworking on Oct 20, 2016 11:42:00 GMT -8
Jameyz, are you overwriting the startup ravlay template in the user library? Reason I ask is because it doesn't work for me and my method has been to save a separate Ravlay for every new song.
Every time I start up the Raven software it reverts to two racks as the user library template is two racks. It will not store a single rack space in the separate Ravlays.
It seems that if you use a single ravlay the Raven will call up the selected icon for a specifically named track, this is pretty cool, and along with the fact that Batch commands have to be reinstantiated into Raven button block templates, including naming them etc. it makes it a much easier idea to use a single Ravlay. Getting even more into the concept, I'm wondering if there's any downside to overwriting the generic startup template Ravlay? It's easy enough in DP to have DP start up with a generic project that also opens up the Raven template Ravlay.
|
|
|
|
Post by jameyz on Oct 21, 2016 6:35:23 GMT -8
Jameyz, are you overwriting the startup ravlay template in the user library? Reason I ask is because it doesn't work for me and my method has been to save a separate Ravlay for every new song. Every time I start up the Raven software it reverts to two racks as the user library template is two racks. It will not store a single rack space in the separate Ravlays. Whenever you press "Set User Default" this replaces the ravlay in the user library. It seems that if you use a single ravlay the Raven will call up the selected icon for a specifically named track, this is pretty cool, and along with the fact that Batch commands have to be reinstantiated into Raven button block templates, including naming them etc. it makes it a much easier idea to use a single Ravlay. Getting even more into the concept, I'm wondering if there's any downside to overwriting the generic startup template Ravlay? It's easy enough in DP to have DP start up with a generic project that also opens up the Raven template Ravlay. The generic template that Raven starts up with lives inside the actual Raven Application, you could probably get away with replacing this with your own but it would every time you update/re instal the Raven. |
|
|
|
Post by machinesworking on Nov 1, 2016 14:58:05 GMT -8
The generic template that Raven starts up with lives inside the actual Raven Application, you could probably get away with replacing this with your own but it would every time you update/re instal the Raven. Yeah probably smarter to start up with your custom Ravlay by a blank DP project that uses startup clippings to instantiate it. Hey the inital problem though, UPDD Gesture settings window started showing up on startup, anythign I can do to make that stop? |
|
|
|
Post by jameyz on Nov 1, 2016 16:15:02 GMT -8
Hey the inital problem though, UPDD Gesture settings window started showing up on startup, anythign I can do to make that stop? This is fixed in the next touch driver update. It will launch at startup, but won't open the window every time... |
|
