OK, thanks.

It sounds like I should probably use the PVOC_CUSTOM facility to write and read ftable windows.

Regards,
Mike

-----Original Message-----
>From: Richard Dobson 
>Sent: Aug 19, 2007 12:16 PM
>To: Developer discussions 
>Subject: Re: [Cs-dev] Proposed use of function tables as windows in phase vocoders
>
>"Normal" pvoc has hopsize (overlap) >> 1,
>
>pvoc using SDFT gives us hopsize  = 1
>
>Anything that is not sliding must be jumping!
>
>Richard Dobson
>
>
>
>
>
>
>Michael Gogins wrote:
>> What is the "jumping version?"
>> 
>> Regards,
>> Mike
>> 
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >>  http://get.splunk.com/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

In internal opcode code, yes. But, just to clarify the general picture: 
there is no need (nor advantage) to expose PVOC_CUSTOM directly in an 
opcode; the -1 window number in the opcode can stay as it is (with the 
understanding that we can't support it for the SDFT). It is important to 
have opcodes independent of specific file format stuff wherever 
possible. For a pvsfwrite opcode, the internal implementation would use 
PVOC_CUSTOM, but again we would want to avoid using PVOC_CUSTOM as a 
parameter value at opcode level.

In principle, someone could devise an opcode to write an fsig to an SDIF 
file, comnplete with custom window data. They would have many mountains 
to climb (and streams to ford...), but in principle it is possible.

Though they will want to avoid doing that for the sliding version!



Richard Dobson




Michael Gogins wrote:
> OK, thanks.
> 
> It sounds like I should probably use the PVOC_CUSTOM facility to write and read ftable windows.
> 
> Regards,
> Mike
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net