Re: [Audacity-quality] analyze.ny
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2014-02-10 00:13:34
|
> From Steve the Fiddle <ste...@gm...> > Sun, 9 Feb 2014 13:11:00 +0000 > Subject: [Audacity-quality] analyze.ny > > On 9 February 2014 03:05, Gale Andrews <ga...@au...> wrote: > > > >> From Vaughan Johnson <va...@au...> > >> Sat, 25 Jan 2014 19:02:51 -0800 > >> Subject: [Audacity-quality] analyze.ny > >> > On 1/25/2014 1:07 PM, Steve the Fiddle wrote: > >> > On 25 January 2014 15:04, Steve the Fiddle <ste...@gm...> wrote: > >> >> On 24 January 2014 23:20, Gale Andrews <ga...@au...> wrote: > >> >>>[...] > >> >>>>> Would it be better if we want example plug-ins to make a set of > >> >>>>> three barebones plug-ins, one generator, one effect, one analyzer, > >> >>>>> ship the set from: > >> >>>>> http://wiki.audacityteam.org/wiki/Download_Nyquist_Plug-ins > >> > > >> > Attached is a set of three "barebones" plug-ins. > >> > >> Thanks, Steve! Great. I don't see any reason for these to not be posted > >> on wiki as such. > >> > >> Or any reason for analyze.ny to not be removed from code repository, and > >> the Win installer script simplified. > > > > I think we can do both those. > > > > There may be a few minor corrections needed in Steve's example > > plug-ins. > > > > ** analyze.ny ** > > > > Perhaps "Labelling" should be "labeling" (US English) in > > > > ;action "Labelling start and end of selection..." > > > > > > ** process.ny ** > > > > Is http://lv2plug.in/ns/lv2core/#AmplifierPlugin a better category? > > > > ;action "Reducing amplitude to half" should have an ellipsis. > > > > > > ** generate.ny ** > > > > I was expecting it to be a generate type rather than a process. > > > > There is a typo in the category link which should be > > http://lv2plug.in/ns/lv2core/#GeneratorPlugin > > Thanks for the corrections, and yes the generate,ny should be ;type generate > > Regarding the categories, should we include that at all? > Currently it is not used, and hopefully when we have some sort of > effect manager it will be more flexible than the fixed, multi-level > categories defined by http://lv2plug.in I think we should include categories given the shipped Nyquist plug-ins do so. There is still the potential that someone compiling Audacity can turn the categories feature on. > If we do specify a default category for these plug-ins then it should > probably be a special "demo" category of some kind as these are not > really practical plug-ins. http://lv2plug.in does not define a "demo" > type. Given that, probably best to leave the categories set to the expected category for what the plug-in does. > Regarding the plug-in name, I think that "Sample ... plug-in" is > ambiguous ("sample plug-in" vs "audio sample"). > How about just "Analyze plug-in", "Generate plug-in" and "Process plug-in"? Replace "Sample" with "Example"? > The posted plug-ins were just to get the ball rolling. > Are we happy about the "complexity" of these plug-ins? > > I think it is useful to demonstrate controls (widgets) in at least one > of the plug-ins (which I have done in generate.ny). Would it be useful > to demonstrate all types of control?. I could add a multi-choice and a > text widget in analyze.ny Yes that's a good idea. The analyze plug-in is the most "useless" one of the three - it doesn't show how to label 5 seconds from the start or similar. Gale > >> > [...] > >> >>> > >> >>> True. But how much time would writing a barebones example > >> >>> of each type need, compared to fixing the Workbench up? > >> >>> And could we not reuse those barebones efforts in the > >> >>> Workbench, if it was released? > >> >> > >> >> No problem with putting "barebones" plug-ins on the wiki, though few > >> >> users are likely to find them there. > >> > >> More so there than in the code repository, I'd guess. > >> > >> - V > > > > Each of the Generate, Process and Analyze types have links in > > the Manual to the Wiki. > > > > We could even point out in the Manual that there is an example of > > each type on the Wiki if you think it's important. > > > > > > > > Gale > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |