xwax

On Wed, 8 Dec 2010, Matthieu Caron wrote:

> Hi all,
> I am using xwax to scratch and I get very good results with alsa. I now 
> need to use it with jack... But with jack scratches sound terrible...
> I configured jack to have very small latency (fx 2ms (or even less) 
> according to qjackctl) but it doesn't help....
> Do you have any idea?

There's nothing immediately different about the JACK implementation that 
would make it sound worse, can you describe the sound you are hearing? Or 
perhaps even post a recording online and include a link.

> Another issue:
> when playing flac or ogg files (created with ardour), xwax read the 
> files too quickly (maybe twice the normal speed...)

It sounds like the file is not stereo 44100Hz. In some cases the import 
script will do the conversion, in some cases it won't. Perhaps a 
workaround is to remove the FLAC and Ogg entries from the import script, 
and always fallback to ffmpeg or sox.

-- 
Mark

Hi,
You can find two examples, one recorded with ALSA (export_alsa.ogg) and 
one with JACK (export_jack.ogg) at http://mcaron.free.fr/xwax/. I hope 
it can help.
Maybe my settings in JACK are not correct?
I run under Fedora (first under fedora12 with a RT kernel from CCRMA and 
now under fedora 14 with the normal kernel - I have this problem in 
both) and have an audiophile 24/96.

The second issue is solved with stereo 44100Hz files. Thank you.


Le 12/12/2010 12:52, Mark Hills a écrit :
> On Wed, 8 Dec 2010, Matthieu Caron wrote:
>
>> Hi all,
>> I am using xwax to scratch and I get very good results with alsa. I now
>> need to use it with jack... But with jack scratches sound terrible...
>> I configured jack to have very small latency (fx 2ms (or even less)
>> according to qjackctl) but it doesn't help....
>> Do you have any idea?
> There's nothing immediately different about the JACK implementation that
> would make it sound worse, can you describe the sound you are hearing? Or
> perhaps even post a recording online and include a link.
>
>> Another issue:
>> when playing flac or ogg files (created with ardour), xwax read the
>> files too quickly (maybe twice the normal speed...)
> It sounds like the file is not stereo 44100Hz. In some cases the import
> script will do the conversion, in some cases it won't. Perhaps a
> workaround is to remove the FLAC and Ogg entries from the import script,
> and always fallback to ffmpeg or sox.
>

Hi Matthieu,

My experience has been that tuning Jack audio is much more difficult
than ALSA audio.  It's taken me several tries to find the right settings
for my Firewire Stanton Scratchamp 2.

Most importantly, do you have your system setup so that your user can
run xwax and jack in realtime? (See: http://jackaudio.org/faq ,
http://help.ubuntu.com/community/UbuntuStudioPreparation#Real-Time
Support , http://help.ubuntu.com/community/FireWire ) .  It's very
possible that xwax and/or jack are not running at a high enough
priority.

HTH,

Charles


On Wed, 2010-12-15 at 00:39 +0100, Matthieu Caron wrote:
> Hi,
> You can find two examples, one recorded with ALSA (export_alsa.ogg) and 
> one with JACK (export_jack.ogg) at http://mcaron.free.fr/xwax/. I hope 
> it can help.
> Maybe my settings in JACK are not correct?
> I run under Fedora (first under fedora12 with a RT kernel from CCRMA and 
> now under fedora 14 with the normal kernel - I have this problem in 
> both) and have an audiophile 24/96.
> 
> The second issue is solved with stereo 44100Hz files. Thank you.
> 
> 
> Le 12/12/2010 12:52, Mark Hills a écrit :
> > On Wed, 8 Dec 2010, Matthieu Caron wrote:
> >
> >> Hi all,
> >> I am using xwax to scratch and I get very good results with alsa. I now
> >> need to use it with jack... But with jack scratches sound terrible...
> >> I configured jack to have very small latency (fx 2ms (or even less)
> >> according to qjackctl) but it doesn't help....
> >> Do you have any idea?
> > There's nothing immediately different about the JACK implementation that
> > would make it sound worse, can you describe the sound you are hearing? Or
> > perhaps even post a recording online and include a link.
> >
> >> Another issue:
> >> when playing flac or ogg files (created with ardour), xwax read the
> >> files too quickly (maybe twice the normal speed...)
> > It sounds like the file is not stereo 44100Hz. In some cases the import
> > script will do the conversion, in some cases it won't. Perhaps a
> > workaround is to remove the FLAC and Ogg entries from the import script,
> > and always fallback to ffmpeg or sox.
> >
> 
> 
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d

Sorry have to be quick...!
I am using RHEL5 with alsa-lib-1.0.17-1.el5.
I am using custom RT kernel 2.6.28.
I use the following commands with jack server
/usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p128 -n2 -S -Xseq
I am using asus xonar d1 and intel onboard sound card.  I use alsa-in and alsa-out jack utils to use both soundcards
Using xwax with jack-rack I get amazing sounding real time effects when scratching and playing normally.  The response time is super fast.
Let me know if you need to know any other config I have.
thanks,
matt


> From: charles@...
> To: xwax-devel@...
> Date: Tue, 14 Dec 2010 15:57:27 -0800
> Subject: Re: [xwax-devel] xwax and jack
> 
> Hi Matthieu,
> 
> My experience has been that tuning Jack audio is much more difficult
> than ALSA audio.  It's taken me several tries to find the right settings
> for my Firewire Stanton Scratchamp 2.
> 
> Most importantly, do you have your system setup so that your user can
> run xwax and jack in realtime? (See: http://jackaudio.org/faq ,
> http://help.ubuntu.com/community/UbuntuStudioPreparation#Real-Time
> Support , http://help.ubuntu.com/community/FireWire ) .  It's very
> possible that xwax and/or jack are not running at a high enough
> priority.
> 
> HTH,
> 
> Charles
> 
> 
> On Wed, 2010-12-15 at 00:39 +0100, Matthieu Caron wrote:
> > Hi,
> > You can find two examples, one recorded with ALSA (export_alsa.ogg) and 
> > one with JACK (export_jack.ogg) at http://mcaron.free.fr/xwax/. I hope 
> > it can help.
> > Maybe my settings in JACK are not correct?
> > I run under Fedora (first under fedora12 with a RT kernel from CCRMA and 
> > now under fedora 14 with the normal kernel - I have this problem in 
> > both) and have an audiophile 24/96.
> > 
> > The second issue is solved with stereo 44100Hz files. Thank you.
> > 
> > 
> > Le 12/12/2010 12:52, Mark Hills a écrit :
> > > On Wed, 8 Dec 2010, Matthieu Caron wrote:
> > >
> > >> Hi all,
> > >> I am using xwax to scratch and I get very good results with alsa. I now
> > >> need to use it with jack... But with jack scratches sound terrible...
> > >> I configured jack to have very small latency (fx 2ms (or even less)
> > >> according to qjackctl) but it doesn't help....
> > >> Do you have any idea?
> > > There's nothing immediately different about the JACK implementation that
> > > would make it sound worse, can you describe the sound you are hearing? Or
> > > perhaps even post a recording online and include a link.
> > >
> > >> Another issue:
> > >> when playing flac or ogg files (created with ardour), xwax read the
> > >> files too quickly (maybe twice the normal speed...)
> > > It sounds like the file is not stereo 44100Hz. In some cases the import
> > > script will do the conversion, in some cases it won't. Perhaps a
> > > workaround is to remove the FLAC and Ogg entries from the import script,
> > > and always fallback to ffmpeg or sox.
> > >
> > 
> > 
> > ------------------------------------------------------------------------------
> > Lotusphere 2011
> > Register now for Lotusphere 2011 and learn how
> > to connect the dots, take your collaborative environment
> > to the next level, and enter the era of Social Business.
> > http://p.sf.net/sfu/lotusphere-d2d
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d

Thanks for your inputs Charles and Matt.
Nothing helps unfortunately.

I can run jack with RT capabilities (+ frames/period = 64, sample/rate = 
44100, periods/buffer = 2) and xwax without any xrun but I still have 
the same issue.
Maybe xwax is not running RT... even if I followed the instructions. Is 
there a way to check?
Since everything is fine with alsa, do you have any idea in which 
direction I should investigate?
Thanks again.


On 12/16/2010 09:57 AM, Intamixx Music Company wrote:
> Sorry have to be quick...!
> I am using RHEL5 with alsa-lib-1.0.17-1.el5.
> I am using custom RT kernel 2.6.28.
> I use the following commands with jack server
> /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p128 -n2 -S -Xseq
> I am using asus xonar d1 and intel onboard sound card.  I use alsa-in 
> and alsa-out jack utils to use both soundcards
> Using xwax with jack-rack I get amazing sounding real time effects 
> when scratching and playing normally.  The response time is super fast.
> Let me know if you need to know any other config I have.
> thanks,
> matt
>
>
> > From: charles@...
> > To: xwax-devel@...
> > Date: Tue, 14 Dec 2010 15:57:27 -0800
> > Subject: Re: [xwax-devel] xwax and jack
> >
> > Hi Matthieu,
> >
> > My experience has been that tuning Jack audio is much more difficult
> > than ALSA audio. It's taken me several tries to find the right settings
> > for my Firewire Stanton Scratchamp 2.
> >
> > Most importantly, do you have your system setup so that your user can
> > run xwax and jack in realtime? (See: http://jackaudio.org/faq ,
> > http://help.ubuntu.com/community/UbuntuStudioPreparation#Real-Time
> > Support , http://help.ubuntu.com/community/FireWire ) . It's very
> > possible that xwax and/or jack are not running at a high enough
> > priority.
> >
> > HTH,
> >
> > Charles
> >
> >
> > On Wed, 2010-12-15 at 00:39 +0100, Matthieu Caron wrote:
> > > Hi,
> > > You can find two examples, one recorded with ALSA 
> (export_alsa.ogg) and
> > > one with JACK (export_jack.ogg) at http://mcaron.free.fr/xwax/. I 
> hope
> > > it can help.
> > > Maybe my settings in JACK are not correct?
> > > I run under Fedora (first under fedora12 with a RT kernel from 
> CCRMA and
> > > now under fedora 14 with the normal kernel - I have this problem in
> > > both) and have an audiophile 24/96.
> > >
> > > The second issue is solved with stereo 44100Hz files. Thank you.
> > >
> > >
> > > Le 12/12/2010 12:52, Mark Hills a écrit :
> > > > On Wed, 8 Dec 2010, Matthieu Caron wrote:
> > > >
> > > >> Hi all,
> > > >> I am using xwax to scratch and I get very good results with 
> alsa. I now
> > > >> need to use it with jack... But with jack scratches sound 
> terrible...
> > > >> I configured jack to have very small latency (fx 2ms (or even less)
> > > >> according to qjackctl) but it doesn't help....
> > > >> Do you have any idea?
> > > > There's nothing immediately different about the JACK 
> implementation that
> > > > would make it sound worse, can you describe the sound you are 
> hearing? Or
> > > > perhaps even post a recording online and include a link.
> > > >
> > > >> Another issue:
> > > >> when playing flac or ogg files (created with ardour), xwax read the
> > > >> files too quickly (maybe twice the normal speed...)
> > > > It sounds like the file is not stereo 44100Hz. In some cases the 
> import
> > > > script will do the conversion, in some cases it won't. Perhaps a
> > > > workaround is to remove the FLAC and Ogg entries from the import 
> script,
> > > > and always fallback to ffmpeg or sox.
> > > >
> > >
> > >
> > > 
> ------------------------------------------------------------------------------
> > > Lotusphere 2011
> > > Register now for Lotusphere 2011 and learn how
> > > to connect the dots, take your collaborative environment
> > > to the next level, and enter the era of Social Business.
> > > http://p.sf.net/sfu/lotusphere-d2d
> >
> >
> >
> >
> > 
> ------------------------------------------------------------------------------
> > Lotusphere 2011
> > Register now for Lotusphere 2011 and learn how
> > to connect the dots, take your collaborative environment
> > to the next level, and enter the era of Social Business.
> > http://p.sf.net/sfu/lotusphere-d2d
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d

Sorry to bother you again...

I have found out that xwax with Alsa is running with RTPRIO = 80.
($ ps -LO rtprio /proc_num/)

With Jack, xwax is always running with RTPRIO = 15, whatever the 
settings I write in /etc/security/limits.d .
I tried in limits.d:
     @realtime - rtprio 20
     @realtime - memlock unlimited
or/and
     * - rtprio 99
     * - memlock 4194304
     * - nice -10
or/and
     @jackuser - rtprio 20
     @jackuser - memlock 131072

and adding my username in "realtime" and "jackuser" groups.

Xwax is running with RTPRIO = 15, whatever the settings.
This is maybe the cause of my problem.
Where does this value  15 come from?
Do you have any idea of what I've done wrong?
Thanks


On 12/16/2010 02:56 PM, Matthieu Caron wrote:
> Thanks for your inputs Charles and Matt.
> Nothing helps unfortunately.
>
> I can run jack with RT capabilities (+ frames/period = 64, sample/rate 
> = 44100, periods/buffer = 2) and xwax without any xrun but I still 
> have the same issue.
> Maybe xwax is not running RT... even if I followed the instructions. 
> Is there a way to check?
> Since everything is fine with alsa, do you have any idea in which 
> direction I should investigate?
> Thanks again.
>
>
> On 12/16/2010 09:57 AM, Intamixx Music Company wrote:
>> Sorry have to be quick...!
>> I am using RHEL5 with alsa-lib-1.0.17-1.el5.
>> I am using custom RT kernel 2.6.28.
>> I use the following commands with jack server
>> /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p128 -n2 -S -Xseq
>> I am using asus xonar d1 and intel onboard sound card.  I use alsa-in 
>> and alsa-out jack utils to use both soundcards
>> Using xwax with jack-rack I get amazing sounding real time effects 
>> when scratching and playing normally.  The response time is super fast.
>> Let me know if you need to know any other config I have.
>> thanks,
>> matt
>>
>>
>> > From: charles@...
>> > To: xwax-devel@...
>> > Date: Tue, 14 Dec 2010 15:57:27 -0800
>> > Subject: Re: [xwax-devel] xwax and jack
>> >
>> > Hi Matthieu,
>> >
>> > My experience has been that tuning Jack audio is much more difficult
>> > than ALSA audio. It's taken me several tries to find the right settings
>> > for my Firewire Stanton Scratchamp 2.
>> >
>> > Most importantly, do you have your system setup so that your user can
>> > run xwax and jack in realtime? (See: http://jackaudio.org/faq ,
>> > http://help.ubuntu.com/community/UbuntuStudioPreparation#Real-Time
>> > Support , http://help.ubuntu.com/community/FireWire ) . It's very
>> > possible that xwax and/or jack are not running at a high enough
>> > priority.
>> >
>> > HTH,
>> >
>> > Charles
>> >
>> >
>> > On Wed, 2010-12-15 at 00:39 +0100, Matthieu Caron wrote:
>> > > Hi,
>> > > You can find two examples, one recorded with ALSA 
>> (export_alsa.ogg) and
>> > > one with JACK (export_jack.ogg) at http://mcaron.free.fr/xwax/. I 
>> hope
>> > > it can help.
>> > > Maybe my settings in JACK are not correct?
>> > > I run under Fedora (first under fedora12 with a RT kernel from 
>> CCRMA and
>> > > now under fedora 14 with the normal kernel - I have this problem in
>> > > both) and have an audiophile 24/96.
>> > >
>> > > The second issue is solved with stereo 44100Hz files. Thank you.
>> > >
>> > >
>> > > Le 12/12/2010 12:52, Mark Hills a écrit :
>> > > > On Wed, 8 Dec 2010, Matthieu Caron wrote:
>> > > >
>> > > >> Hi all,
>> > > >> I am using xwax to scratch and I get very good results with 
>> alsa. I now
>> > > >> need to use it with jack... But with jack scratches sound 
>> terrible...
>> > > >> I configured jack to have very small latency (fx 2ms (or even 
>> less)
>> > > >> according to qjackctl) but it doesn't help....
>> > > >> Do you have any idea?
>> > > > There's nothing immediately different about the JACK 
>> implementation that
>> > > > would make it sound worse, can you describe the sound you are 
>> hearing? Or
>> > > > perhaps even post a recording online and include a link.
>> > > >
>> > > >> Another issue:
>> > > >> when playing flac or ogg files (created with ardour), xwax 
>> read the
>> > > >> files too quickly (maybe twice the normal speed...)
>> > > > It sounds like the file is not stereo 44100Hz. In some cases 
>> the import
>> > > > script will do the conversion, in some cases it won't. Perhaps a
>> > > > workaround is to remove the FLAC and Ogg entries from the 
>> import script,
>> > > > and always fallback to ffmpeg or sox.
>> > > >
>> > >
>> > >
>> > > 
>> ------------------------------------------------------------------------------
>> > > Lotusphere 2011
>> > > Register now for Lotusphere 2011 and learn how
>> > > to connect the dots, take your collaborative environment
>> > > to the next level, and enter the era of Social Business.
>> > > http://p.sf.net/sfu/lotusphere-d2d
>> >
>> >
>> >
>> >
>> > 
>> ------------------------------------------------------------------------------
>> > Lotusphere 2011
>> > Register now for Lotusphere 2011 and learn how
>> > to connect the dots, take your collaborative environment
>> > to the next level, and enter the era of Social Business.
>> > http://p.sf.net/sfu/lotusphere-d2d
>>
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>> http://p.sf.net/sfu/lotusphere-d2d
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d

On Thu, 16 Dec 2010, Matthieu Caron wrote:

> Sorry to bother you again...

No worries! That's what the mailing list is for.

> I have found out that xwax with Alsa is running with RTPRIO = 80.
> ($ ps -LO rtprio /proc_num/)
> 
> With Jack, xwax is always running with RTPRIO = 15, whatever the settings I
> write in /etc/security/limits.d .

This sounds correct. When JACK is used, it handles the high-priority audio 
thread on behalf of xwax. So if you are only using JACK, xwax's realtime 
thread (priority 80) doesn't even start.

[...]
> Where does this value  15 come from?

Not sure. Are the rest of the apps in the system at 15?

I'm watching this thread, but haven't had any good suggestions to offer so 
far. How did you make the recordings before? Perhaps you could take a 
recording from within JACK; eg. route the audio straight through to 
Ardour to determine whether the problem is with xwax feeding audio into 
JACK, or with JACK feeding audio to the soundcard.

-- 
Mark

On 12/16/2010 08:18 PM, Mark Hills wrote:
> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>
>> Sorry to bother you again...
> No worries! That's what the mailing list is for.
>
>> I have found out that xwax with Alsa is running with RTPRIO = 80.
>> ($ ps -LO rtprio /proc_num/)
>>
>> With Jack, xwax is always running with RTPRIO = 15, whatever the settings I
>> write in /etc/security/limits.d .
> This sounds correct. When JACK is used, it handles the high-priority audio
> thread on behalf of xwax. So if you are only using JACK, xwax's realtime
> thread (priority 80) doesn't even start.
Hi Mark, hi all,
If I set Jack priority (from qjackctl's setup panel) to the maximum 
value (89), xwax's realtime thread gets a priority (RTPRIO) of 84. So it 
looks like  xwax's realtime thread does actually start when using Jack 
on my computer (but you wrote it shouldn't?)
Having the priority to 84 doesn't make a difference.

> [...]
>> Where does this value  15 come from?
> Not sure. Are the rest of the apps in the system at 15?
Seems that it was a pro-rata of the default priority of jackd (20).
So:
Jackd priority = 20 =>  xwax priority = 15
Jackd priority = 89 =>  xwax priority = 84

> I'm watching this thread, but haven't had any good suggestions to offer so
> far. How did you make the recordings before? Perhaps you could take a
> recording from within JACK; eg. route the audio straight through to
> Ardour to determine whether the problem is with xwax feeding audio into
> JACK, or with JACK feeding audio to the soundcard.
>
Regarding the previous recording (export_jack.ogg):
xwax's output was directly routed to Ardour. So the problem seems to be 
with xwax feeding audio into JACK.

On Thu, 16 Dec 2010, Matthieu Caron wrote:

> On 12/16/2010 08:18 PM, Mark Hills wrote:
> > On Thu, 16 Dec 2010, Matthieu Caron wrote:
> > 
> > > Sorry to bother you again...
> > No worries! That's what the mailing list is for.
> > 
> > > I have found out that xwax with Alsa is running with RTPRIO = 80.
> > > ($ ps -LO rtprio /proc_num/)
> > > 
> > > With Jack, xwax is always running with RTPRIO = 15, whatever the settings
> > > I
> > > write in /etc/security/limits.d .
> > This sounds correct. When JACK is used, it handles the high-priority audio
> > thread on behalf of xwax. So if you are only using JACK, xwax's realtime
> > thread (priority 80) doesn't even start.
> Hi Mark, hi all,
> If I set Jack priority (from qjackctl's setup panel) to the maximum value
> (89), xwax's realtime thread gets a priority (RTPRIO) of 84. So it looks like
> xwax's realtime thread does actually start when using Jack on my computer (but
> you wrote it shouldn't?)

I'm not familiar with the implementation details of JACK, but it sounds 
like this thread is a part of JACK's operation, not one of xwax's own. So 
it would make sense that it is calling process_callback() from jack.c.

You can confirm if xwax is starting its own thread. If it is, it will 
print:

  Launching realtime thread to handle devices...

to the console.

> Having the priority to 84 doesn't make a difference.
> 
> > [...]
> > > Where does this value  15 come from?
> > Not sure. Are the rest of the apps in the system at 15?
> Seems that it was a pro-rata of the default priority of jackd (20).
> So:
> Jackd priority = 20 =>  xwax priority = 15
> Jackd priority = 89 =>  xwax priority = 84
> 
> > I'm watching this thread, but haven't had any good suggestions to offer so
> > far. How did you make the recordings before? Perhaps you could take a
> > recording from within JACK; eg. route the audio straight through to
> > Ardour to determine whether the problem is with xwax feeding audio into
> > JACK, or with JACK feeding audio to the soundcard.
> > 
> Regarding the previous recording (export_jack.ogg):
> xwax's output was directly routed to Ardour. So the problem seems to be with
> xwax feeding audio into JACK.

It's not a bug I've seen before, but it sounds almost like you have the 
same buffers of audio being repeated. The most likely bug surrounds the 
processing in process_deck() of jack.c.

I'm not aware of any bugs in the xwax JACK output, so it would be good to 
get to the bottom of this.

Can you modify the value of MAX_BLOCK in jack.c and see if this changes 
the sound you hear? Perhaps use some music to test, rather than 
scratching.

-- 
Mark

On 12/16/2010 11:36 PM, Mark Hills wrote:
> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>
>> On 12/16/2010 08:18 PM, Mark Hills wrote:
>>> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>>>
>>>> Sorry to bother you again...
>>> No worries! That's what the mailing list is for.
>>>
>>>> I have found out that xwax with Alsa is running with RTPRIO = 80.
>>>> ($ ps -LO rtprio /proc_num/)
>>>>
>>>> With Jack, xwax is always running with RTPRIO = 15, whatever the settings
>>>> I
>>>> write in /etc/security/limits.d .
>>> This sounds correct. When JACK is used, it handles the high-priority audio
>>> thread on behalf of xwax. So if you are only using JACK, xwax's realtime
>>> thread (priority 80) doesn't even start.
>> Hi Mark, hi all,
>> If I set Jack priority (from qjackctl's setup panel) to the maximum value
>> (89), xwax's realtime thread gets a priority (RTPRIO) of 84. So it looks like
>> xwax's realtime thread does actually start when using Jack on my computer (but
>> you wrote it shouldn't?)
> I'm not familiar with the implementation details of JACK, but it sounds
> like this thread is a part of JACK's operation, not one of xwax's own. So
> it would make sense that it is calling process_callback() from jack.c.
>
> You can confirm if xwax is starting its own thread. If it is, it will
> print:
>
>    Launching realtime thread to handle devices...
>
> to the console.
>
xwax is not starting its own thread. "Launching realtime thread to 
handle devices... " is not printed.
>> Having the priority to 84 doesn't make a difference.
>>
>>> [...]
>>>> Where does this value  15 come from?
>>> Not sure. Are the rest of the apps in the system at 15?
>> Seems that it was a pro-rata of the default priority of jackd (20).
>> So:
>> Jackd priority = 20 =>   xwax priority = 15
>> Jackd priority = 89 =>   xwax priority = 84
>>
>>> I'm watching this thread, but haven't had any good suggestions to offer so
>>> far. How did you make the recordings before? Perhaps you could take a
>>> recording from within JACK; eg. route the audio straight through to
>>> Ardour to determine whether the problem is with xwax feeding audio into
>>> JACK, or with JACK feeding audio to the soundcard.
>>>
>> Regarding the previous recording (export_jack.ogg):
>> xwax's output was directly routed to Ardour. So the problem seems to be with
>> xwax feeding audio into JACK.
> It's not a bug I've seen before, but it sounds almost like you have the
> same buffers of audio being repeated. The most likely bug surrounds the
> processing in process_deck() of jack.c.
>
> I'm not aware of any bugs in the xwax JACK output, so it would be good to
> get to the bottom of this.
>
> Can you modify the value of MAX_BLOCK in jack.c and see if this changes
> the sound you hear? Perhaps use some music to test, rather than
> scratching.
>
I modified the value of MAX_BLOCK (with values from 1 up to 100000) and 
this doesn't change the sound I hear.

I borrowed a sound card (audigy se) and xwax and jack are working fine.
The problem should be with my audiophile 24/96...
Is someone using this card (or has a tip)?
Thanks


On 12/17/2010 12:43 AM, Matthieu Caron wrote:
> On 12/16/2010 11:36 PM, Mark Hills wrote:
>> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>>
>>> On 12/16/2010 08:18 PM, Mark Hills wrote:
>>>> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>>>>
>>>>> Sorry to bother you again...
>>>> No worries! That's what the mailing list is for.
>>>>
>>>>> I have found out that xwax with Alsa is running with RTPRIO = 80.
>>>>> ($ ps -LO rtprio /proc_num/)
>>>>>
>>>>> With Jack, xwax is always running with RTPRIO = 15, whatever the settings
>>>>> I
>>>>> write in /etc/security/limits.d .
>>>> This sounds correct. When JACK is used, it handles the high-priority audio
>>>> thread on behalf of xwax. So if you are only using JACK, xwax's realtime
>>>> thread (priority 80) doesn't even start.
>>> Hi Mark, hi all,
>>> If I set Jack priority (from qjackctl's setup panel) to the maximum value
>>> (89), xwax's realtime thread gets a priority (RTPRIO) of 84. So it looks like
>>> xwax's realtime thread does actually start when using Jack on my computer (but
>>> you wrote it shouldn't?)
>> I'm not familiar with the implementation details of JACK, but it sounds
>> like this thread is a part of JACK's operation, not one of xwax's own. So
>> it would make sense that it is calling process_callback() from jack.c.
>>
>> You can confirm if xwax is starting its own thread. If it is, it will
>> print:
>>
>>     Launching realtime thread to handle devices...
>>
>> to the console.
>>
> xwax is not starting its own thread. "Launching realtime thread to
> handle devices... " is not printed.
>>> Having the priority to 84 doesn't make a difference.
>>>
>>>> [...]
>>>>> Where does this value  15 come from?
>>>> Not sure. Are the rest of the apps in the system at 15?
>>> Seems that it was a pro-rata of the default priority of jackd (20).
>>> So:
>>> Jackd priority = 20 =>    xwax priority = 15
>>> Jackd priority = 89 =>    xwax priority = 84
>>>
>>>> I'm watching this thread, but haven't had any good suggestions to offer so
>>>> far. How did you make the recordings before? Perhaps you could take a
>>>> recording from within JACK; eg. route the audio straight through to
>>>> Ardour to determine whether the problem is with xwax feeding audio into
>>>> JACK, or with JACK feeding audio to the soundcard.
>>>>
>>> Regarding the previous recording (export_jack.ogg):
>>> xwax's output was directly routed to Ardour. So the problem seems to be with
>>> xwax feeding audio into JACK.
>> It's not a bug I've seen before, but it sounds almost like you have the
>> same buffers of audio being repeated. The most likely bug surrounds the
>> processing in process_deck() of jack.c.
>>
>> I'm not aware of any bugs in the xwax JACK output, so it would be good to
>> get to the bottom of this.
>>
>> Can you modify the value of MAX_BLOCK in jack.c and see if this changes
>> the sound you hear? Perhaps use some music to test, rather than
>> scratching.
>>
> I modified the value of MAX_BLOCK (with values from 1 up to 100000) and
> this doesn't change the sound I hear.
>
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
>

Well.... I found the issue...... Which was that my input sound was too 
high.... so obvious.

I was confused because it's working great with ALSA.

So....
Why is there a difference between input levels in ALSA and Jack?
(Is the sound amplified by jack?)

Comment regarding xwax:
xwax does a very good job by adapting the input level to its needs , so 
it is easy to get strong /circle/ in the timecode scope.
As I got a strong circle for almost all input volume, it is difficult to 
know if I am close or far from the ideal input level.

My amplifier (NAD PP 2i) doesn't have a gain button. So I am using 
jack-rack to reduce the input level for xwax. (no option to reduce input 
in my mixer(audiophile 24/96)).
Is there a better way?

Xwax works great now. I am verrrry happy. Thank you for a nice software.


Le 18/12/2010 01:31, Matthieu Caron a écrit :
> I borrowed a sound card (audigy se) and xwax and jack are working fine.
> The problem should be with my audiophile 24/96...
> Is someone using this card (or has a tip)?
> Thanks
>
>
> On 12/17/2010 12:43 AM, Matthieu Caron wrote:
>> On 12/16/2010 11:36 PM, Mark Hills wrote:
>>> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>>>
>>>> On 12/16/2010 08:18 PM, Mark Hills wrote:
>>>>> On Thu, 16 Dec 2010, Matthieu Caron wrote:
>>>>>
>>>>>> Sorry to bother you again...
>>>>> No worries! That's what the mailing list is for.
>>>>>
>>>>>> I have found out that xwax with Alsa is running with RTPRIO = 80.
>>>>>> ($ ps -LO rtprio /proc_num/)
>>>>>>
>>>>>> With Jack, xwax is always running with RTPRIO = 15, whatever the settings
>>>>>> I
>>>>>> write in /etc/security/limits.d .
>>>>> This sounds correct. When JACK is used, it handles the high-priority audio
>>>>> thread on behalf of xwax. So if you are only using JACK, xwax's realtime
>>>>> thread (priority 80) doesn't even start.
>>>> Hi Mark, hi all,
>>>> If I set Jack priority (from qjackctl's setup panel) to the maximum value
>>>> (89), xwax's realtime thread gets a priority (RTPRIO) of 84. So it looks like
>>>> xwax's realtime thread does actually start when using Jack on my computer (but
>>>> you wrote it shouldn't?)
>>> I'm not familiar with the implementation details of JACK, but it sounds
>>> like this thread is a part of JACK's operation, not one of xwax's own. So
>>> it would make sense that it is calling process_callback() from jack.c.
>>>
>>> You can confirm if xwax is starting its own thread. If it is, it will
>>> print:
>>>
>>>      Launching realtime thread to handle devices...
>>>
>>> to the console.
>>>
>> xwax is not starting its own thread. "Launching realtime thread to
>> handle devices... " is not printed.
>>>> Having the priority to 84 doesn't make a difference.
>>>>
>>>>> [...]
>>>>>> Where does this value  15 come from?
>>>>> Not sure. Are the rest of the apps in the system at 15?
>>>> Seems that it was a pro-rata of the default priority of jackd (20).
>>>> So:
>>>> Jackd priority = 20 =>     xwax priority = 15
>>>> Jackd priority = 89 =>     xwax priority = 84
>>>>
>>>>> I'm watching this thread, but haven't had any good suggestions to offer so
>>>>> far. How did you make the recordings before? Perhaps you could take a
>>>>> recording from within JACK; eg. route the audio straight through to
>>>>> Ardour to determine whether the problem is with xwax feeding audio into
>>>>> JACK, or with JACK feeding audio to the soundcard.
>>>>>
>>>> Regarding the previous recording (export_jack.ogg):
>>>> xwax's output was directly routed to Ardour. So the problem seems to be with
>>>> xwax feeding audio into JACK.
>>> It's not a bug I've seen before, but it sounds almost like you have the
>>> same buffers of audio being repeated. The most likely bug surrounds the
>>> processing in process_deck() of jack.c.
>>>
>>> I'm not aware of any bugs in the xwax JACK output, so it would be good to
>>> get to the bottom of this.
>>>
>>> Can you modify the value of MAX_BLOCK in jack.c and see if this changes
>>> the sound you hear? Perhaps use some music to test, rather than
>>> scratching.
>>>
>> I modified the value of MAX_BLOCK (with values from 1 up to 100000) and
>> this doesn't change the sound I hear.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>> http://p.sf.net/sfu/lotusphere-d2d
>>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
>

On Wed, 22 Dec 2010, Matthieu Caron wrote:

> Well.... I found the issue...... Which was that my input sound was too
> high.... so obvious.
> 
> I was confused because it's working great with ALSA.

Was it possible to see this in the scope? ie. was the circle no longer a 
circle, but a square?
 
> So....
> Why is there a difference between input levels in ALSA and Jack?
> (Is the sound amplified by jack?)

I don't know. But it's entirely possible I made a mistake in the code. 
Perhaps you can generate a full scale test tone using a JACK output, and 
feed that into xwax and see what level it comes in.

> Comment regarding xwax:
> xwax does a very good job by adapting the input level to its needs , so it is
> easy to get strong /circle/ in the timecode scope.
> As I got a strong circle for almost all input volume, it is difficult to know
> if I am close or far from the ideal input level.

xwax doesn't care about the volume, as long as it can decode the two 
circles. But when scratching it's possible you hit the edges, and that's 
sometimes not so clear in the scope, but it is there.
 
> My amplifier (NAD PP 2i) doesn't have a gain button. So I am using jack-rack
> to reduce the input level for xwax. (no option to reduce input in my
> mixer(audiophile 24/96)).
> Is there a better way?

If you can reduce the level in the digital domain then it means something 
strange is happening somewhere. eg. that the audio is being artificially 
amplified within JACK.

I just checked the xwax jack.c and it seems sensible at a glance; audio 
valies from JACK of +/-1.0 float are translated to +/-32768.
 
> Xwax works great now. I am verrrry happy. Thank you for a nice software.

Glad you worked it out! Enjoy xwax-ing.

-- 
Mark

On Sat, 4 Dec 2010, Andreas Gustafsson wrote:

> Im having problem with the absolute positioning for traktor_a /
> traktor_b timecodes. It works in speeds between 10% and 60% any faster
> and the timecode is not read, only the pitch.

It sounds most likely that your input audio is clipping, which would 
destroy the part of the signal used for absolute postioning. This would 
explain why you can get the timecode at lower speeds, becuase the input 
audio is at lower volume.

What does the scope display look like? Is it a pair of circles, or has it 
become square?

-- 
Mark

Apperently the signal was not strong enough.

Putting some more pressure on the needle did the trick...

Best regards,
Andreas

lör 2010-12-04 klockan 10:10 +0100 skrev Andreas Gustafsson:
> Hi!
> 
> Im having problem with the absolute positioning for traktor_a /
> traktor_b timecodes. It works in speeds between 10% and 60% any faster
> and the timecode is not read, only the pitch.
> 
> The site http://www.xwax.co.uk/overview.html says "All vinyls are
> supported with absolute positioning".
> 
> Is this a known issue?
> 
> Having same problem in xwax 0.7-5 thats packed for debian as well as the
> 0.8 version on the web-page.
> 
> Thanks!
> Andreas
> 
> 
> 
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly 
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus 
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d