Problem

Attempts to carry out license transactions by using the Syncrosoft License Control Center (LCC) fail.
For example, one of the following error messages appears:

"The license server is not running."

"The license could not be downloaded because it is not recognized by the local License Database."

"TokenActivationContainer: XML Parsing error." 

Background

Already in 2009, the LCC has been replaced by the eLicenser Control Center which allows for a more convenient and secure license management. After a 2-year transition period the LCC server has been disabled in October 2011.
Since then license transactions can only be completed by using the eLicenser Control Center.

Solution

Please simply install the latest eLicenser Control Center before you download or transfer a license.

The latest version for your operating system can be found here:

www.elicenser.net/en/latest_downloads.html

Many Steinberg programs store their license in the so called Soft-eLicenser, a virtual license container on the hard disk.
 
Transferring the license from the Soft-eLicenser to an USB-eLicenser (copy protection device) offers various advantages:

• With your license on an USB-eLicenser you can install and use your Steinberg program on as many computers as you like. To authorise the installation you want to use just connect the USB-eLicenser.
• Programs that are using the Soft-eLicenser can only be activated on computers with internet access. An USB-eLicenser enables activation of your Steinberg software on computers that are not connected to the internet. 
• Licenses stored on the hard disk need to be reactivated online after reinstalling the operating system or switching to another computer. Using an USB-eLicenser makes online reactivation redundant.. 
• Furthermore, the license transfer to USB-eLicenser is a necessary condition to be able to upgrade to a higher program version that requires an USB-eLicenser. 

USB-eLicensers are available from any Steinberg dealer and, of course, at our online shop. 

This is how it works: 

• Install the latest eLicenser Control Center on the computer on which you've already activated your Steinberg program: http://www.elicenser.net/en/latest_downloads.html 
• Open the eLicenser Control Center. On Windows computers you'll find it under Programs > eLicenser in the Start menu. On Macs in the "Applications" folder. 
• Connect the USB-eLicenser. On Windows wait until the driver installation has finished. 
• The eLicenser Control Center will now show you both Soft-eLicenser (hard disk symbol) and USB-eLicenser.
• Click on the Soft-eLicenser to select it. 
• In the list to the right, click on the Soft-eLicenser license you wish to transfer to grab it and drag it to the entry of the other USB-eLicenser license while holding down the mouse button.
• As soon as you release the mouse button the license will be transferred. 

Problem

Reason

Solution

Dear Steinberg user,

Apple's Mac OS X 10.7 Lion has been released and you might want to upgrade to this new operating system as soon as possible.
Below you can find a chart with the current status.

Please note that all products released in September 2011 or later should automatically be Mac OS X Lion compatible. For details, please always refer to the system requirements on the corresponding product pages on our website. Those products won't be listed here anymore.

Additional information on Cubase - Mac OS X Lion (10.7.) compatibility

Valid for Cubase AI 5, Cubase LE 5, Cubase Essential 5, Cubase (+Studio)5, Cubase LE/AI/Elements 6 and Cubase (+Artist) 6:

Problem:
ASIO Ports may have a different naming. Loading projects created with the same system setup on previous Mac OS X version (10.6) may result in "Missing Ports" window for the ASIO ports.
Workaround:
Re-map the ports in the "Missing Ports" window, consider to set the checkmark in the "Map Always" column then.
Solution:
Under investigation.

Problem:
PowerPC plug-ins are missing and can not be loaded or found, affecting e.g. Monologue, Embracer and Tonic
Workaround:
None. Apple does not provide the Rosetta component anymore, required to run PowerPC code on Intel-based Macintosh computers.
Solution:
If you rely on specific PowerPC plug-ins, do not update to Mac OS X Lion (10.7) or consider using alternative plug-ins!

Valid for Cubase LE/AI/Elements 6 and Cubase (+Artist) 6:

Problem:
Starting Cubase for the first time and using the Built-in Audio Driver of Mac OS X may result in not correctly applied ASIO Buffer Size settings.
Workaround:
In Cubase go to menu "Devices" > "Device Setup..." > "VST Audio System" > "Built-In Audio" and click either on "Reset" or open the Control Panel and select a Buffer Size.
Solution:
Under investigation.

Valid for Cubase 5.5.3 and Cubase Studio 5.5.3

Problem:
Due to the fact that Apple has dropped Rosetta in Mac OS X 10.7, Cubase 5.5.3 and Cubase Studio 5.5.3 are not starting up because of issues with the VST Bridge, when trying to initialize PowerPC based plug-ins.
Workaround:
Please remove the VST Bridge component by proceeding as follows:

• Make sure that Cubase is not running, then go to Finder and browse to Applications.
• Cmd-click (or right-click) the Cubase 5.app file and select “Show package contents”.
• Browse into folder Contents/Components
• Cmd-click (or right-click) the "VSTPlugManager.bundle" file and select “Show package contents”.
• Browse into folder Contents/Resources
• Remove "VSTBridgeApp"
• Close all folders, re-start Cubase.

The other alternative is to remove the PowerPC Plug-ins itself on Lion systems, e.g. the ones contained inside the Cubase application bundle (Contents/VSTPlugins... Filter: All files containing the name "Tonic", Synth: All files containing the name "Embracer" and "Monologue", Restoration:"DeEsser.vst"). Then there may be 3rd party plug-ins installed in /Library/Audio/Plug-Ins, either on user level or system level (or both).

Problem

Error message:
„Application LCC2 exclusive“ has caused the Following error: „Unable to Save SLD files in POS folder. Please adjust filesystems permissions correctly”
or
At least one connected eLicenser contains licenses wich cannot be used with the installed version of 'eLicenser Control'.

Cause

Some program or driver installation has changed rights in the folder
C:\Program Files\
Therefore, the eLD-Files, which are necessary for the interpretation of the licenses can not be loaded and the eLCC tries to update the ELD-Files,  which will fail due to changes in the rights structure.

Solution

Issue

An already existing Sequel 2 LE (OEM version) installation might prevent the Sequel 2 (retail version) installer on Windows from completing the installation of additional content for HALionOne.

In order to avoid or repair an uncomplete content installation please follow the steps below.

Solution

• If Sequel 2 has not been installed yet:

  • Before installing Sequel 2 please uninstall HALionOne!
    This can be done via Window's Start menu. Go to (All) Programs > Steinberg HALionOne and select Uninstall.
    Alternatively, you can use the Windows control panel Software (Windows XP) or Programs and Features (Vista/Windows 7) to uninstall all HALionOne components.
  • Afterwards, simply install Sequel 2 from DVD.

• If Sequel 2 has been installed already:

  • Please uninstall HALionOne!
    This can be done via Window's Start menu. Go to (All) Programs > Steinberg HALionOne and select Uninstall.
    Alternatively, you can use the Windows control panel Software (Windows XP) or Programs and Features (Vista/Windows 7) to uninstall all HALionOne components.
  • On the Sequel 2 DVD go to the folder Sequel 2 for Windows\Additional Content\HALionOne and double-click HALionOne_Setup.exe.
  • Follow the on-screen instructions in order to complete the proper installation of HALionOne and its content. 

Microsoft Windows Vista and Windows 7 operating systems are available in two versions: the 32-bit and 64-bit edition. The main difference between these versions is the size of RAM that can be addressed by the operating system and applications.

Windows x86 (32-bit) version

A 32-bit operating system like Microsoft Windows Vista allows you to run 32-bit applications only, while each application can address up to 2 GB of the available RAM. Generally, all Steinberg applications are available as a 32-bit binary and can be run with 32-bit versions of Microsoft Windows Vista and Windows 7.

Windows x64 (64-bit) version

The 64-bit versions of Microsoft Windows Vista and Windows 7 let you run 32-bit as well as native 64-bit applications such as Cubase 6 or Cubase 6 x64 (Please have in mind that Cubase 6 and the Cubase 6 family are only supported on Windows 7). Thanks to the OS built-in compatibility layer that allows 32-bit software to run on 64-bit operating systems, all Steinberg 32-bit applications supporting 32-bit versions of Windows Vista and Windows 7 are supported on 64-bit operating systems as well. The difference is once again the amount of RAM available to applications. While a 32-bit application running on a 64-bit operating system can address up to 4 GB of RAM, (which is already twice as much as under a 32-bit version of Windows), a native 64-bit application such as Cubase 6 x64 supports a much larger RAM capacity.

For many of its products, Steinberg already provides both 32-bit and 64-bit versions that are found on the same installer disc. This allows you to choose which version best fits your current requirements. Please note that if your installer includes the 32-bit version, but not the 64-bit version (such as Sequel), your product does support Microsoft Windows Vista 64-bit / Windows 7 64-bit versions but is not able to access more than 4 GB of RAM at a time. If a native x64 application is also included, the system requirements on the corresponding Steinberg product page mentions that a native x64 version is included.

Please note that there are further differences between the 32-bit and 64-bit versions of Steinberg applications. For example, some components may currently not be available in 64-bit, such as QuickTime and Rewire. Generally, 64-bit VST hosts won't be able to run 32-bit VST plug-ins, but only native 64-bit VST plug-ins. However, Cubase 5 x64 can also support 32-bit VST plug-ins thanks to VST Bridge technology from Steinberg, which allows 32-bit VST plug-ins to run in a 64-bit host environment, Please note that compatibility issues may still occur owing to technical limitations in the bridging process. These limitations do not affect running 32-bit Steinberg host applications under Microsoft Windows Vista/Windows 7 64-bit versions and affect only native x64 host applications.

We’d like to update you on the development and certification process regarding Mac OS X 10.6 (Snow Leopard) for current Steinberg products. We see the certification of our products for Snow Leopard as a major development milestone and an important step that will help musicians and producers get the most out of the latest operating system.

You can find a list of Mac OS X 10.6 (Snow Leopard) compatible Steinberg applications below. Please make sure that you always use the latest updates available!
For products that become available after the release of this article, check the corresponding product pages and the system requirements on supported operating systems.

Please note that all other applications that are not listed here are not officially compatible with Mac OS X Snow Leopard and no further updates are planned.

We’d like to update you on the development and certification process regarding Windows 7 for current Steinberg products. We see the certification of our products for Windows 7 as a major development milestone and an important step that will help musicians and producers get the most out of the latest operating systems.

You can find a list of Windows 7 compatible Steinberg applications below. Please make sure that you always use the latest updates available!
For products that become available after the release of this article, check the corresponding product pages and the system requirements on supported operating systems.

Please note that all other applications that are not listed here are not officially compatible with Windows 7 and no further updates are planned.

Problem:
Under rare circumstances, if you use the "Generic Low Latency ASIO Driver" and export a mp3 file with a small bitrate (< 100 kbps) the program might crash.

Workaround:
Please use a higher bitrate (for example 128 kbps).

The following troubleshooting tips & instructions are basically valid for all Steinberg sequencers running on Windows since Cubase SX 1, Nuendo 1 and Sequel 1.

Overview

1. Updating the eLicenser Control Center
2. Initialising Preferences
3. Updating the Sequencer
4. Reinstalling the Sequencer
5. Updating Device Drivers
6. VST Plug-in Troubles (Cubase and Nuendo only)
7. MIDI Timing Troubles

1. Updating the eLicenser Control Center

2. Initialising Preferences

Corrupted program preference files can bring your Steinberg sequencer into all kinds of troubles, particularly after installing an update.
Fortunately, refreshing the preferences is quite easy:

• Quit the sequencer.
• Go to "Start menu > (All) Programs > *Your Steinberg Sequencer* and select "Open *Your Steinberg Sequencer* Application Data Folder". 
It's a direct link to the folder where all program relevant settings and preferences are stored. It will be opened in a new Windows Explorer window.
• Go up one level in the directory tree by hitting Alt + Up Arrow (Windows Vista, Windows 7) or Backspace (XP, above Enter key). 
Now you are in the Steinberg folder within the "Application Data" (XP) resp. "Roaming" folder (Windows Vista, Windows 7) of Windows.
• Locate the folder which is named the same as your sequencer, for example "Cubase 5".
• Rename it (for example to "Cubase 5 hidden") in order to hide it from the sequencer.

Next time you start the sequencer it will create a new folder with fresh preferences and default settings - which hopefully fixes the problem you've experienced.

Please note: If you find folders of previous Steinberg sequencer installations make sure to hide them too by renaming or removing them. Otherwise the sequencer would try to comply with them when creating fresh preferences. And exactly this could be the source of errors.

Initialising the sequencer's preferences does not necessarily mean that you lose all settings. For example if you have defined your own set of key commands that you want to keep you can replace the corresponding file (Key Commands.xml) in the freshly created folder by a copy of the same file taken from the folder you've disabled by renaming.

Alternative ways: Instead of renaming it you also can move the preferences folder of your sequencer from Steinberg's application data folder to another place, for example the Desktop. You even can simply trash it if you are sure that your user settings are not that hard to rebuild. Another approach: Since in many cases the file "Defaults.xml" will be the trouble maker you also could try if renaming or deleting only this particular file already solves the problem.

This Knowledge Base article provides further information on Cubase's preferences and their location: Cubase and Nuendo Program Preferences Files in Detail

Making a backup of the preferences obviously is a good idea, especially when you customize a lot. And it's easy: Simply keep a copy of the preferences folder that you can fall back on whenever you need to reset the preferences to your preferred settings.

3. Updating the Sequencer

Check if your Steinberg sequencer is up-to-date. A current version might include a solution for the problem you are experiencing. Updates are available here: Downloads on www.steinberg.net
The "Version History" document on the same page will tell you which issues have been addressed.

4. Reinstalling the Sequencer

Reinstalling the complete program is only necessary on rare occasions. In general these steps will suffice:

• Go to "Start menu > (All) Programs > *Your Steinberg Sequencer*, select "Uninstall" and follow the instructions of the uninstaller.
• Optional: Of course, the uninstaller only deletes files it previously has installed. If you find a remaining program folder under "C:\Program Files\Steinberg" take a look inside and check if it contains files that you want to keep. If not, delete the folder.
• Optional: Remove (or hide) the preferences folder (see information on "Initialising Preferences" above).
• Install the sequencer from your original CD/DVD.
• Install available updates provided here: www.steinberg.net/en/support/downloads.html

5. Updating Device Drivers

Your Steinberg sequencer is dependent on flawlessly working audio and MIDI interfaces. Many problems are caused by bad device drivers. Check the homepage of your gear's manufacturer for updates. If you have installed drivers from a CD-R that came with an interface you can almost be sure that they are fatally outdated.

6. VST Plug-in Troubles (Cubase and Nuendo only)

If Cubase/Nuendo hangs or quits during the start up or while loading a specific project file it is likely that an installed VST plug-in is causing trouble.
Temporarily hiding installed VST plug-ins from Cubase/Nuendo is an easy and effective way to verify if a specific plug indeed is sabotaging your sequencer.
Of course, for this operation you need to know all VST plug-ins folders Cubase/Nuendo is knowing...

Locating VST Plug-in Folders

• In Cubase/Nuendo, select "Plug-in Information" from the "Devices" menu.
• Make sure the "VST PlugIns" tab is selected and click on "VST 2.x Paths".
• The VST 2 paths known to Cubase/Nuendo will be listed. Write them down, make a screenshot or simply memorize them.
• Additionally consider the VST 3 plug-ins folder: C:\Program Files\Common Files\VST3

Hiding VST Plug-ins

The following steps describe only one possible application of the "hiding stragegy". Of course you can have your own approach if you've understood the basic idea.

• Quit Cubase/Nuendo.
• Navigate to the first VST plug-in folder (refer to the note or screenshot you've made before, or your memory).
• Assuming the folder is named "VSTPlugins", rename it to "VSTPlugins_hidden". This will hide it from Cubase/Nuendo.
• Restart Cubase/Nuendo.
• If necessary, load the problematic project. In this case Cubase/Nuendo will complain about missing plug-ins. Simply ignore corresponding error messages.

If the problem persists you know that it is obviously not related to a VST plug-in inside this hidden folder. In this case rename the folder to its original name and repeat the procedure with the next VST plug-ins folder on your list.

If hiding one of the folders actually fixed the problem you still don't know the bad guy but, after all, you know where he is living... In order to identify the problematic plug-in create a new folder next to the hidden one and give him the original name, in this example "VSTPlugins". Now you can move the most suspicious plug from the renamed folder (e.g. "VSTPlugins_hidden") to the new one (e.g. "VSTPlugins"). Restart Cubase/Nuendo and see if it still runs correctly. Repeat moving plug-ins and restarting Cubase/Nuendo until you've finally isolated the trouble maker. In case you have a lot of plug-ins installed moving half of the them at a time might speed up the search.

7. MIDI Timing Troubles

Don't despair if incoming MIDI data will not be recorded correctly, for example with a constant offset, although you already have updated the MIDI driver. The following instructions will probably fix the problem:

Cubase SE/SL/SX 3.1 and Nuendo 3.1 or later

• In Cubase/Nuendo, select "Devices Setup..." from the "Devices" menu.
• In the "Device Setup" window click on "MIDI > MIDI Port Setup".
• Installed MIDI ports should now be listed in the right part of the window.
• Enable the option "Use System Timestamp for 'Windows MIDI'." which you find beneath the listed ports. 
Depending on the installed MIDI driver "Use System Timestamp for 'Windows DirectMusic'." might also be available. Enable it, too. 
(If system timestamp already has been used unmark the option. In other words: Change the status of the "Use System Timestamp..." option.)
• Click on OK in order to close the Device Setup window and enjoy accurate MIDI data recording.

Older Cubase and Nuendo Versions

• Please refer to this Knowledge Base article: "PC Windows MIDI port configuration and troubleshooting"

The following troubleshooting tips & instructions are basically valid for all Steinberg sequencers running on Mac OS X since Cubase SX 1, Nuendo 1 and Sequel

Overview

1. Updating the License Control Center
2. Initialising Preferences
3. Updating the Sequencer
4. Reinstalling the Sequencer
5. Updating Device Drivers
6. Hiding the Public VST Plug-ins Folder (nur Cubase und Nuendo)
7. Further Articles

1. Updating the License Control Center

The most common reason for USB-eLicenser (dongle, formerly named Steinberg Key), Soft-eLicenser and/or license related problems is an outdated or corrupted License Control Center (LCC) installation.
So if an USB-eLicenser or a specific license on it is not recognized, or you get any LCC error messages when starting your Steinberg sequencer, you should download and install the latest LCC version at first: Download License Control Center
In case the installation fails try to install again after you've unplugged the USB-eLicenser.

This knowledgebase article provides further and more detailed assistance in solving dongle and license related issues: "USB-eLicenser - Details, tips and troubleshooting"

If your Steinberg sequencer is protected by a Soft-eLicenser you will find more information in the "Soft-eLicenser FAQ".

2. Initialising Preferences

Corrupted application preference files can bring your Steinberg sequencer into all kinds of troubles, particularly after installing an update. Fortunately, refreshing the preferences files is quite easy:

• Quit the sequencer.
• Go to "User Home/Library/Preferences" and locate the folder which is named the same as your sequencer, for example "Cubase 5". This folder contains all preference files of your sequencer.
• Rename it (for example to "Cubase 5 hidden") in order to hide it from the sequencer.

Next time you start the sequencer it will create a new folder with fresh preferences and default settings - which hopefully fixes the problem you've experienced.

Please note: If you find folders of previous Steinberg sequencer installations make sure to hide them too by renaming or removing them. Otherwise the sequencer would try to comply with them when creating fresh preferences. And exactly this could be the source of any error.

Initialising the sequencer's preferences does not necessarily mean that you lose all settings. For example if you have defined your own set of key commands that you want to keep you can replace the corresponding file ("Key Commands.xml") in the freshly created folder by a copy of the same file taken from the folder you've disabled by renaming.

Alternative ways: Instead of renaming it you also can move the preferences folder of your sequencer from the User/Library/Prefences folder to another place, for example the Desktop. You even can simply trash it if you are sure that your user settings are not that hard to rebuild.
Another approach: Since in many cases the file Defaults.xml will be the trouble maker you could also try if renaming only this particular file already solves the problem.

This Knowledge Base article provides further information on the preferences of Cubase and Nuendo and their location: Cubase and Nuendo Program Preferences Files in Detail

Making a backup of the preferences obviously is a good idea, especially when you customize a lot. And it's easy: Simply right-click on the preferences folder of your Steinberg sequencer within User Home/Library/Preferences and select Create Archive of (Tiger) or Compress (Leopard) from the contextual menu. This creates a Zip file that you can always fall back on if you need to reset the preferences to your preferred settings. Of course you could as well keep a common copy of the folder at a location of your choice.

3. Updating the Sequencer

Check if your Steinberg sequencer is up-to-date. A current version might include a solution for the problem you are experiencing. Updates are available here
The Version History document on the same page will tell you which issues have been addressed.

4. Reinstalling the Sequencer

Reinstalling the complete application is only necessary on rare occasions. In general these steps will suffice:

• Go to Applications and trash the application file, for example "Cubase 5".
• Optional: Go to User Home/Library/Preferences and remove (or hide) the preferences folder (see information on Initialising Preferences above).
• Install the sequencer from the original CD/DVD.
• Install available updates provided here: Downloads on www.steinberg.net

In case the reinstallation fails this Knowledge base article provides instructions on how to manually remove Cubase related files: Mac OS X: How do I uninstall an application completely?

5. Updating Device Drivers

Your Steinberg sequencer is dependent on flawlessly working audio and MIDI interfaces. Many problems are caused by bad device drivers. Check the homepage of your gear's manufacturer for updates. If you have installed drivers from a CD-R that came with an interface you can almost be sure that they are fatally outdated.

6. Hiding the Public VST Plug-ins Folder (Cubase and Nuendo only)

If your Steinberg sequencer hangs or quits during the start up or while loading a specific project file it is likely that an installed VST plug-in is causing trouble.
This is how you can verify if a specific plug indeed is sabotaging Cubase.

• Quit your Steinberg sequencer.
• Go to Library/Audio/Plug-Ins and locate the folder VST. This is the default location for all VST plug-ins in Mac OS X.
• Rename the folder (for example to "VST_hidden") in order to hide it temporarily from the sequencer.
• Restart the sequencer (and, if necessary, load the problematic project).

If the problem persists you know that it is obviously not related to a VST plug-in. In this case rename the folder to its original name "VST".
If renaming the VST folder fixed the problem the source of error obviously is located in the renamed plug-ins folder. In order to find out the bad guy create a new folder next to the disabled one and name it "VST". Now you can move the most suspicious plug from the renamed folder ("VST_hidden") folder to the new one ("VST"). Restart your Steinberg sequencer and see if it still runs correctly. Repeat moving plug-ins and restarting the sequencer until you've finally isolated the trouble maker. In case you have a lot of plug-ins installed moving half of the them at a time might speed up the search.

7. Further Articles

In these articles you'll find further solution for problems on your Mac:
Optimizing Mac OS X for DAWs / Mac Performance Trouble Shooting
USB-eLicenser - Details, tips and troubleshooting
Soft-eLicenser FAQ
Mac OS X: How do I uninstall an application completely?

Welcome to the Resale Wizard for used Steinberg software! After answering a few questions you'll know what to consider when you are planning to sell your Steinberg Software.

Please note that educational products or licenses are personal.
They cannot be passed on or sold to any other third party or person.

START RESALE WIZARD...

Problem:
If you´re using the software "HEAR" on your Mac system, it may happen that the Core-Audio driver becomes inactive for operations with your sequencer software. In some cases the sequencer software will even start up without any error message!

Solution:
Delete all "HEAR" components from your operating system.
Then go into this directory:
APPLICATIONS->UTILITIES->AUDIO/MIDI-SETUP
here, please open the AGGREGATE DEVICE EDITOR and delete the entry AGGREGATE-AUDI-DEVICE from the list.
In addition to a complete removal of all "HEAR" components, please delete the folder "HAL" in: LIBRARY->AUDIO->PLUG-INS->HAL

Finally just close the active entries "COREAUDIO" and "USEREVENTAGENT" in your activity monitor (Utilities).

In single cases the installation of Sequel might cause a disfunction of HALionOne in the following Cubase versions: Cubase AI 4, LE 4, Essential 4 and Studio 4 in version 4.1 or higher.

The problem can be solved by re-installing the HALionOne content packs from the original installation disc. The corresponding installation files ("*.msi") can be found in this directory:

Additional Content\Sound Frame\HALionOne Soundbanks\

The problem can be prevented by unistalling HALionOne prior to the installation of Sequel 2! (Windows: It is strictly recommended to use the "Add or Remove Programs" function in the control panel)

Problem:
After updating from Sequel 1 to Sequel 2, the Sub Style "Drum 'n' Bass" is missing.

Cause:
When starting Sequel 2 for the first time, certain program preferences from Sequel 1 will be taken over so you can start a new project without delay. In some cases it can happen that this Sub Style is not displayed.

Solution:

PC Windows

1. Exit Sequel 2
2. In Windows, go to the Start Menu > Programs -> Sequel 2
3. There, start "Open Sequel 2 Application Data Folder".

A new Explorer windows opens with all files and folders of the preferences for the host application. As an alternative you can browse to this location by yourself using the path e.g. "C:\Documents & Settings\[login username]\Application Data\Steinberg\Sequel 2"

   4.  Delete the "Mediabay" file

Mac OS X 

1. Exit Sequel 2
2. Open the "Finder" and go to the folder: Users > [login user name] > Library > Preferences > Sequel 2
3. Delete the "Mediabay" file

Now the Mediabay will be rebuild on starting Sequel 2. You will find two Drum 'n' Bass entries: one contains the MIDI loops and the other the audio loops.

Problem:
Sequel 2 projects and the new content sets cannot be opened in Cubase Studio 4, Cubase 4 and Nuendo 4.

Cause:
We had to change the name "Soundframe" to "VST Sound". This also changed the used file extensions. Older Cubase Studio 4, Cubase 4 and Nuendo 4 versions are currently not compatible with this new naming and thus cannot read or load them.

Solution:
Please download the latest Cubase (Studio) 4 and Nuendo 4 updates, so you are able to open the Sequel 2 projects and content sets.

Problem

When I preview sounds via the onboard soundcard of my Samsung X20/ X25 notebook in the Mediabay of Sequel 2 the sound is distorted.

Solution 1

This problem can be solved by using an external soundcard or by installing the ASIO4all driver. This generic ASIO driver can be downloaded from www.asio4all.com and allows to work with lower latencies.

Solution 2

Select "ASIO DirectX Full Duplex Driver" in Sequel 2 as the audio connection. Now close Sequel 2. In Windows go to START --> PROGRAMS --> SEQUEL 2 and select "ASIO DirectX Full Duplex Setup". In this menu you select at Sync Reference "Direct Sound Output". Now uncheck the checkbox of your soundcard at the "Direct Sound input channels".

This article provides useful instructions on how to optimize Mac OS X for digital audio workstations. The first part is focusing on general operating system maintenance. More specific trouble shooting tips can be found in the second part which is dealing with CPU and performance related issues.

1. General Mac OS X Maintenance

1.1 Repairing Permissions

This is a classic Mac OS X trouble shooting issue. You'll get very different advices when it comes to the Repair Permissions function of the Disk Utility in Mac OS X. Some people recommend to repair permissions on a regular basis, some do this even before and after every single installation. Others never repair permissions without running into problems. At least it is important to know that there is the possibility of repairing permissions in case you are experiencing troubles with your system and/or Cubase:

• Go to Applications/Utilities and start Disk Utility.
  
• On the left side of the Disk Utility window select your system volume/partition.
  
• On the right side make sure the First Aid tab is selected and then click on the Repair Disk Permissions button. (Of course you may click on Verify Disk Permissons at first. But as most of the time there are some permissions that need to be repaired you can save some time by skipping the verification and starting the repair at once.)

Apple articles dealing with permissions:

About Disk Utility's Repair Disk Permissions feature
Troubleshooting permissions issues in Mac OS X

1.2 Running Maintenance Scripts

Mac OS X is a pretty carefree operating system. However, since some built-in maintenance scripts are scheduled to be executed in the middle of the night, some manual operation is necessary from time to time when your Mac is asleep at night. In Apple's words: "Mac OS X performs background maintenance tasks at certain times if the computer is not in sleep mode. If your computer is shut down or in sleep at the designated times, the maintenance does not occur. In that case, you may want or need to run these manually."

Read more: Mac OS X: How to force background maintenance tasks

1.3 Updating Mac OS X

You don't have to be the first one to install and run a Mac OS X update that has just been released. But in general it is good to keep your system up to date. At least when you want to keep your applications and drivers up to date. If you are unsure if a specific Mac OS X or QuickTime update is recommendable simply do a search in our user forums. New OS updates are discussed on www.cubase.net almost immediately after the release and you can assume that eventual problems will be reported very soon by less prudent resp. bolder users.

1.4 Optimizing Hard Disks

Before you think about optimizing your hard drive (because someone told you this is a very important thing to do) please read this Apple article:

About disk optimization with Mac OS X

2. Possible Causes of Unusually High CPU Load

The following information might be of help if the VST Performance Meter in one of our applications is showing an unusually high load or even drop-outs and peaks are visible and audible.

2.1 Latency/Buffer Setting

The "ASIO" part of the VST Performance Window (Devices menu) indicates how much resources are left to calculate the audio data and forward it to the audio driver in time. If the latency is very low (which is corresponding to a very small buffer size) time might be too short for proper signal processing. Depending on the system, the audio interface and the running project, it might make sense to increase the latency/buffer setting. Please refer to the manual of the corresponding audio interface for details.

Updating the audio driver might also improve the overall system performance and allow using latencies which weren't usable before. Generally, internal audio cards using the PCI or PCIe bus are able to provide lower latencies than external USB or Firewire based audio interfaces.

2.2 Processor Perfomance Setting

On some Macs it is possible to adjust the processor's performance in order to save battery power. Open the Energy Saver panel (Apple menu > System Preferences...) in order to make sure that your Mac is calculating at full throttle... If available on your system, you'll find the corresponding settings under Options/Optimization.

Also note that MacBooks and MacBooks Pro do reduce processor speed if the battery is not inserted in order to prevent a an overload of the A/C adaptor.

2.3 Multi/Multicore Processors

Multiple cores and/or processors need system resources to synchronize the cores. This can also lead to peaks, drop-outs and a generally higher basic load. For details, please refer to this article.

2.4 Hyper-Threading

Since Mac Pros are fitted with Intel's i7 (Nehalem) processors Hyper-Threading is a subject, that has to be considered in the Mac world, too. Detailed information can be found here.

2.5 VST Bridge

The VST Bridge enables old PowerPC (G4/G5 processors) based plug-ins to run on Intel-based Macs. Please note that certain "VST bridged" plug-ins create high processor loads and can cause performance issues. In general, it is recommended to use current plug-in versions that run natively on Intel-based Macs, if available. Check the plug-in manufacturer's site for update if you experience performance troubles with a PowerPC plug-in. For further details, please refer to this article.

2.6 Apple Airport

Apple Airport (WLAN) can cause performance issues when running challenging realtime applications. Particularly when working on large projects with a high basic load, disabling Airport might tip the scales.

One big advantage of Steinberg applications is that most of them are cross-platform and can be used on either Mac OS X or Windows XP/Vista. In addition, the file exchange between different systems can easily be handled using external hard drives, USB sticks and the likes nowadays. There is one thing to keep in mind though: the file system. Not every file system is compatible with all operating systems. 

HFS+ (Hierarchical File System)

• Preferred Mac OS X file system
• Incompatible with Windows operating systems

NTFS (New Technology File System)

• Preferred Windows XP and Windows Vista file system
• Mac OS X can only read NTFS partitions. Writing is not possible!

FAT32 (File Allocation Table)

• Older Microsoft file system
• Both Mac OS X and Windows operating systems can read from and write to FAT32 formatted drives.

Keeping the compatibility in mind, FAT32 should be the preferred file system if you have to constantly exchange files between both "worlds". However, current MS operating systems limit the maximum available partition size to 32 GB. Larger partitions can only be formatted using NTFS.
In order to circumvent this limitation one can use several applications by 3rd party developers. Two examples are:

• Disk Director from Acronis (commercial)
• GParted (free, ISO image for creating a bootable CD)

Another option would be Macdrive which enables Windows XP and Vista to access HFS formatted drives or partitions.

Using the above mentioned applications is at your own risk! Steinberg Media Technologies cannot take any responsibility for data loss or damaged data carriers.

Problem:
The following problems can occur when using the ASIO driver of the Creative Labs Soundblaster Audigy Hardware if it is not used with 48 kHz samplerate:

• Audio and MIDI do not run synchronized
• MIDI events are recorded with an offset
• Audioloops are not correctly time-strechted to the song tempo
• Playback has wrong pitch (sounds detuned)

These problems can occur in Sequel specifically because Sequel runs with 44.1 kHz only! In Cubase the samplerate can be set in the project settings dialogue.

Solution:
If you work with 48 kHz samplerate, all mentioned problems usually do not occur. In Sequel you should use the DirectX Full Duplex driver instead of the ASIO driver, which allows proper work as well, though the latency of this driver with 46 ms is quite high. Sequel 2 introduced the "Generic Low Latency ASIO Driver" which can also be used. Another solution is to replace the hardware with audio hardware offering dedicated ASIO 2.0 drivers without samplerate limitations.

The installation of Sequel requires a few gigabytes of free space on the harddisk. The most space consuming part are the Soundframe content files of Sequel, these files contain all the audio loops for example. If you have the need to move these Soundframe content files to a new location (another harddisk or partition) after the installation of Sequel, you can do this following these steps:

Mac OS X

The installer of Sequel uses a default location to store the content files, which is on your system harddisk in "\Library\Application Support\Steinberg\SoundFrame". This folder contains 13 Soundframe files with a total size of ~5 GB. To move these files and to make sure that Sequel can find them in the new location, please do this:  

1. Create a new folder at the location, where you want the Soundframe content files to be placed, e.g. on another harddisk or partition, name the folder e.g. "Sequel Soundframe".
2. Now copy the 13 Soundframe content files to the new folder.
3. After that make sure to delete the files from the origin location.
4. Now here is the trick: To make Sequel aware of the new location for the content you have to create Alias files (shortcuts) from each Soundframe content file to put these aliases into the folder "\Library\Application Support\Steinberg\SoundFrame".
5. To do this select all Soundframe content files from the new location, then open the right-click, respectively the context menu in the Finder and select "Create Alias".
6. Now drag all Alias-files into the folder "\Library\Application Support\Steinberg\ SoundFrame".

It sounds more complicated than it is actually. What happens is that Sequel reads the Soundframe content always from the folder "\Library\Application Support\Steinberg\SoundFrame". By placing Alias-files there, the search for content is routed to the new location automatically and is read from the new location instead.

PC Windows

The installer of Sequel uses a default location to store the content files, which is on your system harddisk in "\Program Files\Common Files\Steinberg\Soundframe". This folder contains 13 Soundframe files with a total size of ~5 GB. To move these files and to make sure that Sequel can find them in the new location, please do this:  

1. Create a new folder at the location, where you want the Soundframe content files to be placed, e.g. on another harddisk or partition, name the folder e.g. "Sequel Soundframe".
2. Now copy the 13 Soundframe content files to the new folder.
3. After that make sure to delete the files from the origin location.
4. Now here is the trick: To make Sequel aware of the new location for the content you have to create shortcuts from each Soundframe content file to put these shortcuts into the folder "\Program Files\Common Files\Steinberg\Soundframe".
5. To do this select all Soundframe content files from the new location, then open the right-click, respectively the context menu in the Explorer and select "Create Shortcut".
6. Now drag all shortcut files into the folder "\Program Files\Common Files\Steinberg\ Soundframe".

It sounds more complicated than it is actually. What happens is that Sequel reads the Soundframe content always from the folder "\Library\Application Support\Steinberg\SoundFrame". By placing Alias-files there, the search for content is routed to the new location automatically and is read from the new location instead.

Additional advice...
When you start Sequel after moving the Soundframe content files, it can happen that Sequel presents a message asking you to locate the content files manually. You can ignore this message by clicking on "Ignore"! Sequel will continue to load and finds the content anyway. You can verify this by looking up the MediaBay if all loops are displayed as usual.

After you had registered Sequel to your user account at MySteinberg, you have received an email with an activation code for 500 additional Bonus Loops for Sequel (Soundframe Pack 01). The loops have already been installed with Sequel and all you need to do is to start the eLicenser Control Center/License Control Center and use the "Enter Activation Code" (eLCC)/"Download License" (LCC) for downloading the Bonus Loops license by entering the activation code from the email you have received. 

After that you may ask yourself how to identify the new loops in Sequels MediaBay. In the MediaBay just click on the field "All Content", then select "Bonus Loops". Now you can just browse through the Bonus Loops for easy preview.

Here you can select what to see in the MediaBay...

While working with a project, a message might appear informing you about a sample rate change although nothing obvious has been changed. Usually, the sample rate only changes whenever the driver of the audio interface receives additional digital signals containing a different sample rate.
If e.g. an external component is connected to the audio interface via ADAT or Wordclock, the sample rate changes - provided that the audio interface is not the clock master and the sample rate does not match the project's sample rate. As a solution, you might be able to set the audio interface to a fixed sample rate or to build a setup with the audio interface being the digital clock master.

If you work with video files in your project, the imported video could be the reason for sample rate changes as well. Once the video includes an audio file (often in 48 kHz), it may happen that this audio portion switches the sample rate. Here, we can only recommend to seperate the audio material from the video file (e.g. using Virtual Dub from www.virtualdub.org) and to import the video without the audio first of all.

A third Windows only option is that audio in the sequencer and in Windows are both routed through the same inputs and outputs of the audio interface. Whenever Windows plays back a sound in a different sample rate, it can happen that again the sample rate changes. More details on this one can be found here.

This article answers frequently asked questions about the "Soft-eLicenser" and related topics.

1. What is a "Soft-eLicenser"?
A Soft-eLicenser (in short: SeL) is a virtual form of the USB-eLicenser (Steinberg Key). A file on the hard disk is created and is used as a container to store licenses instead of using the USB device. This container file has a number just like a normal USB-eLicenser (2 x 10 digits). The number is generated by a combination of hardware components of the system and is bound to the system where it was generated by installing the eLicenser Control Center. Certain changes to the core hardware changes the number of the SeL and renders it invalid! A reactivation of the licenses is needed then (described below).
It is recommended to only use the eLicenser Control Center and not the older Syncrosoft License Control Center so be sure to have the latest version of the eLCC installed.

2. Which products are using the SeL for storing licenses (as off August 2011)?

• Cubase AI 5, Cubase AI 4
• Cubase LE 4, Cubase LE 5
• Cubase Elements 6
• MP3 Encoder
• Sequel 1, Sequel 2 
• Sequel LE 2
• Sequel Content Sets
• VST Sound Instrument Sets
• VST Sound Loop Sets
• WaveLab Essential 6
• WaveLab Elements 7
• WaveLab LE 6, WaveLab LE 7

3. Is it possible to transfer licenses from the SeL to a USB-eLicenser?
Yes, this is possible since version 5.4.8.0 of the License Control Center (LCC) and with all versions of its successor eLicenser Control Center. An internet connection is required for the transfer and activation of licenses. A license transfer from USB-eLicenser to SeL is not possible.

4. What do I have to do if my SeL does not contain licenses anymore?
If your SeL is empty (or deleted) due to a hard disk crash, substantial changes to the computer hardware configuration (respectively you have new computer) or a new installation of an operating system and does not contain licenses anymore, please start a Reactivation procedure at the Mysteinberg website. You need the new SeL number of your system. Only for Sequel, you'll also need either the "Essential Product License Information" card, which was included with your product or the already registered old activation code.

5. What is the detailed procedure for a reactivation?
This is a general step-by-step guide:

• You need a user account at the MySteinberg website, please log in with your account data
• On the left side click at "Activation & Reactivation"
• Click on the name of the product which you want to reactivate.
• Click on "Reactivation"
• Follow the instructions there, enter you new SeL number.
• For Sequel also enter the activation code from the card "Essential Product License Information" or the last used activation code you can find in MySteinberg.
• Now click on "Request new Activation Code"
• Repeat the procedure for each additional product

In "Show registered products" -> "Activation codes received online" those requested activation codes are listed. You will also receive an email with an activation code for each reactivation you have started. Use the eLicenser Control Center and use the “Enter Activation Code” button to download the product license onto your SeL.

6. Is it possible to activate a product on a computer without Internet connection?
A computer which is not connected to the internet can not be used to activate a SeL-protected product. Unlike the USB-eLicenser whose licenses can be managed independently from the computer where the software products are installed onto, it is not possible to create a SeL with licenses to use it on another computer afterwards. This is due to the fact that an SeL is bound to the hardware where it was created on.

7. Is it possible to utilize a SeL-protected product on several computers?
No, this is not possible! The respective product can only be active on one computer at a time. If you need additional installations in parallel on other computers you need to purchase the required amount of program licenses for that.

8. I have a PowerPC-based Apple computer. My SeL is declared as invalid, how can I resolve that?
This problem is solved by installing the latest version of the eLicenser Control Center.

9. How can I sell a SeL-protected product?
Please have a look at our Resale Wizard!

When you buy Sequel, you automatically purchase the right to use the contained sounds and loops, so you can use them without limit in any production.

To play Sequel's hundreds of instruments, you need a MIDI keyboard as well as an audio card or interface with a MIDI connection. Your music store will have a huge range of MIDI keyboards, all the way from compact two-octave models to huge 88-key keyboards with weighted keys. The MIDI keyboard is connected to a MIDI socket on the audio interface; most audio interfaces have a MIDI socket to connect to keyboards. Using a standard MIDI cable, connect the MIDI Out on the keyboard with the MIDI In on the audio interface. Now you're ready to play all the on-board instruments in Sequel!

Many newer MIDI keyboards also have a USB connector. This is even easier to set up, as the keyboard is simply plugged into a free USB port on your computer, so you don't even have to use a MIDI cable.

Since Sequel 2 it is possible to play the instruments with the computer keyboard. More information can be found here

Sequel comes ready with 4500 loops, and when you register [link] Sequel, you'll receive a code to unlock an extra 500 loops! If that's not enough, you can use Content Sets from us or other companies.

Sequel 1

If you don't have a MIDI keyboard connected to your computer, can you still enter the notes using your mouse. First, create an Instrument Track. In the Pilot Zone, click on "Add New Track" and choose a sound from "Instrument" list. Then just create a new Part in the Arrange Zone on this new track. Double click again on the part to open Key Editor in the multizone area. Hold the Alt key pressed to draw the notes. You can see the pitch of the note on the piano roll on the left hand-side.

Sequel 2

With Sequel 2 you have the possibility to use a virtual keyboard.The virtual keyboard allows you to play and record MIDI notes by using your computer keyboard or mouse. This is useful if you have no external MIDI instruments at hand and you do not want to draw in notes with the pencil tool.

You can also use the virtual keyboard for previewing instrument presets on the Mediabay page.

Note that the maximum number of notes that can be played at one time varies between the different operating systems and hardware configurations.

Please also visit our Sequel homepage where you can find a video where the virtual keyboard is being shown and explained. The direct link to it www.sequel-music.net

When you activate Sequel, a special unique code is generated for your system and stored in the so called Soft-eLicenser. The Soft-eLicenser is a virtual License container and cannot be transfered to another computer. That's why your Sequel installation can only be used on one computer.

But alternatively you can transfer your Sequel license to a USB-eLicenser. In this way you can use Sequel on any system that is equipped with a Sequel installation and an attached USB-eLicenser.

When you activate Sequel, you must have an active internet connection available on your system. This is because your personal Sequel license is downloaded from our server after you've entered your Activation Code. The internet connection is only needed this one time to activate your software. After that of course, you can use it without internet access whenever you want.

There is no way to activate the software offline. However you can do the activation on any other internet capable pc if you get an USB-eLicenser.
Once the license is stored on the USB-eLicenser you can run the software on every computer where the dongle is plugged in.

The Activation Code in the Sequel box can only be used once. If you have to reinstall your operating system from scratch, for example after a hard drive crash or if you buy a completely new computer, you’ll need a new Activation Code for Sequel. Without it, you won’t be able to use Sequel on the new system. As a registered Sequel customer, you can order a new Code at MySteinberg. If you forgot to register your copy of Sequel before installing it on the new system, please get in touch with your Steinberg Support.
 
We have additional details in this soft-eLicenser FAQ!

Registering Sequel brings you a lot of advantages like technical support, update downloads and a new Activation Code should you need it. And as a Thank You from us for registering, you also get an additional 500 Sequel loops - absolutely free! Click here for a full guide on how to register.

If you hit a note on your keyboard and get a noticeable delay before the sound is heard, you're hearing the so-called latency of your audio system. Latency is the time between the input and output of a signal.

Sequel 1:
For a low latency, you need a sound card or audio interface for your computer that has ASIO-compatible drivers. You can use Sequel with the Windows standard DirectX audio drivers, but if you're playing the instruments in Sequel with a keyboard, you should use ASIO drivers. Check if an ASIO driver is available for your audio hardware and if it's selected in Sequel. If your soundcard or audio chip does not have an ASIO driver, you should select the "ASIO DirectX Full Duplex" driver that is installed with Sequel. As an alternative you could also use a "generic" ASIO driver. You can download this "ASIO4all" driver from www.asio4all.com.

Sequel 2:
With Windows Vista Sequel 2 runs at very low latencies even without external ASIO hardware using the Vista Core Audio driver.

Additional information:
With Macintosh computers, the integrated Core Audio driver normally works at low latency. If you use an external audio hardware, you should set Sequel to use the driver supplied with the hardware.

For more information on selecting drivers, please see the Sequel manual.

To record vocals or acoustic instruments, you need to connect a microphone to your computer. There are different ways to do this. Many computers have a microphone connection built-in which includes a so-called pre-amp. The preamp is needed to amplify the microphone's signal. For better recording quality, you can use an additional sound card or external audio interface, most of which have a special microphone input.

If you already have an audio interface but it doesn't have an extra microphone input, then you'll need either an additional microphone preamp or a mixer with a microphone input to hook up to your audio interface. Your music instrument store can help you find the right device.

With electric guitar and electric bass, you can record directly into Sequel without needing a microphone. Many audio interfaces on the market today have a special instrument input (also called "high ohm" or "hi-z" input) that are specially built for recording electric guitar or bass directly. If you have an audio interface without a special instrument input, you can add a separate guitar preamp to your system. For help in finding the right interface, ask at your music instruments store.

Electronic instruments like keyboards and synthesizers can be hooked up directly to the stereo input in your computer or audio interface. A special hardware or input is not needed to record them in Sequel.

No, Sequel's heart belongs to music. Video import is not implemented.

No, Sequel is not compatible to ReWire programs.

If the crackling occurs simultaneously to audio signal peaks the output of your audio card is probably overdriven. In this case the problem can be solved by decreasing the level of a specific channel or the Master Channel whch controls the overall volume.
An overload is indicated by a red sign in the Master Channel. 

Another possible reason for crackling could be the audio buffer of your soundcard. If the buffer is too small your system will be overcharged and cause distorted and stuttering playback. You can change the buffer size on Sequel's Program Settings page (lowest icon on the Multi Zone):

Click on the 'Setup...' button in the 'Audio Connection' line under 'Audio Settings'.

If you are using a PC the control panel of your audio card opens. Here you can set the buffer size.

On a Mac you'll see a small pop-up window which allows to select the buffer size in a pull-down menu.

Please consider that the buffer size affects the so called latency. While larger buffers ensure that playback will occur without glitches, the latency will be higher which might be annoying when playing software instruments.

Please refer to Sequel's manual for more information on latency and audio buffers. 

If you experience audio drop outs or crackles when using graphical elements of the Sequel user interface on PC Windows system, then set the Sequel window to full screen using the "maximize" button at the right upper corner of the Sequel user interface.

Currently, Sequel cannot load or create multichannel (surround) audio files. Only mono and stereo files are supported.

The import of Sequel projects into Cubase and the access to the Sequel Loop library is available for Cubase Studio 4 and Cubase 4 Users with version 4.1 or higher. It is possible to access the VST Sound Library with Cubase Essential 4, the import of Sequel projects into Cubase Essential 4 is not possible.
The import of Cubase projects into Sequel is neither possible nor planned.

The wish to convert an instrument track to an audio track can come if you e.g. want to save CPU resources. In most cases the playback of an audio track is much less exhausting unlike the generation of sound on an instrument track in realtime.

You can do the conversion with these steps:

• Open the project where you want to convert instrument tracks to audio.
• This time you do not want to export the whole project, instead set the desired instrument track to "Solo", so that you can hear it on its own. Only this single track shall be exported.
• Now start the function "Export Project as Audio File..." and select the export location, name, file format and export bits. Please remember the location where you save the file for later steps, when it comes to integrating the file into your project again (or sorting it into the Media Bay).
• Now start the export!

After the export has been finished you want to import the just created audio file back into your project. This is done by "drag and drop".

• Use the Finder (Mac OS X) respectively the Explorer (PC Windows) to navigate into the folder where you exported audio file is stored.
• Select the file and drag it into the Sequel project window, then drop it.
• Sequel automatically creates a new audio track and places the file there.
• Make sure the file is correctly placed within the context of the rest of the project.

If all went well you can now delete the instrument track to release CPU resources. All further editing possibilities for audio material is now useable for you. If you have several instrument tracks to convert to individual audio tracks, repeat the procedure as many times as needed.

Tip: Store you own audio material in the Media Bay

If you want to use your self created audio material in other projects the best way is to store it into the Media Bay before. Drag and drop the audio file into the Media Bay (page must be open) instead of dragging it into the project area. You can now tag it with attributes in order to allow easy sorting and finding.

Sequel always tries to playback audio according to the tempo set in the project, indepedent of the origin tempo of the used audio loop. If the origin tempo (which is stored inside the audio loop) is different to the project tempo then the audio material is automatically time-stretched in realtime.  

There are different modes for time-stretching available, allowing you to optimize the quality of the time-stretching result to suit the audio material as best as possible. When an audio loop is dragged into the project, a stretch mode is already selected usually.  

Now it can happen that the pre-selected stretch mode is not the best one. A drum loop often sounds better when the mode "Drums" is selected. However, if the loop contains tonal elements then the "Mix" mode can be a better choice. It is worthwhile to experiment with the different stretch modes!

The effect of the different modes are more extreme, the more the origin tempo of an audio loop is different from the tempo used in the project. To check for the origin tempo have a look at the column "Tempo" at the Media Bay page.

Problem:
Initially, it is impossible to add files from the mediabay or record new material to the installed Sequel demo and tutorial. The audio tracks cannot be record enabled and when trying to drag and drop files into the project nothing happens.

Cause:
The default settings do not allow to modify the existing projects. Therefore, those projects are write protected and Sequel loads them using the path "demos and tutorials".

Solution:
All projects you want to add new media to need to be copied into another folder. A new project location has to be defined in the program settings page and the Sequel demo and tutorial projects of your choice have to be moved from the Sequel application folder into that new folder. You can of course use an already defined folder as well.
If you reload the projects from that new folder, you can record enable the tracks (please make sure that a defined input from your audio card is selected on those tracks!) and you can add new material from the media bay or from other locations by dragging and dropping them into the project.

If you have created a new project, the above procedure is not relevant.

Basically, Sequel always exports a project from the first to the last part. If you only want to have excerpts of your project exported, you can either mute parts or whole tracks. All muted tracks/parts won't be included into your mixdown.

To prepare an audio recording in Sequel the following points should be checked:

• Is the correct driver for the audio connection at the "Program Settings Page" in Sequel selected?
• Which audio hardware is used, e.g. the integrated audio hardware of your computer or do you work with additionally purchased audio hardware?
• Have you checked for proper audio cable connections?
• Is your instrument to be recorded creating enough level?
• Do you have selected the used audio input for the audio track in Sequel (the input selection field is visible at medium track height or higher)? 

The following steps are describing the setup when integrated audio hardware of your computer is used:

Mac OS X

Here is the procedure to change the preferred audio input:

• Go to the Apple menu and select "System Preferences..."
• There, start the control panel "Sound"
• Select the tab "Input" and select the desired input source, e.g. Line-In input.
• You can also adjust the input level here, for the case your input signal is too weak (or too heavy).

PC Windows

If you work with the ASIO DirectX Full Duplex driver in Sequel then make the following settings in Windows:

• Go to the Windows Start menu > Control Panels > Sounds and Audio Devices > Tab: Volume and click on "Advanced..." The Volume Control appears. Alternatively you can open this windows by double clicking on the loudspeaker symbol at the right bottom of the task bar.
• In the Volume Control windows go to menu "Options" and select "Properties"
• There, select "Recording" for "Adjust volume for", then click "OK".
• The "Recording Control" windows appears. There, use the "Select" checkmark to select your desired input source, e.g. Line-In.
• You can also adjust the input level here, for the case your input signal is too weak (or too heavy).

Additional information:

• If you want high quality recordings and being able to work with low latency it is recommended to get dedicated audio hardware from your music retail store.
• These devices are usually delivered with dedicated drivers and control panel software where you can setup the signal flow and input routing. The settings made in Windows / Mac OS X are not relevant anymore.
• If you have a problem with feedback please consult this article here.
• For additional information and general setup scenarios please also consult the operation manual of Sequel!

The import of MP3 files can easily be done by using drag and drop from a standard file browser (e.g. Apple Finder, Windows Explorer, Total Commander) or directly from the desktop into the Sequel project. As soon as you drag an audio or MIDI file into the Sequel project window, a small "+" symbol and the position within the project appears next to the mouse pointer. When the mouse button is released, the dragged file will be placed into the project. If you use MP3 files, it might take some time for Sequel to decode the file.

Sequel 1
The export of MP3 files from Sequel is unfortunately not possible. If you need to have a smaller, encoded file you'll have to use the "Export to iTunes" option (has to be installed separately on a Windows PC system). The exported file will be an AAC file.
Alternatively, you can of course export your mix as a wave/aiff file and let any third party application encode it into MP3.

Sequel 2
The export of MP3 files directly from Sequel 2 is now possible. This function is limited to 20 trail encodings or a period of 30 trail days from the installation data (whichever comes first). After this period, the function will be disabled until you purchase the MP3 encoder for Sequel 2. Furthermore it is also possible to use the free "export to iTunes" option of Sequel. Please notice that you have to install iTunes for this.

Can I use additional VST instruments in Sequel?
No, you can only use the integrated VST instruments.

In Sequel you normally work along a musical grid, where the resolution is determined from the zoom level. There are situations where it can make sense to be free of any grid snapping to move or align parts. You can turn the grid snap off by using the button located at the right side of the time line (see the marking in the screenshot). If the button is green the grid is active. If it is red the grid snap is off and you can freely move parts or size them. Further details are described in the Sequel operation manual.

Having completed your Sequel project, you can export all tracks including the effects and automation into a folder of your choice by selecting the file menu and "Export project as audio file". Please keep in mind to choose "16 Bit" and "Wave File" (PC) or "AIFF File" (Mac) in the export dialog first of all as this is the standard format used for audio CDs and it should be compatible with all applications able to write CDs.
The newly created audio files can now be loaded into any application of your choice for burning a CD.

A second option would be to use "Export project to iTunes" because iTunes itself is able to burn CDs as well. An installed and current version of iTunes (7.1 or higher) is of course required for this to work.

For more information on exporting projects and burning CDs, please have a closer look at the Sequel export tutorial and the documentation of the application you intend to use for creating an audio CD.

If you hear feedback from your loudspeakers after you have record-enabled an audio track in Sequel, please keep the following in mind:

• This problem often occurs with laptop computers equipped with an integrated microphone in the housing.
• If the microphone input is selected as the preferred record source a click on the record-enable button in Sequel opens the microphone input.
• All incoming signals are now routed to the audio track in order to get recorded.
• At the same time you hear the input signal with your loudspeakers. This is necessary so that you can hear yourself while recording something.
• But this also means that a feedback can be easily created, which is a quite disturbing situation.

A record-enabled audio track in Sequel

The easiest way to solve this problem is by using headphones. It is important that you monitor with headphones and not with your loudspeakers. If the loudspeakers are emitting any audio signal it is likely that you get a feedback again.

If you do not want to record with an integrated microphone at all, the best solution is to make sure that it is no longer defined as a preferred record source. How to change this depends on your used operating system and audio hardware drivers.

Mac OS X

Here is the procedure to change the preferred audio input:

• Go to the Apple menu and select "System Preferences..."
• There, start the control panel "Sound"
• Select the tab "Input" and change the selection from the integrated microphone to something else, e.g. Line-In input.

PC Windows

If you work with the ASIO DirectX Full Duplex driver in Sequel then make the following settings in Windows:

• Go to the Windows Start menu > Control Panels > Sounds and Audio Devices > Tab: Volume and click on "Advanced..." The Volume Control appears. Alternatively you can open this windows by double clicking on the loudspeaker symbol at the right bottom of the task bar.
• In the Volume Control windows go to menu "Options" and select "Properties"
• There, select "Recording" for "Adjust volume for", then click "OK".
• The "Recording Control" windows appears. There, remove the "Select" checkmark for the intergrated microphone and select e.g. Line-In as the new audio input source.

To create an Arrange Part on the Arrange Track in Sequel press and hold [ALT]/[Option] on your computer keyboard. The cursor will turn into a pencil. Click and drag an Arranger Part of the desired length. You can find more details and a tutorials about the Arranger Track and its Parts in the operation manual of Sequel.

Cubase (Studio/Essential/AI/LE) 4 and Nuendo introduce the Windows installer (.msi) format which offers more possibilities like repairing, modifying and adding certain components to an already existing installation. Also, administrators have several options available how to install applications or enabling users with restricted rights to install the application themselves. Here are three of the most important command lines to be entered in the Windows command shell:

If the admin himself wants to install e.g. Cubase 4 for all users, he has to enter

• msiexec /i cubase4.msi ALLUSERS=1

If he wants to allow the currently logged in user to install the application on his own with restricted user rights he has to use

• msiexec /ju cubase4.msi

If he wants to open the installation for all restricted user accounts he has to use

• msiexec /jm cubase4.msi

In the latter two examples, the user can now install the application on his own.

All command entries require that the admin has changed the directory path to the path the msi actually resides in. If the DVD-ROM containing the Cubase4.msi is located in the DVD drive F:\ please proceed as follows:

• Open the command shell (Start -> Run -> Enter "cmd" and click on "OK"). The Windows command shell window appears.
• Change the directory path to the DVD drive by typing "cd /d F:\Cubase 4 for Windows"
• Press "Enter".

You are now in the correct directory and you can proceed by using one of the command lines listed above.

As a rule, Steinberg software runs on all standard computers, provided that these satisfy the system requirements printed on the given product's package. Happily, you'll see that today's market offers a computer to suit every application and budget. Affordable computers for smaller projects are readily available, as are highly specialized multiprocessor systems for professional applications in the music and movie industries. You'll even find powerful systems for mobile use so that nothing stands in the way of deploying Steinberg software on stage and producing music on the go, away from your studio.
 
Depending on what you wish to accomplish with the software, your computing demands may entail special requirements. These requirements hinge upon the type of project you intend to work on. Several performance-related factors figure prominently, such as sample rate and bit depth, as well as the number of tracks, plug-ins, instrument voices and effects used in a project. So, if you need a computer to realize elaborate projects, ask yourself this question:
 
"Which computer is right for my application?"

Read more...

eLicenser Control Center

The following files have to be deleted manually in order to completely remove the eLicenser Control Center (eLCC):

• /Applications/eLicenser Control Center
• /Library/Application Support/eLicenser
• /Library/Receipts/SyncrosoftLicenseControl.pkg
• /Library/Receipts/eLicenserControl.pkg
• /Library/Receipts/LCC.pkg
• /Library/Receipts/NOS.pkg 
• /Library/Receipts/POS.pkg
• Beginning with Mac OS X 10.6 also:
  in /var/db/receipts/ all files that start with "com.syncrosoft" and "com.eLicenser".

Please uninstall eLicenser Control Center via Start > Control Panel > Software (Windows XP) or Programs and Features (Vista, Windows 7).

Important: Please close all applications before starting the uninstallation! 

Afterwards, please verify whether any of these files are still on the system and delete them manually:

In order to be able to see all files and folders, Windows Explorer needs to be set up correctly: Menu Tools (in Windows Vista you have to press "Alt" to see the menus) > Folder Options > View > Hidden files and folders > Show hidden files and folders

• XP: C:\Documents and Settings\All Users\Application Data\eLicenser
  Vista: C:\ProgramData\eLicenser
  
• C:\Windows\system32\:
  All "SynsoNos", "Synsopos" and "Synsoacc" files
• Only on 64-bit installations:
  C:\WINDOWS\SysWOW64\SYNSOACC.dll
  C:\WINDOWS\SysWOW64\SYNSOACC-Hilfe.chm
  C:\WINDOWS\SysWOW64\SYNSOACC-Help.chm
  C:\WINDOWS\SysWOW64\SYNSOACC-Aide.chm
  C:\WINDOWS\SysWOW64\SYNSOPOS.exe
  
• Driver 32-bit Windows:
  C:\WINDOWS\system32\drivers\SynasUSB.sys
  C:\WINDOWS\inf\SynasUSB.inf
  Driver 64-bit Windows:
  C:\WINDOWS\system32\drivers\SynUSB64.sys
  C:\WINDOWS\inf\SynUSB64.inf 

Syncrosoft License Control Center (outdated) 

The following files have to be deleted manually in order to completely remove the old License Control Center (LCC):

• /Applications/License Control Center
• /Library/Syncrosoft
• /Library/Application Support/Syncrosoft
• /Library/Logs/Syncrosoft/
• /Users/[current user]/Library/Logs

After uninstalling the Syncrosoft License Control Center using the standard Control Panel > Software (XP) or Programs and Features (Vista) function, check whether the following files are still there and remove them manually.
In order to see all files and folders, please check whether Windows Explorer is configured correctly: Menu Tools (in Vista you have to press "Alt" to see the menus) > Folder Options > View > Hidden files and folders > Show hidden files and folders

• XP: C:\Documents and Settings\All Users\Application Data\Syncrosoft
  Vista: C:\ProgramData\Syncrosoft
  
• C:\Windows\system32\:
  All "SynsoNos", "Synsopos" and "Synsoacc"files
• Only on 64-bit installations:
  C:\WINDOWS\SysWOW64\SYNSOACC.dll
  C:\WINDOWS\SysWOW64\SYNSOACC-Hilfe.chm
  C:\WINDOWS\SysWOW64\SYNSOACC-Help.chm
  C:\WINDOWS\SysWOW64\SYNSOACC-Aide.chm
  C:\WINDOWS\SysWOW64\SYNSOPOS.exe
  
• Driver 32-bit Windows:
  C:\WINDOWS\system32\drivers\SynasUSB.sys
  C:\WINDOWS\inf\SynasUSB.inf
  Driver 64-bit Windows:
  C:\WINDOWS\system32\drivers\SynUSB64.sys
  C:\WINDOWS\inf\SynUSB64.inf 

Please note: Do not delete log files and folders unless it is absolutely necessary or recommended by Steinberg support! Interrupted license downloads and the list of already used activation key codes will be lost!

Boot Camp allows you to install Windows XP, Vista or Windows 7 on Intel based Macintosh systems alongside Mac OS X and use it without any performance losings.
However, we cannot take any responsibility for issues you might run into as we do not officially test this combination.

Additional information:
Apple Boot Camp
Overview on Universal Binary compatible products

You possibly have seen such messages while working with Cubase or Nuendo.

On PC Windows systems it looks like this:

On Mac OS X such a message appears this way:

First of all: Don´t panic! The message tries to tell you that an error occured in the application while working with it and that the application is not able to continue to function properly any longer.

1. Close the message by clicking on "Cancel"
2. Go to the menu >File >Save As... immediately and save your project using a new file name (do not overwrite already existing projects!)
3. Exit the application

On Mac OS X the application exits itself and leaves the message as displayed above only.

The next thing is to start the application again and to load the last version of your project. Normally you should be able to continue your work without further incidents.
Reasons for Error and Exception messages
Naturally these messages are not a freak of nature. Here are some reasons why they can occur:

• You have found an application error, a bug so to speak. For example by doing a specific action or by triggering a row of program functions
• An external component has crashed, this could be FX-plugins, VST instruments, drivers of the system or another 3rd party component which was in use by the application
• Your system suffers from a hardware problem such like problems with power supply or fluctuation, improper working or defective memory modules, problems due to high CPU load resulting in possibe overheating of the CPU, etc.

In order to narrow down the problem the application saves a log-file with information logging various parameters of the system at the time of the crash.  If you get error messages repeatedly you should make sure that at least no hardware problem is involved. For more details the log-file needs to be sent to Steinberg for further analysis. To do that these steps and details are important:

• PC Windows: The log-file is saved in the same folder where the application has been installed into, e.g. "c:\program files\steinberg\cubase sx 3\cubasesx3.log". The file appears as text file in the Windows Explorer.
• Mac OS X: Here, the log-file is saved into a separate folder. You can find it in your user-folder in >Library >Logs >CrashReporter. For e.g. Cubase SX 3 the file is named "Cubase SX 3.crash.log".
• Please send the file as attachment to an email to the responsible support crew. From there log-files will be forwarded to the development department. Please do not copy the content of the log-file into an email, instead always attach the file as a whole.
• Please add some details of what you did inside the application when the error occured, e.g. a specific row of used functions or the last action before the crash happend. Additionally it can be important to list used plugins and details to your system configuration.
• It can happen that we need additional information after you have sent a log file in order to properly reproduce the problem.

When uninstalling Cubase or Nuendo, preferences won´t be removed automatically. This is because the preferences contain your personal settings such like key commands, device maps, presets for VST plugins etc. The uninstaller only removes files which have been installed by it.

If you want to remove preferences please do this:

Mac OS X

1. Exit Cubase resp. Nuendo. 
2. Open the Finder and go to the folder: Users/*Your Username*/Library/Preferences/*Your Cubase resp. Nuendo version*
3. Create a new empty folder on your desktop
4. Select all files and folders from the preferences folder and move them into the empty folder on the desktop.
   The preferences folder needs to be empty after that.

Mac OS X 10.7 (Lion)

*The Library folder for  the main user account is not visible anymore on Lion, that means that users will not find it and will not be able to delete the preferences.
To access that folder you need to go to the menu "Go", then hold down the ALT key on your computer keyboard and click on the appearing "Library" entry.

Then you will be able to access the Library and delete the preferences.

Windows

1. Exit Cubase resp. Nuendo.
2. In Windows go to the Start menu > (All) Programs > *Your Cubase resp. Nuendo version*
3. There, start "Open *Cubase resp. Nuendo* Application Data Folder"
   
   A new Explorer window opens with all files and folders of the preferences for the host application. As an alternative you can browse to this location by yourself using this path:
   
   XP: c:\Documents & Settings\*Your Username*\Application Data\Steinberg\*Your Cubase resp. Nuendo version*
   Vista: c:\Users\*Your Username*\AppData\Roaming\Steinberg\*Your Cubase resp. Nuendo version*#
4. Select all files and folders from the preferences folder and move them into the empty folder on the desktop.
   The host application preferences folder needs to be empty after that.

Mac & Windows

Now, when you start Cubase resp. Nuendo again, The program will use the default settings and the preferences files (which you've just removed) will be created freshly. If you need specific settings of preferences again, take the copy of the files in question in the backup folder on the desktop and move them back to the host applications preferences folder.

For details which file of the preferences is responsible for specific settings please refer to the operation manual of the host application for details, chapter "Customizing", section "Where are the settings stored?".

If you are sure that all preferences can be deleted you do not need to create a backup copy. Instead just delete the files and folders.

A recording in Audio CD quality (stereo, 16 bit, 44.1 kHz) requires a data transfer rate of about 0.168 MB per second or circa 10 MB per minute:

This article lists the current status of compatibility and interchangeability of project files between different Cubase, Sequel and Nuendo versions.

_{(1) Nuendo 5 projects can be opened in Nuendo 4.3. If the SurroundPanner V5 is used the panning will not be compatible with Nuendo 4.3. Additionally Nuendo 5 uses Unicode, therefore special characters might not be displayed properly in Nuendo 4.3. If the Nuendo 5 project contains audio files with special characters, these files have to be assigned manually when opening the project in Nuendo 4.3.}

In this table you can look up which applications are able to open projects of another. The left column is your used application while the top most row determines from which version your project file comes from.

General notes

• Of course you can also exchange projects between Mac OS X and PC Windows systems. 
• Settings of functions or areas of the program which are not available in the used application, will be discarded.
• Loading projects of a bigger variant into a smaller one might lead to a different mix result. For instance, loading Cubase 6 projects into Cubase Artist 6 will cut off the additional insert plug-ins. Single Note Access edits will be ignored but the data is not lost. Additional audio and instrument tracks will be loaded but cannot be edited.
• Please keep in mind that we do not provide downward compatibility officially, e.g. loading a Nuendo 4 or Cubase 4 project into an older program version is at your own risk! The same applies to Sequel projects.
• Loading Cubase projects into Nuendo without the NEK installed is possible. Cubase specific data will be processed but can not be edited though. If its important for you to regularly exchange and edit Cubase projects in Nuendo we recommend to install the Nuendo Expansion Kit.
• Sequel projects can be loaded directly into Cubase (Studio) and Nuendo versions 4 and higher. Sequel, respectively its content, has to be installed on the used system. For Nuendo, we recommend to have the Nuendo Expansion Kit installed in order to hear the playback of Instrument Tracks contained within Sequel projects.
• As a last tip please save projects which have been created with an older version of the application with a new name instead of overwriting it. This way you keep the original file!

With the release of Cubase 4/Cubase Studio 4 in autumn 2006 Steinberg offered the first Universal Binary products to run on the Intel based Macintosh systems. Several other Steinberg applications followed soon. All applications that are not listed in the compatibility list at the bottom of this text do not run at all or at least not satisfactorily on Apples current Intel based Macintosh hardware. Although it is possible to run our PowerPC based applications using the Rosetta technology, one can expect a heavily reduced performance. Please note that we do not offer any support for the combination of Intel based Macintosh systems and our PowerPC compatible products!

Available Universal Binary compatible products (updated June 22nd, 2011)

• Nuendo 5
• Nuendo 4
• Cubase 6
• Cubase 5
• Cubase 4
• Cubase Artist 6
• Cubase Studio 5
• Cubase Studio 4
• Cubase Elements 6
• Cubase Essential 5
• Cubase Essential 4
• Cubase AI 4
• Cubase AI 5
• Cubase LE 4
• Cubase LE 5
• Sequel
• Sequel 2
• Steinberg MI|2 & MI|4
• HALion Sonic
• HALion 3
• HALion 4
• HALion Player (Retail und OEM)
• HALion Symphonic Orchestra
• HALion String Edition 2
• Houston
• Groove Agent 3
• MR816 (CS)X
• CC121
• CI1
• CI2
• CI2+
• The Grand 3

 1. Please examine your system and make sure that all device drivers of the system are up to date. This involves the drivers of the audio hardware as well as the chipset drivers and the display card drivers. Also Windows XP/Vista should be up to date (Service Packs and updates/hot fixes). You should avoid using dedicated mouse and keyboard drivers, instead use the drivers provided by Windows!

2. Systems with shared memory display setups are not advisable. They often can be found on mobile systems (laptops). It is advisable to throttle or deactivate hardware acceleration for the display card (Display Settings--> troubleshooting). Also check the control panel of your display card driver and deactivate any option that could be a strain to your system. 

3. The Windows option "Adjust for best performance": In the Control Panel -> System -> Advanced system settings -> Performance Settings, you can find the option „Adjust for best performance“. This option should be checked.

4. Audio interface related settings:

• Onboard Soundcards: If your mainboards provides an onboard soundcard it should be configured to be the standard playback device in the Windows Sound and Audio Settings. Thus, the Windows system sound will be played back by the onboard device without affecting the audio signal of your audio interface or soundcard. However, if playback issues occur it can also be advisable to deactivate the onboard device in the BIOS of your system. Onboard soundcards cannot be recommended for the usage with our products since they do not allow working with low latencies due to missing ASIO drivers. Furthermore, most onboard soundchips are equipped with substandard AD/DA converters and only offer low signal quality (high noise level, non-linear frequency response, bad electrostatic shield).
• Latency/Buffer Setting: If you experience audio drop-outs or crackles take a look at the "ASIO" part of the VST Performance Window (Devices menu). It indicates how much resources are left to calculate the audio data and forward it to the audio driver in time. If the latency is very low (which is corresponding to a very small buffer size) time might be too short for proper signal processing. Depending on the system, the audio interface and the running project, it might make sense to increase the latency/buffer setting. Please refer to the manual of the corresponding audio interface for details. Updating the audio driver might also improve the overall system performance and allow using latencies which weren't usable before. Generally, internal audio cards using the PCI or PCIe bus are able to provide lower latencies than external USB or Firewire based audio interfaces.

5. Processor scheduling: It might make sense to set the processor scheduling to "Background services":

• Go to Windows Start menu, select "Control Panels"
• There, start "System"
• Windows XP: select the tab "Advanced"
• Windows Vista: click on "Advanced system properties" to open "System Properties" and select the tab "Advanced"
• Click on "Settings" in the section "Performance"
• In the window "Performance Options" select the tab "Advanced"
• There you find the "Processor scheduling" options, set it to "Background services"

Especially Windows XP users should apply these settings.

6. Any energy saving options should be deactivated or set to "none". The system should be configured for continues operations. If this is not done, hard disks will throttle in speed or toggle off after a while and some processors will down clock and slow down. Because of this, our products could stop functioning correctly.

7. Programs that are running in background can cause issues while working with our products or even already during installation. These programs are mostly configured to automatically start when Windows boots up, e.g. virus scanners, security software, firewalls, printer and media software. It is advisable to deactivate these programs and slim out your auto start. You can mostly configure this through the settings of the program itself or you must manually deactivate them through typing "msconfig" (without the "") via Start -> Run. A freeware tool that could help you organizing your auto start would be “Startup Control Panel” which can be found on www.mlin.net.

8. Also, current PC systems feature speed stepping technologies (Intel: EIST, AMD: Cool ‘n’ Quiet) that automatically adjust the CPU clock depending on the overall system strain. If drop outs occur during playback, it might make sense to disable this feature in the BIOS settings of your motherboard and see whether this improves the performance.

9. Last but not least, please keep in mind that we do not recommend using Intel’s Hyper-Threading technology on multicore systems like the Intel i7 processor or older Extreme Edition and Xeon CPUs by Intel as Hyper-Threading can also have a negative side-effect on the performance. Again, disable it in the BIOS if you encounter any performance issues. For details on Hyper-Threading please have a look at this article.