Trying to get Reaper running with wineasio

  • wendalltan
Posted: Mon, 01/19/2009 - 16:03
Hi everyone, I converted to Linux a couple years ago and have not yet found an acceptible replacement for my old Windows audio studio. I'm hoping 64 Studio will solve this. My hope is to run Reaper through wine and wineasio, and take advantage of Jack and low latency in Linux while still having access to some of my windows VST instruments that I enjoy. I'm following the instructions at http://www.64studio.com/node/636, but the debian repository http://apt.harleystudio.co.za/ etch main does not appear to be available. Wineasio is not available through synaptic or apt-get. I tried to download wineasio-x, but that doesn't seem to do the trick (when I run the regsvr32 wineasio.dll command, I get this error message: Failed to load DLL wineasio.dll Is there a different repository I should use to get wineasio? Any help in getting me past that point in the tutorial above would be greatly appreciated.

thanks you got it

  • wendalltan
  • 01/19/09
  • Tue, 01/27/2009 - 03:19
D'oh! I had plugged in an old oxygen 8 midi controller after I'd set up Jack and Reaper and now Jack wants to use it as the Default device. Setting the device explicitly to my audio card fixed everything. Can't wait to take this for a spin. Thanks everyone for your huge help.

Hi! Go for 2 frames/period

  • Pablo
  • 07/11/07
  • Mon, 01/26/2009 - 21:14
Hi! Go for 2 frames/period (n value). You seem to have n=4. However, this might not be the only setup value that is wrong. Have you got more than one audio card, maybe an onboard audio card? Sometimes ALSA gives different numbers to the available cards. You have an arrow on the right of "interface" in qjackctl. Check that. To solve this and give consistent numbers to your audio cards follow the FAQ. You can type "cat /proc/asound/cards" and "cat /proc/asound/modules" to know about your cards and modules. Make your main card number 0. Anyway, if you have an onboard audio card, and you won't use it at all, the best thing you can do is to disable it in the BIOS. Good to hear you have Reaper up and running. By the way, you have the "amd64" version, don't you? I've got the i686 (32 bit). I don't need to start jackbridge. But for you want to do... I think you can't run VST instruments through Reaper with the amd64 version. Regards. Pablo

Thanks

  • wendalltan
  • 01/19/09
  • Mon, 01/26/2009 - 15:35
That worked! My apologies for missing that step in the instructions. Unfortunately it only worked twice, and now whenever I start Jack using qjackctrl, I get this in the error message: Could not connect to JACK server as client. Please check the messages window for more info. I don't think I've changed anything in the jack settings or sound card, so I'm not sure why this has started happening. Any ideas on what's wrong would be a great help. Here is the output of the Messages in qjackctl: 07:20:41.662 Patchbay deactivated. 07:20:41.729 Statistics reset. JACK tmpdir identified as [/dev/shm] 07:20:41.812 MIDI connection graph change. 07:20:41.983 MIDI connection change. 07:20:43.908 Startup script... 07:20:43.908 artsshell -q terminate JACK tmpdir identified as [/dev/shm] can't create mcop directory Creating link /home/wendall/.kde/socket-64studio. 07:20:44.607 Startup script terminated with exit status=256. 07:20:44.607 JACK is starting... 07:20:44.608 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p128 -n4 07:20:44.612 JACK was started with PID=4655 (0x122f). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Enhanced3DNow! detected SSE2 detected apparent rate = 44100 creating alsa driver ... hw:0|hw:0|128|4|44100|0|0|nomon|swmeter|-|32bit control device hw:0 ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode cannot load driver module alsa no message buffer overruns 07:20:44.759 JACK was stopped successfully. 07:20:44.759 Post-shutdown script... 07:20:44.760 killall jackd jackd: no process killed 07:20:44.990 Post-shutdown script terminated with exit status=256. 07:20:46.633 Could not connect to JACK server as client. Please check the messages window for more info. JACK tmpdir identified as [/dev/shm]

Jackbridge

  • Quentin Harley
  • 05/24/07
  • Fri, 01/23/2009 - 23:51
Did you start jackbridge befor you attempted your Reaper session?

thanks

  • wendalltan
  • 01/19/09
  • Fri, 01/23/2009 - 16:36
Hi and thanks for the reply. I'm guessing my Jack setup is alright, I can launch other native linux audio apps like Hydrogen and see it pop up as a source using qjackctl and hitting the Connect button to get to the patch bay. However, when I open Reaper, I get the message: There was an error opening your audio hardware: Error initializing ASIO driver Would you like to view your audio device configuration? Hitting yes there goes to the audio device config, ASIO is selected, Wine ASIO Drive is selected as ASIO type, the inputs and outputs drop-down menus are empty, clicking the ASIO config button doesn't do anything (I don't think it ever does, though, even when running properly on wine). On my qjackctl preferences setting I have this set up: realtime on I've tried both on and off for the following items: Monitor, HW Monitor, SW Monitor 1024 frames/period 44100 sample rate 2 periods/buffers 256 port maximum 500 ms timeout everything else is pretty well set to jack defaults on the prefs. It seems like the ASIO driver is having a hard time. I plan to try to download a different wine-friendly audio app today and test to see if it's Reaper having a problem with wineasio or if it's somewhere upstream from there. As always, any ideas are always welcome. Thanks for the help so far!

Re: Trying to get Reaper running with wineasio

  • Pablo
  • 07/11/07
  • Thu, 01/22/2009 - 22:42
Hi wendalltan, "I should see some Wave In and Wave Out devices here on this tab as well, but there are none" Don't worry about this, jackd will take care of the audio signals. "Also, when running winecfg from the command line, I still see the error: fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96, disabling mixer" I've got the same card and the same "fixme". I don't know the reason behind this message but I don't worry about it. Again, you will use jackd for audio. By the way, to control this card you should use envy24control, not alsamixer. What you need to do is to start JACK Control (from the menu or by typing qjackctl in the terminal). Make sure the setup is OK and it runs stable. Then start REAPER and go to the Preferences -> Audio Device and choose Audio:ASIO and ASIO: Wine ASIO driver. You should see then the ASIO_reaper connections in the "connect" window of Jack control, audio tab. You will have to make the proper connections (by selecting and clicking the connect button). I hope this helps you get started. There are other alternatives for using VST instrument in Linux. Mine is dssi-vst but there are more. For the moment, let's hope you can get Reaper up and running! Cheers. Pablo

thanks

  • wendalltan
  • 01/19/09
  • Tue, 01/20/2009 - 00:08
thanks for the updated link. I'm able to get wineasio off that repository. After downloading wine and wineasio, I open winecfg and go to the audio tab. I get this message: There is no audio driver currently specified in the registry. A recommended driver has been selected for you. You can use this driver or select another driver if available. This takes me to the Audio tab in winecfg, which has Alsa already checked with the following subitems: Midi Out Devices
Midi Through Port-0
M Audio Audiophile 24/96 MIDI
Midi In Devices
Midi Through Port-0
M Audio Audiophile 24/96 MIDI
I should see some Wave In and Wave Out devices here on this tab as well, but there are none. Also, when running winecfg from the command line, I still see the error: fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96, disabling mixer All these things are identical to the symptoms when I compiled wineasio-64 myself on a previous 64 studio install, even though I'm now using the wineasio supplied by Mr. Quentin Harley (thanks). Is there something I'm missing to getting the digital audio portion of my sound card working with wineasio? Any help is again greatly appreciated.

Repository link...

  • Quentin Harley
  • 05/24/07
  • Mon, 01/19/2009 - 22:03
I added a new temporary link to the repository. deb http://www.harleystudio.co.za/apt/ etch main Hope it helps! Q

My Bad...

  • Quentin Harley
  • 05/24/07
  • Mon, 01/19/2009 - 21:43
My apt repository went down without me noticing... Working on it and it should be up soon(ish) Will let you know. Try runing winecfg before running jackbridge. Cheers, Quentin

update

  • wendalltan
  • 01/19/09
  • Mon, 01/19/2009 - 19:54
I've re-installed 64 studio and gotten a bit further with this. I was still unable to get wineasio from the repositories, so I compiled and installed wineasio-64, and am able to run the regsvr32 command and can run jackbridge and the system seems happy. But when I launch winecfg, I get this error: fixme:mixer:ALSA_MixerInit No master control found on M Audio Audiophile 24/96, disabling mixer The Audio tab on winecfg shows only Alsa, which is checked, but there are no audio in's or out's-- only MIDI is available. I've seen references to this around, but no solutions yet. Please let me know if anyone knows how to get this working. Thanks!