Jack2 Issue - 2nd Part

[Marco Castorina]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi guys,
 i'm trying the latest version of Jack 1.9.2. The server starts normally:

20:13:58.608 JACK is starting...

20:13:58.609 /usr/local/bin/jackd -R -P89 -t1000 -m -dalsa -r44100 -p128 -n3 -D -Chw:0,1 -Phw:0,0 -Xseq -H -M

jackdmp 1.9.2

Copyright 2001-2005 Paul Davis and others.

Copyright 2004-2008 Grame.

jackdmp 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 server starting in realtime mode with priority 89

20:13:58.636 JACK was started with PID=4712.

Acquire audio card Audio0

Failed to acquire device name : Audio0 error : Input/output error

Error playback audio device hw:0,0 cannot be acquired, trying to open it anyway...

creating alsa driver ... hw:0,0|hw:0,1|128|3|44100|0|0|hwmon|hwmeter|-|32bit

Using ALSA driver USB-Audio running on M-Audio FastTrack Pro at usb-0000:00:1d.1-1, full speed

configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 3 periods

ALSA: final selected sample format for capture: 16bit little-endian

ALSA: use 3 periods for capture

ALSA: final selected sample format for playback: 16bit little-endian

ALSA: use 3 periods for playback

20:13:58.672 ALSA connection graph change.

port created: Midi-Through:midi/playback_1

port created: Midi-Through:midi/capture_1

port created: FastTrack-Pro:midi/playback_1

port created: FastTrack-Pro:midi/capture_1

port created: TiMidity:midi/capture_1

port created: TiMidity:midi/capture_2

port created: TiMidity:midi/capture_3

port created: TiMidity:midi/capture_4

alsa_driver_xrun_recovery

JackAudioDriver::ProcessAsync: read error, skip cycle

20:14:00.665 Server configuration saved to "/home/marco/.jackdrc".

20:14:00.668 Statistics reset.

20:14:00.689 Client activated.

20:14:00.727 JACK connection change.

But when i use it with other programs (vsthost, lv2rack, jackrack, qsynth...), i get xrun like this:

JackEngine::XRun: client = Wine_ASIO_Jack_Client was not run: state = 2

JackAudioDriver::ProcessAsync Process error

20:18:15.852 XRUN callback (1).

Is it a known problem? It depends on hardware or software i'm using? Bad installation?

Thanks as always!

Marco

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Stéphane Letz]

Le 1 juil. 09 à 20:48, Marco Castorina a écrit :

> Hi guys,
>  i'm trying the latest version of Jack 1.9.2. The server starts  
> normally:
>
> p, li { white-space: pre-wrap; }
> 20:13:58.608 JACK is starting...
> 20:13:58.609 /usr/local/bin/jackd -R -P89 -t1000 -m -dalsa -r44100 -
> p128 -n3 -D -Chw:0,1 -Phw:0,0 -Xseq -H -M
> jackdmp 1.9.2
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2008 Grame.
> jackdmp 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 server starting in realtime mode with priority 89
> 20:13:58.636 JACK was started with PID=4712.
> Acquire audio card Audio0
> Failed to acquire device name : Audio0 error : Input/output error
> Error playback audio device hw:0,0 cannot be acquired, trying to  
> open it anyway...
> creating alsa driver ... hw:0,0|hw:0,1|128|3|44100|0|0|hwmon|
> hwmeter|-|32bit
> Using ALSA driver USB-Audio running on M-Audio FastTrack Pro at  
> usb-0000:00:1d.1-1, full speed
> configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 3  
> periods
> ALSA: final selected sample format for capture: 16bit little-endian
> ALSA: use 3 periods for capture
> ALSA: final selected sample format for playback: 16bit little-endian
> ALSA: use 3 periods for playback
> 20:13:58.672 ALSA connection graph change.
> port created: Midi-Through:midi/playback_1
> port created: Midi-Through:midi/capture_1
> port created: FastTrack-Pro:midi/playback_1
> port created: FastTrack-Pro:midi/capture_1
> port created: TiMidity:midi/capture_1
> port created: TiMidity:midi/capture_2
> port created: TiMidity:midi/capture_3
> port created: TiMidity:midi/capture_4
> alsa_driver_xrun_recovery
> JackAudioDriver::ProcessAsync: read error, skip cycle
> 20:14:00.665 Server configuration saved to "/home/marco/.jackdrc".
> 20:14:00.668 Statistics reset.
> 20:14:00.689 Client activated.
> 20:14:00.727 JACK connection change.
>
> But when i use it with other programs (vsthost, lv2rack, jackrack,  
> qsynth...), i get xrun like this:
> JackEngine::XRun: client = Wine_ASIO_Jack_Client was not run: state  
> = 2
> JackAudioDriver::ProcessAsync Process error
> 20:18:15.852 XRUN callback (1).
> Is it a known problem? It depends on hardware or software i'm  
> using? Bad installation?
>
> Thanks as always!
>
> Marco
>

Does it work in playback mode only?


Stephane
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

[Ralf Mardorf]

Marco Castorina wrote:

> Hi guys,
>  i'm trying the latest version of Jack 1.9.2. The server starts normally:
>
> 20:13:58.608 JACK is starting...
>
> 20:13:58.609 /usr/local/bin/jackd -R -P89 -t1000 -m -dalsa -r44100
> -p128 -n3 -D -Chw:0,1 -Phw:0,0 -Xseq -H -M
>
> jackdmp 1.9.2
>
> Copyright 2001-2005 Paul Davis and others.
>
> Copyright 2004-2008 Grame.
>
> jackdmp 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 server starting in realtime mode with priority 89
>
> 20:13:58.636 JACK was started with PID=4712.
>
> Acquire audio card Audio0
>
> Failed to acquire device name : Audio0 error : Input/output error
>
> Error playback audio device hw:0,0 cannot be acquired, trying to open
> it anyway...
>
> creating alsa driver ...
> hw:0,0|hw:0,1|128|3|44100|0|0|hwmon|hwmeter|-|32bit
>
> Using ALSA driver USB-Audio running on M-Audio FastTrack Pro at
> usb-0000:00:1d.1-1, full speed
>
> configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 3 periods
>
> ALSA: final selected sample format for capture: 16bit little-endian
>
> ALSA: use 3 periods for capture
>
> ALSA: final selected sample format for playback: 16bit little-endian
>
> ALSA: use 3 periods for playback
>
> 20:13:58.672 ALSA connection graph change.
>
> port created: Midi-Through:midi/playback_1
>
> port created: Midi-Through:midi/capture_1
>
> port created: FastTrack-Pro:midi/playback_1
>
> port created: FastTrack-Pro:midi/capture_1
>
> port created: TiMidity:midi/capture_1
>
> port created: TiMidity:midi/capture_2
>
> port created: TiMidity:midi/capture_3
>
> port created: TiMidity:midi/capture_4
>
> alsa_driver_xrun_recovery
>
> JackAudioDriver::ProcessAsync: read error, skip cycle
>
> 20:14:00.665 Server configuration saved to "/home/marco/.jackdrc".
>
> 20:14:00.668 Statistics reset.
>
> 20:14:00.689 Client activated.
>
> 20:14:00.727 JACK connection change.
>
>
> But when i use it with other programs (vsthost, lv2rack, jackrack,
> qsynth...), i get xrun like this:
>
> JackEngine::XRun: client = Wine_ASIO_Jack_Client was not run: state = 2
>
> JackAudioD river::ProcessAsync Process error
>
> 20:18:15.852 XRUN callback (1).
>
> Is it a known problem? It depends on hardware or software i'm using?
> Bad installation?
>
>
> Thanks as always!
>
>
> Marco
>

What does it mean, that you 'get' xruns and this messages? Do you hear
any glitches? I often get this 'Async Process error' when I don't do
anything and I often get xruns, if I launch an application, but when I
play or record, assumed the latency isn't set to low, I never hear any
glitches and I also don't get this messages. When I try to keep the
latency too low, I hear some glitches, but most times without getting
any messages. I can stand Those glitches. For the mastering I increase
latency. Latency for me most times is set a little bit higher, than for
other people using similar sound cards, this might because of my mobo or
because I use JAMin all the time, so the load is very high.

Is there the need to set '-p128 -n3'? If not try to use -p higher than
128, but -n2.
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org