Defining Channel sets over script pipe (was: Getting and Setting the selection...

2 messages Options
Embed this post
Permalink
John Martin Goddard

Defining Channel sets over script pipe (was: Getting and Setting the selection...

Reply Threaded More More options
Print post
Permalink
Hello again,

> I believe it's possible to set the selected track by number already,
> using something like: "Select: Type=Range FirstTrack=2 LastTrack=2",
> although it might still be good to have a more direct way of doing this.
> Since more than one track may be selected, any 'GetSelected' command
> would need to return a list of track numbers.

Could the set of selected tracks best be communicated using a bitfield?

I don't know what the maximum number of tracks are, but perhaps a byte length parameter could be also be used.

This starts to look like a binary communication protocol, and I don't know how it
could or would be used in the Perl scripting world, can you?


I'm interested to use this bitfield to communicate all kinds of sets of tracks:
Those which are muted, in solo, and perhaps for other criteria, such as track type (for example, all the audio tracks) or even whether the gain or pan are set above or below a given threshold.

What are your thoughts?
Marty

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Markus Meyer

Re: Defining Channel sets over script pipe (was: Getting and Setting the selection...

Reply Threaded More More options
Print post
Permalink
John Martin Goddard schrieb:
> Could the set of selected tracks best be communicated using a bitfield?
>  
I would rather use something human-readable, like a string, say
something like "00001111001110011" where "1" means "selected" and "0"
means "unselected". Bitfields only really have a value if file
size/bandwidth really matters (as in, say, embedded systems and device
drivers), otherwise they are just confusing, harder to code and not
worth the few bytes saved.


Markus


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
audacity-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/audacity-devel