I'm stuck for a name of a new opcode I'm preparing. It's a pvs opcode,  
it reads from a table (e.g.  with GEN01), analyses it and
produces a fsig.

Currently, it's called pvstanal (as in pvsanal with a t in the  
middle), but it's probably easily confused with pvsanal.

So, does anyone have a suggestion?

Victor


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

glad to hear about a new pvs opcode ...
there is pvsfread, and pvsbufread -
so perhaps pvstabread? or pvsiftread?
but i don't know which arguments it uses, and my english is definitely  
too poor ...

	joachim


Am 25.10.2010 um 22:20 schrieb Victor Lazzarini:

> I'm stuck for a name of a new opcode I'm preparing. It's a pvs  
> opcode, it reads from a table (e.g.  with GEN01), analyses it and
> produces a fsig.
>
> Currently, it's called pvstanal (as in pvsanal with a t in the  
> middle), but it's probably easily confused with pvsanal.
>
> So, does anyone have a suggestion?
>
> Victor
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

It is good not to have names that are too long, if at all possible (I 
wrote, having made some quite long ones!). While I see the potential for 
confusion, I am not bothered by "pvstanal" as a name. A shorter name 
could be "pvsaft" or "pvsftan" (or something...).

Richard Dobson


On 25/10/2010 21:36, joachim heintz wrote:
> glad to hear about a new pvs opcode ...
> there is pvsfread, and pvsbufread -
> so perhaps pvstabread? or pvsiftread?
> but i don't know which arguments it uses, and my english is definitely
> too poor ...
>
> joachim
>
>
> Am 25.10.2010 um 22:20 schrieb Victor Lazzarini:
>
>> I'm stuck for a name of a new opcode I'm preparing. It's a pvs opcode,
>> it reads from a table (e.g. with GEN01), analyses it and
>> produces a fsig.
>>
>> Currently, it's called pvstanal (as in pvsanal with a t in the
>> middle), but it's probably easily confused with pvsanal.
>>
>> So, does anyone have a suggestion?
>>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I like the read idea...maybe pvstread. Keeps it within the old 8 character
framework and seems more descriptive of what you describe as its function
than "anal." In any case, it will be useful--Thanks!

--David Mooney

> It is good not to have names that are too long, if at all possible (I
> wrote, having made some quite long ones!). While I see the potential for
> confusion, I am not bothered by "pvstanal" as a name. A shorter name
> could be "pvsaft" or "pvsftan" (or something...).
>
> Richard Dobson
>
>
> On 25/10/2010 21:36, joachim heintz wrote:
>> glad to hear about a new pvs opcode ...
>> there is pvsfread, and pvsbufread -
>> so perhaps pvstabread? or pvsiftread?
>> but i don't know which arguments it uses, and my english is definitely
>> too poor ...
>>
>> joachim
>>
>>
>> Am 25.10.2010 um 22:20 schrieb Victor Lazzarini:
>>
>>> I'm stuck for a name of a new opcode I'm preparing. It's a pvs opcode,
>>> it reads from a table (e.g. with GEN01), analyses it and
>>> produces a fsig.
>>>
>>> Currently, it's called pvstanal (as in pvsanal with a t in the
>>> middle), but it's probably easily confused with pvsanal.
>>>
>>> So, does anyone have a suggestion?
>>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>

In many other cases a digit has been added to a similar opcode:

adsynt
adsynt2

dcblock
dcblock2

FLcolor
Flcolor2

flooper
flooper2


etc....

That scheme seems fine to me.

-Lou


On Oct 25, 2010, at 4:20 PM, Victor Lazzarini wrote:

> I'm stuck for a name of a new opcode I'm preparing. It's a pvs  
> opcode, it reads from a table (e.g.  with GEN01), analyses it and
> produces a fsig.
>
> Currently, it's called pvstanal (as in pvsanal with a t in the  
> middle), but it's probably easily confused with pvsanal.
>
> So, does anyone have a suggestion?
>
> Victor
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Pvstabanal?

MKG from cell phone

On Oct 25, 2010 8:51 PM, "Louis Cohen" <loucohen@jolc.net> wrote:

In many other cases a digit has been added to a similar opcode:

adsynt
adsynt2

dcblock
dcblock2

FLcolor
Flcolor2

flooper
flooper2


etc....

That scheme seems fine to me.

-Lou

On Oct 25, 2010, at 4:20 PM, Victor Lazzarini wrote:

> I'm stuck for a name of a new opcode I'm ...

oooh, a bit too banal ? :-)

pvstab might be enough, but could be confused with pvsftr/pvsftw,
...pvsantab(us) ?

sorry, bad jokes, I'll go get my coffee...
Oeyvind

2010/10/26 Michael Gogins :
> Pvstabanal?
>
> MKG from cell phone
>
> On Oct 25, 2010 8:51 PM, "Louis Cohen"  wrote:
>
> In many other cases a digit has been added to a similar opcode:
>
> adsynt
> adsynt2
>
> dcblock
> dcblock2
>
> FLcolor
> Flcolor2
>
> flooper
> flooper2
>
>
> etc....
>
> That scheme seems fine to me.
>
> -Lou
>
>
> On Oct 25, 2010, at 4:20 PM, Victor Lazzarini wrote:
>
>> I'm stuck for a name of a new opcode I'm ...


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

was pvstabnal already mentioned?

menno

Thanks everyone for the ideas. One thing to bear in mind is that
'read'  might imply reading PV data from table (which is already done  
by pvsftr etc),
while what this does is to read samples from a table, then analyse  
them, producing
an fsig, hence the 'anal'.

I think  I like pvsftanal better than pvstanal and I agree with  
shorter names.
But I have not decided yet. If anyone has more ideas, please keep them  
coming.

  Victor

On 25 Oct 2010, at 23:29, moko@city-net.com wrote:

> I like the read idea...maybe pvstread. Keeps it within the old 8  
> character
> framework and seems more descriptive of what you describe as its  
> function
> than "anal." In any case, it will be useful--Thanks!
>
> --David Mooney
>
>> It is good not to have names that are too long, if at all possible (I
>> wrote, having made some quite long ones!). While I see the  
>> potential for
>> confusion, I am not bothered by "pvstanal" as a name. A shorter name
>> could be "pvsaft" or "pvsftan" (or something...).
>>
>> Richard Dobson
>>
>>
>> On 25/10/2010 21:36, joachim heintz wrote:
>>> glad to hear about a new pvs opcode ...
>>> there is pvsfread, and pvsbufread -
>>> so perhaps pvstabread? or pvsiftread?
>>> but i don't know which arguments it uses, and my english is  
>>> definitely
>>> too poor ...
>>>
>>> joachim
>>>
>>>
>>> Am 25.10.2010 um 22:20 schrieb Victor Lazzarini:
>>>
>>>> I'm stuck for a name of a new opcode I'm preparing. It's a pvs  
>>>> opcode,
>>>> it reads from a table (e.g. with GEN01), analyses it and
>>>> produces a fsig.
>>>>
>>>> Currently, it's called pvstanal (as in pvsanal with a t in the
>>>> middle), but it's probably easily confused with pvsanal.
>>>>
>>>> So, does anyone have a suggestion?
>>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/? 
>> group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe
>> csound"
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>
>
> -- 
> mheller@city-net.com
> dmooney@city-net.com
> Opaque Melodies:
> http://www.city-net.com/~moko/
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hooray! :-)

2010/10/26 Victor Lazzarini :
> Well, there are two opcodes (mincer and tpscal) already in 5.12 (OSX) that
> use phase locking (the second one also does onset detection).
> For the next release, tpscal changes name to temposcal and I have a version
> of it producing fsigs (which is what I am trying to name).
> I'm also working on a 'frequency locking' version of phase locking for
> fsigs. Plus a couple of new methods for extracting the spectral envelope,
> which will go into pvscale, pvshift and pvsvoc, improving the quality of the
> formant preservation (which is currently poor). I'm planning
> opcodes to manipulate the spectral envelope as well.
> (By the way, If anyone's in Edinburgh on 5/11, I'll demonstrate some of
> these things in a talk at the Soundings festival).
> Victor
> On 26 Oct 2010, at 11:30, peiman khosravi wrote:
>
> This morning I realised that in Logic pro's vocoder instrument (not a
> particularly good one either) the analysis part of the signal is simply
> called 'Ana'. Is that apple being overly politically correct?!
>
> Since there is talk about new pvs opcodes, how is the phase-locking
> implementation going?
>
> Best,
> Peiman
>
> On 26 October 2010 11:08, Adam  wrote:
>>
>> pvsftfs             bit of a mouthful, might be too much.
>>
>>
>> On Tuesday 26 October 2010 09:55 pm, Victor Lazzarini wrote:
>> > Thanks everyone for the ideas. One thing to bear in mind is that
>> > 'read'  might imply reading PV data from table (which is already done
>> > by pvsftr etc),
>> > while what this does is to read samples from a table, then analyse
>> > them, producing
>> > an fsig, hence the 'anal'.
>> >
>> > I think  I like pvsftanal better than pvstanal and I agree with
>> > shorter names.
>> > But I have not decided yet. If anyone has more ideas, please keep them
>> > coming.
>> >
>> >   Victor
>> >
>> > On 25 Oct 2010, at 23:29, moko@city-net.com wrote:
>> > > I like the read idea...maybe pvstread. Keeps it within the old 8
>> > > character
>> > > framework and seems more descriptive of what you describe as its
>> > > function
>> > > than "anal." In any case, it will be useful--Thanks!
>> > >
>> > > --David Mooney
>> > >
>> > >> It is good not to have names that are too long, if at all possible (I
>> > >> wrote, having made some quite long ones!). While I see the
>> > >> potential for
>> > >> confusion, I am not bothered by "pvstanal" as a name. A shorter name
>> > >> could be "pvsaft" or "pvsftan" (or something...).
>> > >>
>> > >> Richard Dobson
>> > >>
>> > >> On 25/10/2010 21:36, joachim heintz wrote:
>> > >>> glad to hear about a new pvs opcode ...
>> > >>> there is pvsfread, and pvsbufread -
>> > >>> so perhaps pvstabread? or pvsiftread?
>> > >>> but i don't know which arguments it uses, and my english is
>> > >>> definitely
>> > >>> too poor ...
>> > >>>
>> > >>> joachim
>> > >>>
>> > >>> Am 25.10.2010 um 22:20 schrieb Victor Lazzarini:
>> > >>>> I'm stuck for a name of a new opcode I'm preparing. It's a pvs
>> > >>>> opcode,
>> > >>>> it reads from a table (e.g. with GEN01), analyses it and
>> > >>>> produces a fsig.
>> > >>>>
>> > >>>> Currently, it's called pvstanal (as in pvsanal with a t in the
>> > >>>> middle), but it's probably easily confused with pvsanal.
>> > >>>>
>> > >>>> So, does anyone have a suggestion?
>> > >>
>> > >> Send bugs reports to the Sourceforge bug tracker
>> > >>            https://sourceforge.net/tracker/?
>> > >> group_id=81968&atid=564599
>> > >> Discussions of bugs and features can be posted here
>> > >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> > >> "unsubscribe
>> > >> csound"
>> > >>
>> > >>
>> > >> --
>> > >> This message has been scanned for viruses and
>> > >> dangerous content by MailScanner, and is
>> > >> believed to be clean.
>> > >
>> > > --
>> > > mheller@city-net.com
>> > > dmooney@city-net.com
>> > > Opaque Melodies:
>> > > http://www.city-net.com/~moko/
>> > >
>> > >
>> > >
>> > > Send bugs reports to the Sourceforge bug tracker
>> > >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > > Discussions of bugs and features can be posted here
>> > > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> > > "unsubscribe csound"
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"