From: Martin D. <Mar...@we...> - 2009-10-17 09:22:12
|
Hi all, When Muse (1.0rc3) is playing and I jump back to an earlier position in the song (e.g. via the locator GUI) I sometimes hear a crackling sound for a few seconds. It does not happen when I play the song sequentially and it always goes away after a few seconds. It sounds as if something got confused and then "settles" after a while. I wonder if this has anything to do with audio plugins which are not properly reset. I saw an option in ardour which controls resetting plugins and there is no such option in Muse. Has anybody else noticed this? -- Martin |
From: Robert J. <spa...@gm...> - 2009-10-17 09:59:19
|
Hello Martin, Indeed I have and so far I haven't been able to find the cause. I think it happens even without plugins so I don't think they are involved. You wouldn't by any chance be running a multi-core system? As I have written before I have a distinct feeling this is worse on multi-cores. Even happens during playback... /Robert 2009/10/17 Martin Drautzburg <Mar...@we...> > Hi all, > > When Muse (1.0rc3) is playing and I jump back to an earlier position in > the > song (e.g. via the locator GUI) I sometimes hear a crackling sound for a > few > seconds. It does not happen when I play the song sequentially and it always > goes away after a few seconds. It sounds as if something got confused and > then "settles" after a while. > > I wonder if this has anything to do with audio plugins which are not > properly > reset. I saw an option in ardour which controls resetting plugins and there > is no such option in Muse. > > Has anybody else noticed this? > > -- > Martin > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user > |
From: Viktor M. <vi...@ma...> - 2009-10-17 13:56:48
|
> > I sometimes hear a crackling sound for a few > seconds.... > > You wouldn't by any chance be running a multi-core system? > Yes, I am on a dual core system, just installed the latest CVS, crackling sound is there on playback, though not always. Viktor www.meditera.co.uk |
From: Martin D. <Mar...@we...> - 2009-10-17 17:38:31
|
On Saturday, 17. October 2009 11:59:01 Robert Jonsson wrote: > Hello Martin, > > Indeed I have and so far I haven't been able to find the cause. I think it > happens even without plugins so I don't think they are involved. > > You wouldn't by any chance be running a multi-core system? Yes, I am on a Core2 duo system. If that is the cause, it should help to tie muse to one core? If that is really a multi-core issue I wonder what Muse could possibly do wrong in this respect. I mean the code is unaware of multi-core, this is all handled by the OS. So it might well be an alsa or a jack issue. Then this problem should be present in all audio applications, which might well be the case, but I wouln't know it because I am using Muse almost exclusively. I will google for similar problems in ardour and other applications. |
From: Martin D. <Mar...@we...> - 2009-10-18 17:52:25
|
On Saturday, 17. October 2009 19:37:15 Martin Drautzburg wrote: I tried a few things and here is what I found: > I will google for similar problems in ardour and other applications. I did not find anything relevant for such a subtle problem. > Yes, I am on a Core2 duo system. If that is the cause, it should help to > tie muse to one core? I tried to bind Muse to a single CPU by running /home/martin >sudo taskset -p 1 6289 pid 6289's current affinity mask: 3 pid 6289's new affinity mask: 1 But that didn't fix the cackling. I tried the same with jackd, but again I can still reproduce the crackling. I also found that relocating within the song (which I did A LOT for testing this) sometimes stops jack. I see messages on stderr like FIFO 0x8ae0810 underrun... 0 WaveTrack::getData(MartinRaw) fifo underrun FIFO 0x8a90ca0 underrun... 0 WaveTrack::getData(JolaRaw) fifo underrun ... and then a window pops up saying: "Jack has detected a performance problem which has lead to MusE being disconnected ...." For some reasons this happens a lot more when using the marker window than when I click on the "bar" ruler on the GUI. I set the jackd timeout to 500 msecs and this seems to fix this problem. Then I played with other jackd settings. I increased the periods/buffer from 32 to 256 and the crackling seems gone. I had set it to 32 when I had gotten my new core2 duo machine, because I felt it should be fast enough to handle that. Maybe other users have the same tendency, which created the rumor that it has something to do with dual-core systems. Setting -p 256 also fixed another nuisance: with -p32 or -p64 I can hear a faint high-pitched hiss as soon as muse starts, even though it is not playing. It is better with -p64 than with -p32. With -p 256 it is not completely gone but hardly noticable (way below the noise level of my wireless fm headphone, I can only hear it with a wired headphone). I am not sure if this is audio related at all. It could well be interferences of the power supply or something like that. So here's my current .jackdrc /usr/bin/jackd -R -t500 -dalsa -r48000 -p256 -n3 -D -Chw:0 -Phw:0 -Xseq This gives me 16msecs latency. Nothing to write home about, but acceptable. For now all is fine. No more crackling, no more high pitched noise. -- Martin |
From: MST <bab...@gm...> - 2009-10-18 19:14:02
|
Hi, I don't want to wake sleeping dogs, but in ardour forum there was a discussion about strange noise appearing ... http://ardour.org/node/3063 Of course I do not say it has to do with your problems. Good luck, Michael -------- Original-Nachricht -------- > Datum: Sun, 18 Oct 2009 19:48:39 +0200 > Von: Martin Drautzburg <Mar...@we...> > An: lmu...@li... > Betreff: Re: [Lmuse-user] Crackling sound after rewind > On Saturday, 17. October 2009 19:37:15 Martin Drautzburg wrote: > > I tried a few things and here is what I found: > > > I will google for similar problems in ardour and other applications. > > I did not find anything relevant for such a subtle problem. > > > Yes, I am on a Core2 duo system. If that is the cause, it should help to > > tie muse to one core? > > I tried to bind Muse to a single CPU by running > > /home/martin >sudo taskset -p 1 6289 > pid 6289's current affinity mask: 3 > pid 6289's new affinity mask: 1 > > But that didn't fix the cackling. I tried the same with jackd, but again I > can > still reproduce the crackling. > > I also found that relocating within the song (which I did A LOT for > testing > this) sometimes stops jack. I see messages on stderr like > > FIFO 0x8ae0810 underrun... 0 > WaveTrack::getData(MartinRaw) fifo underrun > FIFO 0x8a90ca0 underrun... 0 > WaveTrack::getData(JolaRaw) fifo underrun > ... > and then a window pops up saying: "Jack has detected a performance problem > which has lead to MusE being disconnected ...." For some reasons this > happens > a lot more when using the marker window than when I click on the "bar" > ruler > on the GUI. I set the jackd timeout to 500 msecs and this seems to fix > this > problem. > > Then I played with other jackd settings. I increased the periods/buffer > from > 32 to 256 and the crackling seems gone. I had set it to 32 when I had > gotten > my new core2 duo machine, because I felt it should be fast enough to > handle > that. Maybe other users have the same tendency, which created the rumor > that > it has something to do with dual-core systems. > > Setting -p 256 also fixed another nuisance: with -p32 or -p64 I can hear a > faint high-pitched hiss as soon as muse starts, even though it is not > playing. It is better with -p64 than with -p32. With -p 256 it is not > completely gone but hardly noticable (way below the noise level of my > wireless fm headphone, I can only hear it with a wired headphone). I am > not > sure if this is audio related at all. It could well be interferences of > the > power supply or something like that. > > So here's my current .jackdrc > > /usr/bin/jackd -R -t500 -dalsa -r48000 -p256 -n3 -D -Chw:0 -Phw:0 -Xseq > > This gives me 16msecs latency. Nothing to write home about, but > acceptable. > > For now all is fine. No more crackling, no more high pitched noise. > > -- > Martin > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02 |
From: Robert J. <spa...@gm...> - 2009-10-18 21:59:04
|
Ok, very good that having larger buffers helped. Hopefully this is the state for most people. I still have the problems but I can work around it. /Robert 2009/10/18 Martin Drautzburg <Mar...@we...> > On Saturday, 17. October 2009 19:37:15 Martin Drautzburg wrote: > > I tried a few things and here is what I found: > > > I will google for similar problems in ardour and other applications. > > I did not find anything relevant for such a subtle problem. > > > Yes, I am on a Core2 duo system. If that is the cause, it should help to > > tie muse to one core? > > I tried to bind Muse to a single CPU by running > > /home/martin >sudo taskset -p 1 6289 > pid 6289's current affinity mask: 3 > pid 6289's new affinity mask: 1 > > But that didn't fix the cackling. I tried the same with jackd, but again I > can > still reproduce the crackling. > > I also found that relocating within the song (which I did A LOT for testing > this) sometimes stops jack. I see messages on stderr like > > FIFO 0x8ae0810 underrun... 0 > WaveTrack::getData(MartinRaw) fifo underrun > FIFO 0x8a90ca0 underrun... 0 > WaveTrack::getData(JolaRaw) fifo underrun > ... > and then a window pops up saying: "Jack has detected a performance problem > which has lead to MusE being disconnected ...." For some reasons this > happens > a lot more when using the marker window than when I click on the "bar" > ruler > on the GUI. I set the jackd timeout to 500 msecs and this seems to fix this > problem. > > Then I played with other jackd settings. I increased the periods/buffer > from > 32 to 256 and the crackling seems gone. I had set it to 32 when I had > gotten > my new core2 duo machine, because I felt it should be fast enough to handle > that. Maybe other users have the same tendency, which created the rumor > that > it has something to do with dual-core systems. > > Setting -p 256 also fixed another nuisance: with -p32 or -p64 I can hear a > faint high-pitched hiss as soon as muse starts, even though it is not > playing. It is better with -p64 than with -p32. With -p 256 it is not > completely gone but hardly noticable (way below the noise level of my > wireless fm headphone, I can only hear it with a wired headphone). I am not > sure if this is audio related at all. It could well be interferences of the > power supply or something like that. > > So here's my current .jackdrc > > /usr/bin/jackd -R -t500 -dalsa -r48000 -p256 -n3 -D -Chw:0 -Phw:0 -Xseq > > This gives me 16msecs latency. Nothing to write home about, but acceptable. > > For now all is fine. No more crackling, no more high pitched noise. > > -- > Martin > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user > |
From: Mr. K. <kp...@st...> - 2009-10-20 03:51:02
|
This something that I think has always happened with Muse for me but I thought it was a jack/perfomance/resource issue. I would think that jumping the song pointer around would not be a normal event so I thought the response was acceptable. Is audio actually a "plugin" for Muse? Does anyone know if doing a similar function in ardour or rosegarden exhibit the same response? Quoting Martin Drautzburg <Mar...@we...>: > Hi all, > > When Muse (1.0rc3) is playing and I jump back to an earlier position in the > > song (e.g. via the locator GUI) I sometimes hear a crackling sound for a few > > seconds. It does not happen when I play the song sequentially and it always > goes away after a few seconds. It sounds as if something got confused and > then "settles" after a while. > > I wonder if this has anything to do with audio plugins which are not properly > > reset. I saw an option in ardour which controls resetting plugins and there > is no such option in Muse. > > Has anybody else noticed this? > > -- > Martin > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user > --- --- | | | Studio K Productions LLC Keith C. Perry, Exec. Producer | | http://studiokproductions.com kp...@st... | | +1.215.525.4165 x2033 | | | --- --- ______________________________________ This email account is being hosted by: VCSN, Inc : http://vcsn.com |
From: Geoff B. <ge...@la...> - 2009-10-20 04:05:43
|
On Tuesday 20 October 2009 14:50:49 Mr. KP wrote: > Is audio actually a "plugin" for Muse? Does anyone know if doing a > similar function in ardour or rosegarden exhibit the same response? > not for me ;) crackling used to be a result of having a via/asus/acer chipset , but that was years ago. pci/dma issues. i had some issues with my AMD X2 dual core in the early days but again long ago. I get no crackling at all. BTW, I don't use MusE for audio at all... never have. g. |
From: Mr. K. <kp...@st...> - 2009-10-21 00:33:08
Attachments:
qjackd.png
|
Just to chime in on this with some more tests... I'm running Muse on a AMD Turion x64 (1.6Ghz) with 2Gb RAM. I'm in my everyday config (boot both procs with a non-realtime kernel). In this configuration, I run qjackctl to my Roland M-1000 digital mixer (via usb) in what I call "radio mode" which is to say that I'm using a high latency (34.8 msec - see the attached image for the exact config) Test song: a single stereo audio loop (the baggage room bump from Adult Swim if anyone cares) about 20 measures at 93.6 BPM (4/4 time). Track and Out volumes were set to 0dB. Test Set #1 1) Loop Noise (i.e. sample artifacts heard after play loop) no 2) Forward Scrub Noise (i.e. draging red play cursor forward at least 3 measures generates aritfacts after cursor is released) no 3) Reverse Scrub Noise (i.e. draging red play cursor backward at least 3 measures generates aritfacts after cursor is released) no 4) Forward Jump Noise (i.e. clicking on a measure at least 3 measures ahead generates aritfacts) yes, consistantly for all cases, amount of noise vaired 5) Reverse Jump Noise (i.e. clicking on a measure at least 3 measures behind generates aritfacts) yes, consistantly for all cases, amount of noise vaired So, #4 and #5 I think is what was reported here but its kind of suprising since there was no noise during scrubbing (#2 and #3). Now to test single core work. Instead of rebooting in my single proc config I used the taskset program (which is what most people would do). For the next group of tests I fired up a shell on my second proc with "taskset 0x02 xterm" (for those who don't know this, when you use taskset this way anything launched from that shell will use the same processor affinity). From there I ran qjackctl and used the same config as above. I then loaded Muse and the same song file. Test Set #2 (single processor) 1) Loop Noise (i.e. sample artifacts heard after play loop) no 2) Forward Scrub Noise (i.e. draging red play cursor forward at least 3 measures generates aritfacts after cursor is released) no 3) Reverse Scrub Noise (i.e. draging red play cursor backward at least 3 measures generates aritfacts after cursor is released) no 4) Forward Jump Noise (i.e. clicking on a measure at least 3 measures ahead generates aritfacts) no 5) Reverse Jump Noise (i.e. clicking on a measure at least 3 measures behind generates aritfacts) no Sure enough the jump noise issue went away when only running with one processor. At one point I starting clicking all around the song *trying* to get some noise and I couldn't. Also in both cases I did not get any jack xruns. Hope this is useful. Quoting Martin Drautzburg <Mar...@we...>: > On Saturday, 17. October 2009 19:37:15 Martin Drautzburg wrote: > > I tried a few things and here is what I found: > > > I will google for similar problems in ardour and other applications. > > I did not find anything relevant for such a subtle problem. > > > Yes, I am on a Core2 duo system. If that is the cause, it should help to > > tie muse to one core? > > I tried to bind Muse to a single CPU by running > > /home/martin >sudo taskset -p 1 6289 > pid 6289's current affinity mask: 3 > pid 6289's new affinity mask: 1 > > But that didn't fix the cackling. I tried the same with jackd, but again I > can > still reproduce the crackling. > > I also found that relocating within the song (which I did A LOT for testing > this) sometimes stops jack. I see messages on stderr like > > FIFO 0x8ae0810 underrun... 0 > WaveTrack::getData(MartinRaw) fifo underrun > FIFO 0x8a90ca0 underrun... 0 > WaveTrack::getData(JolaRaw) fifo underrun > ... > and then a window pops up saying: "Jack has detected a performance problem > which has lead to MusE being disconnected ...." For some reasons this happens > > a lot more when using the marker window than when I click on the "bar" ruler > > on the GUI. I set the jackd timeout to 500 msecs and this seems to fix this > problem. > > Then I played with other jackd settings. I increased the periods/buffer from > > 32 to 256 and the crackling seems gone. I had set it to 32 when I had gotten > > my new core2 duo machine, because I felt it should be fast enough to handle > that. Maybe other users have the same tendency, which created the rumor that > > it has something to do with dual-core systems. > > Setting -p 256 also fixed another nuisance: with -p32 or -p64 I can hear a > faint high-pitched hiss as soon as muse starts, even though it is not > playing. It is better with -p64 than with -p32. With -p 256 it is not > completely gone but hardly noticable (way below the noise level of my > wireless fm headphone, I can only hear it with a wired headphone). I am not > sure if this is audio related at all. It could well be interferences of the > power supply or something like that. > > So here's my current .jackdrc > > /usr/bin/jackd -R -t500 -dalsa -r48000 -p256 -n3 -D -Chw:0 -Phw:0 -Xseq > > This gives me 16msecs latency. Nothing to write home about, but acceptable. > > For now all is fine. No more crackling, no more high pitched noise. > > -- > Martin > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user > --- --- | | | Studio K Productions LLC Keith C. Perry, Exec. Producer | | http://studiokproductions.com kp...@st... | | +1.215.525.4165 x2033 | | | --- --- ______________________________________ This email account is being hosted by: VCSN, Inc : http://vcsn.com |
From: Tim <ter...@ro...> - 2009-11-05 04:37:28
|
Hi Keith. Maybe a question you already answered at this point, but if you are using Jack 1, did you remember to compile Jack with the --with-default-tmpdir option? I always find it essential to turn that on. And if it's Jack version 2, I read in the docs that it still uses FIFOs and is not very stable. It wasn't for me. Any xruns? QJackCtl may say 'RT' but check the messages (verbose on, AND capture std out) it might not be really be, uh, realtime... In the last few weeks I have switched my production to a different machine, roughly same age as old one (P4 2.2G ~10 years), but with a much newer distro (old Mandriva 2007.1, new 2009.1) (That's when I found a few age-related muse bugs, hence my recent commit.) So I can report that after about 1 week of getting everything rock solid (getting the RT kernel, turning on realtime and setting limits, compiling Jack as above), I have heard crackling noise in muse once, ~2 days ago. Not a hiss, hum, oscillation, distortion, or aliasing, but crackling like a fire. It remained there no matter what until I restarted Jack. Also it appeared to be the cause of crashing simply by moving the red cursor around. I'm using Jack 0.116.2 In case anyone else suspects this too, IIRC the crashes were at AudioTrack::getData() at the line: ir->track->copyData(...) which I suspect means the route track was invalid. Weird... Watching, waiting, always something lurking in there... Tim. On Tuesday 20 October 2009 08:12:25 pm Mr. KP wrote: > Just to chime in on this with some more tests... > > I'm running Muse on a AMD Turion x64 (1.6Ghz) with 2Gb RAM. I'm in my > everyday config (boot both procs with a non-realtime kernel). In this > configuration, I run qjackctl to my Roland M-1000 digital mixer (via usb) > in what I call "radio mode" which is to say that I'm using a high latency > (34.8 msec - see the attached image for the exact config) > > Test song: > a single stereo audio loop (the baggage room bump from Adult Swim if anyone > cares) about 20 measures at 93.6 BPM (4/4 time). Track and Out volumes > were set to 0dB. > > Test Set #1 > 1) Loop Noise (i.e. sample artifacts heard after play loop) > no > > 2) Forward Scrub Noise (i.e. draging red play cursor forward at least 3 > measures generates aritfacts after cursor is released) > no > > 3) Reverse Scrub Noise (i.e. draging red play cursor backward at least 3 > measures generates aritfacts after cursor is released) > no > > 4) Forward Jump Noise (i.e. clicking on a measure at least 3 measures ahead > generates aritfacts) > yes, consistantly for all cases, amount of noise vaired > > 5) Reverse Jump Noise (i.e. clicking on a measure at least 3 measures > behind generates aritfacts) > yes, consistantly for all cases, amount of noise vaired > > > So, #4 and #5 I think is what was reported here but its kind of suprising > since there was no noise during scrubbing (#2 and #3). Now to test single > core work. Instead of rebooting in my single proc config I used the > taskset program (which is what most people would do). For the next group > of tests I fired up a shell on my second proc with "taskset 0x02 xterm" > (for those who don't know this, when you use taskset this way anything > launched from that shell will use the same processor affinity). From there > I ran qjackctl and used the same config as above. I then loaded Muse and > the same song file. > > > Test Set #2 (single processor) > 1) Loop Noise (i.e. sample artifacts heard after play loop) > no > > 2) Forward Scrub Noise (i.e. draging red play cursor forward at least 3 > measures generates aritfacts after cursor is released) > no > > 3) Reverse Scrub Noise (i.e. draging red play cursor backward at least 3 > measures generates aritfacts after cursor is released) > no > > 4) Forward Jump Noise (i.e. clicking on a measure at least 3 measures ahead > generates aritfacts) > no > > 5) Reverse Jump Noise (i.e. clicking on a measure at least 3 measures > behind generates aritfacts) > no > > > Sure enough the jump noise issue went away when only running with one > processor. At one point I starting clicking all around the song *trying* > to get some noise and I couldn't. > > Also in both cases I did not get any jack xruns. > > Hope this is useful. > > Quoting Martin Drautzburg <Mar...@we...>: > > On Saturday, 17. October 2009 19:37:15 Martin Drautzburg wrote: > > > > I tried a few things and here is what I found: > > > I will google for similar problems in ardour and other applications. > > > > I did not find anything relevant for such a subtle problem. > > > > > Yes, I am on a Core2 duo system. If that is the cause, it should help > > > to tie muse to one core? > > > > I tried to bind Muse to a single CPU by running > > > > /home/martin >sudo taskset -p 1 6289 > > pid 6289's current affinity mask: 3 > > pid 6289's new affinity mask: 1 > > > > But that didn't fix the cackling. I tried the same with jackd, but again > > I can > > still reproduce the crackling. > > > > I also found that relocating within the song (which I did A LOT for > > testing this) sometimes stops jack. I see messages on stderr like > > > > FIFO 0x8ae0810 underrun... 0 > > WaveTrack::getData(MartinRaw) fifo underrun > > FIFO 0x8a90ca0 underrun... 0 > > WaveTrack::getData(JolaRaw) fifo underrun > > ... > > and then a window pops up saying: "Jack has detected a performance > > problem which has lead to MusE being disconnected ...." For some reasons > > this happens > > > > a lot more when using the marker window than when I click on the "bar" > > ruler > > > > on the GUI. I set the jackd timeout to 500 msecs and this seems to fix > > this problem. > > > > Then I played with other jackd settings. I increased the periods/buffer > > from > > > > 32 to 256 and the crackling seems gone. I had set it to 32 when I had > > gotten > > > > my new core2 duo machine, because I felt it should be fast enough to > > handle that. Maybe other users have the same tendency, which created the > > rumor that > > > > it has something to do with dual-core systems. > > > > Setting -p 256 also fixed another nuisance: with -p32 or -p64 I can hear > > a faint high-pitched hiss as soon as muse starts, even though it is not > > playing. It is better with -p64 than with -p32. With -p 256 it is not > > completely gone but hardly noticable (way below the noise level of my > > wireless fm headphone, I can only hear it with a wired headphone). I am > > not sure if this is audio related at all. It could well be interferences > > of the power supply or something like that. > > > > So here's my current .jackdrc > > > > /usr/bin/jackd -R -t500 -dalsa -r48000 -p256 -n3 -D -Chw:0 -Phw:0 -Xseq > > > > This gives me 16msecs latency. Nothing to write home about, but > > acceptable. > > > > For now all is fine. No more crackling, no more high pitched noise. > > > > -- > > Martin > > > > ------------------------------------------------------------------------- > >----- Come build with us! The BlackBerry(R) Developer Conference in SF, CA > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and stay > > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > > http://p.sf.net/sfu/devconference > > _______________________________________________ > > Lmuse-user mailing list > > Lmu...@li... > > https://lists.sourceforge.net/lists/listinfo/lmuse-user > > --- --- > > | Studio K Productions LLC Keith C. Perry, Exec. Producer | > | http://studiokproductions.com kp...@st... | > | +1.215.525.4165 x2033 | > > --- --- > > > ______________________________________ > This email account is being hosted by: > VCSN, Inc : http://vcsn.com |