Reload Frameset Home German Pages

Setup of the EWS64 in Cubase 5:
Getting into the details...

Contents:
  1. Introduction
  2. ASIO multimedia driver setup
  3. ASIO DirectX driver setup
  4. ASIO DirectX fullduplex driver setup
  5. Terratec EWS64 ASIO driver setup
  6. Cubase audiosystem settings
  7. Additional important settings in Cubase 5
  8. Cubase MME settings
  9. Additional information for EWS64 drivers
  10. Control Panel and FX Panel settings for Cubase
  11. How many MIDI-voices does the EWS64 play at the same time ?

1. Introduction

You have to make several configuration for running the EWS64 with Cubase 5 reliably. Otherwise you will run in several troubles.
Before you configure the Cubase settings you should complete first the following settings in the Windows control panel:
First reduce (in case of Windows 9x) the count of 'Virtual Channels' to a minimum (look at chapter 'Virtual Channels'). Next step is to optimize the 'Wave Play Buffer Latency' (look at chapter 'Wave Play Buffer Latency'). Set the Codec as prefered Play and Record device in the Control panel/Multimedia.
After these steps you can configure the cubase 5 settings.

Back to the top

2. ASIO multimedia driver setup

Cubase ASIO multimedia driver setup
 
You will find these settings in the 'Advanced options' in the included 'ASIO Multimedia Setup' of Cubase 5.
In these settings you have to determine the buffersizes of all inputs and outputs including the unused. You have to do this for all cases: 32.000 Hz, 44.100 Hz and 48.000 Hz.
Cubase is able to do this automatically (but not always successfully!). Donīt forget to switch the particular samplerate in the control panel of the EWS64.
As 'Sync Reference' choose 'Sampleposition - Output', at 'Card Options' select 'Full duplex', 'open all devices before start' and 'use 16-bit only'. Based on my experience the option "start input first" should be deactivted.
In the Prioritylist of the Outputs the 'EWS Wave Play #1' should be placed on the first postition. In this case the 'EWS Wave Play #1' is the 'Sync Reference'.

After these steps you should determine the Buffersizes for all In- and Outputs (and additionals soundcards if existing). Test your configuration with the button 'Run Simulation'.

Important:
If you will get as result: 'Test is completed successfully', the ASIO-Multimedia-driver will work with Cubase. In case of any other result you have wrong settings (Buffersize or Latency settings).

Attention:
In most cases extensive tests are necessary to get the correct settings.


Hint:
For testing under Windows 9x use the Program 'WAVBENCH.EXE' from Terratec. This program can change the 'Wave Play Buffer Latency' without Windows reboot. Windows 2000/XP user can change this setting via control panel without Windows reboot.

Note:
Donīt forget the buffersize determination for all samplerates: 32.000 Hz, 44.100 Hz and 48.000 Hz. There are different values for each samplerate.

Very important note for the 'Codec' of the EWS64:
My very important recommendation is to deactivate the Codec if you work with Cubase. Be sure, that the 'EWS64 Codec Play' and the 'EWS64 Codec Record' are switched off. Nevertheless you have to determine the buffersize for both devices.

Don't activate all 'EWS64 Wave Play Drivers' !
There are two important reasons to do so. On my Cubase-setup only 'EWS64 Wave Play #1' and 'EWS64 Wave Play #2' are active for 2 Virtual Channels and that is normally enough. This configuration has two advantages:
The first is - Lower Processor Usage and the second is - an additional audioprogramm can work at the same time while running Cubase 5. For this program (for example WaveLab) you can configure 'EWS64 Wave Play #3' as output, and 'EWS64 Wave Play #4' will keep free for other requirements (for example 'Windows Sound System').
With this configuration the programs coexist without any problems. They can play audiodata at the same time. Recording at the same time is not possible.

A last hint to Buffersize:
Sometimes the automatic determination of the buffersizes doesnīt work correctly. The simulation returns errors with the automatically found values.
In this case you should test the values from the following tables. Doubleclick on the particular value to change it manually.
Each 'EWS Wave Play driver' should have the same value. The count of 'EWS Wave Play drivers' equals the count of 'Virtual channels' of your system configuration. The tables are based on 4 'Virtual channels'.
In the first table are my results with Cubase 5.0, in the second table are my results with Cubase 5.1.
Note:
The values of the first table are often useable with cubase 5.1 too. The automatic determination of Cubase 5.1 brings different values and I cannot say which of the valuesets is the better choice. You just can try it. Nevertheless the values of table 2 often work fine and should be tried first.

Table 1: Buffersizes, determined in Cubase 5.0 (R1-R4)
 
Device Buffersize 32 kHz Buffersize 44,1 kHz Buffersize 48 kHz State
EWS64 Wave Play #1 3072 4096 4608 Active device
EWS64 Wave Play #2 3072 4096 4608 Active device
EWS64 Wave Play #3 3072 4096 4608 Possibly active device
EWS64 Wave Play #4 3072 4096 4608 Possibly active device
EWS64 Codec Play 4000 5512 6000 Inactive device
EWS64 Wave Record 3072 4096 or 8192 4608 Active device
EWS64 Codec Record 4000 5512 6000 Inactive device

Table 2: Buffersizes, determined in Cubase 5.1 (R1)
 
Device Buffersize 32 kHz Buffersize 44,1 kHz Buffersize 48 kHz State
EWS64 Wave Play #1 4096 4096 4096 Active device
EWS64 Wave Play #2 4096 4096 4096 Active device
EWS64 Wave Play #3 4096 4096 4096 Possibly active device
EWS64 Wave Play #4 4096 4096 4096 Possibly active device
EWS64 Codec Play 4000 5512 6000 Inactive device
EWS64 Wave Record 4096 4096 or 8192 8192 or 4096 Active device
EWS64 Codec Record 5120 7072 7680 Inactive device

Back to the top

3. ASIO DirectX driver setup

I. Windows 9x user:
You will find these settings in the Cubase menu 'Options/Audio Setup/System' button 'ASIO Control Panel'. Before you can do this setup you have to select 'ASIO directX driver' as ASIO-device.
For this EWS64 driver you need to do a the following settings:
Move the 'EWS64 DirectSound driver #1' to the top position and activate it. So this driver will be the Sync Reference. If you want to use additional Virtual Channels you can activate more EWS64 DirectSound drivers (#2, #3...). The buffersize should have the standard determination value of '3000'.
Important:
The 'CS4232 DirectSound driver' (EWS64 Codec) entry should normally set inactive.
Hint:
Unfortunately the entries of the 'EWS64 DirectSound driver list' are too large. The important last digits with the driver number (#1, #2..) are invisible. If you select an entry, you can see the full name below the window! So you can find the 'EWS64 DirectSound driver #1' entry for making the described settings.

The ASIO DirectX driver for Windows 9x:

ASIO DirectX setup for Windows 9x
 
II. Windows 2000/XP user:
You will find these settings in the Cubase menu 'options/audiosettings/system' button 'ASIO control panel'.
In Windows 2000/XP you cannot access the 'Virtual channels' via directX (like in Windows 9x). Only the 'Codec' is supported from directX under Windows 2000/XP. Therefore you can select the codec only in this menu.
The buffersize should have the standard determination value of 3000.

Special note:
I don't recommend to use this driver with Cubase!

The 'Virtual channels' aren't available (only Playback by Codec), also you cannot record with this driver.

The 'ASIO DirectX driver' in Windows 2000/XP:

The 'ASIO DirectX driver' in Windows 2000/XP
 
Back to the top

4. ASIO DirectX full duplex driver setup

I. Windows 9x user:
You will find these settings in the included 'ASIO directX setup' of Cubase 5.
You have to setup 5 settings: The ASIO DirectX full duplex driver in Windows 9x

The ASIO DirectX full duplex driver in Windows 9x
 
II. Windows 2000/XP user:
You will find these settings in the included 'ASIO directX setup' of Cubase 5.
Windows 2000 doesnīt support the access of the 'Virtual channels' via directX. W2k supports the access of the EWS64 Codec via directX only.
Therefore in w2k the menu 'Direct Sound Output Ports' offers the Codec only for selection.

Important note:
I don't recommend to use this driver with Cubase!


The ASIO DirectX full duplex driver in Windows 2000/XP:

The ASIO DirectX full duplex driver in Windows 2000/XP
 
Back to the top

5. Terratec EWS64 ASIO driver setup

I. Windows 9x user:
You will find these settings in the cubase menu 'Options/Audio Setup/System' button 'ASIO Control Panel'. First you have to select the 'TerraTec EWS64 ASIO driver' as your ASIO-device.
You have to make several settings: Terratec EWS64 ASIO driver settings in Windows 9x:

Terratec EWS64 ASIO driver settings in Windows 9x
 
II. Windows 2000/XP user:
You will find these settings in the cubase menu 'Options/Audio Setup/System' button 'ASIO Control Panel'. First you have to select the 'TerraTec EWS64 ASIO driver' as your ASIO-device.
You can make several settings: TerraTec EWS64 ASIO driver settings in Windows 2000/XP:

'TerraTec EWS64 ASIO driver settings' in Windows 2000/XP:
 
Back to the top

6. Cubase Audio System Setup

Cubase Audio System Setup
 
You will find these settings in the cubase menu 'Options/Audio Setup/System'. My following references for settings are advices only. Different settings for your PC might be possible. Look at your Cubase manual during your tests. At chapter 'Audio Optimizing' you'll find a lot of hints to all settings.

Hints to every setting:
Back to the top

7. Additional important settings in Cubase 5

For a good working with Cubase without any problems you have to do some additional settings: Back to the top

8. Cubase MME-settings

Cubase MME-settings
 
These settings are configurable with the program 'Setup MME' which is delivered with Cubase. You can configure which MIDI-ports will be used from Cubase and in which priority they are shown.
In 'MME-Outputs' it is recommended to put 'EWS64 Play' to the first position. With this setting every MIDI-tracks are using the EWS64-Synthesizer as their default.
MIDI ports reserved for other programs (like Ed!son) should be deactivated, especially the non-multiclientable ports of the EWS64 (Outputs: EWS64XL MIDI 2, EWS64XL FM Synthesis and all installed virtual MIDI-ports; Inputs: EWS64XL MIDI 2, all installed virtual MIDI-ports and all installed EWS64-MIDI-monitor-clients).
The conditions for the outputs 'EWS64XL MIDI Play' und 'EWS64XL MIDI 1' and the input 'EWS64XL MIDI Record' are different. These ports are multi clientable (depending on your configuration in the 'Windows control panel/Device Manager/TerraTec Audio Devices/EWS64 Synthesizer Settings'). You can use these ports simultaneously with different audio software (e.g. Ed!son), even if they are activated in Cubase. This is easily possible with increasing the value of MIDI-clients in the 'EWS64 Synthesizer Settings/MIDI-clients' to values bigger than '1'.
Conclusion:
The MIDI-Setup for the EWS64 is a very complex theme and you have to get a lot of experience for success. On the other hand no other known soundcard offers multi clientable MIDI drivers!
I guess in practice itīs a very usefull feature. For each other soundcards you need any third party software (like Hubis MIDI-Loopback-Device) to enjoy the advantages of multi clientable MIDI-devices.

Back to the top

9. Additional information for EWS64 drivers

At this place I will give additional hints about the several EWS64-driver which are usable for Cubase.

I. Windows 9x-User:

Windows 9x user can choose up to seven different driver configurations:
  1. ASIO directX driver (latency: 203 ms)
  2. ASIO directX full duplex driver (latency: 46 ms)
  3. ASIO multimedia driver (latency: 557 ms)
  4. TerraTec EWS64 ASIO driver (2 channel-playback no recording) (latency: 12 ms min.)
  5. TerraTec EWS64 ASIO driver (2 channel-playback with recording) (latency: 23 ms min.)
  6. TerraTec EWS64 ASIO driver (4 channel-playback no recording) (latency: 23 ms min.)
  7. TerraTec EWS64 ASIO driver (4 channel-playback with recording) (latency: 46 ms min.)
A good question at this place is: What's the best choice ?

It's quite difficult to find the right answer: The best solution always depends on what you want to do with your EWS64.
For recordings of VST-instruments configuration #4 is the best choice. You will have the smallest latency and hear all sounds immediately after touching the keys.
For the distribution of the internal effects (Chorus and Reverb) and native playback over the virtual channels configuration #2 and #3 are the best choice. Especially in case of legacy PCs with low CPU power these settings are very usefull. You can use the internal effects in place of VST-effects.
4-channel productions are possible only with configuration #1, #2, #3, #6 or #7.

Fact is: There is no configuration, which could be the best choice for all requirements.

I'm using configurations #4 or #5 as default, because I like VST-instruments and these configurations offer the smallest latency (12ms or 23ms min.).
During the work with a Cubase song itīs possible to change the configuration:
Configuration #4 for recording VST-instruments (with buffersize 512 and latency 12ms) and Configuration #5 for recording audio tracks (increase the buffersize to at least 1024!). Itīs the best way to adapt the configuration on the actual requirements.

I donīt use the configuration #1 because I donīt see any advantage and recording is impossible.

With configuration #1, #2 and #3 itīs possible to use the particular features of the 'Virtual channels'.
Configuration #2 has the smaller latency, but configuration #3 often runs much more stabil and offers a final mixdown when other drivers fail. Unfortunatelly #3 is unsuitable for VST-instruments (latency: 557ms)

II. Windows 2000/XP user:

The EWS64 synthesizer doesn't work with directX-driver. Therefore three configurations are usefull only:
  1. ASIO multimedia driver (latency: 557 ms)
  2. Terratec EWS64 ASIO driver (2 channel-playback with recording) (latency: 17 ms min.)
  3. Terratec EWS64 ASIO driver (4 channel-playback with recording) (latency: 34 ms min.)
For recordings of VST-instruments configuration #2 is the best choice. You will have a latency of 17 ms (with ASIO-Buffersize/Channel value '512').
Configuration #3 is usefull if you need both outputs of the EWS64. The 'ASIO Buffersize/Channel' has to be 1024 (or bigger). The latency increases to 34ms min.
Configuration #1 is usefull if you need the particular features of the 'Virtual channels'. In any other case the both ASIO drivers are the better choice.

Hint:
Make several tests to find out which configuration is the best for your situation. Basicly the ASIO-drivers are the best choice.

Back to the top

10. Settings for the EWS64-Control Panel and the FX-Panel with Cubase

Settings for the EWS64-Control-Panel and the FX-Panel with Cubase
 
If you plan to use reverb and chorus in your Cubase song, you have to activate these effects in the FX-panel first. Additional you must set the 'MIDI Reverb Send' and the 'MIDI Chorus Send' values to #64 for correct working of both effects in Cubase.
If you want to set the EQ with my 'EWS64 Master-Mixermap', please set the Equalizer to '4-Band EQ' for activating the EQ-controllers in this mixermap.
The controlling of the MIDI-Master Volume and the settings of programs and any effect-values are very comfortable with my 'EWS64 Master-Mixermap'. The advantage is: You can save the settings with a mixermap-snapshot in a mixertrack. If you load the song any time later the identical settings are sent to the EWS64!

Important note about the EWS64-equalizer:
If you want to use the EWS64-equalizer for music production, than you need a work around. The equalizer works for the 'Out1' only, but you cannot choose 'Out1' as recording input. In recordsetting 'Mix' for waverecords the EQ not included too.
Therefore we have only one wayout:
Use a cinch cable to connect the 'DIG Out 1' with 'DIG In'. Now you can make records via 'DIG In' including the EQ. The EQ doesn't work with 'Out 2' anyway.

Note about the switch 'Clip on/off' in the EWS64 control panel:
How does it works: with 'clip on' overrides of the synthesizer will caught softly. This avoids horrably sounding distortions. The electronic works near like a limiter of professional mixers or amplifiers.
The sense of activating 'clip on' depends on the situation:
Case 1: you want to playback a bigger MIDI-song recording to an audiotrack at the same time. Set 'clip on' to avoid digital clippings in your record.
Case 2: You want to remaster audio data to a Digital Audio Tape (DAT) or want to remix several audio tracks to a single track. Set 'clip off' to get a 1:1 result without any changes of the original audio dynamic.

Back to the top

11. How many MIDI-voices does the EWS64 play at the same time?

The count of the simultaneously playable MIDI-voices depends on the number of activated 'Virtual channels' and the activated EWS64-effects (reverb, chorus, echo In2, EQ and V-Space).
Basicly we can say: The more 'Virtual channels' or effects are active the less MIDI-voices are playable at the same time.
The reason for this is the internal structure of the EWS64-synthesizer. It is organized into 64 so called 'slots'. Each slot is able to play either a mono audio track (no matter if MIDI or audio) or the slot is used for an EWS64-effect.
The following table will give an overview about usage of slots in case of virtual channels and effects. This will give you the possibility to calculate the remaining slots for MIDI-voices depending on your individual EWS64-setup. The following example shows a method how to calculate the available MIDI-voices:
Let us assume, that 4 Virtual channels, Reverb, Chorus and EQ 4-Band Mode are active and Echo In 2 and V-Space are inactive. In this case we need for the Virtual channels 8 Slots, for Reverb 13 slots, for Chorus 3 slots and for EQ 8 Slots.
This means in practise: 64 (the total amount of slots) -8 -13 -3 -8 = 32 Slots. In this case 32 slots will be available for MIDI-voices.

What can we finally say as result ?
You should always turn off all unused effects in the FX-panel! That will increase your amount of available MIDI-voices. Especially 'V-Space' and 'Echo In 2' are used rarely and should be switched off normally. Also you shouldn't use to much 'Virtual channels'. For example a decreasing from 8 to 4 VCs will offer 8 additional slots for MIDI-voices.

At this place further important infos:
It depends also on the particular instruments, how many MIDI-voices the EWS64 is able to play at the same time.
A mono-instrument needs just one slot for each voice, a stereo instrument needs two (one for left channel and one for right channel). In case of 32 free slots any stereo instrument only can play 16 voices simultaneously.
This fact will be harder in case of instruments with many samples per key (multi layer instruments). In case of 3 simultaneous stereo layers we need 6 slots for each key. In case of 32 free slots we only can play 5 voices of such an instrument at the same time.

Back to the top

Back to home

C/O 2002-2012: Werner Ogrodnik (Cologne, Germany)