Search found 8 matches

Return

Re: Workflow for Managing song sections?

Also don't forget that nothing is stopping you from having multiple projects open at once. Each can be a totally blank slate. If you have a LOT of plugins open (with samples), there might be a delay when switching between them (i.e. activating different project windows)...but other than that, no reason to stress.

Fun fact: You can copy and paste parts from one project to another, and if the same instrument is not in the other project, it will automatically create an instance of that instrument WITH ITS INSERTS AND EQs ETC to accommodate the part in question 8-) I do this all the time to re-use parts in other projects.
by meta-redundant
Tue Feb 04, 2014 10:56 pm
 
Jump to forum
Jump to topic

Re: 7.5 Bug: VST performance peak?

Thought I would share some of my own recent (and highly insane) tests!

I was getting weird spikes on a brand new Xeon workstation build. My older 2008 computer ran 7.5 fine. I noticed that it was centered primarily around locating the cursor in the project - clicking here, clicking there. After further experimentation, I realized it was caused by doing anything mouse-heavy. So, I did the following:

--Disabled my high-end Radeon GPU.
--Reverted to the on-board Intel integrated graphics.
--UNINSTALLED the Intel graphics driver, and used the generic Microsoft (!) driver (weird, but keep reading...)
--I went to the Troubleshooting tab of the graphics adapter, clicked the "Change Settings..." button, and moved the "Hardware Acceleration" slider one notch to the left (read about trying this in an old Nuendo forum post). For further info see http://www.wikihow.com/Turn-off-Hardware-Acceleration. I only moved it ONE notch, not all the way off!

Guess what: all CPU spike problems completely disappeared .

For confirmation, I then updated the generic driver to use the latest Intel build, and all the problems reappeared . In my case it is definitely related to the graphics rendering -- and what's weird is that using generic (software) rendering is an improvement!

The problem is that you can't just move this slider and forget about it, because the Change Settings... --> Hardware Acceleration slider is only available when using the generic Microsoft driver -- the entire "Change Settings" button is greyed out when using any vendor-specific drivers :(

FWIW, moving the slider one notch to the left disables "cursor and bitmap accelerations."

Try it yourself and see if the same thing happens for you! If so, this is definitely worth pursuing from a Support perspective.
by meta-redundant
Thu Feb 06, 2014 7:15 am
 
Jump to forum
Jump to topic

Got it sorted!

Earlier I posted how spikes and occasional clicks were definitely related to graphics for me, and how I was able to prove this by removing the AMD and Intel drivers entirely. Problem is, this is not workable in the long term because it disables just about every graphic option (including Aero).

I decided to try Fabio's advice and install a much older AMD driver - 12.1. And guess what - not only did the CPU peaks disappear, but the average load also decreased as well!! I am so happy to get to the bottom of this - it wasn't completely unworkable before, just annoying...and now it is like a new lease on life! For me the red peak indicator never lights up now, not even momentarily. Here's what I did if you have a Radeon (AMD) card of any kind and want to give it a try:

--Download driver package 12.1. You can do this from the AMD site by choosing your hardware and OS, but then when presented with the most recent driver, instead click on "Previous Drivers and Software" in the bar on the right. I chose the oldest one, v12.1 built on 1/25/2012.

--Completely uninstall all current AMD drivers and software. On windows, do this through Control Panel:
http://support.amd.com/en-us/kb-articles/Pages/GPU57RemoveOldGraphicsDrivers.aspx

--Reboot.

--Install the package you downloaded in the first step. I did NOT install Catalyst Control Center NOR any of the video transcoding options.

--Reboot that bad dog!

I mentioned earlier that moving the slider to disable mouse cursor enhancement also worked, and coupled with Fabio's comments about plugins "overriding the the default behavior of the pointer", I feel that this is definitely a contributing problem for many people who are getting CPU spikes (at least on Windows). Important note: I did not actually need to have any plugin windows open to get the spikes - the plugins only needed to be instantiated somewhere in the project.

THANKS FABIO for the suggestion! 8-)
by meta-redundant
Thu Feb 06, 2014 11:44 pm
 
Jump to forum
Jump to topic

Re: Moving midi in grid (key editor)

Cubase considers this a "Nudge" command.

Go into File --> Key Commands, navigate to the folder called "Nudge", and assign a key command to the "Left" and "Right" values.

The amount of nudging will occur according to the current Grid setting (i.e. if the Grid is 16th notes, the left/right nudging will also be 16th notes).

Good luck!
by meta-redundant
Thu May 08, 2014 9:44 pm
 
Jump to forum
Jump to topic

Re: How do film composers deal with large DAW projects for f

Try the freeze method, it's fun ;) You can even re-freeze tracks that now have MIDI data on them in order to make them audio-only. It's great for large film templates.

I had an idea that might solve the VEP bussing issue for large projects -- and that would be to create one VEP instance *per instrument*, then have them all aggregated into one metaframe. But, not sure if this would be an inefficient way of working CPU-wise. I mostly use Kontakt, and there is now no penalty for multiple instances of Kontakt vs. multiple instruments in one instance - I wonder if VEP works the same way. Only one way to find out I guess ;)
by meta-redundant
Sat Oct 11, 2014 9:16 pm
 
Jump to forum
Jump to topic

Re: How do film composers deal with large DAW projects for f

I don't really see the point of VEPro to be honest. My orchestral template is massive, and working directly inside of Cubase has proven to be the most hassle-free. All of my template tracks have a cc1/cc11 reset message at the beginning of them, and each are frozen. So I can load a template with 200+ tracks instantly. If I need a track, I just unfreeze it, which takes 2 seconds. VEPro supposedly makes large templates easier because you can decouple the sample save/recall from your host, but you still have to load that massive amount of samples at some point. But, a Cubase template with frozen tracks means you will only load the samples you need when you actually need them. Zero waiting time for anything.

I own VEPro, and the biggest problem with it is the bussing. I use Instrument Tracks - I do this because I constantly need to EQ, effect, and tweak the audio associated with each track. It's easy to assign a hotkey to open the Channel Settings window for the selected track. I want the EQ for 1st Violin, I select that track and press my Channel Settings hotkey. When using VEPro however, the general workflow is to create a server and connect to it via multiple MIDI tracks -- so if you need to find the audio output associated with a given MIDI track in a large template...good luck to you. And when you select that audio track, guess what happens - your MIDI track is unselected, so you can't play a note on your keyboard and hear the change you made to the audio output...you have to go back and find that MIDI track again. Infuriating. Separate MIDI and audio tracks is so 1997.

The other problem is automation. Automation parameters for plugins hosted in Cubase show up by name. I have track Quick Control assignments tied to each instrument in my template, and they can be intuitively automated. When using VEPro however, you get destination names like Parameter 1, Parameter 2, etc. Seriously, what the heck is that. Who knows what "Parameter 1" is controlling. I sure don't.

VEPro is like most other hosts-within-a-host -- it inserts this additional layer between you, your plugins, and your workflow. Everything you do is one extra step, even if it supposedly does better with x64 core handling blah blah blah. I sure didn't notice any improvement. It's one of those products I just don't get. I think it's mostly useful for people who need to wrap VSTs somehow (ProTools or x86 Win users).

Lol, sorry to be so negative - your mileage may vary ;)
by meta-redundant
Sat Oct 11, 2014 8:21 am
 
Jump to forum
Jump to topic

You are not authorised to read this forum.
by meta-redundant
Tue Oct 14, 2014 6:40 pm
 
Jump to forum
Jump to topic

Re: Moving midi tracks between Cubase projects

1) Not the tracks but the PARTS on the tracks. Select a part in one project and drop it in a blank area in the new project. It will also automatically bring the tracks' settings like EQ etc over.

2) But, the best way is probably to select all the tracks in question, then go to File --> Export --> Selected Tracks. Then do File --> Import --> Track Archive in the new project (selecting the file you exported a moment ago). That should bring everything from the other project into the new one.

Good luck!
by meta-redundant
Thu Oct 16, 2014 12:50 am
 
Jump to forum
Jump to topic