[RWP] reaaccess problem - It will not get installed on reaper 32bit, in windows 64bit

Indigo 33indigo at charter.net
Fri Aug 29 12:53:18 EDT 2014


Hadi, here are some notes I snipped from a forum on problems running the 
eMu 1212M and 1616M on 64 bit Windows 7.
I realized that I instinctivly followed many of these instructions when 
I installed my 1616M, which works in 64 bit Win7.
Actually, the computer it's in has a tray in front so I can switch hard 
drives, so when I decided to run the 1616M in 64 bit Windows 7, I just 
left the 1010 PCIE card in its slot in the motherboard, stuck a brand 
new blank hard drive into the drive tray, and installed 64 bit Windows 7 
onto it, then the 2012 Beta driver and Patchmix driver, and it works.
I did the suggestions at the bottom of these suggestions  for 
configuring the default audio device in Windows Sound in control panel, 
which I would always do anyway.
Other than that, Reaper already is set to record on 24 bits 44.1k by 
default, and I've been using that.
I select a 1616 24 bit 44.1k session template from among the session 
templates and hit enter on it, which apparently selects that as the 
default session template.
The factory default template seems to give me all I can get, as far as 
input jacks are concerned.
I can't think of anything else I did this time, but when I had been 
running the eMu 0404 USB on XP, and then bought and installed the 1616M, 
I made sure to search for all Creative files on the computer and delete 
every single one.
Creative uses very similar programming on all their drivers and files, 
and I read on eMu forums to be sure to clear out any previous Creative 
files before installing another Creative product.
Below are some user suggestions that pretty much cover all that one 
should do to make an eMu product work in 64 bit Windows 7.
Yes, it's a hassling product, but it sure has nice sound!
Indi
  Suggestions, snip:
install the eMu and remove the motherboard sound card EARLY in the 
process, if possible. I didn't remove the motherboard sound the first 
time - that may have been part of the problem. Second install - I 
installed Windows itself, then immediately removed the internal sound, 
rebooted cold, and installed the eMu. All other software including OS 
patches were installed afterward. Based on other installs on XP with 
some of Creative's earlier drivers - there were a lot of things that 
could go wrong - especially in the internal routing of audio. The more 
recent drivers have installed easier. Also - don't install any 
additional hardware, especially plug-in devices before the eMu software 
(have nothing but mouse, keyboard, and video monitor connected at  
first; - then add other devices one at a time. Be sure to do a System 
Restore Point on Windows before installing each additional item, that 
way you can back up if needed if a particular device additon or software 
addition messes things up.
I am not running the Win 7 beta drivers - I have downloaded them, but 
what I have is working already. I installed Windows 7 Pro on the brand 
new computer - without the eMu PCI card installed. I then went into 
BIOS, and turned off the internal motherboard sound device. I then 
turned off Windows User Account Control (the part that causes a popup 
for anything requiring Administrator access) and shut down - this is 
necessary for UAC to be shut off.
I then installed the eMu PCI cards along with the extension box, brought 
Windows back up. When it attempted to detect hardware, I cancelled the 
auto-detect.

I then loaded the eMu latest Vista drivers, which ran without complaint.
  After it loaded, I rebooted, and loaded the eMu PatchMix Vista 
drivers, which also ran without complaint. Finally, I turned Windows UAC 
back on, and rebooted so that it would be back on. End of process, 
except installation of all other software.

Comments: During all the above, I had NO other devices already connected 
to the computer except the video monitor, mouse, and keyboard. All other 
devices were added and recognised AFTER install of the eMu. Not sure if 
this is critical or not - but it has been my experience that audio stuff 
breaks sometimes due to multiple devices attempting to use the same 
software interrupt.
Cool 48KHz
I made sure that in my control panel I opened up Hardware and Sound then 
under Sound I selected Manage audio devices. The Sound Folder displays 
and in it are the following Tabs: Playback,Recording Sounds, Communication

Each tab will show devices For instance under Playback you might have 
Speakers
Headphones
Digital Audio (S/PDIF)
Speakers (again if you have two sets)
I highlight each choice and click the Properties button
On the following Properties pages you get various tabs once again
usually General is included With headphones I got
GENERAL LEVELS ENHANCEMENTS ADVANCED I clicked on the Advanced tab and 
there I had the ability to choose the DEFAULT FORMAT I choose the following
2 channel, 24 bit, 48000Hz (Studio Quality) and then there is a Test button

Once that is accomplished (And check all devices that might let you 
choose a default Format)and everything is set to 24 bit 48000Hz You 
should be all set Now load an appropiate session template into PatchMix 
DSP and you should be recognized and can produce audio. The Key seems to 
be making sure evrything is set to 24 bit 48000Hz or 48KHz.
  That seems to allow windows to see and recognize your Emu devices. I 
use the 1212M myself and had problems till I took the above approach 
with both VISTA 64 and WIN 7 64

The same holds for the 32bit versions.

simple solution.

If you will go into Audio and then click on the drivers tab you will 
notice both the "input" and the "output" windows. You will also most 
likely notice that that every input and output is checked. The EMU 1616m 
defaults to the 15/16 ASIO driver, however Sonar defaults to output 1/2 
of the EMU driver.

My simple fix was to uncheck all the of the drivers listed except for 
15. I clicked ok and got out of the Audio section. Restarted Sonar just 
to be sure of a fresh start and wahlah...it all worked.

Not even eMu or Sweetwater suggested this.

I think the confusing part for initially was seeing Sonar defaulting to 
output 1/2...and that was the output I was using on the breakout 
box...but that was different than the ASIO driver.
Unsnip.













More information about the Rwp mailing list