Fwd: control track slider

5 Messages

George Fazekas

Reply Threaded

James,

I'd like to look into that control track we discussed last week and
thought looking at your existing
threshold slider code would be a good start. My initial scan through
track related classes
wasn't too successful in finding it. Is it in CVS head already?

general question: do you recommend working with the latest beta or the
cvs head for small changes.
to be honest my latest checkout is about a year old (i have found it
quite stable to work with:-)

thanks,
Gy

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel

James Crook

Re: Fwd: control track slider

Reply Threaded

George Fazekas wrote:
> James,
>
> General question: do you recommend working with the latest beta or the
> cvs head for small changes.
> to be honest my latest checkout is about a year old (i have found it
> quite stable to work with:-)
>
Generally I would say CVS head - that's what most active developers are
using.
> I'd like to look into that control track we discussed last week and
> thought looking at your existing
> threshold slider code would be a good start. My initial scan through
> track related classes
> wasn't too successful in finding it. Is it in CVS head already?
>
The by-track threshold slider is only in audacity-extra. You can see a
screenshot of it here:

http://sourceforge.net/project/screenshots.php?group_id=191299&ssid=54865

You can see the threshold lines on the graph and that the slider has
four 'pips'. The code relies on being able to treat the wavetracks as
wxControls, which we can't yet do in Audacity. I don't recommend trying
to port that slider code at this stage. Porting it back to Audacity is
significant work. There is a much better return on investment in doing
the other part of labels-using-threshold. I'd suggest that the initial
version use an ordinary slider in a dialog called up from a menu. That
would prove the functionality of adjusting multiple labels based on a
graph and a threshold - without the complexity of the custom slider.

The labeltrack code in Audacity is probably the best place to start
looking at how to do labels-from-threshold. It's going to be simplest
for you to delete labels and recreate them rather than to adjust / merge
/ split as thresholds are moved up or down. Probably the text on the
labels needs to be auto-generated, as attempting to keep the text that a
user may have typed in looks (a) tricky, and (b) less useful. Once the
threshold is so high that there are no labels, all the text will have
been lost anyway, so trying to keep it as the threshold is adjusted
doesn't gain us much.

What thresholding options are you thinking of providing?

--James

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel

George Fazekas

Re: Fwd: control track slider

Reply Threaded

>
> You can see the threshold lines on the graph and that the slider has
> four 'pips'. The code relies on being able to treat the wavetracks as
> wxControls, which we can't yet do in Audacity. I don't recommend
> trying
> to port that slider code at this stage. Porting it back to Audacity
> is
> significant work. There is a much better return on investment in
> doing
> the other part of labels-using-threshold. I'd suggest that the
> initial
> version use an ordinary slider in a dialog called up from a menu.
> That
> would prove the fun

> ctionality of adjusting multiple labels based on a
> graph and a threshold - without the complexity of the custom slider.

> The labeltrack code in Audacity is probably the best place to start
> looking at how to do labels-from-threshold. It's going to be simplest
> for you to delete labels and recreate them rather than to adjust /
> merge
> / split as thresholds are moved up or down. Probably the text on the
> labels needs to be auto-generated, as attempting to keep the text
> that a
> user may have typed in looks (a) tricky, and (b) less useful. Once
> the
> threshold is so high that there are no labels, all the text will have
> been lost anyway, so trying to keep it as the threshold is adjusted
> doesn't gain us much.
>
> What thresholding options are you thinking of providing?

OK. I agree. I did this kind of work with label tracks which also
involved deleting
and regenerating all labels. For a start, some kind of 'noise'
threshold plus
two additional thresholds to set up hysteresis when set slightly apart
would be good.
Optionally peak picking or a variable median filter could also be
interesting.
(e.g. using two tick boxes in the dialog to switch to these modes.)

George

>
> --James
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel

George Fazekas

Re: Fwd: control track slider

Reply Threaded

Hello,

I did some work on this a few weeks ago, but has to do lots of other
things in the mean time unfortunately.
Right now it can display regularly sampled 1D data returned from a
vamp plugin.
I had an idea for converting the data into an editable curve, similar
to the envelope of a wave track.
James, do you think that's worth pursuing / makes sense for the
application you have in mind?

George

On May 1, 2008, at 2:23 PM, James Crook wrote:

> George Fazekas wrote:
>> James,
>>
>> General question: do you recommend working with the latest beta or
>> the
>> cvs head for small changes.
>> to be honest my latest checkout is about a year old (i have found it
>> quite stable to work with:-)
>>
> Generally I would say CVS head - that's what most active developers
> are
> using.
>> I'd like to look into that control track we discussed last week and
>> thought looking at your existing
>> threshold slider code would be a good start. My initial scan through
>> track related classes
>> wasn't too successful in finding it. Is it in CVS head already?
>>
> The by-track threshold slider is only in audacity-extra. You can
> see a
> screenshot of it here:
>
> http://sourceforge.net/project/screenshots.php?group_id=191299&ssid=54865
>
> You can see the threshold lines on the graph and that the slider has
> four 'pips'. The code relies on being able to treat the wavetracks as
> wxControls, which we can't yet do in Audacity. I don't recommend
> trying
> to port that slider code at this stage. Porting it back to Audacity
> is
> significant work. There is a much better return on investment in
> doing
> the other part of labels-using-threshold. I'd suggest that the
> initial
> version use an ordinary slider in a dialog called up from a menu.
> That
> would prove the functionality of adjusting multiple labels based on a
> graph and a threshold - without the complexity of the custom slider.
>
> The labeltrack code in Audacity is probably the best place to start
> looking at how to do labels-from-threshold. It's going to be simplest
> for you to delete labels and recreate them rather than to adjust /
> merge
> / split as thresholds are moved up or down. Probably the text on the
> labels needs to be auto-generated, as attempting to keep the text
> that a
> user may have typed in looks (a) tricky, and (b) less useful. Once
> the
> threshold is so high that there are no labels, all the text will have
> been lost anyway, so trying to keep it as the threshold is adjusted
> doesn't gain us much.
>
> What thresholding options are you thinking of providing?
>
> --James
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
audacity-devel mailing list
audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel

James Crook

Re: Fwd: control track slider

Reply Threaded

George,

Please post a screenshot of what you currently have and say a bit more
about what you plan.

I have a medium term picture of where I'd like to get to. Conversion
from sampled data to editable curve is nice to have, and hard to do
really well (how dense to make the control points?), but I don't see it
as having as big a payoff for the work invested as some of the other
changes being discussed.

--James.

George Fazekas wrote:

> Hello,
>
> I did some work on this a few weeks ago, but has to do lots of other
> things in the mean time unfortunately.
> Right now it can display regularly sampled 1D data returned from a
> vamp plugin.
> I had an idea for converting the data into an editable curve, similar
> to the envelope of a wave track.
> James, do you think that's worth pursuing / makes sense for the
> application you have in mind?
>
> George
>
> On May 1, 2008, at 2:23 PM, James Crook wrote:
>
>
>> George Fazekas wrote:
>>
>>> James,
>>>
>>> General question: do you recommend working with the latest beta or
>>> the
>>> cvs head for small changes.
>>> to be honest my latest checkout is about a year old (i have found it
>>> quite stable to work with:-)
>>>
>>>
>> Generally I would say CVS head - that's what most active developers
>> are
>> using.
>>
>>> I'd like to look into that control track we discussed last week and
>>> thought looking at your existing
>>> threshold slider code would be a good start. My initial scan through
>>> track related classes
>>> wasn't too successful in finding it. Is it in CVS head already?
>>>
>>>
>> The by-track threshold slider is only in audacity-extra. You can
>> see a
>> screenshot of it here:
>>
>> http://sourceforge.net/project/screenshots.php?group_id=191299&ssid=54865
>>
>> You can see the threshold lines on the graph and that the slider has
>> four 'pips'. The code relies on being able to treat the wavetracks as
>> wxControls, which we can't yet do in Audacity. I don't recommend
>> trying
>> to port that slider code at this stage. Porting it back to Audacity
>> is
>> significant work. There is a much better return on investment in
>> doing
>> the other part of labels-using-threshold. I'd suggest that the
>> initial
>> version use an ordinary slider in a dialog called up from a menu.
>> That
>> would prove the functionality of adjusting multiple labels based on a
>> graph and a threshold - without the complexity of the custom slider.
>>
>> The labeltrack code in Audacity is probably the best place to start
>> looking at how to do labels-from-threshold. It's going to be simplest
>> for you to delete labels and recreate them rather than to adjust /
>> merge
>> / split as thresholds are moved up or down. Probably the text on the
>> labels needs to be auto-generated, as attempting to keep the text
>> that a
>> user may have typed in looks (a) tricky, and (b) less useful. Once
>> the
>> threshold is so high that there are no labels, all the text will have
>> been lost anyway, so trying to keep it as the threshold is adjusted
>> doesn't gain us much.
>>
>> What thresholding options are you thinking of providing?
>>
>> --James
>>
>>
>>
>