Reaper under 4.2

[danboid]

I'm having difficulty getting Reaper working as well under 4.2 as it did under 4.1 - under 4.2 its being very temperamental.

First off - GMaq - have you still got a wine 1.3.2 package you could upload to your package archive for me to try? That brings me nicely onto my second question with all this in that when I compile wine myself (like I have just done with 1.3.11) I cannot get wineasio to work properly. The wineasio option in the audio menu doesn't work against my custom wine build so instead I have to run:

regsvr32 /usr/lib/wine/wineasio.dll.so

Which tells me its successfully registered the lib but then when I start reaper and choose ASIO for the sound driver both the boxes (first and last) for both Input and Output are empty. Am I just compiling wine with the wrong prefix? How do you compile wine gmaq? I've just being doing good ol' 'configure; make; make install' basically and as I've said in the 4.2 announcement thread I'll be damned if I can find the asio-sdk required to recompile wineasio.

Am I right in thinking that I won't be able to use a frequency higher than 48Khz when using audio apps under wine? It'd be a shame if thats the case as we do most of our recording at 96Khz.

Heres roughly the cycle I've been going through with testing different versions of wine against reaper 3.74:

rm -rf ~/.wine
apt-get(/aptitude) remove wine
dpkg -i wine-versionblah.deb
winecfg -> Audio Tab -> Choose 48000 for default sample rate -> Apply/OK (not sure this step is really necessary)
wine reaper374-install.exe
register wineasio.dll
start JACK at 48Khz
Run reaper, say yes to selecting audio device
Choose ASIO for audio device/ Wine ASIO driver
Change request sample rate to 48000 and tick box to left (not sure if this step is necessary either?)

I then normally quit reaper and reload it to make sure its using my chosen settings, add a new MIDI item and VSTi (like Crystal) to a track, open the MIDI editor and push some of the keys displayed on the left of the MIDI editor and if I'm lucky I'll get some sound but most of the time thats not what happens. Maybe I should use and older version of Reaper?

I'd love to hear from anyone who's got Reaper running well under 4.2 who can explain where I'm going wrong or what the best combo of wine + reaper versions is. God forbid I end up having to dual-boot with real windows!

Thanks!

[GMaq]

danboid,

I'll look into it, Reaper as you must know, like Ardour-VST is a real pass-with-a-push proposition in Linux, they are offered as a convenience, you are actually the first person to even mention the "R" word here, New Kernels, new Wines, new ffado, various hardwares with differing performance issues, various Windows VST plugins ... I'm started to get buried in Wine related complaints here and there is no magic-bullet fix that will just work for everyone.

I have always used Ardour-VST myself and thought if an ape like me could get it up and running perhaps I should share it, same with Reaper, but I am re-thinking everything but fst-VST support from now on...I'll redo a Wine 1.3.2 package and put it up in the next day or two and you can see how it goes. I simply can't troubleshoot all this Wine related stuff, there are just not enough hours in the day and no relief because everyone's system is different.

[danboid]

Gmaq

Of course I'm fully aware there are never any guarantees anything will work where wine is involved so I eagerly await the day A3 stabilises and we have some good LV2 softsynths to use with it- I just thought it was best to ask here before taking my woes to the Reaper forum but I'm not confident they'd really be able or bothered about helping.

Thanks for uploading 1.3.2 for me for testing but could you please explain how you build (not package) wine and where you download the asio-sdk after you've signed up and logged in with a Steinberg account please in case I also need to rebuild wineasio?

Thanks!

[GMaq]

@danboid

I test and run Reaper and give it a cursory look before each release, I have to fess up to not extensively testing the MIDI though, I tested it a few versions ago and found the MIDI aspect of Reaper to be quite unstable with JACK with lots of random freeze ups. It would seem to me the Reaper Audio engine is quite Wine friendly...MIDI not so much.

re: Wine,

No special magic really...

Code:

./configure --prefix=/usr --disable-tests --enable-maintainer-mode

then:

Code:

make

then as Root:

Code:

checkinstall -D

if you want a package...OR of course:

Code:

make install

if you just want to install it

[GMaq]

OK,

Here is the Wine package, remember to uninstall your existing version first if you are downgrading: http://www.bandshed.net/checkinstall/wine_1.3.2avlinux-2_i386.deb

WRT the Steinberg asio-sdk PM me and we'll see if we can figure something out.

[rcurtiss]

I was having a lot of trouble figuring out the midi end as well, but stumbled on the simple solution.

1) Open winecfg and choose the audio tab.
2) ONLY check the box next to ALSA
3) apply the changes and exit winecfg
4) open reaper and open the options>>preferences menu and find MIDI Devices under Audio
5) Configure your inputs by double-clicking on the input you want
6) check the box next to "Enable input from this device" and click "ok"
7) click "apply" in the lower right of the preferences pane and then click "ok"
8) exit reaper and open your winecfg again. This time also check the box next to Jack
9) start your Jack server and open reaper again.
10) Your midi devices should still be there and enabled.

In short, ALSA needs to show reaper the MIDI ports before you start messing with Jack altogether.
I don't know why, I just traced my steps back and instead of setting up the Jack output first, I started with the MIDI and all was stable.
I re-tried this over several boots of the live-cd and it was still responding better when I started with the MIDI and went forward from there.
Hope this helps.

-Randy Curtiss

[GMaq]

Thanks for sharing that info.

[wyeth]

There is a specific reaper/linux topic  http://forum.cockos.com/showthread.php?t=26690

I use reaper  sometimes, but have never marked the winecfg box for jack, just the alsa box. I have
read that in the past, wine itself made little or no use of jackd, beyond presenting wineasio to things that do, and that in some instances, having both marked, may create an odd problem. Don't know if wine uses jackd2
for anything or not. For some time now, reaper has autoconnected to jackd, and accepted routing to other jackd inputs.

(my video old videocard was unsupported by any debian, so no AVlinux, now I will try again later this week with
a new card, and 4.2. )