Search found 6 matches


KeyCommand Utility - Now Testing Mac Support

UPDATE: 11/13/2013: New version with an updated css that uses smaller fonts. Added a "." to the empty cells.

There is now a bit of script that lets you more easily choose MAC or PC

#change these two values to identify MAC or PC
my @mods = @PCmods; #set to @MACmods or @PCmods case senstive
my @abrs = @PCabr; #set to @MACabr or @PCabr case senstive

Find this section and set the value after the = sign.

Typical disclaimer - this program isn't designed to do anything useful. If you accidently get it to do something you find agreeable, then that's a bonus. Should running it on your computer ruin your parents credit rating or modify the future beyond your ability to live in it (FZ reference FTW), that's on you.

perl script linked at the bottom of this post
Put the two files from the zip at the bottom of this post, in the directory that has your Key Commands.xml file in it.

Run the script
It will create a KeyCommands.html file
Open KeyCommands.html in your browser of choice.
Bask in the glory of my L33T Perl skillz...

There is a css file with a "background-color: xxxx" value for each command class of command. You can use internet colors or hex color values. Google css background-color for explanation of choices.

NOTE: There are some odd keyboard choices like '-' and '+' that are not treated normally. For example + should really be 'SHIFT+='. But because the + is treated as it's own symbol, there is a + row that can only ever have 1 command mapped to it. And you can never have a 'SHIFT+='. Hope that makes sense.

NOTE 2: If you hover your mouse over a command, it will show you the complete name as it is in the Cubase key command list like below;

Here is the original thread
Key Command Utility
by JMCecil
Sun Dec 30, 2012 3:41 am
Jump to forum
Jump to topic

Re: Mid-side lop-side

Voxengo msed is a good plug for decoding. :)
by Woodcrest Studio
Thu Oct 24, 2013 1:24 pm
Jump to forum
Jump to topic

Re: Ability to set up shortcut keys in VariAudio window

Do you mean toggling between segment editing and pitch editing? Tab does that.
by Soul-Burn
Tue Dec 03, 2013 1:37 pm
Jump to forum
Jump to topic

Re: Virgin Territory: Thoughts / Reactions

EDIT: This post too was edited to be correct...

i understand; but i am sceptical about how often the circustances fit for VT actually arise. the confusion involved in figuring out where a certain parameter will end up after VT passed is just too much for me personally.

Forgive me, but I think you're still thinking about it the wrong way.

If you load up a project and move your parameters around without writing any automation, you expect them to stay where they were when you last touched them, right? So if you move your rhythm guitar faders down to -6dB without writing it as automation, you expect them to be there until you move them the next time, yes? And this is regardless of if you close/re-open the project. Now, if you have VT turned on, without having written any automation, it should behave the same way. You touch and move a fader, and it should stay there until you move it again.

Now consider automation as just being the computer moving the fader for you, in a way that is predictable (because you told it to). So say you've decided to have the guitars at -3dB for the chorus, which happens a minute into the song. You've only moved the fader manually so far, so you go to the chorus and you engage automation and write -3dB for that section. Now you've moved the fader. Without VT the fader will return to -6dB before/after. With VT the fader will stay at -3dB after having passed the chorus. If you then touch it anywhere else it'll stay where you leave it, it won't move to either -3dB or -6dB, just wherever you left it.

So it should actually be entirely predictable. If you move the fader outside of where automation exists, then it stays where you left it. Once you read automation though - in the chorus that you automated - it'll stay at the last value of that written automation (-6dB). Here's an example:

VT: ON, automation -3dB at chorus.
Intro: You move the fader to -10dB and let go.
Verse: -10dB
Chorus: -3dB (automation read)
Verse: -3dB
Outro: You move the fader to -7dB where it remains until you press stop.

now you stop and press play again;

Intro: -3dB
Verse: -3dB
Chorus: -3dB (automation read)
Verse: -3dB
Outro: -3dB

When automation was written for the Chorus one automation point was written at the beginning of the timeline. That automation point is the same value as the first point written in the chorus - in this case -3dB. So when you started playback the second time it read that very first data point.

So as you can see the purpose of VT is not to make your levels 100% repeatable, for that you need to write automation either throughout all VT, or not use VT at all. Instead it's so that you can avoid having to disable automation read every time you want to experiment with a section. So in the above example when you have already written the chorus automation, you end up with the same experience automating the verse. You can just move parameters around without them "snapping" to pre-recorded automation values. Then you punch that automation in for the verse and move on to the next section.

See how the thinking is slightly different?
by Lydiot
Fri Jan 16, 2015 11:34 pm
Jump to forum
Jump to topic

Re: Virgin Territory: Thoughts / Reactions

Say you have a guitar that you want way down in the mix but haven't quite settled on how far, but you do know that you want it a bit louder in the chorus. I was hoping that with VT I could just draw in the boost and get a relative boost but what happened was that the level responded absolutely .
If I am reading you correctly, then you simply need to use Trim Mode in this instance ;).
by vic_france
Thu Jan 22, 2015 8:09 pm
Jump to forum
Jump to topic

The best features aren't always sexy.

Workflow aside (each DAW has it's own strengths and each user has their own preferences), I feel Cubase has the richest feature set and covers more bases than any other audio program. But... there are glaring issues that still prevent Cubase from being MY all-in-one solution.

1. Inability to reorder Mixconsole tracks independently from the Arrange window.
Everyone wants this, and they've wanted it forever.

2. No Mixconsole Undo.
Make it optional, make it separate from the arrange window undo, make it happen.

3. Nasty Mixconsole GUI.
Improve visual track separation in the fader section, find an answer to the hover button issues most everyone hates. Maybe even strive for some visual consistency between the different windows/features. Call me crazy.

4. Mouse scrolling in Mixconsole changes parameters.
Just make it an option you can turn on/off. I understand some people might dig that workflow, but for me it's a deal breaker when it's combined with the lack of mixer undo. I'd rather be able to just scroll through the tracks fearlessly without the threat of changing any values. If there's already a way to do this, please let me know.

5. No multi-track audio warp in the Arrange window.
In addition to the sample editor, add the ability to make edits directly to the audio regions. This makes time correction edits across tracks so much easier.

6. Stereo to mono tracks and vice versa.
Generally super useful.

Cubase is already great, but it could be even better - at least for me. Now that these ground breaking ideas have been unleashed on the world, I fully expect Steinberg to implement all of these changes by the next update. ;) Cheers.
by knitsudge
Fri Jan 23, 2015 5:25 am
Jump to forum
Jump to topic