E-MU 1616m, 1212m, 1820m, 0404 Audio Interface - Complete Windows 10 (1903 & Above) Installation Guide

[kodebode2]

Please see the more recent update at the end of this post....

Big thank you to all who have made this workaround possible - I thought it good to provide a comment that describes what worked for me, cos some of the steps needed modification.

I have included the original steps from the 1st post, and my comments are below each step. In Italics

My card is an Emu 1212M, and I was upgrading from Windows 10 1809 to Windows 10 1903.

After the upgrade, as expected I could not get the EMU Mixer app - Patchmix DSP, to work properly.


Download the E-MU_Windows_10_Install.zip file from https://1drv.ms/u/s!Ar-KCv7xikVOh23zeXTESuD8k2ih.

I did download this, only to see the contents, not that I do not trust the provide of this compilation, but as a precaution, I would suggest that rather than use the executables included in this, do try to find the relevant executables - i.e the exe's referred to, in these instructions, from the most trustworthy sources you can find on the internet.

In order to get the EMU 1212M working on Windows 10 1809, in the first place, this is a bit of a no-brainer cos these are the very same executables, which I had used for the install - so it was a no-brainer, I already had these saved somewhere.

The directory for the newer Creative Labs card, can be derived by unzipping the related .exe XFTI_PCDRV_L11_2_40_0018.exe, which you can find from a reliable source if you google. Extract this using an unzip app like 7-zip into c:\temp\XFTI_PCDRV_L11_2_40_0018

Now, there are two files which are included in this download, which you will need to extract, and place into

C:\temp\EMU_Driver_Fix.ps1

and

C:\temp\FilesToReplace.csv

The .ps1 file is a script. Typically one has to be careful about downloading scripts, but this script does nothing harmful, just copies files from the more current Creative Labs driver to overwrite the files from the vintage EMU driver install.

I repeat, rather than use the executables in the compiled download, for your absolute safety, I recommend you find the originals from trusted sources, and use these instead.



Extract the zip file to your main Windows 10 drive and change the name of the folder to "temp". (C:\temp)

Please see comment above. The only files I would recommend to be extracted from this are the .ps1 and .csv in the comment above.


Remove all current E-MU Drivers and PatchMix software.

Definitely this is a necessary step - removing all old software. But I would suggest you also restart the computer normally at least once, after the uninstall, rather than go straight to a safe mode on the 1st restart.

Why? I ran into a big issue, where for some reason, if I followed the initial instruction verbatim, without rebooting after the uninstall, and went straight to SAFE MODE, things did not work, and I was also unable to attempt to redo the install of EmuPMX_PCDrv_US_2_30_00_BETA.exe.

This exe simply would not go ahead to install again, cos I think it detected that there were already install files on the computer, and until I deleted them using the remove.ps1 (see below), a reinstall of a corrupted install, was not possible.

I had to create a script which was based on the 2nd column of files in the .csv, which simply deleted files aso follows

So I placed all these statements in a remove.ps1 file and to recover from my incomplete installation/uninstall, while in safe mode, I executed the remove.ps1 file from windows powershell.

If for any reason, you wish to start the whole install again, I would recommend that after running any uninstall steps via the usual process - e.g via Control Panel, Programs, and uninstall of EMU software, you could in SAFE MODE, run remove.ps1, to ensure that any files have been removed before you restart the install.

My remove.ps1, was my lifesaver from a corrupted install/uninstall. Without this it was impossible for me to attempt to restart the install.

i.e in Windows powershell :

set-executionpolicy unrestricted -scope localmachine
and press Enter. You may need to answer Y.

./remove.ps1
and press enter

Contents of remove.ps1 are below

del C:\Windows\system32\ctasio64.dll
del C:\Windows\system32\ctcoinst.dll
del C:\Windows\system32\ctdlang.dat
del C:\Windows\system32\ctdnlstr.dat
del C:\Windows\system32\ctdpxy64.dll
del C:\Windows\system32\ctdvinst.dll
del C:\Windows\system32\CTMLFX64.dll
del C:\Windows\system32\ctosur64.dll
del C:\Windows\system32\CtxfiRes.dll
del C:\Windows\system32\data\ctd20x.dat
del C:\Windows\system32\data\CTP0460V.DAT
del C:\Windows\system32\data\CTP0460W.DAT
del C:\Windows\system32\data\CTP0462V.DAT
del C:\Windows\system32\data\CTP0462W.DAT
del C:\Windows\system32\data\CTP0463V.DAT
del C:\Windows\system32\data\CTP0463W.DAT
del C:\Windows\system32\data\CTP0464V.DAT
del C:\Windows\system32\data\CTP0464W.DAT
del C:\Windows\system32\data\CTP0465V.DAT
del C:\Windows\system32\data\CTP0465W.DAT
del C:\Windows\system32\data\CTP0466V.DAT
del C:\Windows\system32\data\CTP0466W.DAT
del C:\Windows\system32\data\CTP0468V.DAT
del C:\Windows\system32\data\CTP0468W.DAT
del C:\Windows\system32\data\CTP0469V.DAT
del C:\Windows\system32\data\CTP0469W.DAT
del C:\Windows\system32\data\CTP046AV.DAT
del C:\Windows\system32\data\CTP046AW.DAT
del C:\Windows\system32\data\CTP046BV.DAT
del C:\Windows\system32\data\CTP046BW.DAT
del C:\Windows\system32\data\CTP046CV.DAT
del C:\Windows\system32\data\CTP046CW.DAT
del C:\Windows\system32\data\CTP0550V.DAT
del C:\Windows\system32\data\CTP0550W.DAT
del C:\Windows\system32\data\CTP055AV.DAT
del C:\Windows\system32\data\CTP055AW.DAT
del C:\Windows\system32\data\CTP0678V.DAT
del C:\Windows\system32\data\CTP0678W.DAT
del C:\Windows\system32\data\CTP0679V.DAT
del C:\Windows\system32\data\CTP0679W.DAT
del C:\Windows\system32\data\CTP0730V.DAT
del C:\Windows\system32\data\CTP0730W.DAT
del C:\Windows\system32\data\CTP073AV.DAT
del C:\Windows\system32\data\CTP073AW.DAT
del C:\Windows\system32\data\CTP0760V.DAT
del C:\Windows\system32\data\CTP0760W.DAT
del C:\Windows\system32\data\CTP0772V.DAT
del C:\Windows\system32\data\CTP0772W.DAT
del C:\Windows\system32\data\CTP0773V.DAT
del C:\Windows\system32\data\CTP0773W.DAT
del C:\Windows\system32\data\CTP0775V.DAT
del C:\Windows\system32\data\CTP0775W.DAT
del C:\Windows\system32\data\CTP0776V.DAT
del C:\Windows\system32\data\CTP0776W.DAT
del C:\Windows\system32\data\CTP0779V.DAT
del C:\Windows\system32\data\CTP0779W.DAT
del C:\Windows\system32\data\CTP0880V.DAT
del C:\Windows\system32\data\CTP0880W.DAT
del C:\Windows\system32\data\CTP0881V.DAT
del C:\Windows\system32\data\CTP0881W.DAT
del C:\Windows\system32\data\CTP0882V.DAT
del C:\Windows\system32\data\CTP0882W.DAT
del C:\Windows\system32\data\CTP0883V.DAT
del C:\Windows\system32\data\CTP0883W.DAT
del C:\Windows\system32\data\CTP0886V.DAT
del C:\Windows\system32\data\CTP0886W.DAT
del C:\Windows\system32\data\CTP0888V.DAT
del C:\Windows\system32\data\CTP0888W.DAT
del C:\Windows\system32\data\CTP0889V.DAT
del C:\Windows\system32\data\CTP0889W.DAT
del C:\Windows\system32\data\cts20x.dat
del C:\Windows\system32\drivers\ct20xflt.sys
del C:\Windows\system32\drivers\CT20XUT.sys
del C:\Windows\system32\drivers\ctac32k.sys
del C:\Windows\system32\drivers\ctaud2k.sys
del C:\Windows\system32\drivers\CTEXFIFX.sys
del C:\Windows\system32\drivers\CTHWIUT.sys
del C:\Windows\system32\drivers\ctoss2k.sys
del C:\Windows\system32\drivers\ctprxy2k.sys
del C:\Windows\system32\drivers\ctsfm2k.sys
del C:\Windows\system32\drivers\emupia2k.sys
del C:\Windows\system32\drivers\ha20x2k.sys
del C:\Windows\system32\drivers\pfmodnt.sys
del C:\Windows\system32\instwdm.ini
del C:\Windows\system32\regplib.exe
del C:\Windows\SysWOW64\a3d.dll
del C:\Windows\SysWOW64\ac3api.dll
del C:\Windows\SysWOW64\AddCat.exe
del C:\Windows\SysWOW64\ct_oal.dll
del C:\Windows\SysWOW64\Ct20xspi.dll
del C:\Windows\SysWOW64\ctasio.dll
del C:\Windows\SysWOW64\ctdlang.dat
del C:\Windows\SysWOW64\ctdnlstr.dat
del C:\Windows\SysWOW64\ctdproxy.dll
del C:\Windows\SysWOW64\ctemupia.dll
del C:\Windows\SysWOW64\CTMLFX32.dll
del C:\Windows\SysWOW64\ctosuser.dll
del C:\Windows\SysWOW64\CTxfiBtn.dll
del C:\Windows\SysWOW64\Ctxfihlp.exe
del C:\Windows\SysWOW64\CTxfiReg.exe
del C:\Windows\SysWOW64\CTXFIRES.DLL
del C:\Windows\SysWOW64\CTxfispi.exe
del C:\Windows\SysWOW64\CTxfiSpk.dll
del C:\Windows\SysWOW64\ctzapxx.ini
del C:\Windows\SysWOW64\devreg.dll
del C:\Windows\SysWOW64\eaxac3.dll
del C:\Windows\SysWOW64\enlocstr.exe
del C:\Windows\SysWOW64\instwdm.ini
del C:\Windows\SysWOW64\killapps.exe
del C:\Windows\SysWOW64\oalinst.exe
del C:\Windows\SysWOW64\piaproxy.dll



Install the EmuPMX_PCDrv_US_2_30_00_BETA drivers and RESTART INTO SAFE MODE by holding the shift key when clicking on Restart. Choose Troubleshoot, Advanced Options, Start-up Settings and click Restart. When the start-up options appear, press F4.

Ast stated above after the install of the beta drivers, reboot at least once in normal mode, then
restart in safe mode.

Rather than use option 4 or F4 for SAFE MODE, you may want to use option 5 or F5 to enable networking, just in case you need to browse the instructions from kvraudio, while you are in safe mode !!


Once in safe mode right-click on the start button and open Windows PowerShell (Admin). Type into the PowerShell window


From another post, I realised this does not work. you need to type in "powershell" in the search window next to, on the right of the start button and click on a run as admin option which shows up in a panel.


set-executionpolicy unrestricted -scope localmachine
and press Enter. Then type

cd c:/temp
and press Enter. Then type

./EMU_Driver_Fix

to run a modified version of ClubHouseKey's script. This will replace our windows files with the updated files. Performing this step in a normal Windows environment will either cause the script to not run at all due to script settings within Windows or some files will not get overwritten because they're in use.

Restart Windows normally and then install the EmuPMX_PCApp_US_2_20_00 PatchMix Software.
You should now have successfully installed your E-MU Audio Interface.

It is suggested you install this patchmix software as administrator. from what I read in another post

If ASIO isn't working then click on Start and type regedit and click on Registry Editor. Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run, right-click AsioThk32Reg and choose Modify. Change CTASIO.DLL to CTASIO64.DLL.

I did not have to use this ASIO correction step


At any point where an EMU install or uninstall suggests you reboot, please reboot into normal mode. Strongly advised

End result.

I think this upgrade to Window 10 1903, causes the EMU soundcard to be even more efficient from a CPU perspective, than the old install I had in Windows 10 1809.

When I run Youtube video alongside playing a heavily sampled piano, using only a dedicated spinning drive, I no longer feel the need to upgrade to an SSD (which I will do inevitably), but everything feels so smooth, and well oiled, it all just works.

The video drivers in Windows 1903 are definitely more efficient and use less of the Intel integrated GPU, for display of video.

And in Reaper, where my previous RT Max would increase to the 10's or hundreds of milliseconds occasionally, indicating that there was some interrupt related issue with the computer not being able to catch up with the requests for resources, now after several minutes of simultaneously playing back video and using the sampled piano in real time, the max wait is less than 5 milliseconds.

I.e things are operating more efficiently. I run at 48k, 196 buffers (i.e 4 milliseconds target using the EMU ASIO utility, enabled via my DAW) Output latency is reported as 4.4 milliseconds.

My key point is that, at this relatively quick output latency, everything is buttery smooth, No audio stutters at all no matter how heavy I am on the sustain pedal. It just sounds absolutely glitch free, like a proper piano..

From a creativity standpoint, this has really changed everything for me. I can approach the sampled piano, with so much confidence not having to change my pedalling style to accomodate what had been limitations, but now I am free to play anything that I am capable of.

I did not expect this additional bonus by following this workaround install of drivers.

For a sound card that I have had for 16 years, to now be able to use it better, by upgrading to Windows 1903 and use the modified install process for the drivers, is awesome. The EMU1212M is an incredible sounding audio interface, mine is the PCI version from way back.

And now no glitches whatsoever with demanding sampled pianos...

I am in a sonic heaven, and creatively, not needing to upgrade my hardware for a while to add an SSD, or get a more powerful CPU, cos I am in effect using more modern more efficient drivers from a recent EMU/Creative labs audio interface, purpose written for Windows 10, is more than I could have hoped for.

I am obviously ecstatic, with the final result. Sonically as well as just creatively, and not having to upgrade to a more modern audio interface is such a relief.

Buttery smooth audio - with zero glitches at excellent low latencies. What more can one ask for.

And it works all the way up to 192k, if I wish to do this. Not that I do most of the time, stick to 48k predominantly, But in other words, everything works.

Awesome.

Thanks to all contributors.




EDITED on 5th October 2020 to add :

It appears that replacing only the ctoss2k.sys is a much more glitch free method, rather than replacing the large list of files. So I wrote a modified .ps1 command file which points to a modified .csv file which has only one file in it for copying over from the files extracted from the newer Creative Labs audio card which is compatible with Windows 10 1903 and above.

I pretty much restarted by 1st uninstalling both the app then the driver, then repeating the process as described earlier but now replacing only one file - ctoss2k.sys.

I also ran a command to reset the execution mode back to normal - not happy about leaving things untidy and unsecure - somewhat suspect like opening a back door.

set-executionpolicy -ExecutionPolicy default -scope localmachine

This command returns the execution policy of the local machine back to the default which is "Restricted". Much happier about this.

Now I can do things I could not do before - reliably run a demanding sampled piano @ 96k. without any worrisome glitches - the method replacing many files gives lots of glitches on my system @ 96k, so the one file replacement is definitely a lot more recommended by me.

[speedymonk]

Have you tried it up to 192K? I can't get past 44.1. How is it set up in patchmix for you at 48, 96 and 192? Physical imputs and routing.

[AudioManiak]

To make the card work, you need to replace only 1 the ctoss2k.sys file. This makes the card more stable. I lost some glitches when I replaced only 1 file. How replace I wrote on the previous page.
Just replace ctoss2k.sys in the E-mu driver installation file, and install driver.

[kodebode2]

Have you tried it up to 192K? I can't get past 44.1. How is it set up in patchmix for you at 48, 96 and 192? Physical imputs and routing.

In Patchmix there's a button near the top for creating a new session - see image below.

Then you can choose the sample rate you wish the card to operate at.

Typically I created sessions for all my most frequently used sample rates, and saved them as session files. So after any install or some user error on my part, I can always go back to a stable config by opening a pre-saved session, typically I also include the sample rate in the same of the saved session file so its easy to know which session is which.

The new session window also has some templates, like examples, which you may wish to use. I'm pretty savvy with Patchmix, so in my case if I was starting from scratch, I'd use the default session example and build it into what I need.

new Patchmix.png

[kodebode2]

To make the card work, you need to replace only 1 the ctoss2k.sys file. This makes the card more stable. I lost some glitches when I replaced only 1 file. How replace I wrote on the previous page.
Just replace ctoss2k.sys in the E-mu driver installation file, and install driver.

You may be right, in which case, all that one has to do is modify the .csv file to include only this file.

Maybe someday, I will try it out. Now that I understand how the install works, I expect I should be able to accomplish this is about 30 minutes, max. i.e the whole process. Worth trying.. Right now I run pretty stable at 48K and 192 samples buffer. giving me a reported output latency of 4.3 milliseconds., IMHO, much more stable than using only the original EMU1212M BETA drivers for Windows 7 - 64 bit, which is what I was using pre - Windows 10 1903.

If I try out your method of copying over only one file, the ctoss2k.sys, what I'd be interested in improving is to see if I can get stable operation down to 96 buffer samples, which brings the reported output latency down to 2.3 seconds. @ 48k. Not that This is necessary, cos I'm ok with what I have. If your method brings this kind of performance improvement at really low latencies, then I can be assured of even more stability/CPU efficiency when I run at my current 192 samples buffer.

[kodebode2]

Have you tried it up to 192K? I can't get past 44.1. How is it set up in patchmix for you at 48, 96 and 192? Physical imputs and routing.

Thought it better to do a video of this, would be easier for you to understand.

Changing Sample rate in Patchmix.gif

[speedymonk]

I understand how to change by sessions. It is the routings that are giving me fits besides red mixer strips.

[kodebode2]

I understand how to change by sessions. It is the routings that are giving me fits besides red mixer strips.

The Patchmix app is a very flexible tool. But this flexibility could also make it complex, if one is not clear on how it works, and to a novice user it will be difficult to troubleshoot.

So the way I look at it is - it's just a digital audio mixer, similar to a live audio mixing console, with audio, and one has to understand how it works :

It routes audio between these sources and destinations.

1. Physical Inputs (Digital and Analog)
2. Physical Outputs (Digital and Analog)
3. ASIO Inputs - to send audio into ASIO apps
4. ASIO Outputs - to send audio out of ASIO apps
5. Windows WDM Inputs, to receive audio from Windows apps - such as Youtube or Spotify. or your browser.
6. Windows WDM outputs, to send audio to Windows apps which can record audio, such as Zoom, Skype, or any other Windows audio recorder such as Audacity.

It has advanced tools to facilitate the routing of audio through external inserted hardware, such as a hardware reverb, and back into the audio interface.

It has some digital effects, i.e its own plugins...

The Patchmix tool , routes audio between sources and destinations, with some important features :

1. All audio is controlled by strips which you add through the button with the asterisk (star) on the top left. By this you choose the audio sources that are added, to the mixer.

2. All audio sources added via strips automatically route their audio to the main mix and monitor mix outputs.

3. The level of the main mix and monitor mix, can be controlled via faders, or dials to the right of the screen. There is also an outputs assignment button on the top right, which assists in determining which signal, Monitor mix or Main Mix, is routed to each physical audio output (digital or analog).

4. Each strip also has sends which you can use to send audio to an Aux1 and and Aux 2.

5. Unlike typical audio mixers, Patchmix does not have traditional options for EQ, Compression, etc. If you need these, this is achieved via INSERTed plugins on each strip.

6. Probably the most important rule is that if you wish to route any audio in any other way, from the default, described above, the only way to achieve this is via a special INSERT known as the "Insert Send - (Output to ASIO/WAVE or Physical Out). There are other send insert options, more advanced, than this, but I will not cover them here. You can access all the plugins, and INSERT plugins, via right click on each strip, and you can have multiple inserts - up to 6 inserts, per strip.

So with this fundamental understanding, you have to ask yourself What do you wish to route to where? What is the source and what is the destination. My suggestion is to delete all strips, so you start from a blank slate.

A lot of this channel selection in strips is based on stereo pairs. !!important note. While it is also possible to have mono sources..!!

I will use an example.

I wish to send audio from my DAW to the audio outputs - physical 1 and 2.

So the next question is - what kind of audio does my DAW use to send audio out - ASIO or WDM?

Assume it is ASIO, then next question is which ASIO outputs am I sending this output from the DAW to?

Assume it is ASIO 1/2 i.e a stereo pair, which is the output of my DAW..

So we wish to send audio from DAW - to ASIO 1/2, and route this to the Main Audio interface outputs Left/Right.

(Please note the physical and digital inputs and outputs available will depend on your connected EMU audio device(s)).

STEP 1. Select ASIO 1/2 as a strip - using the create strip button at the top left (this is the button with an asterisk). Assume this is the 1st strip i.e Stereo 1.

STEP 2. Using right click, insert a Peak Meter on the strip, as the 1st insert, so you can get some kind of visual feedback when audio is passing through this strip.

STEP 3. Adjust the volume using the volume fader on this Stereo 1 strip or adjust the overall volume on the Main mix using the Main Mix fader.

STEP 4. Play back some recorded audio from your DAW.

Job done.

If you have any other specific routing which you need, and if your attempts do not succeed, do let me know. But I suggest you 1st ensure you can get audio out from your DAW, using the example I have given above, so we are sure your audio card is working properly, and not assuming this.

the key to success with Patchmix is to be methodical, What's my input source, where do I want to send it, is there a default audio path to achieve this, or do I need to use an INSERT to achieve this routing?

The default routing is from the strip, to the Main Mix and Monitor Mix busses.

Unfortunately what this requires if you are routing certain audio, such as routing a physical audio input to a DAW, via an ASIO input, using a SEND insert. By default this audio input will automatically be routed to the Main Mix and Monitor Mix, which could cause a feedback loop, if your input is a microphone. If you wish to monitor via the DAW, you then have to mute the strip, via the Mute buttons. This does not affect the routing of the physical audio inputs to your DAW. It is a good habit to insert a Peak Meter as the 1st INSERT, in every strip, to get some visual confirmation that audio is passing through.

[speedymonk]

Thanks. I will see what I can do.

[boombaxx]

anyone want to buy a 12/12m pci

[kodebode2]

anyone want to buy a 12/12m pci

What does it come with?

1. Daughter card,
2. MIDI cables - how many?
3. Software Disks - which ones?

And how much - including postage. I'm in the UK

[kodebode2]

To make the card work, you need to replace only 1 the ctoss2k.sys file. This makes the card more stable. I lost some glitches when I replaced only 1 file. How replace I wrote on the previous page.
Just replace ctoss2k.sys in the E-mu driver installation file, and install driver.

I did try out your method. And It definitely works. I was also able to replace the file without needing to restart into safe mode.

Only needed to exit Patchmix and disable EMU audio driver, replace ctoss2k.sys, then enable EMU Driver - Patchmix was automatically restarted.

Awesome... Thanks,

I cannot tell the difference from the method which needs replacement of many more files, but this your method also works.

[speedymonk]

Thanks. I will see what I can do.

Well I am either dense or just not setting up ,properly. This is what I have. Analog synths and keyboards running through my mackie LM3204 analog mixer. Stereo out of the mixer go to 3L/R on the Audio Dock. Output 4 l/R (monitor) goes to amp. Computer audio goes to L2/R2.

44.1 operates properly. No issues. I can see routings and they work.

48 does not give me options to have either 2 L/R or 3 L/R as inputs. I made new strips but the option doesn't exist. Only ADAT options exist which do not have. What am I missing here. I am finally retired and have been wanting to record for ages when I bought this card under the XP days. Didn't have time then but do now. Will be going into Bandlab as my DAW. Do I first need to set windows up for the higher resolution and Bandlab too? I would think I set the card up first. Anything beyond 44.1 says "Do not have sufficient EMU hardware".

I did the fix and am on Windows 2004. All else is good.

Thank you.



Appreciate any solutions you may have.

[kodebode2]

Thanks. I will see what I can do.

Well I am either dense or just not setting up ,properly. This is what I have. Analog synths and keyboards running through my mackie LM3204 analog mixer. Stereo out of the mixer go to 3L/R on the Audio Dock. Output 4 l/R (monitor) goes to amp. Computer audio goes to L2/R2.

44.1 operates properly. No issues. I can see routings and they work.

48 does not give me options to have either 2 L/R or 3 L/R as inputs. I made new strips but the option doesn't exist. Only ADAT options exist which do not have. What am I missing here. I am finally retired and have been wanting to record for ages when I bought this card under the XP days. Didn't have time then but do now. Will be going into Bandlab as my DAW. Do I first need to set windows up for the higher resolution and Bandlab too? I would think I set the card up first. Anything beyond 44.1 says "Do not have sufficient EMU hardware".

I did the fix and am on Windows 2004. All else is good.

Thank you.



Appreciate any solutions you may have.

I wish I could do more, but can't. Especially as our devices are not identical. Mine is a 1212M, no dock. Normally settings for 44.1 and 48k should be easily interchangeable with ease.

I have done another video, at the end of this post, of how to change sample rate between 44.1 k and 48k, and vice versa. It should be very easy. to change an existing 44.1k session to run at 48k.

If you want to use any higher sample rates, you will need to setup a new session, as there is no way to change between 44.1k or 48k, and any higher sample rates.

The interchangeable rates are :

1. 44.1 and 48k,
2. 88.2k and 96k
3. 176.4k and 192k

One important aspect of all EMU audio devices, when you go to higher sample rates, certain inputs and outputs are no longer available.

In general the higher sample rates reduce the number of available channels.

The best way to find out what inputs/outputs are available, at each sample rate, is to check the manual.

[speedymonk]

Yeah, I thought it would be easy to change the sample rates from 44.1 to 48, too. However... it doesn't work. So... stuck with 44.1 which is ok for now. Will likely buy Focusrite Clarette Thunderbolt used down the road. Thanks again.