Cubase 6.5 mixdown probleem

steve r

Stamgast
Lid sinds
1 augustus 2005
Berichten
260
Zit afgelopen 2 weken veel op synthforum met debiele vragen i know.
Hopelijk na deze is het afgelopen.

Als ik een mixdown maak en ja ik heb stereo out geselecteerd. Dan neemt hij vaak de kick niet meer op. Of opeens stoppen de synths.

Als ik cubase opnieuw opstart neemt hij de track volledig op alleen bij 5:_30 knalt hij weer de kick er uit.

Hoe the f is this possible ?
 
Dear Mr. Rutten,
This is not a common problem:

1.
You should reset your Cubase by generating a new preferences folder. All preferences will be set back as if Cubase has been freshly installed
In order to do so you must rename the following folder:

PC Windows 7
"OS Disk \User\<Your Username>\AppData\Roaming\Steinberg\Cubase xx"
You must rename to
"OS Disk \User\<Your Username>\AppData\Roaming\Steinberg\Cubase xx inactive"

As the case may be you should also rename the preferences folders of the other Steinberg products in the Steinberg folder. It can be advisable to rename the whole Steinberg folder to Steinberg inactive.
Preferences that you have grown accustomed to and that have taken allot of time to configure like for example key commands can be copied from the inactive folder o the active preferences folder

Windows:
To see hidden files:
1. On the Tools menu in Windows Explorer, click Folder Options.
2. Click the View tab.
3. Under Hidden files and folders, click Show hidden files and folders.
Note To access Windows Explorer, click Start, point to All Programs, and then click Windows Explorer.

2.
Temporarily you should rename your Vst plugin folder. With this approach, you will be able to check if a particular plugin is causing the problem.
The standard VST plugin path for 3red party plugins is

C:\Program Files\Steinberg\VstPlugins
You must rename to
C:\Program Files\Steinberg\VstPlugins inaktiv

If this procedure has fixed the problem, you know that a particular plugin has caused the error.
By copying the plugins of the inactive folder to the active VSTplugin folder one by one, you can make out what plugin in particular is causing the problem.
 
Back
Top