Quote:
Originally Posted by SmoothBro
If you can, download AVLinux 6.03. It's not 64bit, but has a PAE kernel which is supposed to allow you to use all of your memory. Once you put it on a live DVD, boot it up and see if you can connect Jack to your soundcard. If so, register wineasio (in the 'Audio utilities' folder) then install Reaper and run. See if you can access wineasio from Reaper. If so, I would be sure it's a 32bit vs 64bit problem as was said earlier.
|
Thanks, SmoothBro, I did try it with AVLinux, as you suggested and it worked instantly.
I spend a little time to re-setup ubuntu (14.04.01 64-bit still) now focusing more on not mixing up 64-bit and 32-bit.
So I installed wine running: apt-get install wine1.6-amd64
Installed wineasio in 64-bit from the kxstudio-repositories and registered that.
Only I don't know about Jack. I simply got that through: apt-get install jackd
Unfortunately Reaper still doesn't work with Asio.
BUT:
With Jack started, running Reaper and there opening the audio preferences and chosing ASIO, a message shows up in Jack's log, telling:
ERROR: Cannot read socket fd = 17 err = No such file or directory
ERROR: Unknown request 0
I searched for explanation of that message but couldn't find anything.
This could probably again be an issue of running 64bit/32bit, as Jack Winter assumed earlier (?):
Quote:
Originally Posted by Jack Winter
I think quite possibly it's a question of 32 vs 64bit? If your linux is 64b and you try to run 32b wineasio it will need 32b jack client libs. Might be called something like libjack0:i386 or lib32-jack, etc (depending on distro). Note that 64b reaper works fine in 64b wine..
To clarify something, wineasio has absolutely nothing to do with winecfg, as it talks directly to jack. If the above assumption is correct, then 32b wineasio would talk to the 32b jack client libs, which would use shared mem to communicate with the 64b jack server. There are also a couple of registry entries (and iirc environment variables) that can make wineasio start the jack server if it's not already running.
|
Can someone tell about that error messages? Does it point me to some missing (i386-)libraries or something?
Could it be a problem with Jack being 32-bit (?) or is it in 64-bit automatically by installing it from a 64-bit machine? Sorry, I don't have any clue, yet...
Maybe I did some things wrong in the installation process as described above?
Any suggestions are much apreciated! Thanks!