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!