Search found 20 matches


Re: steinberg power scheme and cpu core parking ?

No...Steinberg power scheme does not disable core parking.

This requires an edit to the registry.....I guess if you found a utility to do this it is simply writing the registry changes for you.
by Grim
Mon Feb 17, 2014 3:50 pm
Jump to forum
Jump to topic

Re: Cubase 7.5.20

you loose the multitimbral functionality. For each channel you need a different dll. I know there is a workaround for that, but my IQ isn't high enough to take that into account.

Not sure what you mean by this.

I'm a new VEPPER (v5) but I can use as many outputs as any VSTi provides with a single instance inside VEP5 (Kontakt, Play4, etc).
You click the little plus sign on the first output and another is created - from the same DLL.

by HughH
Fri Mar 21, 2014 5:21 pm
Jump to forum
Jump to topic

Re: MIDI and VSTs

I don't know if it's possible in Artist, but it's certainly possible in Cubase.

1) Create the instruments you want to use as VST Instruments in the rack (NOT instrument tracks, as they will not work).
2) Create the MIDI track you want, with MIDI data on it.
3) Ensure that MIDI Sends is available in your inspector (right-click on it and tick it, if not)
4) Turn on Send #1, and set the output (which will start out as "not connected") to the first VST Instrument
5) Turn on Send #2, and set the output to the Second VST Instrument.

You should be good to go. You can, of course, send the "usual" output to a VST Instrument as well (or external MIDI or wherever), so you can have up to 5 instruments driven by the one track (original plus 4 sends)
by djaychela
Mon Apr 14, 2014 8:39 pm
Jump to forum
Jump to topic

Re: Activation issue

No need to send a support request. Just log into your MySteinberg account, click on your Cubase Elements 7, and you should see the "Software reactivation" button. You will need to provide your newly created Soft-eLicenser number (found in the eLCC).
by Scab Pickens
Wed Apr 16, 2014 8:10 pm
Jump to forum
Jump to topic

Re: Some basic questions - i7 or Xeon E5?

It's an English site but very good, they do music specialist builds and their engineers are pretty efficient and communicative. They will be able to tell you the latest developments and qualities of recording machines.
One of the staff posts on the Sound on Sound forum as Peter Kaine if you need a quick reference.
by Buchanan
Fri Apr 18, 2014 6:26 pm
Jump to forum
Jump to topic

Re: Not one '4-20' reference in the lounge today?

I know us Dutchies have this reputation but I've never tried it and never will.

@Roel: Oh sorry, ik zag een Nederlandse naam dus ik gokte het er maar op ;).
by Strophoid
Mon Apr 21, 2014 2:49 pm
Jump to forum
Jump to topic

Re: vstsoundfile for checkup

All working fine here.

Orchestra one in particular is great stuff :)
by fstaudio
Mon Apr 21, 2014 8:20 pm
Jump to forum
Jump to topic

Re: vstsoundfile for checkup

I will hopefully check it out soon to see how you did things.
by mpayne0
Tue Apr 22, 2014 1:40 pm
Jump to forum
Jump to topic

Re: a PLAYER version of cubase

As someone who has used Cubase live every weekend since SX3 a major YES!

But I doubt they will do that because there are just not enough of us to
make $$$ for 'SteinYamy'.

But never say never.
by curteye
Sat Sep 20, 2014 1:17 am
Jump to forum
Jump to topic

Re: Halion 5 performance issues

I think I've worked the cause at this end. Looks like a problem with teh Yamaha USB MIDI driver when more than 1 device is connected. I have an S90 and Motif-Rack-ES connected via USB to the PC, and this problem with Halion and the performance meter going off the scale only appears when I have the Motif device powered up, even though it is not used in the project.
by G.e.o.f.f.
Wed Oct 01, 2014 7:24 am
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: Build huge templates?

Hi All.

Back working on this issue. I eventually set up my 8DIO ADAGIO Strings Collection as trackpresets to try the modular idea I described in the initial post. It works OK. But I recently saw this video:

And became somewhat envious of the ease with which the composer is able to instantly choose articulations from his collection. Seems like a HUGE benefit to "the flow". But it means having a huge template. I recently doubled my ram to 28GB, so I am hoping that having a larger template is possible and I'm back to trying to figure this out.

I came across a few resources that others may find helpful.

A PDF tutorial (quite extensive) by Tobias Escher on setting up an orchestral template with VEPro:

An interesting tidbit on the ThinkSpace forum about a potential limitation in Cubase that adds time to loading large templates:

A cool idea on organizing a large template in cubase over on the Soundsonline forum:

Anyway, back on it. If anyone has suggestions, they are welcome. Thanks.
by nke
Thu Nov 06, 2014 12:52 pm
Jump to forum
Jump to topic

Re: One step past Instrument Freeze? Bounce to audio?

What you want to do is FILE>EXPORT>AUDIO MIXDOWN.
On the dialog, at top left, switch to "batch export" and select the instruments you want to bounce. At bottom under "import to project" choose "audio track" ("Pool" will auto select).
This will export any selected tracks, within the locator region, including any inserts and fader settings.
Use the naming conventions however you'd like to best be able to identify the tracks (this is where logical track naming shows its benefits!)
After its done, you'll have each instrument bounced to separate audio tracks. After making sure they sound how you like, you can delete the original VSTi tracks.

DONE. ;)
by enjneer
Tue Nov 11, 2014 5:18 pm
Jump to forum
Jump to topic

Re: Hidden Cubase 8 features!

record output to track on midi inserts (wasn't there before i think ) :P
by mozizo
Tue Dec 09, 2014 1:01 am
Jump to forum
Jump to topic

Re: Hidden Cubase 8 features!

I hope this isn't a duplicate. I jumped from 6.5 to 8 and so may have missed something, but I thought that Constrain Delay Compensation was a global feature, switching off plugins to reduce latency when recording. This is clearly described in the manual.

But what I didn't know is that CDC is available in individual instrument tracks - it is hidden by default and not mentioned in the manual unless I missed it. Presumably, it bypasses plugins just on the track and leaves other channels unchanged? Anybody else know any more?
by Parrotspain
Thu Jan 08, 2015 12:23 am
Jump to forum
Jump to topic

List of musicians available for remote recordings

The idea behind VST Connect is interesting but it assumes you know some professionals available for remote recordings. So, I think it would be useful to collect somewhere a list of musicians available for remote recording and their fees.

For example, I wish to add real saxophone to a project I am working on, but I don't know any professional to arrange a VST Connect session with...that's why such a list would be handy.
by dr4kan
Fri Nov 15, 2013 10:24 pm
Jump to forum
Jump to topic

Re: Are the recent failings by steinberg related to YAMAHA?

I've been using cubase since SX and recommending it to everyone i talk to for so many years. I do not recall them ever being this incompetent, flat out ignoring their own user base. I know that fairly recently they became owned by Yamaha but i haven't kept up with the details of it.

How long ago was the switch and do any of you feel like it might be related to what we are dealing with?


I've been using Cubase since SX as well and I don't see incompetence at Steinberg or see them ignoring their user base!

In fact, I see that one of the feature requests I made during 7.5 usage was even implemented in Pro 8 and makes my usage easier every day as a result - that's certainly not ignoring the users!

That being said, there's so many different usage scenarios of this product I personally feel they should be doing more during the BETA phase with the current user base. Allowing users to BETA new versions in order to maximize the bug identification or workflow issues before final release.
It's really quite easy to issue a time limited BETA license for a Beta Test version when using an eLicenser!
by fretthefret
Thu Jan 22, 2015 1:09 am
Jump to forum
Jump to topic

Re: HALion 5.1 udpate available

Hi all,

Sorry for the inconvenience. We can confirm that there are issues with the Windows installer and with the MegaTrig module and we are already preparing a 5.1.1 update that will fix both issues.
by Matthias Quellmann
Wed Jan 28, 2015 11:35 am
Jump to forum
Jump to topic

Windows Optimizations-guide working with DAWs and plugins!

I have made a Windows Optimizations-guide working with DAWs and plugins that has all the right and valid information, how to setup computers running windows system. Many have no real knowledge about this and there are tons of websites on the Internet state all kinds of bad advice and tweaks that often are counter productive instead of fixing anything.

I hope my guide will help you and answer some of your questions you might have.

AERO on Windows VISTA, Windows 7 Windows 8.1, Windows 10 - OS-X Cocoa Frameworks

AERO need to be ON to direct all graphic processing to use graphic card -GPU instead of the CPU. You don't want to use the CPU for the graphic representation in windows. Today, there are non benefits to disable AERO, just the opposite.

Any visual you see in windows are 3D,2D, API calls, GDI and DirectX and Windows programs/ apps include DAWs use your graphic card to run all 3D, 2D, API calls, GDI and DirectX visual acceleration in windows that are then connected to windows visual and graphical representations called AERO.

All graphical representation in windows is handle 100% by the GPU and the RAM on board of the graphic card when AERO is turned on. If you turn AERO OFF, all graphic visual get directed to the CPU again. (old behavior). Today that doesn't work because graphical visual in windows are programed and based on AERO and direct API calls, resulting in errors working with Windows, DAWs and other programs if you have AERO turn OFF.

API-graphical calls

So what is API calls? There are important technology included in Windows AERO interface that are very important part of windows interface. There are direct connections to the graphical representations that is called direct API calls. Developer use direct API-calls in example Cubase and other programs and the API-support is available in the form of the Windows Software Development Kit (SDK). SDK providing documentation and tools necessary to build software based upon the Windows API-calls that are associated to the Windows interface. Microsoft has provided the DirectX set of APIs as part of every Windows since Windows 95.

DSP coding will just increase every day so we will see more GPU based coding and add of more functions to the audio plugins use the GPU processing in example Cubase and Native Instruments in the near future. So it can be good idea to invest in a better graphic card without going crazy. In fact already today many 3 part manufactories base all their GUI code and API calls around AERO. This is true since Windows Vista and GPU processing and directed to the GPU and API-calls are used on both Windows VISTA 7 / 8.1, Windows 10 and OS-X, Linux and Ubuntu . On OS-X you can't disable their coca framework (Open-GL) and that is a good thing. I hope Microsoft will do the same and take away the legacy option so you can't disable AERO in the near future.

Windows XP background - History.

On Windows 95, 98 and XP all graphic were directed to the CPU only. On XP and older systems, windows and programs graphical representation and processing were directed to the CPU not the GPU on the graphic card.

There for it was recommend to use as so low graphic as possible because it took away CPU resources from the DAW programs and plugins. Its because all the programs, plugins and windows graphical interface shared the CPU. Today that old legacy behavior and operation is history.

About Process scheduler on XP to "background task".

This old tweak must be the most confused tweak since XP windows.
That tweak has been used and abused since Matthias Carsten at RME come up with this great tweak on XP only.

It was meant to be used with specific RME hardware on XP platform only to provide better low latency from 23ms to 3ms. Even Mattias Carsten that is the original founder of this tweak say as I do and Microsoft and all the tech Gurus in the world say the same thing; ---> on VISTA, Windows 7,Windows 8.1 and Windows 10 it should be set to PROGRAM.

Audio or ASIO are not a background task in windows.


Some people ask if MIDI is a background task? No, its not a background task either.
Its a real time operation. MIDI messages are made up of 8-bit words, and are transmitted serially at a rate of 31.25 kbaud.

POWER Schema

POWER Schema shall always be set on "Performance-mode" even for Laptop. Check in "Device manger" manually. Make sure in "Power-management" on all USB port isn't set to sleep/disable.


Disable all Speed step, C-wait and Sleep.
Hyperthreading shall be set to =ON
Turbo Mode can be ON as default. In some rare cases you can turn Turbo mode off.

UAC-User Account Control

You can go ahead and disable that in Windows VISTA, Windows 7 and Windows 8.1. In Windows 8.1 its no needed as in Windows 8.1 has another kernel core protection further down inside the core base that has stronger protections against bad code then UAC.

Windows hibernation

Windows hibernation can be a good idea to take away to free up space especially if you use SSD on /C: Windows.
Check the Internet how to do that.

Virtual Memory -" page sys"- settings.

You'll receive many different opinions on how to deal with the page-file. Some will say that you should completely disable it. Their logic goes that Windows is inefficient at using the page-file, and if you have plenty of memory you should just disable it since RAM is a lot faster than traditional hard drives. By disabling Virtual Memory, you are forcing Windows to use the RAM instead of the disk.

The only problem is that windows Virtual memory and page-sys functionality doesn't work like that. Because Windows will never page-sys the applications you are currently working with anyway so it will not make your computer performance any faster by disabling the page-sys.

What can happen instead is that your apps are going to start crashing, since there's no virtual memory for Windows to allocate. And even worse, your system will crash or become very unstable.

So what settings and how to proceed?

On Windows VISTA, Windows 7, Windows 8.1 and Windows 10 or later , let windows mange your Virtual memory regardless how many gigs of RAM you have installed. I have 32GB RAM myself. Let Windows manage your Virtual Memory - page Sys-file on "C: drive"- only. Do not use any extra partition for page sys either.

If you have more then one harddrive installed in your system, set all other drives then "C:" to "None" page sys-file. You only need one.

On windows XP only, it can be good to manage your page-sys file yourself. Set virtual memory to X1,5 times the RAM installed in the computer. Set the same value of both Max and Minimum. But these settings are only for Windows XP .

Core parking on Windows 7 and Windows 8.1

Disable core parking can be a good idea on some systems. This is advance operation require "reg-edit" operation so if you have no experience with systems you can mess up your system completely. On Windows 8.1 its much easier. check the Internet how to do that. ... 61804.aspx

Best Regards
by Freddie H
Fri Feb 06, 2015 1:09 pm
Jump to forum
Jump to topic

Re: Focusrite 18i20 and direct connect in cubase

I think I can help you finding a solution... If I understand you good you want to have control by the input faders (not the gain which is controlled by hardware) and your outputs in your Cubase... anyway probably this will gonna help you...
Try to set your Focusrite Mixer in the routing on "mixing" preset if you have (I have Liquid 56 and there is)... if you don't, then set in the routing section DAW 1-2 to Main Mix, Daw 3-4 to Output 3-4 or whatever you are using and how many you have connected... In the mixer/fader section set DAW 1-2 to ASIO OUT. On ther main mixer output of the mixer/fader section do not set nothing... unnattach whatever you have there...
You can also mute all the channels in Focusrite Mixer to be sure you are not duubling signal.
Now, open Cubase and try to connect anything how you wanted or do even better and my advice for you is to get to know with Control Room feature in Cubase... it's really nice and it could be usefull tool for you...
here is a link to a post about how to work with CR... the beggining of the post you have a links to a youtube lessons which are made very easily to understand.
I hope it'll help...
by emaraz
Wed Mar 18, 2015 1:58 am
Jump to forum
Jump to topic