gwc-general — Gnome Wave Cleaner discussion list

Re: [Gwc-general] LADSPA plugin(s)

[Jeff W. <we...@ya...>]

Hi Nik,

I have been lax in keeping gwc-lib up to date, so it does not represent
the best technology that is found in gwc-0.21-05.  I had intended 
integrating
gwc and gwc-lib, but never got around to it.

Sadly, you can't turn either the denoising or the declicking algorithms into
LADSPA plugins, or I would have done that instead of gwc-lib.  It is because
the gwc algorithms are non-causal (if I remember the term correctly), 
i.e. it
is not 1 frame in and 1 frame out, the algorithms work on overlapping 
frames,
and declicking literally runs from the end to start instead of vice-versa.

If someone wanted to take gwc-0.21-05 and re-create the gwc-lib from it,
and then make gwc use gwc-lib, that would be a great step forward.  There
may be a small speed penalty but we can evaluate that.

Cheers,
Jeff

Nik wrote:

> Hi,
>
> My original concept was to write a LADSPA plugin to incorporate the 
> functionality of Gramofile into Audacity. When I posted about this on 
> the Audacity forums, the reply was that previous discussion had 
> decided to wait until GWC was separated into frontend and backend, and 
> then use the gwc-lib to create such a plugin.
>
> So, I'm putting my hand up to attempt this work. My questions are:
>
> 1. Is the gwc-lib-0.05 that I downloaded from SourceForge recent 
> enough to perform this work? It seems to be a little light - and 
> possibly a little out of date?
>
> 2. Is the code in the more recent GWC gwc-0.21-05 easily separated 
> into frontend and backend? I've built gwc from it, and it seems to 
> have no obvious library.
>
> 3. I notice in the TODO file a task to LADSPA-ise the filters. This is 
> certainly in the realm of what I'm looking at doing. Can anyone offer 
> any help in identifying the files needed by such a plugin?
>
> 4. Has anyone already started work on this, and if so, do they want 
> help, or are they hapily progressing in their own time?
>
>
> Any and all responses welcome.
>
>
> Cheers!
> Nik
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding 
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
> !DSPAM:4410e291168321552818589!

[Gwc-general] LADSPA plugin(s)

[Nik <ni...@us...>]

Hi,

My original concept was to write a LADSPA plugin to incorporate the 
functionality of Gramofile into Audacity. When I posted about this on 
the Audacity forums, the reply was that previous discussion had decided 
to wait until GWC was separated into frontend and backend, and then use 
the gwc-lib to create such a plugin.

So, I'm putting my hand up to attempt this work. My questions are:

1. Is the gwc-lib-0.05 that I downloaded from SourceForge recent enough 
to perform this work? It seems to be a little light - and possibly a 
little out of date?

2. Is the code in the more recent GWC gwc-0.21-05 easily separated into 
frontend and backend? I've built gwc from it, and it seems to have no 
obvious library.

3. I notice in the TODO file a task to LADSPA-ise the filters. This is 
certainly in the realm of what I'm looking at doing. Can anyone offer 
any help in identifying the files needed by such a plugin?

4. Has anyone already started work on this, and if so, do they want 
help, or are they hapily progressing in their own time?


Any and all responses welcome.


Cheers!
Nik

[Gwc-general] LADSPA plugin(s)

[Nik <ni...@us...>]

Hi,

My original concept was to write a LADSPA plugin to incorporate the 
functionality of Gramofile into Audacity. When I posted about this on 
the Audacity forums, the reply was that previous discussion had decided 
to wait until GWC was separated into frontend and backend, and then use 
the gwc-lib to create such a plugin.

So, I'm putting my hand up to attempt this work. My questions are:

1. Is the gwc-lib-0.05 that I downloaded from SourceForge recent enough 
to perform this work? It seems to be a little light - and possibly a 
little out of date?

2. Is the code in the more recent GWC gwc-0.21-05 easily separated into 
frontend and backend? I've built gwc from it, and it seems to have no 
obvious library.

3. I notice in the TODO file a task to LADSPA-ise the filters. This is 
certainly in the realm of what I'm looking at doing. Can anyone offer 
any help in identifying the files needed by such a plugin?

4. Has anyone already started work on this, and if so, do they want 
help, or are they hapily progressing in their own time?


Any and all responses welcome.


Cheers!
Nik

Re: [Gwc-general] Thought I had a clue, maybe not

[Jeff W. <we...@ya...>]

2 things to consider:

1) If you tell GWC to only remove the strong clicks, it will leave any 
clicks that
fall below it's threshold of "strong".   These  may still be audible.

2) GWC only displays red lines for the first 1000 clicks not repaired.  
So there may
be > 1000 clicks it couldn't repair.  There are 2 reasons for not 
repairing a click, first
the repair algorithm can just plain fail (the rare case), and second if 
it determines the
width of the click in samples is > 100.

I suggest you extract a small section of audio, no more than 2 seconds 
which has
clicks and get comfortable with what GWC is doing -- you can set the strong
and weak click detection thresholds in the menus, so play around with 
that if
too many clicks are getting thru.

Hope that helps, and keep asking for help if you are stuck or not clear 
on what to do.

Cheers,
Jeff

Bobby Goins wrote:

>OK,  I have the latest gwc up and running.  
>
>I tried to 'remove strong clicks' as 'root' on a wave file taken from vinyl.  
>After some time (since I start this from the command line, I get to watch the 
>samples being processed), gwc tells me that it repaired so many clicks and 
>did not repair so many clicks, and there are red lines on the signal window.  
>This is all well and fine, but the clicks are still showing on the signal 
>window and are still audible when played back.  Saving the file after being 
>repaired gives me what I started out with.   
>
>What am I not doing?
>
>Bob  
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:4407b624181291166326961!
>  
>

[Gwc-general] Thought I had a clue, maybe not

[Bobby G. <go...@ig...>]

OK,  I have the latest gwc up and running.  

I tried to 'remove strong clicks' as 'root' on a wave file taken from vinyl.  
After some time (since I start this from the command line, I get to watch the 
samples being processed), gwc tells me that it repaired so many clicks and 
did not repair so many clicks, and there are red lines on the signal window.  
This is all well and fine, but the clicks are still showing on the signal 
window and are still audible when played back.  Saving the file after being 
repaired gives me what I started out with.   

What am I not doing?

Bob  

[Gwc-general] GWC 0.21-05 released.

[Jeff W. <we...@ya...>]

I just put 0.21-05 up on sourceforge.

There are several bugfixes -- many thanks to David Gesswein for finding 
them, notably
if you have an audio file already open and then do a file->open 
operation the *.gwc file
would get corrupted.

Also I found a big bug in the Lorber-Hoeldrich denoising algorithm 
implementation.  The
bugfix makes the denoising result *dramatically* better.

I've been using FFT_SIZE of 4096, reduction of 0.5, gamma of 0.95, 
Hanning-overlap-add windowing
with Lorber-Hoedrich with great success.

Also,  a few configuration reports have come in about not finding 
libsndfile.  Looks like some of the
linux distributions are installing libsndfile as a binary package for 
you, but you'll also need the
libsndfile-devel package to compile GWC.  I modified the configure 
script to suggest that as well.

Enjoy,
Jeff

Re: [Gwc-general] problem with configure finding libsndfile - solved

[Ken D. <kd...@de...>]

Jeff,

I hate to say it but it seems that while I actually downloaded libsndfile, =
it=20
was really installed from the Suse CDs.

Hope this has not caused much trouble.

Ken

> Did you install libsndfile from the source code or via a pre-compiled=20
> package?  If from a pre-compiled
> package you may need to install a development version of the library as=20
> well.
>=20
> Let me know -- I may need to modify the config script to suggest that too.
>=20
> jw
>=20
> Ken Dere wrote:
>=20
>I have just downloaded gwc-0.21-04 and am trying to compile it. =A0configu=
re=20
>says:
>
>checking for pkg-config... /usr/bin/pkg-config
>checking for sndfile >=3D 1.0.0... configure: error:
>Libsndfile 1.0.2 or greater needed, find it at=20
>http://www.zip.com.au/~erikd/libsndfile/
>OR perhaps configure can not file libsndfile, in which you can try 1 of 2=
=20
>things:
>1) set the environment variable PKG_CONFIG_PATH
> =A0 to find the packag file for libsndfile for example:
> =A0 export PKG_CONFIG_PATH=3D/usr/local/lib/pkgconfig
>2) re-install libsndfile in /usr instead of /usr/local, where it installs =
by=20
>default.
>
>however,=20
>
> =A0
>
>>ls /usr/lib/libsndfile*
>> =A0 =A0
>>
>/usr/lib/libsndfile.so.1 =A0/usr/lib/libsndfile.so.1.0.11
>
>so it seems to me that it is actually there. =A0I also had this problem wi=
th=20
>gwc-0.20-10b
>
>I have tried ./configure --prefix=3D/usr but that does not help
>
>I am running Suse 10.0
>
>TIA
>=20
>Ken Dere
>
=2D-=20
Ken Dere

Re: [Gwc-general] problem with configure finding libsndfile

[Jeff W. <we...@ya...>]

Did you install libsndfile from the source code or via a pre-compiled 
package?  If from a pre-compiled
package you may need to install a development version of the library as 
well.

Let me know -- I may need to modify the config script to suggest that too.

jw

Ken Dere wrote:

>I have just downloaded gwc-0.21-04 and am trying to compile it.  configure 
>says:
>
>checking for pkg-config... /usr/bin/pkg-config
>checking for sndfile >= 1.0.0... configure: error:
>Libsndfile 1.0.2 or greater needed, find it at 
>http://www.zip.com.au/~erikd/libsndfile/
>OR perhaps configure can not file libsndfile, in which you can try 1 of 2 
>things:
>1) set the environment variable PKG_CONFIG_PATH
>   to find the packag file for libsndfile for example:
>   export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
>2) re-install libsndfile in /usr instead of /usr/local, where it installs by 
>default.
>
>however, 
>
>  
>
>>ls /usr/lib/libsndfile*
>>    
>>
>/usr/lib/libsndfile.so.1  /usr/lib/libsndfile.so.1.0.11
>
>so it seems to me that it is actually there.  I also had this problem with 
>gwc-0.20-10b
>
>I have tried ./configure --prefix=/usr but that does not help
>
>I am running Suse 10.0
>
>TIA
> 
>Ken Dere
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:43e50809323564648698647!
>  
>

[Gwc-general] problem with configure finding libsndfile

[Ken D. <kd...@de...>]

I have just downloaded gwc-0.21-04 and am trying to compile it.  configure 
says:

checking for pkg-config... /usr/bin/pkg-config
checking for sndfile >= 1.0.0... configure: error:
Libsndfile 1.0.2 or greater needed, find it at 
http://www.zip.com.au/~erikd/libsndfile/
OR perhaps configure can not file libsndfile, in which you can try 1 of 2 
things:
1) set the environment variable PKG_CONFIG_PATH
   to find the packag file for libsndfile for example:
   export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
2) re-install libsndfile in /usr instead of /usr/local, where it installs by 
default.

however, 

>ls /usr/lib/libsndfile*
/usr/lib/libsndfile.so.1  /usr/lib/libsndfile.so.1.0.11

so it seems to me that it is actually there.  I also had this problem with 
gwc-0.20-10b

I have tried ./configure --prefix=/usr but that does not help

I am running Suse 10.0

TIA
 
Ken Dere

Re: [Gwc-general] Interesting ogg encoding bug

[Jeff W. <we...@ya...>]

Ugg.  Sounds like maybe the oggenc options have changed since that was done.

I never use that feature myself -- being a purist. :D

I will have a look though.

jw

Chris Craig wrote:

> I've come across a fairly interesting bug when encoding a sample using 
> the ogg encoder.
>
> I prefer to use a quality level of 4.99, which produces files with a 
> nominal bitrate around 159 (I find using 5 uses some optimizations 
> that slightly degrade quality, using a nominal bitrate of exactly 159 
> forces this value which I also don't want). Anyway, I had both values 
> entered in the ogg preferences dialogue (4.99 and 159), although only 
> 1 is supposed to be used based on the "Ogg Encoding Mode" selected at 
> the bottom.
>
> What I found was that when the "Ogg Encoding Mode" was set to "Quality 
> Level", the selection was offset by an amount based on the "Nominal 
> Bitrate" value. In this case, with a nominal bitrate value of 159 it 
> would start encoding 1:59 seconds into the selected region, and 
> continue encoding for 1:59 seconds after the selected region. Actually 
> it may be 1.59 seconds, I haven't explored it that deeply.
>
> I checked through encode.c but haven't been able to find where the 
> problem lies. Maybe it's in preferences.c or somewhere else instead. I 
> could see if I can track it down and provide a patch, but of course if 
> you (Jeff) or Charles Morgan would prefer I'll leave it in your hands.
>

Re: [Gwc-general] A few general questions

[Jeff W. <we...@ya...>]

Hi John,

Sorry to take so long to reply.

The feather width "tapers" in (and out) the effect, so you don't have a 
hard edge produced -- think about amplification, and if you multiplied
each sample by 2, then with no feathering, the last sample amplified 
might jump from 1000 to 2000 -- this is almost guaranteed to produce
a new "click artifact..

For the biquad filter (which I admittedly implemented, playing around 
trying to get rid of 60hz hum), I'm not sure on the lowpass and high 
pass exactly what the center frequency refers to.  I have a document 
here titled "The Equivalence of Various Methods of Computing Biquad 
Coefficients for Audio Paramentric Equalizers" by Robert Bristow-Johnson 
which may serve as a starting point for you to investigate.

I think you should equate "center frequency" with "cutoff frequency".  a 
small bandwidth would give a sharp cutoff.

As for deleting the track, and leaving the *.wav.gwc file, the only 
bullet-proofing gwc does is to check that the number of samples, the 
number of channels and the audio rate are the same
for the *.wav.gwc file as the audio file itself.  Not likely a problem 
if you are using track_rec.

jw

John Cirillo wrote:

> Hi, I have been using GWC for a long time now, but some various 
> questions come up from time to time and I forget that I can ask about 
> them here.
> Here are the recent ones:
>
> 1) What is the effect of the 'feather width' parameter on the various 
> things it applies to (amplify, what else?).  I mean, what is it 
> looking at and how does this affect the result?
>
> 2) With the new DSP filters, how to set the center and octaves? 
> Supposing I want to do my own  decrackle by killing off the high end 
> at 8,000 Hz using the highpass function. What would I put?
>
> 3) What would be the effect of deleting a track, but accidentally 
> leaving behind the .wav.gwc file for it, and then recording a new 
> track with the same name and opening it in gwc?  This is a very real 
> possibility when using track_rec to record files so I wondered what 
> would happen (without actually trying it!)
>
> Thanks for any advice on these!
>
> John Cirillo
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
> !DSPAM:43c200df25981182232102!

[Gwc-general] Interesting ogg encoding bug

[Chris C. <ch...@ci...>]

I've come across a fairly interesting bug when encoding a sample using 
the ogg encoder.

I prefer to use a quality level of 4.99, which produces files with a 
nominal bitrate around 159 (I find using 5 uses some optimizations that 
slightly degrade quality, using a nominal bitrate of exactly 159 forces 
this value which I also don't want). Anyway, I had both values entered 
in the ogg preferences dialogue (4.99 and 159), although only 1 is 
supposed to be used based on the "Ogg Encoding Mode" selected at the bottom.

What I found was that when the "Ogg Encoding Mode" was set to "Quality 
Level", the selection was offset by an amount based on the "Nominal 
Bitrate" value. In this case, with a nominal bitrate value of 159 it 
would start encoding 1:59 seconds into the selected region, and continue 
encoding for 1:59 seconds after the selected region. Actually it may be 
1.59 seconds, I haven't explored it that deeply.

I checked through encode.c but haven't been able to find where the 
problem lies. Maybe it's in preferences.c or somewhere else instead. I 
could see if I can track it down and provide a patch, but of course if 
you (Jeff) or Charles Morgan would prefer I'll leave it in your hands.

-- 
Chris Craig
http://ciotog.net

[Gwc-general] A few general questions

[John C. <ci...@pu...>]

Hi, I have been using GWC for a long time now, but some 
various questions come up from time to time and I forget 
that I can ask about them here.
Here are the recent ones:

1) What is the effect of the 'feather width' parameter on 
the various things it applies to (amplify, what else?).  I 
mean, what is it looking at and how does this affect the 
result?

2) With the new DSP filters, how to set the center and 
octaves? Supposing I want to do my own  decrackle by killing 
off the high end at 8,000 Hz using the highpass function. 
What would I put?

3) What would be the effect of deleting a track, but 
accidentally leaving behind the .wav.gwc file for it, and 
then recording a new track with the same name and opening it 
in gwc?  This is a very real possibility when using 
track_rec to record files so I wondered what would happen 
(without actually trying it!)

Thanks for any advice on these!

John Cirillo

[Gwc-general] gwc will not remove clicks

[Bobby G. <go...@ig...>]

gwc will not remove clicks

I am using gwc 0.21.03 on a slackware 10.0 system (1
ghz with 377 MB RAM and 1 GB swap).

On trying to remove clicks on a large wave file (785.7
MB), the remove strong click process took 4.2 hours
correcting over 5000 clicks and not correcting a little
over 100 clicks - or so the output text said. However,
the graphic showed approximately 100 red lines with
none of the clicks actually removed. I saved the
'de-clicked' file as a wave, and it was identical to
the original file.

Did I do something wrong?

[Gwc-general] XSyncBadCounter when encoding mp3

[Geoff <cap...@ya...>]

Hi,

I have been using gwc 0-21-03 happily for the last week in
conjunction with audacity.

I had been doing mp3 encoding under audacity, but decided
to try gwc's capabilities.

I divided a wav into 4 tracks using "mark songs". 
Encoding appeared to succeed but no file was output to the
target directory.

I therefore ran gwc from a terminal, which produces this
output on encoding:

-----------------------------------------

MP3 preset is 4
The program 'gwc' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XSyncBadCounter'.
(Details: serial 27659 error_code 129 request_code 132
minor_code 6) (Note to programmers: normally, X errors are
reported asynchronously; that is, you will receive the
error a while after causing it. To debug your program, run
it with the --sync command line option to change this
behavior. You can then get a meaningful backtrace from your
debugger if you break on the gdk_x_error() function.)
Xlib: unexpected async reply (sequence 0x6c3d)!
Xlib:unexpected async reply (sequence 0x6c43)!
Xlib: unexpected async reply (sequence 0x6d8b)!
Xlib:unexpected async reply (sequence 0x7f8f)!

-----------------------------------------------

This error is entirely reproducible.  Once it has occurred
almost anything else I do with the program produces :

Xlib: sequence lost (0x101f4 > 0x101d6) in reply type 0x5

Further "unexpected async" reply errors then occur and
eventually gwc aborts - for example if I try to encode
another track.

I tried encoding one long track rather than dividing a wav
into sections, but this time the program just hung and had
to be killed.

I am on an smp box (2 x 1ghz PIII), running Xfree86 4.3.0
(getting a little old now), under the icewm WM ..... I
don't run gnome.  Maybe the problem is with my setup.

Geoff

		
___________________________________________________________ 
Yahoo! Model Search 2005 - Find the next catwalk superstars - http://uk.news.yahoo.com/hot/model-search/

Re: Alsa problems (Was: Re: [Gwc-general] GWC 0.21-03 is released)

[Jeff W. <we...@ya...>]

That is good news Johan.  Thanks for being willing to test this out.

Now it looks like the problem is the buffer size GWC is using for ALSA
is too small (512 bytes), which is probably the reason for the remaining
errors.

I'll tackle that next.

Cheers,
Jeff

Johan De Groote wrote:

>Hello Jeff,
>
>Took a bit longer as expected, but we had a long weekend so I hardly saw the 
>pc.
>
>Started wih a clean copy of the code, then replaced the alsa.c by the one you 
>send and spliced in the makefile.fix in makefile.in. Used "./configure 
>--enable-alsa" like the previous time.
>
>Issueing "make" still gives the old problem of "x86-64" not being recognised. 
>But once I change that to "k8" in the Makefile it compiles cleanly.
>
>The change is enormous! Playback doesn't stop anymore, it plays the whole 
>selection. There are still errors, but they do not always give an audible 
>"disturbance". Sometimes you get a slight click but nothing more than you 
>would expect from an LP recording (and much less than on some LPs). I have 
>not yet tried to check if the click comes with the underrun or the other 
>message.
>
>I played a 20 second selection, and below is the output to the terminal.
>
>Thanks,
>Johan
>
>[Terminal output]
>daw gwc-0.21-03 # gwc
>Current stack limit: 8388608 bytes
>ALSA audio_device_best_buffer_size:512 (frames:128)
>##########################################################
>audio_device_processed_bytes: ALSA buffer underrun
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_processed_bytes: ALSA buffer underrun
>Broken pipe
>##########################################################
>audio_device_processed_bytes: ALSA buffer underrun
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_processed_bytes: ALSA buffer underrun
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>##########################################################
>audio_device_processed_bytes: ALSA buffer underrun
>Broken pipe
>
>Stop playback with playback_samples_remaining:0
>##########################################################
>audio_device_processed_bytes: ALSA buffer underrun
>Broken pipe
>Closing the ALSA audio device
>[end terminal output]
>
>On Saturday 12 November 2005 15:49, you wrote:
>  
>
>>Hi James,
>>
>>Good to hear from you!
>>
>>I've been reading a little on ALSA this pase week, and it looks like not 
>>handling
>>the EPIPE error is behind some of GWC's troubles.  I was showing the 
>>"broken pipe"
>>errors consistently at the end of a playback section -- because the playback
>>cursor lags a few milliseconds behind the audio playback, and the call to
>>snd_pcm_delay in function audio_device_processed_bytes would give the
>>EPIPE when the audio_buffer had already emptied.  This does not affect 
>>playback
>>sound quality, but I have trapped that error.
>>
>>I took your thought here about the EPIPE in the 
>>nonblocking_write_buffersize call
>>and added one tweak -- attempt recover the sound device handle before 
>>failing.
>>
>>Attached is my current audio_alsa.c (which changed the function perr to 
>>snd_perr,
>>and recover_write to recover_snd_handle.)  See how this works.  Johan, 
>>let us know.
>>I think there is still problems with the audio buffer size, and when 
>>playback starts
>>there will be a message on the console, if you could tell us what it says:
>>
>>    "ALSA audio_device_best_buffer_size:xxxx (frames:xxxx)"
>>
>>---
>>For the Makefile problem, if you will insert the lines from Makefile.fix 
>>indicated below,
>>it will pick up changes to the audio src.  You can put these lines into 
>>Makefile.in as well
>>and then "configure" will build the right Makefile.  I'd just send my 
>>Makefile but I don't
>>know what other options you may or may not have.  Be sure for the 
>>indents that it is a single
>>tab, or make won't work properly.
>>
>>############### Changes for Makefile ####################################
>>
>>gwc : $(OBJS) meschach.a
>>        $(CC) $(OBJS) $(EFENCE) $(LFLAGS) $(LIBS) -o gwc
>>==>
>>==>  audio_device.o : audio_device.c audio_alsa.c audio_oss.c audio_osx.c
>>==>        $(COMPILE) -c audio_device.c
>>
>>.c.o :
>>        $(COMPILE) -c $<
>>
>>#####################################################################
>>
>>Cheers,
>>Jeff
>>
>>James Tappin wrote:
>>
>>    
>>
>>>On Wednesday 02 November 2005 21:51, Johan De Groote wrote:
>>>JD> I can open it fine, load a file, make a selection etc. But if I hit
>>>playback I JD> get:
>>>JD>
>>>JD> ...
>>>JD> ##########################################################
>>>JD> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>>>JD> Broken pipe
>>>JD> audio_device_processed_bytes: snd_pcm_delay Broken pipe
>>>JD> ##########################################################
>>>JD> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>>>JD> Broken pipe
>>>JD> audio_device_processed_bytes: snd_pcm_delay Broken pipe
>>>JD> ...
>>>JD>
>>>JD> Once this message starts sound stops and so does the cursor. Until I 
>>>      
>>>
>stop
>  
>
>>>JD> playback this message keeps coming in the terminal. The time to get 
>>>      
>>>
>this
>  
>
>>>is JD> variable, but never longer than a few seconds (15 at most). Gwc
>>>doesn't JD> crash, and alsa continues as well. Hitting playback again will
>>>restart the JD> selection, until "it" happens again.
>>>JD>
>>>
>>>Hi, I'm back!
>>>
>>>I think I'm making some progress on this one (which seems to be a similar 
>>>problem to one I was having a while back (April 04) [only then it wasn't 
>>>possible to stop it].  snd_pcm_avail_update() returns -EPIPE if the output 
>>>buffer has emptied, and the driver has tried to get some data. Because  
>>>audio_device_nonblocking_write_buffer_size() bails out on any error, the 
>>>buffer never gets filled so it goes into an infinite loop. I think that the 
>>>answer is at least in part to modify audio_alsa.c, so that a "broken pipe 
>>>error is effectively ignored (patch at the end) -- it could be rearranged 
>>>      
>>>
>to 
>  
>
>>>eliminate the message altogether but I was trying to see what influenced 
>>>      
>>>
>the 
>  
>
>>>problem.
>>>
>>>The other things that may help are to increase the buffer size (in 
>>>audio_device.h) [BTW there is a redundant redefinition of MAXBUFSIZE in 
>>>audio_util.c which ought to be removed.] and not popping windows or 
>>>      
>>>
>generally 
>  
>
>>>doing too much with X while playing back.
>>>
>>>James
>>>
>>>P.S. I've changed distro yet again -- Kubuntu now.
>>>
>>>++ BEGIN PATCH ++
>>>*** audio_alsa.c	2005-11-11 16:28:08.000000000 +0000
>>>--- audio_alsa.c~	2005-11-11 15:57:50.000000000 +0000
>>>***************
>>>*** 267,273 ****
>>>     if (frames < 0) {
>>>         perr("audio_device_nonblocking_write_buffer_size: 
>>>snd_pcm_avail_update",
>>>              frames);
>>>!        if (frames != -EPIPE ) return 0;
>>>     }
>>>     len = snd_pcm_frames_to_bytes(handle, frames);
>>> 
>>>--- 267,273 ----
>>>     if (frames < 0) {
>>>         perr("audio_device_nonblocking_write_buffer_size: 
>>>snd_pcm_avail_update",
>>>              frames);
>>>!          return 0; 
>>>     }
>>>     len = snd_pcm_frames_to_bytes(handle, frames);
>>>++END PATCH++
>>>
>>>
>>>As far as I can tell 
>>> 
>>>
>>>      
>>>
>>    
>>
>
>  
>

Re: Alsa problems (Was: Re: [Gwc-general] GWC 0.21-03 is released)

[Jeff W. <we...@ya...>]

Hi James,

Good to hear from you!

I've been reading a little on ALSA this pase week, and it looks like not 
handling
the EPIPE error is behind some of GWC's troubles.  I was showing the 
"broken pipe"
errors consistently at the end of a playback section -- because the playback
cursor lags a few milliseconds behind the audio playback, and the call to
snd_pcm_delay in function audio_device_processed_bytes would give the
EPIPE when the audio_buffer had already emptied.  This does not affect 
playback
sound quality, but I have trapped that error.

I took your thought here about the EPIPE in the 
nonblocking_write_buffersize call
and added one tweak -- attempt recover the sound device handle before 
failing.

Attached is my current audio_alsa.c (which changed the function perr to 
snd_perr,
and recover_write to recover_snd_handle.)  See how this works.  Johan, 
let us know.
I think there is still problems with the audio buffer size, and when 
playback starts
there will be a message on the console, if you could tell us what it says:

    "ALSA audio_device_best_buffer_size:xxxx (frames:xxxx)"

---
For the Makefile problem, if you will insert the lines from Makefile.fix 
indicated below,
it will pick up changes to the audio src.  You can put these lines into 
Makefile.in as well
and then "configure" will build the right Makefile.  I'd just send my 
Makefile but I don't
know what other options you may or may not have.  Be sure for the 
indents that it is a single
tab, or make won't work properly.

############### Changes for Makefile ####################################

gwc : $(OBJS) meschach.a
        $(CC) $(OBJS) $(EFENCE) $(LFLAGS) $(LIBS) -o gwc
==>
==>  audio_device.o : audio_device.c audio_alsa.c audio_oss.c audio_osx.c
==>        $(COMPILE) -c audio_device.c

.c.o :
        $(COMPILE) -c $<

#####################################################################

Cheers,
Jeff

James Tappin wrote:

>On Wednesday 02 November 2005 21:51, Johan De Groote wrote:
>JD> I can open it fine, load a file, make a selection etc. But if I hit
> playback I JD> get:
>JD>
>JD> ...
>JD> ##########################################################
>JD> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>JD> Broken pipe
>JD> audio_device_processed_bytes: snd_pcm_delay Broken pipe
>JD> ##########################################################
>JD> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>JD> Broken pipe
>JD> audio_device_processed_bytes: snd_pcm_delay Broken pipe
>JD> ...
>JD>
>JD> Once this message starts sound stops and so does the cursor. Until I stop
>JD> playback this message keeps coming in the terminal. The time to get this
> is JD> variable, but never longer than a few seconds (15 at most). Gwc
> doesn't JD> crash, and alsa continues as well. Hitting playback again will
> restart the JD> selection, until "it" happens again.
>JD>
>
>Hi, I'm back!
>
>I think I'm making some progress on this one (which seems to be a similar 
>problem to one I was having a while back (April 04) [only then it wasn't 
>possible to stop it].  snd_pcm_avail_update() returns -EPIPE if the output 
>buffer has emptied, and the driver has tried to get some data. Because  
>audio_device_nonblocking_write_buffer_size() bails out on any error, the 
>buffer never gets filled so it goes into an infinite loop. I think that the 
>answer is at least in part to modify audio_alsa.c, so that a "broken pipe 
>error is effectively ignored (patch at the end) -- it could be rearranged to 
>eliminate the message altogether but I was trying to see what influenced the 
>problem.
>
>The other things that may help are to increase the buffer size (in 
>audio_device.h) [BTW there is a redundant redefinition of MAXBUFSIZE in 
>audio_util.c which ought to be removed.] and not popping windows or generally 
>doing too much with X while playing back.
>
>James
>
>P.S. I've changed distro yet again -- Kubuntu now.
>
>++ BEGIN PATCH ++
>*** audio_alsa.c	2005-11-11 16:28:08.000000000 +0000
>--- audio_alsa.c~	2005-11-11 15:57:50.000000000 +0000
>***************
>*** 267,273 ****
>      if (frames < 0) {
>          perr("audio_device_nonblocking_write_buffer_size: 
>snd_pcm_avail_update",
>               frames);
>!        if (frames != -EPIPE ) return 0;
>      }
>      len = snd_pcm_frames_to_bytes(handle, frames);
>  
>--- 267,273 ----
>      if (frames < 0) {
>          perr("audio_device_nonblocking_write_buffer_size: 
>snd_pcm_avail_update",
>               frames);
>!          return 0; 
>      }
>      len = snd_pcm_frames_to_bytes(handle, frames);
> ++END PATCH++
>
>
>As far as I can tell 
>  
>

Re: Alsa problems (Was: Re: [Gwc-general] GWC 0.21-03 is released)

[James T. <ja...@ta...>]

Just one other comment: it appears that the makefile fails to have included 
files as dependencies, so changing audio_device.h or audio_alsa.c doesn't 
cause a rebuild on a simple "make". I'm not familiar enough with autotools to 
know if there's an easy fix for this.

James

-- 
James Tappin,             O__      "I forget the punishment for using
ja...@ta...       --  \/`    Microsoft --- Something lingering
http://www.tappin.me.uk/            with data loss in it I fancy"  

Alsa problems (Was: Re: [Gwc-general] GWC 0.21-03 is released)

[James T. <ja...@ta...>]

On Wednesday 02 November 2005 21:51, Johan De Groote wrote:
JD> I can open it fine, load a file, make a selection etc. But if I hit
 playback I JD> get:
JD>
JD> ...
JD> ##########################################################
JD> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
JD> Broken pipe
JD> audio_device_processed_bytes: snd_pcm_delay Broken pipe
JD> ##########################################################
JD> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
JD> Broken pipe
JD> audio_device_processed_bytes: snd_pcm_delay Broken pipe
JD> ...
JD>
JD> Once this message starts sound stops and so does the cursor. Until I stop
JD> playback this message keeps coming in the terminal. The time to get this
 is JD> variable, but never longer than a few seconds (15 at most). Gwc
 doesn't JD> crash, and alsa continues as well. Hitting playback again will
 restart the JD> selection, until "it" happens again.
JD>

Hi, I'm back!

I think I'm making some progress on this one (which seems to be a similar 
problem to one I was having a while back (April 04) [only then it wasn't 
possible to stop it].  snd_pcm_avail_update() returns -EPIPE if the output 
buffer has emptied, and the driver has tried to get some data. Because  
audio_device_nonblocking_write_buffer_size() bails out on any error, the 
buffer never gets filled so it goes into an infinite loop. I think that the 
answer is at least in part to modify audio_alsa.c, so that a "broken pipe 
error is effectively ignored (patch at the end) -- it could be rearranged to 
eliminate the message altogether but I was trying to see what influenced the 
problem.

The other things that may help are to increase the buffer size (in 
audio_device.h) [BTW there is a redundant redefinition of MAXBUFSIZE in 
audio_util.c which ought to be removed.] and not popping windows or generally 
doing too much with X while playing back.

James

P.S. I've changed distro yet again -- Kubuntu now.

++ BEGIN PATCH ++
*** audio_alsa.c	2005-11-11 16:28:08.000000000 +0000
--- audio_alsa.c~	2005-11-11 15:57:50.000000000 +0000
***************
*** 267,273 ****
      if (frames < 0) {
          perr("audio_device_nonblocking_write_buffer_size: 
snd_pcm_avail_update",
               frames);
!        if (frames != -EPIPE ) return 0;
      }
      len = snd_pcm_frames_to_bytes(handle, frames);
  
--- 267,273 ----
      if (frames < 0) {
          perr("audio_device_nonblocking_write_buffer_size: 
snd_pcm_avail_update",
               frames);
!          return 0; 
      }
      len = snd_pcm_frames_to_bytes(handle, frames);
 ++END PATCH++


As far as I can tell 
-- 
James Tappin,             O__      "I forget the punishment for using
ja...@ta...       --  \/`    Microsoft --- Something lingering
http://www.tappin.me.uk/            with data loss in it I fancy"  

Re: [Gwc-general] GWC 0.21-03 is released

[Jeff W. <we...@ya...>]

OK.  I'll put understanding ALSA at the top of my reading list :-)

Anyone else have any clues?

In the meantime Johan, you might try configuring gwc, but without
the --enable-alsa flag.  That will cause GWC to use the old OSS interface,
which ALSA emulates.  That may work just fine I ran it that way on
my Fedora Core 1 box for a long time, but there can be reasons
why it might work for me and not for you (primarily the soundcard driver),
you'd just have to try it.

Good luck.  Keep us informed so we can help you.  I believe understanding
what is happening to you and fixing it will make GWC better for everyone!

Thanks,
Jeff


Johan De Groote wrote:

>Hello,
>
>No, when the messages come, playback stops. There is no sound anymore. The 
>cursor also freezes. If you stop the playback and then restart it, it works 
>again (sound and cursor movement) until the messages come. It lasts at most 
>about 20 seconds.
>
>Best regards,
>Johan
>
>On Sunday 06 November 2005 14:07, you wrote:
>  
>
>>Does playback still sound good?   If so I wouldn't worry about
>>the warnings coming to the terminal, those are generated by GWC
>>itself, not ALSA or the kernel.
>>
>>I'd still like to understand more about ALSA, but I'm afraid it
>>will be a while before I get enough time to look into it thoroughly.
>>
>>If, however, playback doesn't sound good, then I'll make time to
>>look at this more closely.
>>
>>Cheers,
>>Jeff
>>
>>Johan De Groote wrote:
>>
>>    
>>
>>>Hello,
>>>
>>>Those changes to the alsa code made me hope, but I don't notice anything of 
>>>      
>>>
>a 
>  
>
>>>change. Used the last source from sourceforge 0.21-03.
>>>
>>>- running under Gentoo 2.6.12 alsa 1.0.9
>>>- ./configure --enable-alsa
>>>- changed the "-mcpu=x86_64 -march=x86_64" to "-mcpu=k8 -march=k8" in order 
>>>      
>>>
>to 
>  
>
>>>compile on a 64bit Opteron system
>>>- "make" and "make install"
>>>
>>>I can open it fine, load a file, make a selection etc. But if I hit 
>>>      
>>>
>playback I 
>  
>
>>>get:
>>>
>>>...
>>>##########################################################
>>>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>>>Broken pipe
>>>audio_device_processed_bytes: snd_pcm_delay Broken pipe
>>>##########################################################
>>>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>>>Broken pipe
>>>audio_device_processed_bytes: snd_pcm_delay Broken pipe
>>>...
>>>
>>>Once this message starts sound stops and so does the cursor. Until I stop 
>>>playback this message keeps coming in the terminal. The time to get this is 
>>>variable, but never longer than a few seconds (15 at most). Gwc doesn't 
>>>crash, and alsa continues as well. Hitting playback again will restart the 
>>>selection, until "it" happens again.
>>>
>>>Anything that I can do to get this running, but I don't know the first 
>>>      
>>>
>thing 
>  
>
>>>about programming let alone debugging. If you need more specific info, 
>>>      
>>>
>files, 
>  
>
>>>have me run some tests,etc just ask. But I don't know anything about it, so 
>>>      
>>>
>I 
>  
>
>>>won't find it myself if no-one educates me on it.
>>>
>>>Since this is the only application for audio restoration...
>>>
>>>regards,
>>>Johan De Groote
>>>
>>>On Sunday 09 October 2005 23:10, Jeff Welty wrote:
>>> 
>>>
>>>      
>>>
>>>>0.21-03 is up on sourceforge today. A few bugfixes. ALSA playback was 
>>>>improved
>>>>(and hopefully OSS playback wasn't degraded). Thanks John Cirillo for 
>>>>noticing the
>>>>playback problem.
>>>>
>>>>There is code for OSX, but as yet no formal mechanism for 
>>>>compiling/linking on OSX. 
>>>>
>>>>Enjoy. 
>>>>Jeff
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email is sponsored by:
>>>>Power Architecture Resource Center: Free content, downloads, discussions,
>>>>and more. http://solutions.newsforge.com/ibmarch.tmpl
>>>>_______________________________________________
>>>>Gwc-general mailing list
>>>>Gwc...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/gwc-general
>>>>
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>-------------------------------------------------------
>>>SF.Net email is sponsored by:
>>>Tame your development challenges with Apache's Geronimo App Server. 
>>>      
>>>
>Download
>  
>
>>>it for free - -and be entered to win a 42" plasma tv or your very own
>>>Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
>>>_______________________________________________
>>>Gwc-general mailing list
>>>Gwc...@li...
>>>https://lists.sourceforge.net/lists/listinfo/gwc-general
>>>
>>>
>>>
>>>
>>> 
>>>
>>>      
>>>
>>
>>    
>>
>
>  
>

Re: [Gwc-general] GWC 0.21-03 is released

[Jeff W. <we...@ya...>]

Does playback still sound good?   If so I wouldn't worry about
the warnings coming to the terminal, those are generated by GWC
itself, not ALSA or the kernel.

I'd still like to understand more about ALSA, but I'm afraid it
will be a while before I get enough time to look into it thoroughly.

If, however, playback doesn't sound good, then I'll make time to
look at this more closely.

Cheers,
Jeff

Johan De Groote wrote:

>Hello,
>
>Those changes to the alsa code made me hope, but I don't notice anything of a 
>change. Used the last source from sourceforge 0.21-03.
>
>- running under Gentoo 2.6.12 alsa 1.0.9
>- ./configure --enable-alsa
>- changed the "-mcpu=x86_64 -march=x86_64" to "-mcpu=k8 -march=k8" in order to 
>compile on a 64bit Opteron system
>- "make" and "make install"
>
>I can open it fine, load a file, make a selection etc. But if I hit playback I 
>get:
>
>...
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>audio_device_processed_bytes: snd_pcm_delay Broken pipe
>##########################################################
>audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
>Broken pipe
>audio_device_processed_bytes: snd_pcm_delay Broken pipe
>...
>
>Once this message starts sound stops and so does the cursor. Until I stop 
>playback this message keeps coming in the terminal. The time to get this is 
>variable, but never longer than a few seconds (15 at most). Gwc doesn't 
>crash, and alsa continues as well. Hitting playback again will restart the 
>selection, until "it" happens again.
>
>Anything that I can do to get this running, but I don't know the first thing 
>about programming let alone debugging. If you need more specific info, files, 
>have me run some tests,etc just ask. But I don't know anything about it, so I 
>won't find it myself if no-one educates me on it.
>
>Since this is the only application for audio restoration...
>
>regards,
>Johan De Groote
>
>On Sunday 09 October 2005 23:10, Jeff Welty wrote:
>  
>
>>0.21-03 is up on sourceforge today. A few bugfixes. ALSA playback was 
>>improved
>>(and hopefully OSS playback wasn't degraded). Thanks John Cirillo for 
>>noticing the
>>playback problem.
>> 
>>There is code for OSX, but as yet no formal mechanism for 
>>compiling/linking on OSX. 
>> 
>>Enjoy. 
>>Jeff
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by:
>>Power Architecture Resource Center: Free content, downloads, discussions,
>>and more. http://solutions.newsforge.com/ibmarch.tmpl
>>_______________________________________________
>>Gwc-general mailing list
>>Gwc...@li...
>>https://lists.sourceforge.net/lists/listinfo/gwc-general
>>
>>
>>    
>>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by:
>Tame your development challenges with Apache's Geronimo App Server. Download
>it for free - -and be entered to win a 42" plasma tv or your very own
>Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:43692934155842084318266!
>  
>

Re: [Gwc-general] GWC 0.21-03 is released

[Johan De G. <joh...@sk...>]

Hello,

Those changes to the alsa code made me hope, but I don't notice anything of a 
change. Used the last source from sourceforge 0.21-03.

- running under Gentoo 2.6.12 alsa 1.0.9
- ./configure --enable-alsa
- changed the "-mcpu=x86_64 -march=x86_64" to "-mcpu=k8 -march=k8" in order to 
compile on a 64bit Opteron system
- "make" and "make install"

I can open it fine, load a file, make a selection etc. But if I hit playback I 
get:

...
##########################################################
audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
Broken pipe
audio_device_processed_bytes: snd_pcm_delay Broken pipe
##########################################################
audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
Broken pipe
audio_device_processed_bytes: snd_pcm_delay Broken pipe
...

Once this message starts sound stops and so does the cursor. Until I stop 
playback this message keeps coming in the terminal. The time to get this is 
variable, but never longer than a few seconds (15 at most). Gwc doesn't 
crash, and alsa continues as well. Hitting playback again will restart the 
selection, until "it" happens again.

Anything that I can do to get this running, but I don't know the first thing 
about programming let alone debugging. If you need more specific info, files, 
have me run some tests,etc just ask. But I don't know anything about it, so I 
won't find it myself if no-one educates me on it.

Since this is the only application for audio restoration...

regards,
Johan De Groote

On Sunday 09 October 2005 23:10, Jeff Welty wrote:
> 0.21-03 is up on sourceforge today. A few bugfixes. ALSA playback was 
> improved
> (and hopefully OSS playback wasn't degraded). Thanks John Cirillo for 
> noticing the
> playback problem.
>  
> There is code for OSX, but as yet no formal mechanism for 
> compiling/linking on OSX. 
>  
> Enjoy. 
> Jeff
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general
> 
> 

[Fwd: Re: [Gwc-general] Cursor stops too soon on 0.20.10]

[John C. <ci...@pu...>]

Jeff,

I just installed GWC 0.21.03 beta.  It looks like the cursor
stalling has been resolved to a great degree.
With 20 seconds or more of audio on the screen, the cursor
appears to make it all the way most of the time.  I notice
as I zoom in more and more the end point gradually creeps
away from the end, but still not bad.  I think one thing
that made it less bothersome in the .19 series was that the
cursor was erased after the last sample was "played". This
didn't bother me and I wouldn't mind if the cursor was again
designed to disappear after the sound card claims that all
of the bytes have been processed (as long as it comes
reasonably close to the end as it does now.)
But it's definitely much better than 0.20.10.  It's very
close to 0.19.7 which was the last 0.19 series that I had
been using.

I wondered if this situation is soundcard-related. I tried
installing gwc on my backup server which has a cheap onboard
VIA sound chip.  Using GWC 0.20.10, the degree of cursor
stopping seems about the same as my es1371 so I don't
understand this. Speaking purely from ignorance I wonder if
it is somehow the driver reporting the early finish?
I am using the stock ess soundsystem on both machines by the
way.

Anyway, it's pretty good now. I can use this. And with the
channel-selection issue probably fixed, it should be much
more pleasant to work with.
Thanks for the quick service!

John


Jeff Welty wrote:
> Ahh, the cursor -- my nemisis.  This has been the constant thorn in 
> GWC's (and my) foot for a long time.
> 
> GWC handles playback with 2 timers -- one for feeding audio to the audio 
> device, and one for redrawing
> the cursor.  The audio playing timer just delivers bytes to the audio 
> device at regular intervals to make
> sure the audio buffers never empty.  But the cursor timer must know how 
> many bytes have actually been
> played in order to get the cursor positioned in the window.  So it 
> queries the audio device to determine
> how many audio bytes have been processed.  I think what is happening is 
> the audio device is saying all
> the bytes have been processed, but what it really means is all the bytes 
> are in my buffer, not necessarily
> processed (played).
> 
> I am more aware of this than before, because I recently (last week) 
> upgraded to Fedora Core 3, and have
> the native alsa audio, and the cursor is stopping for me to soon, or not 
> even showing up at all if the sound
> segment is too short (under 1 second).
> 
> In the short term, I'm going to investigate this a little more, 
> hopefully get to the bottom of it and fix it. In the longer term, I'm 
> going to think about using Jack for the audio playback.
> 
> Thanks again for your feedback.
> jw
> 
> 
> John Cirillo wrote:
> 
>> As a result of a recent system upgrade on Debian I now have GWC 
>> 0.20.10 instead of 0.20.3 (I think)
>> One thing that happens with some severity now is that the cursor stops 
>> about 2/3 of the way across the wave during play.  It just doesn't 
>> make it to the end of the waveform.
>> The side-effect is that I'm not convinced that the cursor is really 
>> keeping up with the played sound at any time.
>> Has anyone else noticed this?  Has the redraw of the cursor been 
>> changed between these two versions?
>> I am at a loss as to what to do now.   I like some of the other 
>> features in this release, so I plan to keep using as long as I can 
>> stand it.   I hope it's not a hardware demand issue. I'm using a 3DFX 
>> Voodoo 3 which isn't so fast by today's standards.
>>
>> John
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads, discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> Gwc-general mailing list
>> Gwc...@li...
>> https://lists.sourceforge.net/lists/listinfo/gwc-general
>>
>>
>>
>> !DSPAM:4348c03684927296568094!
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general
> 

[Fwd: Re: [Gwc-general] Amplify function erratic]

[John C. <ci...@pu...>]

Jeff,

I think most people are wanting to process both channels by
default.
Doing something on a single channel is a special situation
for me, and the rest of the time I am working with both
channels. So my vote is to have it do both channels unless a
single channel is selected. Should it also reset to both
when the viewing range changes? Don't know but probably.

But- then the question comes of how to select a single
channel and how to show it.
I don't want you to have to over-complicate things.
In Cool Edit Pro, you ccouldn't select a single channel
unless you moved the cursor to the upper (or lower) 1/2 of a
channel waveform, I guess the idea is you  really had to
mean you wanted a single channel.  If you clicked anywhere
closer to the center bar, both channels were selected again.
This is not the greatest solution but I don't know of
another way. Since you already did something like that in
the 0.21.03 beta, I'd say leave it and see what comments you
get.

John


Jeff Welty wrote:
> John,
> 
> Thanks for tracking this down.  That all does make sense, and I had 
> spent a little time trying to see if I could
> reproduce the bug, but to no avail.
> 
> GWC is working the way I intended it to, but it is clearly a bug in the 
> documentation and/or a bug in the
> user feedback mechanism that lets you know which channel is currently 
> selected.  GWC has memory of
> the last channel you selected, even if you unselected it with a single 
> click in one of the channel windows.
> 
> I think the proper way to handle this, is that if a channel is not 
> specifically highlighted, then you get both
> channels for any action.
> 
> I solicit your (and other's) feedback from the list on this.
> 
> jw
> 
> John Cirillo wrote:
> 
>> Jeff,
>>
>> After considerable study of this  problem of GWC only processing one 
>> channel, I've come to the conclusion that it's a matter of the focus.  
>> I had always assumed that the action would take place on the "current 
>> view" as that's how the buttons describe it, IE "Amplifies the current 
>> view or selection." But in my case, the program doesn't process both 
>> channels in the current view at times. The test I've found is to click 
>> on the button to "select current view". When I do that, maybe one 
>> channel highlights, or maybe both channels highlight.  This condition 
>> can be forced by clicking the mouse deliberately somewhere in the left 
>> channel window (or the right channel) and clicking "select current 
>> view." Then it can be seen that only one channel gets highlighted.  I 
>> don't think that I had intentionally clicked in a particular channel's 
>> window prior to doing a function, but  in any case the cure is to 
>> click somewhere in the black bar separating the channels prior to 
>> selecting a function.  Then it always does both channels.
>>
>> I honestly do not remember this being a problem last year when I was 
>> still using my Red Hat 7.3 system. The problem seems to have coincided 
>> with installing Debian (sarge). It's still a 2.4 kernel so that's not 
>> the reason. Perhaps some change in KDE or something?  I have done  
>> test installs of every version I have, back to 0.19.5 and they all 
>> have the same behavior on Sarge, yet I am fairly certain that 0.19.7 
>> didn't do this on RH7.3 (I used 0.19.7 for a LONG time on that system).
>>
>> Anyway, now that I know how to check and correct this, it's not a 
>> problem unless I forget.
>> I know that if I use the "select current view" button, I can always 
>> know if it will grab both channels. I don't necessarily want to have 
>> to do that, so I've been cheating by clicking the black separator bar.
>>
>> The conclusion is, I don't think it's a bug in GWC, just an unexpected 
>> behavior.
>> It's too bad that the focus can't be known just by looking (or can it?)
>>
>> John
>>
>> Jeff Welty wrote:
>>
>>> Hi John,
>>>
>>> What you've described sounds like a bug in GWC.  You obviously
>>> know the amplification would only be applied to the selected channel,
>>>
>>> I'll look into this, but it will take a week or so.  In the meantime, if
>>> you have time, try to see if you can determine a sequence of actions
>>> that will alway cause it to fail to work properly.
>>>
>>> Thanks for the bug report!
>>> jw
>>>
>>> John Cirillo wrote:
>>>
>>>> I frequently need to use the Amplify function to bring up
>>>> the level of one or both channels.
>>>> Some of the time, only one channel will amplify (usually the
>>>> left channel) even though I specified both.
>>>> Or even if I specified only right channel amplification, it
>>>> goes through the motions, says it's done, yet no
>>>> amplification was performed.
>>>> I thought at  first maybe I was trying to specify an
>>>> out-of-bounds amount, but that's not it.
>>>> It could say that the max available is 2.8, and I want to go
>>>> from 1.0 to 1.2 or something like that.
>>>> Either one or both channels fail to amplify. Yet, if I try
>>>> to perform the operation 2 or 3 times, it finally amplifies.
>>>> If I deliberately highlight the entire right channel
>>>> waveform and specify amplification on that channel, the odds
>>>> are better but still not always.
>>>> I can't remember when I first started noticing this or
>>>> whether it was always there to some degree.
>>>> At this moment I have GWC 0.19-7 and 0.20-07 both installed.
>>>>  I like the features of 0.20 but sometimes use 0.19-7 if
>>>> 0.20 seems squirrely.  Both of them have this erratic
>>>> amplification behavior.
>>>> I did have the newer 0.20-10 but it was a little too
>>>> unstable on this system.  I currently am running Debian
>>>> Sarge, kernel 2.4.27-2-386 with an AMD Duron if that helps.
>>>> KDE 3.3 environment.
>>>> Is this a GWC issue, or could it be something wrong
>>>> elsewhere?  It's starting to drive me batty as I'm using GWC
>>>> more and more.
>>>>
>>>> Any suggestions appreciated.
>>>>
>>>> John Cirillo
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> 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
>>>> _______________________________________________
>>>> Gwc-general mailing list
>>>> Gwc...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/gwc-general
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads, discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> Gwc-general mailing list
>> Gwc...@li...
>> https://lists.sourceforge.net/lists/listinfo/gwc-general
>>
>>
>>
>> !DSPAM:4348b23783901690014693!
> 
> 
> 
> 

[Gwc-general] GWC 0.21-03 is released

[Jeff W. <we...@ya...>]

0.21-03 is up on sourceforge today. A few bugfixes. ALSA playback was 
improved
(and hopefully OSS playback wasn't degraded). Thanks John Cirillo for 
noticing the
playback problem.
 
There is code for OSX, but as yet no formal mechanism for 
compiling/linking on OSX. 
 
Enjoy. 
Jeff