gwc-general — Gnome Wave Cleaner discussion list

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

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

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!

Re: [Gwc-general] Amplify function erratic

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

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] Cursor stops too soon on 0.20.10

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

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

Re: [Gwc-general] Amplify function erratic

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

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
>>
>>
>>
>> !DSPAM:42f93f1f86851085383841!
> 
> 
> 
> 

Re: [Gwc-general] Amplify function erratic

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

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
>
>
>
> !DSPAM:42f93f1f86851085383841!

[Gwc-general] Amplify function erratic

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

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

[Gwc-general] Compiling GWC with arm-linux-gcc

[prakhar v. <aqu...@ya...>]

Hi All,

I tried following steps to compile gwc with
arm-linux-gcc and got the problem in step2:

step 1: successfully configured and able to make
libsndfile-1.0.11 with arm-linux-gcc

Step2:got error while doing make for 
fftw-3.0.1 . Following error I received:

planner.c:598: internal compiler error: in
extract_insn, at recog.c:2061Please submit a full bug
report,
with preprocessed source if appropriate.
Send email to ar...@co... for
instructions.
make[2]: *** [planner.lo] Error 1
make[2]: Leaving directory
`/home/prakhar/fftw-3.0.1/kernel'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/prakhar/fftw-3.0.1'
make: *** [all] Error 2

Please check it out, if anyone can help me out.I am in
urgent need of it for arm-linux-gcc.

Thanks And Regards
Prakhar



	

	
		
__________________________________________________________
Free antispam, antivirus and 1GB to save all your messages
Only in Yahoo! Mail: http://in.mail.yahoo.com

[Gwc-general] Re: problem getting gwc to use alsa

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

A bit further. It works a bit better if you use "plughw:0,0" for the "Audio 
device" setting. Mostly it plays back for a few seconds (up to about 20 
seconds) before going into the loop (like below). And it recovers if you stop 
the playback. There is no regularity in it, sometimes it plays seconds, next 
time it directly loops.

This is -barely- usable, so I guess I'll continue like this for the moment.

Regards,
Johan

On Thursday 04 August 2005 19:17, Johan De Groote wrote:
> Setting "Settings>Miscellaneous>Audio device" to "plughw:0" indeed makes a 
> difference. Sometimes I even get a very short snippet of sound. But then it 
> just goes into a loop with:
> 
> "aw2 ~ # gwc
> Current stack limit: 8388608 bytes
> leaving start with audio_playback=1
> ##########################################################
> audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
> Broken pipe
> ##########################################################
> audio_device_processed_bytes: snd_pcm_delay
> Broken pipe"
> (in this case it went directly into a loop)
> 
> This card is a bit different from the rest since it doesn't use the mixer, 
> everything goes directly to the card. So maybe I have to set the output 
> channels also in that box. Does anyone knows how to do that?
> 
> So it really looks as alsa is not usable. This is a pity since from 2.6.x 
this 
> is the preferred way of working. Even better would be a jack interface since 
> then even all routing would be taken care of.
> 
> Bigger problem is that OSS emulation on the Hammerfall is not usable for one 
> reason or another. So I will have to add another soundcard (or worse, get 
the 
> onboard sound working).
> 
> Regards,
> Johan
> 
> On Thursday 04 August 2005 15:37, Ken Dere wrote:
> > On Wednesday 03 August 2005 23:05, 
gwc...@li... 
> > wrote:
> > 
> > >
> > > Message: 2
> > > Date: Wed, 03 Aug 2005 06:19:28 -0700
> > > From: Jeff Welty <we...@ya...>
> > > To: joh...@sk...
> > > CC: gwc...@li...
> > > Subject: Re: [Gwc-general] problem getting gwc to use alsa
> > >
> > > I still don't have an ALSA setup. so I can't test this.  But the
> > > settings->miscellaneous->audio device
> > > was created for ALSA users.
> > >
> > > Anyone with alsa care to offer some advice?
> > >
> > > jw
> > >
> > > Johan De Groote wrote:
> > > >Hello, here again...
> > > >
> > > >So I got gwc running under 64bit, but I cannot use alsa.
> > > >
> > > >I have alsa compiled into the 2.6.11 kernel. Using the rme hammerfall
> > > > card. I do have the following installed:
> > > >alsa-lib 1.0.8
> > > >alsa-headers 1.0.8
> > > >alsa-utils 1.0.8
> > > >Other applications using alsa work fine.
> > > >
> > > >I used "./configure --enable-alsa" and recompiled gwc (had forgotten 
this
> > > >option the first time). When I want to play back a file, I get the
> > > > following window: "failed to open output device /dev/dsp0"
> > > >
> > > >if I click "OK", gwc crashes and I have the following in the terminal:
> > > >
> > > >"daw2 ~ # gwc
> > > >Current stack limit: 8388608 bytes
> > > >ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp0
> > > >##########################################################
> > > >audio_device_open: snd_pcm_open
> > > >No such file or directory
> > > >gwc: pcm.c:920: snd_pcm_delay: Assertion `pcm' failed."
> > > >
> > > >So it looks like even if you compile to use alsa that it still looks to
> > > > use the OSS output driver. Or do I have to give an option on the 
command
> > > > line when starting gwc? I don't remember having to do that before and 
> the
> > > > --help doesn't list anything for output selection. Or do I have to use
> > > > some other output device in the "Settings>Miscellaneous"? But then 
what,
> > > > because "hw:0" also doesn't work?
> > > >
> > > >regards,
> > > >Johan
> > > >
> > > >
> > > >
> > > >-------------------------------------------------------
> > > >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > >from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > >informative Webcasts and more! Get everything you need to get up to
> > > >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > >_______________________________________________
> > > >Gwc-general mailing list
> > > >Gwc...@li...
> > > >https://lists.sourceforge.net/lists/listinfo/gwc-general
> > > >
> > > >
> > > >
> > > >!DSPAM:42f0bdc9134501476118180!
> > >
> > > --__--__--
> > >
> > > _______________________________________________
> > > Gwc-general mailing list
> > > Gwc...@li...
> > > https://lists.sourceforge.net/lists/listinfo/gwc-general
> > >
> > >
> > > End of Gwc-general Digest
> > 
> > I think you need to set it to 
> > 
> > plughw:0
> > 
> > in the miscellaneous -preferences- device 
> > 
> > setttings
> > -- 
> > Ken Dere
> > 
> > 
> > -------------------------------------------------------
> > 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
> > 
> > 
> 
> 
> -------------------------------------------------------
> 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
> 
> 

Re: [Gwc-general] Re: Gwc-general digest, Vol 1 #80 - 2 msgs

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

Setting "Settings>Miscellaneous>Audio device" to "plughw:0" indeed makes a 
difference. Sometimes I even get a very short snippet of sound. But then it 
just goes into a loop with:

"aw2 ~ # gwc
Current stack limit: 8388608 bytes
leaving start with audio_playback=1
##########################################################
audio_device_nonblocking_write_buffer_size: snd_pcm_avail_update
Broken pipe
##########################################################
audio_device_processed_bytes: snd_pcm_delay
Broken pipe"
(in this case it went directly into a loop)

This card is a bit different from the rest since it doesn't use the mixer, 
everything goes directly to the card. So maybe I have to set the output 
channels also in that box. Does anyone knows how to do that?

So it really looks as alsa is not usable. This is a pity since from 2.6.x this 
is the preferred way of working. Even better would be a jack interface since 
then even all routing would be taken care of.

Bigger problem is that OSS emulation on the Hammerfall is not usable for one 
reason or another. So I will have to add another soundcard (or worse, get the 
onboard sound working).

Regards,
Johan

On Thursday 04 August 2005 15:37, Ken Dere wrote:
> On Wednesday 03 August 2005 23:05, gwc...@li... 
> wrote:
> 
> >
> > Message: 2
> > Date: Wed, 03 Aug 2005 06:19:28 -0700
> > From: Jeff Welty <we...@ya...>
> > To: joh...@sk...
> > CC: gwc...@li...
> > Subject: Re: [Gwc-general] problem getting gwc to use alsa
> >
> > I still don't have an ALSA setup. so I can't test this.  But the
> > settings->miscellaneous->audio device
> > was created for ALSA users.
> >
> > Anyone with alsa care to offer some advice?
> >
> > jw
> >
> > Johan De Groote wrote:
> > >Hello, here again...
> > >
> > >So I got gwc running under 64bit, but I cannot use alsa.
> > >
> > >I have alsa compiled into the 2.6.11 kernel. Using the rme hammerfall
> > > card. I do have the following installed:
> > >alsa-lib 1.0.8
> > >alsa-headers 1.0.8
> > >alsa-utils 1.0.8
> > >Other applications using alsa work fine.
> > >
> > >I used "./configure --enable-alsa" and recompiled gwc (had forgotten this
> > >option the first time). When I want to play back a file, I get the
> > > following window: "failed to open output device /dev/dsp0"
> > >
> > >if I click "OK", gwc crashes and I have the following in the terminal:
> > >
> > >"daw2 ~ # gwc
> > >Current stack limit: 8388608 bytes
> > >ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp0
> > >##########################################################
> > >audio_device_open: snd_pcm_open
> > >No such file or directory
> > >gwc: pcm.c:920: snd_pcm_delay: Assertion `pcm' failed."
> > >
> > >So it looks like even if you compile to use alsa that it still looks to
> > > use the OSS output driver. Or do I have to give an option on the command
> > > line when starting gwc? I don't remember having to do that before and 
the
> > > --help doesn't list anything for output selection. Or do I have to use
> > > some other output device in the "Settings>Miscellaneous"? But then what,
> > > because "hw:0" also doesn't work?
> > >
> > >regards,
> > >Johan
> > >
> > >
> > >
> > >-------------------------------------------------------
> > >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > >from IBM. Find simple to follow Roadmaps, straightforward articles,
> > >informative Webcasts and more! Get everything you need to get up to
> > >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > >_______________________________________________
> > >Gwc-general mailing list
> > >Gwc...@li...
> > >https://lists.sourceforge.net/lists/listinfo/gwc-general
> > >
> > >
> > >
> > >!DSPAM:42f0bdc9134501476118180!
> >
> > --__--__--
> >
> > _______________________________________________
> > Gwc-general mailing list
> > Gwc...@li...
> > https://lists.sourceforge.net/lists/listinfo/gwc-general
> >
> >
> > End of Gwc-general Digest
> 
> I think you need to set it to 
> 
> plughw:0
> 
> in the miscellaneous -preferences- device 
> 
> setttings
> -- 
> Ken Dere
> 
> 
> -------------------------------------------------------
> 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
> 
> 

[Gwc-general] Re: Gwc-general digest, Vol 1 #80 - 2 msgs

[Ken D. <kpd...@mc...>]

On Wednesday 03 August 2005 23:05, gwc...@li... 
wrote:

>
> Message: 2
> Date: Wed, 03 Aug 2005 06:19:28 -0700
> From: Jeff Welty <we...@ya...>
> To: joh...@sk...
> CC: gwc...@li...
> Subject: Re: [Gwc-general] problem getting gwc to use alsa
>
> I still don't have an ALSA setup. so I can't test this.  But the
> settings->miscellaneous->audio device
> was created for ALSA users.
>
> Anyone with alsa care to offer some advice?
>
> jw
>
> Johan De Groote wrote:
> >Hello, here again...
> >
> >So I got gwc running under 64bit, but I cannot use alsa.
> >
> >I have alsa compiled into the 2.6.11 kernel. Using the rme hammerfall
> > card. I do have the following installed:
> >alsa-lib 1.0.8
> >alsa-headers 1.0.8
> >alsa-utils 1.0.8
> >Other applications using alsa work fine.
> >
> >I used "./configure --enable-alsa" and recompiled gwc (had forgotten this
> >option the first time). When I want to play back a file, I get the
> > following window: "failed to open output device /dev/dsp0"
> >
> >if I click "OK", gwc crashes and I have the following in the terminal:
> >
> >"daw2 ~ # gwc
> >Current stack limit: 8388608 bytes
> >ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp0
> >##########################################################
> >audio_device_open: snd_pcm_open
> >No such file or directory
> >gwc: pcm.c:920: snd_pcm_delay: Assertion `pcm' failed."
> >
> >So it looks like even if you compile to use alsa that it still looks to
> > use the OSS output driver. Or do I have to give an option on the command
> > line when starting gwc? I don't remember having to do that before and the
> > --help doesn't list anything for output selection. Or do I have to use
> > some other output device in the "Settings>Miscellaneous"? But then what,
> > because "hw:0" also doesn't work?
> >
> >regards,
> >Johan
> >
> >
> >
> >-------------------------------------------------------
> >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> >from IBM. Find simple to follow Roadmaps, straightforward articles,
> >informative Webcasts and more! Get everything you need to get up to
> >speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >_______________________________________________
> >Gwc-general mailing list
> >Gwc...@li...
> >https://lists.sourceforge.net/lists/listinfo/gwc-general
> >
> >
> >
> >!DSPAM:42f0bdc9134501476118180!
>
> --__--__--
>
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
> End of Gwc-general Digest

I think you need to set it to 

plughw:0

in the miscellaneous -preferences- device 

setttings
-- 
Ken Dere

Re: [Gwc-general] problem getting gwc to use alsa

[Stewart E. <st...@lu...>]

My only comment is that I tried to use direct ALSA, ran into problems 
that made me think the ALSA support in gwc wasn't really usable, and 
went back to OSS (emulation, that is). I have not had time to 
investigate any further (and I understand ALSA very little, in any case...)

-- Stewart

Jeff Welty wrote:

> I still don't have an ALSA setup. so I can't test this.  But the 
> settings->miscellaneous->audio device
> was created for ALSA users.
>
> Anyone with alsa care to offer some advice?
>
> jw
>
> Johan De Groote wrote:
>
>> Hello, here again...
>>
>> So I got gwc running under 64bit, but I cannot use alsa.
>>
>> I have alsa compiled into the 2.6.11 kernel. Using the rme hammerfall 
>> card. I do have the following installed:
>> alsa-lib 1.0.8
>> alsa-headers 1.0.8
>> alsa-utils 1.0.8
>> Other applications using alsa work fine.
>>
>> I used "./configure --enable-alsa" and recompiled gwc (had forgotten 
>> this option the first time). When I want to play back a file, I get 
>> the following window: "failed to open output device /dev/dsp0"
>>
>> if I click "OK", gwc crashes and I have the following in the terminal:
>>
>> "daw2 ~ # gwc
>> Current stack limit: 8388608 bytes
>> ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp0
>> ##########################################################
>> audio_device_open: snd_pcm_open
>> No such file or directory
>> gwc: pcm.c:920: snd_pcm_delay: Assertion `pcm' failed."
>>
>> So it looks like even if you compile to use alsa that it still looks 
>> to use the OSS output driver. Or do I have to give an option on the 
>> command line when starting gwc? I don't remember having to do that 
>> before and the --help doesn't list anything for output selection. Or 
>> do I have to use some other output device in the 
>> "Settings>Miscellaneous"? But then what, because "hw:0" also doesn't 
>> work?
>>
>> regards,
>> Johan
>>
>>
>>
>> -------------------------------------------------------
>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>> informative Webcasts and more! Get everything you need to get up to
>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> _______________________________________________
>> Gwc-general mailing list
>> Gwc...@li...
>> https://lists.sourceforge.net/lists/listinfo/gwc-general
>>
>>
>>
>> !DSPAM:42f0bdc9134501476118180!
>>  
>>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general

Re: [Gwc-general] problem getting gwc to use alsa

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

I still don't have an ALSA setup. so I can't test this.  But the 
settings->miscellaneous->audio device
was created for ALSA users.

Anyone with alsa care to offer some advice?

jw

Johan De Groote wrote:

>Hello, here again...
>
>So I got gwc running under 64bit, but I cannot use alsa.
>
>I have alsa compiled into the 2.6.11 kernel. Using the rme hammerfall card. I 
>do have the following installed:
>alsa-lib 1.0.8
>alsa-headers 1.0.8
>alsa-utils 1.0.8
>Other applications using alsa work fine.
>
>I used "./configure --enable-alsa" and recompiled gwc (had forgotten this 
>option the first time). When I want to play back a file, I get the following 
>window: "failed to open output device /dev/dsp0"
>
>if I click "OK", gwc crashes and I have the following in the terminal:
>
>"daw2 ~ # gwc
>Current stack limit: 8388608 bytes
>ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp0
>##########################################################
>audio_device_open: snd_pcm_open
>No such file or directory
>gwc: pcm.c:920: snd_pcm_delay: Assertion `pcm' failed."
>
>So it looks like even if you compile to use alsa that it still looks to use 
>the OSS output driver. Or do I have to give an option on the command line 
>when starting gwc? I don't remember having to do that before and the --help 
>doesn't list anything for output selection. Or do I have to use some other 
>output device in the "Settings>Miscellaneous"? But then what, because "hw:0" 
>also doesn't work?
>
>regards,
>Johan
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:42f0bdc9134501476118180!
>  
>

[Gwc-general] problem getting gwc to use alsa

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

Hello, here again...

So I got gwc running under 64bit, but I cannot use alsa.

I have alsa compiled into the 2.6.11 kernel. Using the rme hammerfall card. I 
do have the following installed:
alsa-lib 1.0.8
alsa-headers 1.0.8
alsa-utils 1.0.8
Other applications using alsa work fine.

I used "./configure --enable-alsa" and recompiled gwc (had forgotten this 
option the first time). When I want to play back a file, I get the following 
window: "failed to open output device /dev/dsp0"

if I click "OK", gwc crashes and I have the following in the terminal:

"daw2 ~ # gwc
Current stack limit: 8388608 bytes
ALSA lib pcm.c:2068:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp0
##########################################################
audio_device_open: snd_pcm_open
No such file or directory
gwc: pcm.c:920: snd_pcm_delay: Assertion `pcm' failed."

So it looks like even if you compile to use alsa that it still looks to use 
the OSS output driver. Or do I have to give an option on the command line 
when starting gwc? I don't remember having to do that before and the --help 
doesn't list anything for output selection. Or do I have to use some other 
output device in the "Settings>Miscellaneous"? But then what, because "hw:0" 
also doesn't work?

regards,
Johan

[Gwc-general] 64bit gwc

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

Tried to get gwc working on my Gentoo 2.6.11-gentoo-r7 install. The config 
went fine, but the make failed with:
___________________________________________________________________________________
daw2 gwc-0.20-10b # make
gcc -DDATADIR=\"/usr/local/share\" -DLIBDIR=\"/usr/local/lib\" 
-DAPPNAME=\"gnome_wave_cleaner\"  -DHAVE_FFTW3 -DFFTWPREC=2   -Wall -g -O2 
-mcpu=x86_64 -march=x86_64 -DORBIT2=1 -pthread -DXTHREADS -D_REENTRANT 
-DXUSE_MTSAFE_API -I/usr/include/libgnomeui-2.0 -I/usr/include/libgnome-2.0 
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0 
-I/usr/include/libart-2.0 -I/usr/include/gconf/2 
-I/usr/include/libbonoboui-2.0 -I/usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I/usr/include/orbit-2.0 
-I/usr/include/libbonobo-2.0 -I/usr/include/gnome-vfs-2.0 
-I/usr/lib64/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0 
-I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 
-I/usr/include/freetype2/config -I/usr/include/libxml2     -c dialog.c
`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
dialog.c:1: error: bad value (x86_64) for -march= switch
dialog.c:1: error: bad value (x86_64) for -mtune= switch
make: *** [dialog.o] Error 1
daw2 gwc-0.20-10b #   
__________________________________________________________________________________________

So I changed in the makefile in the line:

CFLAGS = -Wall -g -O2 -mcpu=x86_64 -march=x86_64 -DORBIT2=1 -pthread 
-DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API

in both cases "x86_64" by "k8".
This compiled and installed cleanly with some warnings about '-mcpu' being 
deprecated. It even starts, and I can load a file. I cannot play it however 
since it cannot find /dev/dsp0, but this is quite normal since I only have 
alsa and jack.

Hope this can help someone.

Regards,
Johan

Re: [Gwc-general] Not able to run gwc-0.20-10b

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

1) find out what directory you installed the libsndfile libs, let"s
     say it"s /usr/local/lib
 
 2) look at your /etc/ld.so.conf file -- does it have "/usr/local/lib" 
 (or where-ever you installed the fftw libs) as one of the lines?  If
 not, become root, add the install directory, and issue the command 
 "ldconfig"

jw


prakhar vig wrote:

>Hi All,
>
>I have successfully install
>gwc-0.20-10b,libsndfile-1.0.11 and fftw-3.0.1.
>
>But when I tried to run gwc, with the following
>command
>:
>gwc or ./gwc
>it gave me the following error:
>
>"gwc: error while loading shared libraries:
>libsndfile.so.1: cannot open shared object file: No
>such file or directory"
>
>Can anyone help me regarding this, that how to resolve
>this error and successfully run gwc. I am in dire need
>of it, please help me out at the earliest.
>
>Thanks And Regards
>Prakhar
>
>
>
>		
>_______________________________________________________
>Too much spam in your inbox? Yahoo! Mail gives you the best spam protection for FREE! http://in.mail.yahoo.com
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:42e499f4285541409295358!
>  
>

Re: [Gwc-general] Not able to run gwc-0.20-10b

[Joseph D. <jos...@gm...>]

Running "ldconfig" sometimes helps if you have just installed a
library and the system doesn't seem to be using it.

The manual for the dynamic linker is called "ld.so" so "man ld.so"
will display it.

If ldconfig dosen't work, make sure you have either a file or a
symbolic link called "libsndfile.so.1" in one of the directorys that
the linker looks in.

If you have a file called "libsndfile.so" but no "libsndfile.so.1",
try making a symbolic link called "libsndfile.so.1" which points to
"libsndfile.so".

If the linker still can't find the file, find a copy of it and place
it in /usr/lib.

Joseph

On 25/07/05, prakhar vig <aqu...@ya...> wrote:
> Hi All,
>=20
> I have successfully install
> gwc-0.20-10b,libsndfile-1.0.11 and fftw-3.0.1.
>=20
> But when I tried to run gwc, with the following
> command
> :
> gwc or ./gwc
> it gave me the following error:
>=20
> "gwc: error while loading shared libraries:
> libsndfile.so.1: cannot open shared object file: No
> such file or directory"
>=20
> Can anyone help me regarding this, that how to resolve
> this error and successfully run gwc. I am in dire need
> of it, please help me out at the earliest.
>=20
> Thanks And Regards
> Prakhar
>=20
>=20
>=20
>=20
> _______________________________________________________
> Too much spam in your inbox? Yahoo! Mail gives you the best spam protecti=
on for FREE! http://in.mail.yahoo.com
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> Gwc-general mailing list
> Gwc...@li...
> https://lists.sourceforge.net/lists/listinfo/gwc-general
>=20


--=20
Joseph Daly <jos...@gm...>

[Gwc-general] Not able to run gwc-0.20-10b

[prakhar v. <aqu...@ya...>]

Hi All,

I have successfully install
gwc-0.20-10b,libsndfile-1.0.11 and fftw-3.0.1.

But when I tried to run gwc, with the following
command
:
gwc or ./gwc
it gave me the following error:

"gwc: error while loading shared libraries:
libsndfile.so.1: cannot open shared object file: No
such file or directory"

Can anyone help me regarding this, that how to resolve
this error and successfully run gwc. I am in dire need
of it, please help me out at the earliest.

Thanks And Regards
Prakhar



		
_______________________________________________________
Too much spam in your inbox? Yahoo! Mail gives you the best spam protection for FREE! http://in.mail.yahoo.com

[Gwc-general] compiling gwc under 64bit?

[Donald J. <dja...@ki...>]

On 23-Jun-05, at 11:05 PM, gwc...@li...  
wrote:
>
> Today's Topics:
>
>    1. compiling gwc under 64bit? (Johan De Groote)
>
> --__--__--
>
> Message: 1
> From: Johan De Groote <joh...@sk...>
> Reply-To: joh...@sk...
> To: gwc...@li...
> Date: Fri, 24 Jun 2005 18:39:32 +0000
> Subject: [Gwc-general] compiling gwc under 64bit?
>
> Hello,
>
> Has anyone experience with compiling gwc under 64bit?
>
> Best regards,
> Johan
>

I have successfully compiled gwc under OS X Tiger, Mac G5, with gcc  
4.  Because of the  differences in the various APIs between Linux and  
OS X, there is a significantly large problem in getting all the Fink  
libraries etc that are needed. That took a while :-)

However, the actual code changes were few and  specific to OS X, and  
I don't think there should be a serious problem wrt 64-bit Linux .  I  
suggest you try it and see.




Donald Jardine
67 Hill Street
Kingston, ON
Canada K7L 2M6
Voicemail: 613.542.9601

[Gwc-general] compiling gwc under 64bit?

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

Hello,

Has anyone experience with compiling gwc under 64bit? 

Best regards,
Johan

Re: [Gwc-general] gwc 0.20-10b seems to be very slow

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

In version 0.20-10  an FFT method of click detection was introduced.  It 
is sometimes better than the previous version, but is always MUCH 
slower.  Will you double-check your declick options and make sure you 
are not using the FFT method for click detection?

Thanks,
jw

Ken Dere wrote:

>I recently installed gwc 0.20-10b and found it to be extememely slow in 
>removing large and small pops/clicks when compared with previous versions.  I 
>compiled this one from source.
>
>I then installed 0.20-09 from an rpm and found it to work more or less as I 
>would have expected.
>
>I just upgraded to Suse 9.3 which is why I had to reinstall gwc but the 
>machine is the same.
>
>Ken Dere
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Yahoo.
>Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
>Search APIs Find out how you can build Yahoo! directly into your own
>Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:429cd547226411233319954!
>  
>

[Gwc-general] gwc 0.20-10b seems to be very slow

[Ken D. <kpd...@mc...>]

I recently installed gwc 0.20-10b and found it to be extememely slow in 
removing large and small pops/clicks when compared with previous versions.  I 
compiled this one from source.

I then installed 0.20-09 from an rpm and found it to work more or less as I 
would have expected.

I just upgraded to Suse 9.3 which is why I had to reinstall gwc but the 
machine is the same.

Ken Dere

Re: [Gwc-general] available as a ladspa plugin?

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

That was a few years ago.  It's impossbile, because of the way GWC's 
denoising and declicking
algorithms work (and why you're not likely to see high quality 
denoising/declicking algorithms
implemented in ladspa until its basic architecture changes).

Jeff

David Mulcahy wrote:

>Hi
>I read some time ago now that you were thinking of making a ladspa plugin with 
>similar functionality as gwc.  Is this still in the pipeline or has it been 
>cancelled.
>
>Dave
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: NEC IT Guy Games.
>Get your fingers limbered up and give it your best shot. 4 great events, 4
>opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
>win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
>_______________________________________________
>Gwc-general mailing list
>Gwc...@li...
>https://lists.sourceforge.net/lists/listinfo/gwc-general
>
>
>
>!DSPAM:427a2e2c152061080644946!
>  
>

Re: [Gwc-general] available as a ladspa plugin?

[Esben S. <b0...@es...>]

David Mulcahy <es...@ti...> writes:

> a ladspa plugin with similar functionality as gwc

That would be wickedly nice;)

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
          [sip|iax]:   e     e 
           jid:b0ef@    n     n

[Gwc-general] available as a ladspa plugin?

[David M. <es...@ti...>]

Hi
I read some time ago now that you were thinking of making a ladspa plugin with 
similar functionality as gwc.  Is this still in the pipeline or has it been 
cancelled.

Dave

Re: [Gwc-general] runtime-error with gwc-0.20-10b

[Stewart E. <st...@lu...>]

I don't really know alsa well at all, but my understanding is that
/dev/dsp is the OSS-emulation device, and if you were running in native 
alsa mode you would want to use a different device - I think they're under 
/dev/snd/ .

I played very briefly with trying to run gwc with alsa enabled, but I got 
the impression that the alsa support wasn't very mature.

-- Stewart

-- 
Help get Bill Monroe on a US postage stamp! http://www.billmonroestamp.org/