Trouble getting Reaper working

Unofficial support for the KXStudio Linux distribution and applications.
More info at http://kxstudio.linuxaudio.org/

Moderators: MattKingUSA, khz

hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Trouble getting Reaper working

Post by hebjuzeb »

New install of KXStudio 12.04.1 64-bit via DVD-RW.

- Updated with install

- Restarted, added self to audio group, restarted again, ran welcome screen, force reset of all settings, logged out & in. Ran command "wine64 regsvr32 wineasio.dll" to register WINEAsio.

- Set up JACK via Cadence: i04 as input, selected 2 channels (the i04 has the option for 4 @ 16-bit, or 2 @ 24-bit, I use 2.) Set to 256 frames, 44100.

- Started Reaper, did Audio / Uncheck "close audio device when stopped and application is inactive."

- Chose ASIO as device, all good, relevant fields filled in automatically, 256 frames, 44100 as in JACK.

- Created a track, armed, got 2 seconds of signal, tons of x-runs, (Cadence registering hundreds of them, going through the roof.) At this point JACK doesn't respond at all, won't even turn off. Go to log out, cancelled by Cadence, shut down system and get [series of numbers] URB status -32

Then it's just blackscreen while the URB messages scroll down the screen. Tried a few times, with JACK errors all the way, often at stages where everything was fine before. [EDIT: Ran welcome screen and force-reset settings + logout for every try.]

I did all of this the same way on another machine but with Ubuntu Studio as base (32-bit) and it works fine, even seems more forgiving at low frame-sizes. Guess I could do the same setup on my main machine but that's several more hours of setup, plus I really prefer KDE to XFCE.

Anyway, thanks for reading,
h.
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
manic_b
Established Member
Posts: 48
Joined: Thu Aug 09, 2012 9:39 pm

Re: Trouble getting Reaper working

Post by manic_b »

A bit of an infodump, but here is my (working) Cadence/JACK setup
Attachments
cadence3.png
cadence3.png (66.94 KiB) Viewed 2045 times
cadence2.png
cadence2.png (55.49 KiB) Viewed 2045 times
cadence1.png
cadence1.png (68.87 KiB) Viewed 2045 times
manic_b
Established Member
Posts: 48
Joined: Thu Aug 09, 2012 9:39 pm

Re: Trouble getting Reaper working

Post by manic_b »

Assuming nothing useful there... have you tried using a massive buffer size? How does that affect it?
hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Re: Trouble getting Reaper working

Post by hebjuzeb »

manic_b wrote:Assuming nothing useful there... have you tried using a massive buffer size? How does that affect it?
Well I couldn't fix it, but the info is still useful for troubleshooting, much obliged. I copied your setting exactly, but got the same result: 2 seconds of static, x-runs coming in about 12 at a time, JACK won't stop, and I get the beginning of a Cadence warning window. Then the warning window itself crashes (now, there's a dream come true) without writing any text in the box.

Seeing as you're running a generic kernel, obviously you added PPAs to an existing distro . . . I know there are errors in 2 files of the KX iso and others have told me their isos work fine, but it makes me wonder. Maybe the errors affect some machines, but not others?

Thanks,
h,
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
danboid
Established Member
Posts: 1327
Joined: Sun Aug 26, 2012 11:28 am
Location: England
Has thanked: 1 time
Been thanked: 4 times

Re: Trouble getting Reaper working

Post by danboid »

heb:

AFAIK the reaper inclided with KX is the 32 bit build but you've used the 64-bit wineasio registration command - but wineasio is working? Odd. You should only need to run

regsvr32 wineasio.dll

To run 32-bit wineasio apps like Reaper. You do include the 32bit REAPER with 64-bit KX too right F?

Do you get stacks of xruns when you try recording under qtractor or Ardour or any native JACK app?
hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Re: Trouble getting Reaper working

Post by hebjuzeb »

Hey Dan,

Tried registering 32-bit WINE, got the same result, ending in "The window "Cadence" is not responding. It belongs to the application cadence.py (Process ID = 1798, hostname = localhost)." Restarted, got several minutes of URB status -32 before it would shut down.

I've never used Ardour or Qtraktor . . . Wolftune has some sage advice for situations like these, which is to go for a walk. :wink:

I'll run some errands and give it a try,

Thanks,
h.
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
nils
Established Member
Posts: 541
Joined: Wed Oct 22, 2008 9:05 pm
Has thanked: 35 times
Been thanked: 95 times
Contact:

Re: Trouble getting Reaper working

Post by nils »

Reaper is windows software. The best way to use it is to install and use it on Windows.
hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Re: Trouble getting Reaper working

Post by hebjuzeb »

NilsGey wrote:Reaper is windows software. The best way to use it is to install and use it on Windows.
Yeah, I'm aware of that. There are sometimes issues though . . . Windows has dozens of programs, many useful only for large corporations, running in the background all the time. If you're running CPU-intensive software on an underpowered machine, this sets off the inexplicable CPU-throttling that Intel uses. And if you're dumb enough to buy an Acer (like I was) they're so terrified of any extra heat melting their POS motherboards that they lock you out of the BIOS for this and pretty much all other tweaks.

Anyway, for whatever reason, I want to run Reaper in Linux.
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Re: Trouble getting Reaper working

Post by hebjuzeb »

Tried again using 32-bit, this time JACK failed on restart after configuration. The logs are thousands of characters, included a page worth for posterity. I'm outta here.

Mon Apr 1 19:26:26 2013: Connecting 'alsa2jack:capture_1' to 'system:playback_1'
Mon Apr 1 19:26:26 2013: Connecting 'alsa2jack:capture_2' to 'system:playback_2'
Mon Apr 1 19:26:27 2013: Connecting 'system:capture_1' to 'jack2alsa:playback_1'
Mon Apr 1 19:26:27 2013: Connecting 'system:capture_2' to 'jack2alsa:playback_2'
Mon Apr 1 19:27:04 2013: Saving settings to "/home/yngwie/.config/jack/conf.xml" ...
Mon Apr 1 19:27:18 2013: Saving settings to "/home/yngwie/.config/jack/conf.xml" ...
Mon Apr 1 19:27:19 2013: Stopping jack server...
Mon Apr 1 19:27:19 2013: Client 'system' with PID 0 is out
Mon Apr 1 19:27:19 2013: Client 'cadence-aloop-daemon' with PID 4617 is out
Mon Apr 1 19:27:19 2013: Client 'alsa2jack' with PID 4624 is out
Mon Apr 1 19:27:19 2013: Client 'jack2alsa' with PID 4625 is out
Mon Apr 1 19:27:19 2013: Client 'a2j' with PID 4578 is out
Mon Apr 1 19:27:19 2013: Released audio card Audio0
Mon Apr 1 19:27:21 2013: Starting jack server...
Mon Apr 1 19:27:21 2013: JACK server starting in realtime mode with priority 85
Mon Apr 1 19:27:21 2013: Acquired audio card Audio2
Mon Apr 1 19:27:21 2013: creating alsa driver ... hw:iO4,0|hw:iO4,0|256|2|44100|0|0|nomon|swmeter|-|32bit
Mon Apr 1 19:27:21 2013: Using ALSA driver USB-Audio running on card 2 - Alesis iO4 at usb-0000:00:1d.0-1.1, full speed
Mon Apr 1 19:27:21 2013: configuring for 44100Hz, period = 256 frames (5.8 ms), buffer = 2 periods
Mon Apr 1 19:27:21 2013: ALSA: final selected sample format for capture: 24bit little-endian
Mon Apr 1 19:27:21 2013: ALSA: use 2 periods for capture
Mon Apr 1 19:27:21 2013: ERROR: ALSA: cannot set hardware parameters for capture
Mon Apr 1 19:27:21 2013: ERROR: ALSA: cannot configure capture channel
Mon Apr 1 19:27:21 2013: ERROR: Cannot initialize driver
Mon Apr 1 19:27:21 2013: ERROR: JackServer::Open failed with -1
Mon Apr 1 19:27:21 2013: ERROR: Failed to open server
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
skavar
Established Member
Posts: 97
Joined: Sat Sep 15, 2012 9:21 am

Re: Trouble getting Reaper working

Post by skavar »

Its an alsa error. Try 3 periods instead of 2
manic_b
Established Member
Posts: 48
Joined: Thu Aug 09, 2012 9:39 pm

Re: Trouble getting Reaper working

Post by manic_b »

Interesting that there's nothing about WINEASIO in there at all. Can you find a bit about WINEASIO for us?
ToddMWorth
Established Member
Posts: 225
Joined: Tue Oct 23, 2012 3:59 am

Re: Trouble getting Reaper working

Post by ToddMWorth »

skavar wrote:Its an alsa error. Try 3 periods instead of 2
Also, 256 frames may be adventurous for testing. Take it back to one of the supported USB interface frame sizes (see other thread on here) closer to the default 1024.
hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Re: Trouble getting Reaper working

Post by hebjuzeb »

Hey guys,

Thanks for all the help; things are getting weird . . . since last time,

-re-installed 64-bit to try suggestions. Did everything the same, but
a) registered 32-bit wine, as per Reaper install (thanks Dan.)
b) switched to 3 periods (thanks Manic.)
c) stayed at 1024 frames (thanks Todd.)

Results the same: get 2 seconds of signal, escalating x-runs, then no signal, Jack won't stop, Cadence won't quit, warning screen crashes.
Would have posted logs, but the network manager has gone berserk: sometimes asks for wallet, sometimes asks for authorisation, icon shows "connected," manager toggles between "waiting for authorization" and "configuring." Eventually the icon reds-out. (I gather this is a known KDE bug, perhaps totally unrelated to the install.)

[A little later . . .]

So I tried using the live session from my USB (Unetbootin with persistance.) Noticed a few things right away; everything goes much faster (programs starting, etc.), wireless starts right away without asking for authorisation, no "urb status -32" screens on logout. Had my hopes up, but Reaper acted exactly the same as before. I'll try QTractor in a bit, but here are the logs:

Tue Apr 2 18:49:00 2013: ------------------
Tue Apr 2 18:49:00 2013: Controller activated. Version 1.9.9.5 (unknown) built on Sat Dec 22 18:50:40 2012
Tue Apr 2 18:49:00 2013: Loading settings from "/home/kxstudio/.config/jack/conf.xml" using expat_2.0.1 ...
Tue Apr 2 18:49:00 2013: setting parameter 'engine':'driver':'(null)' to value "alsa"
Tue Apr 2 18:49:00 2013: setting parameter 'engine':'realtime':'(null)' to value "true"
Tue Apr 2 18:49:00 2013: setting parameter 'engine':'realtime-priority':'(null)' to value "85"
Tue Apr 2 18:49:00 2013: setting parameter 'drivers':'alsa':'rate' to value "44100"
Tue Apr 2 18:49:00 2013: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Tue Apr 2 18:49:00 2013: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Tue Apr 2 18:49:00 2013: Listening for D-Bus messages
Tue Apr 2 18:49:00 2013: Starting jack server...
Tue Apr 2 18:49:00 2013: JACK server starting in realtime mode with priority 85
Tue Apr 2 18:49:00 2013: Acquired audio card Audio0
Tue Apr 2 18:49:00 2013: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Tue Apr 2 18:49:00 2013: Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xb4400000 irq 42
Tue Apr 2 18:49:00 2013: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Tue Apr 2 18:49:00 2013: ALSA: final selected sample format for capture: 32bit integer little-endian
Tue Apr 2 18:49:00 2013: ALSA: use 2 periods for capture
Tue Apr 2 18:49:00 2013: ALSA: final selected sample format for playback: 32bit integer little-endian
Tue Apr 2 18:49:00 2013: ALSA: use 2 periods for playback
Tue Apr 2 18:49:00 2013: graph reorder: new port 'system:capture_1'
Tue Apr 2 18:49:00 2013: New client 'system' with PID 0
Tue Apr 2 18:49:00 2013: graph reorder: new port 'system:capture_2'
Tue Apr 2 18:49:00 2013: graph reorder: new port 'system:playback_1'
Tue Apr 2 18:49:00 2013: graph reorder: new port 'system:playback_2'
Tue Apr 2 18:49:00 2013: New client 'cadence-aloop-daemon' with PID 5948
Tue Apr 2 18:49:01 2013: New client 'jack2alsa' with PID 5955
Tue Apr 2 18:49:01 2013: New client 'alsa2jack' with PID 5954
Tue Apr 2 18:49:01 2013: port 'jack2alsa:playback_1' created
Tue Apr 2 18:49:01 2013: port 'jack2alsa:playback_2' created
Tue Apr 2 18:49:01 2013: port 'alsa2jack:capture_1' created
Tue Apr 2 18:49:01 2013: port 'alsa2jack:capture_2' created
Tue Apr 2 18:49:01 2013: New client 'a2j' with PID 5939
Tue Apr 2 18:49:01 2013: port 'a2j:Midi Through [14] (capture): Midi Through Port-0' created
Tue Apr 2 18:49:01 2013: port 'a2j:Midi Through [14] (playback): Midi Through Port-0' created
Tue Apr 2 18:49:01 2013: Connecting 'alsa2jack:capture_1' to 'system:playback_1'
Tue Apr 2 18:49:01 2013: Connecting 'alsa2jack:capture_2' to 'system:playback_2'
Tue Apr 2 18:49:02 2013: Connecting 'system:capture_1' to 'jack2alsa:playback_1'
Tue Apr 2 18:49:02 2013: Connecting 'system:capture_2' to 'jack2alsa:playback_2'
Wed Apr 3 01:51:32 2013: Disconnecting 'system:capture_1' from 'jack2alsa:playback_1'
Wed Apr 3 01:51:32 2013: Disconnecting 'system:capture_2' from 'jack2alsa:playback_2'
Wed Apr 3 01:51:32 2013: Disconnecting 'alsa2jack:capture_1' from 'system:playback_1'
Wed Apr 3 01:51:32 2013: Disconnecting 'alsa2jack:capture_2' from 'system:playback_2'
Wed Apr 3 01:51:32 2013: ERROR: Failed to find port 'jack2alsa:playback_1' to destroy
Wed Apr 3 01:51:32 2013: ERROR: Failed to find port 'jack2alsa:playback_2' to destroy
Wed Apr 3 01:51:32 2013: Client 'jack2alsa' with PID 5955 is out
Wed Apr 3 01:51:32 2013: ERROR: Cannot write socket fd = 17 err = Broken pipe
Wed Apr 3 01:51:32 2013: ERROR: CheckRes error
Wed Apr 3 01:51:32 2013: ERROR: Could not write notification
Wed Apr 3 01:51:32 2013: ERROR: NotifyClient fails name = jack2alsa notification = 1 val1 = 0 val2 = 0
Wed Apr 3 01:51:32 2013: ERROR: Failed to find port 'alsa2jack:capture_1' to destroy
Wed Apr 3 01:51:32 2013: ERROR: Failed to find port 'alsa2jack:capture_2' to destroy
Wed Apr 3 01:51:32 2013: Client 'alsa2jack' with PID 5954 is out
Wed Apr 3 01:51:33 2013: Client 'a2j' with PID 5939 is out
Wed Apr 3 01:51:33 2013: Client 'cadence-aloop-daemon' with PID 5948 is out
Tue Apr 2 19:16:27 2013: ------------------
Tue Apr 2 19:16:27 2013: Controller activated. Version 1.9.9.5 (unknown) built on Sat Dec 22 10:50:40 2012
Tue Apr 2 19:16:28 2013: Loading settings from "/home/kxstudio/.config/jack/conf.xml" using expat_2.0.1 ...
Tue Apr 2 19:16:28 2013: setting parameter 'engine':'driver':'(null)' to value "alsa"
Tue Apr 2 19:16:28 2013: setting parameter 'engine':'realtime':'(null)' to value "true"
Tue Apr 2 19:16:28 2013: setting parameter 'engine':'realtime-priority':'(null)' to value "85"
Tue Apr 2 19:16:28 2013: setting parameter 'drivers':'alsa':'rate' to value "44100"
Tue Apr 2 19:16:28 2013: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Tue Apr 2 19:16:28 2013: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Tue Apr 2 19:16:28 2013: Listening for D-Bus messages
Tue Apr 2 19:16:28 2013: Starting jack server...
Tue Apr 2 19:16:28 2013: JACK server starting in realtime mode with priority 85
Tue Apr 2 19:16:28 2013: Acquired audio card Audio0
Tue Apr 2 19:16:28 2013: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Tue Apr 2 19:16:28 2013: Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xb4400000 irq 43
Tue Apr 2 19:16:28 2013: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Tue Apr 2 19:16:28 2013: ALSA: final selected sample format for capture: 32bit integer little-endian
Tue Apr 2 19:16:28 2013: ALSA: use 2 periods for capture
Tue Apr 2 19:16:28 2013: ALSA: final selected sample format for playback: 32bit integer little-endian
Tue Apr 2 19:16:28 2013: ALSA: use 2 periods for playback
Tue Apr 2 19:16:28 2013: graph reorder: new port 'system:capture_1'
Tue Apr 2 19:16:28 2013: New client 'system' with PID 0
Tue Apr 2 19:16:28 2013: graph reorder: new port 'system:capture_2'
Tue Apr 2 19:16:28 2013: graph reorder: new port 'system:playback_1'
Tue Apr 2 19:16:28 2013: graph reorder: new port 'system:playback_2'
Tue Apr 2 19:16:28 2013: New client 'cadence-aloop-daemon' with PID 5913
Tue Apr 2 19:16:28 2013: New client 'alsa2jack' with PID 5917
Tue Apr 2 19:16:28 2013: New client 'jack2alsa' with PID 5918
Tue Apr 2 19:16:28 2013: port 'jack2alsa:playback_1' created
Tue Apr 2 19:16:28 2013: port 'jack2alsa:playback_2' created
Tue Apr 2 19:16:28 2013: port 'alsa2jack:capture_1' created
Tue Apr 2 19:16:28 2013: port 'alsa2jack:capture_2' created
Tue Apr 2 19:16:29 2013: New client 'a2j' with PID 5877
Tue Apr 2 19:16:29 2013: port 'a2j:Midi Through [14] (capture): Midi Through Port-0' created
Tue Apr 2 19:16:29 2013: port 'a2j:Midi Through [14] (playback): Midi Through Port-0' created
Tue Apr 2 19:16:29 2013: Connecting 'alsa2jack:capture_1' to 'system:playback_1'
Tue Apr 2 19:16:29 2013: Connecting 'alsa2jack:capture_2' to 'system:playback_2'
Tue Apr 2 19:16:30 2013: Connecting 'system:capture_1' to 'jack2alsa:playback_1'
Tue Apr 2 19:16:30 2013: Connecting 'system:capture_2' to 'jack2alsa:playback_2'
Tue Apr 2 20:20:26 2013: ------------------
Tue Apr 2 20:20:26 2013: Controller activated. Version 1.9.9.5 (unknown) built on Sat Dec 22 10:50:40 2012
Tue Apr 2 20:20:27 2013: Loading settings from "/home/kxstudio/.config/jack/conf.xml" using expat_2.0.1 ...
Tue Apr 2 20:20:27 2013: setting parameter 'engine':'driver':'(null)' to value "alsa"
Tue Apr 2 20:20:27 2013: setting parameter 'engine':'realtime':'(null)' to value "true"
Tue Apr 2 20:20:27 2013: setting parameter 'engine':'realtime-priority':'(null)' to value "85"
Tue Apr 2 20:20:27 2013: setting parameter 'drivers':'alsa':'rate' to value "44100"
Tue Apr 2 20:20:27 2013: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Tue Apr 2 20:20:27 2013: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Tue Apr 2 20:20:27 2013: Listening for D-Bus messages
Tue Apr 2 20:20:27 2013: Starting jack server...
Tue Apr 2 20:20:27 2013: JACK server starting in realtime mode with priority 85
Tue Apr 2 20:20:27 2013: Acquired audio card Audio0
Tue Apr 2 20:20:27 2013: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Tue Apr 2 20:20:27 2013: Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xb4400000 irq 42
Tue Apr 2 20:20:27 2013: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Tue Apr 2 20:20:27 2013: ALSA: final selected sample format for capture: 32bit integer little-endian
Tue Apr 2 20:20:27 2013: ALSA: use 2 periods for capture
Tue Apr 2 20:20:27 2013: ALSA: final selected sample format for playback: 32bit integer little-endian
Tue Apr 2 20:20:27 2013: ALSA: use 2 periods for playback
Tue Apr 2 20:20:27 2013: graph reorder: new port 'system:capture_1'
Tue Apr 2 20:20:27 2013: New client 'system' with PID 0
Tue Apr 2 20:20:27 2013: graph reorder: new port 'system:capture_2'
Tue Apr 2 20:20:27 2013: graph reorder: new port 'system:playback_1'
Tue Apr 2 20:20:27 2013: graph reorder: new port 'system:playback_2'
Tue Apr 2 20:20:28 2013: New client 'cadence-aloop-daemon' with PID 5933
Tue Apr 2 20:20:28 2013: New client 'a2j' with PID 5903
Tue Apr 2 20:20:28 2013: New client 'alsa2jack' with PID 5937
Tue Apr 2 20:20:28 2013: New client 'jack2alsa' with PID 5938
Tue Apr 2 20:20:28 2013: port 'a2j:Midi Through [14] (capture): Midi Through Port-0' created
Tue Apr 2 20:20:28 2013: port 'a2j:Midi Through [14] (playback): Midi Through Port-0' created
Tue Apr 2 20:20:28 2013: port 'a2j:iO4 [24] (capture): iO4 MIDI 1' created
Tue Apr 2 20:20:28 2013: port 'a2j:iO4 [24] (playback): iO4 MIDI 1' created
Tue Apr 2 20:20:28 2013: port 'alsa2jack:capture_1' created
Tue Apr 2 20:20:28 2013: port 'alsa2jack:capture_2' created
Tue Apr 2 20:20:28 2013: port 'jack2alsa:playback_1' created
Tue Apr 2 20:20:28 2013: port 'jack2alsa:playback_2' created
Tue Apr 2 20:20:29 2013: Connecting 'alsa2jack:capture_1' to 'system:playback_1'
Tue Apr 2 20:20:29 2013: Connecting 'alsa2jack:capture_2' to 'system:playback_2'
Tue Apr 2 20:20:30 2013: Connecting 'system:capture_1' to 'jack2alsa:playback_1'
Tue Apr 2 20:20:30 2013: Connecting 'system:capture_2' to 'jack2alsa:playback_2'
Tue Apr 2 20:30:58 2013: ------------------
Tue Apr 2 20:30:58 2013: Controller activated. Version 1.9.9.5 (unknown) built on Sat Dec 22 10:50:40 2012
Tue Apr 2 20:30:58 2013: Loading settings from "/home/kxstudio/.config/jack/conf.xml" using expat_2.0.1 ...
Tue Apr 2 20:30:58 2013: setting parameter 'engine':'driver':'(null)' to value "alsa"
Tue Apr 2 20:30:58 2013: setting parameter 'engine':'realtime':'(null)' to value "true"
Tue Apr 2 20:30:58 2013: setting parameter 'engine':'realtime-priority':'(null)' to value "85"
Tue Apr 2 20:30:58 2013: setting parameter 'drivers':'alsa':'rate' to value "44100"
Tue Apr 2 20:30:58 2013: setting parameter 'drivers':'alsa':'nperiods' to value "2"
Tue Apr 2 20:30:58 2013: setting parameter 'drivers':'alsa':'hw-alias' to value "true"
Tue Apr 2 20:30:58 2013: Listening for D-Bus messages
Tue Apr 2 20:30:58 2013: Starting jack server...
Tue Apr 2 20:30:58 2013: JACK server starting in realtime mode with priority 85
Tue Apr 2 20:30:59 2013: Acquired audio card Audio0
Tue Apr 2 20:30:59 2013: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Tue Apr 2 20:30:59 2013: Using ALSA driver HDA-Intel running on card 0 - HDA Intel at 0xb4400000 irq 42
Tue Apr 2 20:30:59 2013: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Tue Apr 2 20:30:59 2013: ALSA: final selected sample format for capture: 32bit integer little-endian
Tue Apr 2 20:30:59 2013: ALSA: use 2 periods for capture
Tue Apr 2 20:30:59 2013: ALSA: final selected sample format for playback: 32bit integer little-endian
Tue Apr 2 20:30:59 2013: ALSA: use 2 periods for playback
Tue Apr 2 20:30:59 2013: graph reorder: new port 'system:capture_1'
Tue Apr 2 20:30:59 2013: New client 'system' with PID 0
Tue Apr 2 20:30:59 2013: graph reorder: new port 'system:capture_2'
Tue Apr 2 20:30:59 2013: graph reorder: new port 'system:playback_1'
Tue Apr 2 20:30:59 2013: graph reorder: new port 'system:playback_2'
Tue Apr 2 20:30:59 2013: New client 'cadence-aloop-daemon' with PID 7465
Tue Apr 2 20:30:59 2013: New client 'alsa2jack' with PID 7470
Tue Apr 2 20:30:59 2013: New client 'jack2alsa' with PID 7471
Tue Apr 2 20:30:59 2013: port 'jack2alsa:playback_1' created
Tue Apr 2 20:30:59 2013: port 'jack2alsa:playback_2' created
Tue Apr 2 20:30:59 2013: port 'alsa2jack:capture_1' created
Tue Apr 2 20:30:59 2013: port 'alsa2jack:capture_2' created
Tue Apr 2 20:30:59 2013: New client 'a2j' with PID 7454
Tue Apr 2 20:30:59 2013: port 'a2j:Midi Through [14] (capture): Midi Through Port-0' created
Tue Apr 2 20:30:59 2013: port 'a2j:Midi Through [14] (playback): Midi Through Port-0' created
Tue Apr 2 20:30:59 2013: port 'a2j:iO4 [24] (capture): iO4 MIDI 1' created
Tue Apr 2 20:30:59 2013: port 'a2j:iO4 [24] (playback): iO4 MIDI 1' created
Tue Apr 2 20:31:00 2013: Connecting 'alsa2jack:capture_1' to 'system:playback_1'
Tue Apr 2 20:31:00 2013: Connecting 'alsa2jack:capture_2' to 'system:playback_2'
Tue Apr 2 20:31:01 2013: Connecting 'system:capture_1' to 'jack2alsa:playback_1'
Tue Apr 2 20:31:01 2013: Connecting 'system:capture_2' to 'jack2alsa:playback_2'
Tue Apr 2 20:34:14 2013: Saving settings to "/home/kxstudio/.config/jack/conf.xml" ...
Tue Apr 2 20:34:37 2013: Saving settings to "/home/kxstudio/.config/jack/conf.xml" ...
Tue Apr 2 20:34:37 2013: Stopping jack server...
Tue Apr 2 20:34:37 2013: Client 'system' with PID 0 is out
Tue Apr 2 20:34:37 2013: Client 'cadence-aloop-daemon' with PID 7465 is out
Tue Apr 2 20:34:37 2013: Client 'alsa2jack' with PID 7470 is out
Tue Apr 2 20:34:37 2013: Client 'jack2alsa' with PID 7471 is out
Tue Apr 2 20:34:37 2013: Client 'a2j' with PID 7454 is out
Tue Apr 2 20:34:37 2013: Released audio card Audio0
Tue Apr 2 20:34:39 2013: Starting jack server...
Tue Apr 2 20:34:39 2013: JACK server starting in realtime mode with priority 85
Tue Apr 2 20:34:39 2013: Acquired audio card Audio2
Tue Apr 2 20:34:39 2013: creating alsa driver ... hw:iO4,0|hw:iO4,0|1024|3|44100|2|2|nomon|swmeter|-|32bit
Tue Apr 2 20:34:39 2013: Using ALSA driver USB-Audio running on card 2 - Alesis iO4 at usb-0000:00:1d.0-1.1, full speed
Tue Apr 2 20:34:39 2013: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
Tue Apr 2 20:34:39 2013: ALSA: final selected sample format for capture: 24bit little-endian
Tue Apr 2 20:34:39 2013: ALSA: use 3 periods for capture
Tue Apr 2 20:34:39 2013: ALSA: final selected sample format for playback: 24bit little-endian
Tue Apr 2 20:34:39 2013: ALSA: use 3 periods for playback
Tue Apr 2 20:34:39 2013: graph reorder: new port 'system:capture_1'
Tue Apr 2 20:34:39 2013: New client 'system' with PID 0
Tue Apr 2 20:34:39 2013: graph reorder: new port 'system:capture_2'
Tue Apr 2 20:34:39 2013: graph reorder: new port 'system:playback_1'
Tue Apr 2 20:34:39 2013: graph reorder: new port 'system:playback_2'
Tue Apr 2 20:35:32 2013: New client 'reaper' with PID 7765
Tue Apr 2 20:35:32 2013: Client 'reaper' with PID 7765 is out
Tue Apr 2 20:35:48 2013: New client 'reaper' with PID 7765
Tue Apr 2 20:35:48 2013: port 'reaper:in_1' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_2' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_3' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_4' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_5' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_6' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_7' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_8' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_9' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_10' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_11' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_12' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_13' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_14' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_15' created
Tue Apr 2 20:35:48 2013: port 'reaper:in_16' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_1' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_2' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_3' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_4' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_5' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_6' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_7' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_8' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_9' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_10' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_11' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_12' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_13' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_14' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_15' created
Tue Apr 2 20:35:48 2013: port 'reaper:out_16' created
Tue Apr 2 20:35:48 2013: Connecting 'system:capture_1' to 'reaper:in_1'
Tue Apr 2 20:35:48 2013: Connecting 'system:capture_2' to 'reaper:in_2'
Tue Apr 2 20:35:48 2013: Connecting 'reaper:out_1' to 'system:playback_1'
Tue Apr 2 20:35:48 2013: Connecting 'reaper:out_2' to 'system:playback_2'
Tue Apr 2 20:36:20 2013: Disconnecting 'system:capture_1' from 'reaper:in_1'
Tue Apr 2 20:36:20 2013: Disconnecting 'system:capture_2' from 'reaper:in_2'
Tue Apr 2 20:36:20 2013: Disconnecting 'reaper:out_1' from 'system:playback_1'
Tue Apr 2 20:36:20 2013: Disconnecting 'reaper:out_2' from 'system:playback_2'
Tue Apr 2 20:36:21 2013: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 464380 err = Connection timed out
Tue Apr 2 20:36:21 2013: ERROR: JackEngine::ClientDeactivate wait error ref = 3 name = reaper
Tue Apr 2 20:36:21 2013: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 92876 err = Connection timed out
Tue Apr 2 20:36:21 2013: ERROR: JackEngine::ClientCloseAux wait error ref = 3
Tue Apr 2 20:36:21 2013: Client 'reaper' with PID 7765 is out
Tue Apr 2 20:36:45 2013: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Tue Apr 2 20:36:45 2013: ERROR: Driver is not running
Tue Apr 2 20:36:45 2013: ERROR: Cannot create new client
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
hebjuzeb
Established Member
Posts: 111
Joined: Sun Feb 05, 2012 1:54 am

Re: Trouble getting Reaper working

Post by hebjuzeb »

So, ran welcome screen, force-reset, logged out, configured JACK (same as Manic's settings,) stopped Jack and tried to restart so I could give Qtractor a go, no dice. Start and "force restart" do nothing, Jack is dead.

Couple of questions,
a) could this be an issue with my audio device? It seems to work OK with Windows (though I far prefer my Steinberg and its audio driver) but nothing else makes sense to me so far.
b) has anyone ever witnessed the KX iso pass disk-check? I've tried many, many combinations, and every one leads to "errors found in 2 files!" (Falk, if you're out there, here's one suggestion I feel qualified to bring up: I know the Unetbootin dialogues aren't your doing but in your coding adventures, please omit exclamation points from error screens . . . it only enrages users. :lol: )

BTW I know KXStudio works perfectly well for many people; I'm resigned to the fact that there's likely a certain amount of "user error" involved in my problems, but it's like a puzzle. Why can't I figure this out?

Thanks for reading,
h.
Acer Aspire 5742, Intel Core i3 370M @ 2.40GHz, 4.00 GB Dual-Channel DDR3 @ 532MHz, Intel(R) HD Graphics, Alesis iO4 audio device.
danboid
Established Member
Posts: 1327
Joined: Sun Aug 26, 2012 11:28 am
Location: England
Has thanked: 1 time
Been thanked: 4 times

Re: Trouble getting Reaper working

Post by danboid »

Hi Heb!

It looks like you are trying to use some Alesis USB audio device right? Can you not get JACK running on your onboard audio? I'm presuming you have onboard audio on your machine too.

I would aim to get JACK running well with qtractor before delving into REAPER and wineasio.

I'm writing a guide to setting up JACK soon but I can condense the jist as this. You may want to try running JACK at 48000 instead of 44100 as some devices like running at 48k better. Try starting JACK using both 44.1 and 48 at ONLY period sizes of 2 or 3 but at varying buffer sizes. 1024 is the best buffer size to start with. You're unlikely to get smaller tham 128 and you don't really want to go any bigger than 2048.
Post Reply