Re: [Jackit-devel] Re: jack, PREEMPT_DESKTOP, delayed interrupts?

* Florian Schmidt <mista.tapas <at> gmx.net> wrote:

> > JACK sources already include a CHECK_PREEMPTION() macro which expands
> > to Ingo's special gettimeofday() calls.  The trace is turned on and
> > then off automatically before and after the realtime critical section
> > in the process thread (see libjack/client.c).  
> 
> Just for completeness sake:
> 
> you need to build jackd with --enable-preemption-check

this is another feature, unrelated to latency tracing. So (an adapted 
version of) the latency-tracing patch i sent should still be tried.

--enable-preemption-check does the 'send SIGUSR2 if jackd gets scheduled 
unexpectedly'. That might unearth latencies, but it does not by itself 
measure latencies. Right now we are more interested in the latencies 
themselves.

i suspect the confusion comes from the API hacks i'm using: user-space 
tracing is started/stopped via:

	gettimeofday(0,1);
	gettimeofday(0,0);

while 'jackd does not want to be scheduled' flag is switched on/off via:

	gettimeofday(1,1);
	gettimeofday(1,0);

ВЗЫСКАНИЕ ДОЛГОВ С ПРИМЕНЕНИЕМ УГОЛОВНО-ПРОЦЕССУАЛЬНЫХ СРЕДСТВ ВОЗДЕЙСТВИЯ

Re: [Jackit-devel] Re: jack, PREEMPT_DESKTOP, delayed interrupts?

Ingo Molnar <mingo <at> elte.hu> writes:

> i suspect the confusion comes from the API hacks i'm using: user-space 
> tracing is started/stopped via:
>
> 	gettimeofday(0,1);
> 	gettimeofday(0,0);
>
> while 'jackd does not want to be scheduled' flag is switched on/off via:
>
> 	gettimeofday(1,1);
> 	gettimeofday(1,0);

D'oh!  No wonder I was confused.

Sorry to have mixed up the conversation with erroneous information,
but glad to have the gettimeofday() API clarified.
--

-- 
  joq

Мотивация, или Как вызвать у людей желание работать

Re: AUDIGY 2 NX USB - "DRIVER NT: could not start driver" - Was: User question about decent external audio interface.

Sunday 28 August 2005 19:28 Melanie wrote:
> Hi,
>
> SoundBlaster Audigy NX works for me. One stereo input only, but 3
> stereo outputs. Sound quality is good  <at> 48 kHz.
>
> Melanie

Now I have my AUDIGY 2 NX USB plugged in and set up with alsa.

But,
I get the error "DRIVER NT: could not start driver" when trying out the pasted 
commands at the end. 

I am running without any /etc/asound.conf or ~/.asroundrc

jonas <at> jw jonas $ jackd --version
jackd version 0.99.0 tmpdir /dev/shm protocol 13

alsa-driver is from gentoo:
media-sound/alsa-driver- 1.0.9b

Here's the error:

jonas <at> jw jonas $ cat /proc/asound/devices
 25: [0- 1]: digital audio capture
 16: [0- 0]: digital audio playback
 24: [0- 0]: digital audio capture
  0: [0- 0]: ctl
  1:       : sequencer
 33:       : timer
 36: [1- 0]: hardware dependent
 48: [1- 0]: digital audio playback
 56: [1- 0]: digital audio capture
 32: [1- 0]: ctl
jonas <at> jw jonas $ /usr/bin/jackd  -d alsa -d hw:1 -n 2 -p 64
jackd 0.99.0
Copyright 2001-2003 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

loading driver ..
creating alsa driver ... hw:1|hw:1|64|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 48000Hz, period = 64 frames, buffer = 2 periods
Couldn't open hw:1 for 32bit samples trying 24bit instead
Couldn't open hw:1 for 32bit samples trying 24bit instead
could not start playback (Broken pipe)
DRIVER NT: could not start driver
cannot start driver
jonas <at> jw jonas $ 

Any hints?
--

-- 
Jonas Widarsson

tel: +46 271 152 00 - tel: +46 271 121 42 (hemma/home) - gsm: +46 70 539 64 79
MSN: jonas <at> widarsson.com ICQ: 72016688 jabber: jonas <at> widarsson.com

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: AUDIGY 2 NX USB - "DRIVER NT: could not start driver" - Was: User question about decent external audio interface.

On Thu, 2005-09-01 at 20:22 +0200, Jonas Widarsson wrote:
> jonas <at> jw jonas $ /usr/bin/jackd  -d alsa -d hw:1 -n 2 -p 64

> DRIVER NT: could not start driver
> cannot start driver
> jonas <at> jw jonas $ 

64 frames with a USB device?  No way in hell is that going to work.
It's barely possible with PCI.

Try -n 3 -p 512.  If that works then try -p 256.

Lee

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: AUDIGY 2 NX USB - "DRIVER NT: could not start driver" - Was: User question about decent external audio interface.

Thursday 01 September 2005 20:27 Lee Revell wrote:
> On Thu, 2005-09-01 at 20:22 +0200, Jonas Widarsson wrote:
> > jonas <at> jw jonas $ /usr/bin/jackd  -d alsa -d hw:1 -n 2 -p 64
> >
> > DRIVER NT: could not start driver
> > cannot start driver
> > jonas <at> jw jonas $
>
> 64 frames with a USB device?  No way in hell is that going to work.
> It's barely possible with PCI.
>
> Try -n 3 -p 512.  If that works then try -p 256.
>
> Lee

That's not what it is complaining about.
I know it should be slower...

And I am getting the same results with your suggestion,
DRIVER NT: could not start driver

According to [1] I assume it means non threaded. I don't see any way to get 
around it yet.

I can stress the values a bit and if I set -p 32 then I get the error I would 
associate with your assumption:
ALSA: cannot set period size to 32 frames for capture

[1]:
http://www.google.se/url?sa=t&ct=res&cd=4&url=http%3A//jackit.sourceforge.net/cgi-bin/lxr/http/source/libjack/driver.c&ei=6koXQ-2LNKeGiAL_rdDDDA
--

-- 
Jonas Widarsson

tel: +46 271 152 00 - tel: +46 271 121 42 (hemma/home) - gsm: +46 70 539 64 79
MSN: jonas <at> widarsson.com ICQ: 72016688 jabber: jonas <at> widarsson.com

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: AUDIGY 2 NX USB - "DRIVER NT: could not start driver" - Was: User question about decent external audio interface.

Thursday 01 September 2005 20:22 Jonas Widarsson wrote:
> Sunday 28 August 2005 19:28 Melanie wrote:
> > Hi,
> >
> > SoundBlaster Audigy NX works for me. One stereo input only, but 3
> > stereo outputs. Sound quality is good  <at> 48 kHz.
> >
> > Melanie
>
> Now I have my AUDIGY 2 NX USB plugged in and set up with alsa.
>
> But,
> I get the error "DRIVER NT: could not start driver" [...]

I use this alsa configuration:

pcm.usb-audio {
        type hw
        card 0
}

ctl.usb-audio {
        type hw
        card 0
}

pcm.audigy {
        type plug
        slave {
                pcm "hw:0"
#                format S16_LE
                rate 48000
#                rate 44100
        }
}

ctl.audigy {
   type hw
   card 0
}

Then I can get it up, but not use it.
It looks like this:

jonas <at> jw jonas $ /usr/bin/jackd  -d alsa -d audigy -n 5 -p 256
jackd 0.99.0
Copyright 2001-2003 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

loading driver ..
creating alsa driver ... audigy|audigy|256|5|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 256 frames, buffer = 5 periods
You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a hardware device
instead rather than using the plug layer. Usually the name of the
hardware device that corresponds to the first soun
You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a hardware device
instead rather than using the plug layer. Usually the name of the
hardware device that corresponds to the first soun

Then I start qjackconnect to try some connections, and immediately jackd ends 
like this:

could not complete playback of 256 frames: error = -32
cycle execution failure, exiting
DRIVER NT: could not run driver cycle
jack main caught signal 12
jonas <at> jw jonas $

I don't know what to do.
If I try to access the device without the slave pcm I get this immediately:

jonas <at> jw jonas $ /usr/bin/jackd  -d alsa -d usb-audio -n 5 -p 256
jackd 0.99.0
Copyright 2001-2003 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

loading driver ..
creating alsa driver ... usb-audio|usb-audio|256|5|48000|0|0|nomon|swmeter|-|
32bit
configuring for 48000Hz, period = 256 frames, buffer = 5 periods
Couldn't open usb-audio for 32bit samples trying 24bit instead
Couldn't open usb-audio for 32bit samples trying 24bit instead
could not start playback (Broken pipe)
DRIVER NT: could not start driver
cannot start driver
jonas <at> jw jonas $ 

--

-- 
Jonas Widarsson

tel: +46 271 152 00 - tel: +46 271 121 42 (hemma/home) - gsm: +46 70 539 64 79
MSN: jonas <at> widarsson.com ICQ: 72016688 jabber: jonas <at> widarsson.com

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: AUDIGY 2 NX USB - "DRIVER NT: could not start driver" - Was: User question about decent external audio interface.

On Thu, 2005-09-01 at 22:41 +0200, Jonas Widarsson wrote:
> I use this alsa configuration:

What if you lose the .asoundrc and just use -d hw:0,0?

Lee

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: AUDIGY 2 NX USB - "DRIVER NT: could not start driver" - Was: User question about decent external audio interface.

Lee Revell wrote:
> On Thu, 2005-09-01 at 20:22 +0200, Jonas Widarsson wrote:
>> jonas <at> jw jonas $ /usr/bin/jackd  -d alsa -d hw:1 -n 2 -p 64
> 
>> DRIVER NT: could not start driver
>> cannot start driver
>> jonas <at> jw jonas $ 
> 
> 64 frames with a USB device?  No way in hell is that going to work.
> It's barely possible with PCI.
> 

My laptop and my Tascam US-224 can :) No xruns, no glitches. But much 
special care must be taken first: its on a full Ingo's RT patched 2.6 
kernel, usb-hcd in the highest SCHED_FIFO rtprio, snd-usb-usx2y loaded 
with nrpacks=1 and thanks to Kartsen Wiese's awesome "rawusb" mode of a 
specialized alsa/usx2y jackd backend (thru a dedicated hwdep interface), 
pumping full-duplex low-lat audio as been perfectly possible. However, 
if just one, any one of those conditions are not met, sure hell is in 
the house :))

Going back to the topic, when using the regular alsa backend of jackd's, 
on which all other usb-audio interfaces are still confined, things can 
hardly run below 256x2, if at all. At least without lots of pops and 
crackles. And so it seems, that it just doesn't matter which kernel 
tunning you're into. So Lee is dead right about trying first longer 
periods; the default 1024x2 setting should work. Try it first!

Cheers.
--

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf