Another solution is to change block sizes depending upon event times. In other words, whenever an event occurs, a previous block may be interrupted and a new block may be started. I believe this is the general idea in Vessel which is part of LuaAV, based on the Synz C++ unit generator library.

Regards,
Mike

-----Original Message-----
>From: Andres Cabrera 
>Sent: Oct 20, 2008 12:09 PM
>To: Developer discussions 
>Subject: Re: [Cs-dev] Sample accurate k-rate was Re: Questions about	musmon/insert
>
>I understand that all events are rounded to k-periods (e.g. score and
>MIDI events), so when you increase the size of kr, you are actually
>adding jitter to the precision of event timing. It would be nice if
>events had some sort of time stamp that indicated to which sample
>within the k period the event belonged to, so that opcodes that want
>to take advantage of this can do so, while others can simply ignore it
>and continue with the previous behavior. This would enable sample
>accurate syncing of events even if the opcode receives k-rate
>information. The opcode would have to keep track of this internally,
>naturally.
>My goal is to have score and MIDI events with no jitter, no matter the
>size of kr. Maybe there's a better way to do this?
>
>Cheers,
>Andrés
>
>On Mon, Oct 20, 2008 at 9:23 AM, Victor Lazzarini
> wrote:
>> Explain a little more , please?
>>
>> At 15:09 20/10/2008, you wrote:
>>>How hard would it be to time tag events within a control period? It
>>>would be great if opcodes could have sample accurate processing of
>>>k-rate signals (like MIDI for instance).
>>>
>>>Cheers,
>>>Andrés
>>>
>>>On Mon, Oct 20, 2008 at 5:43 AM, jpff  wrote:
>>> > That is one of my current concerns -- I have not looked at Beatmode.
>>> > Anyone got a simple example I can try?
>>> > ==John ffitch
>>> >
>>> > -------------------------------------------------------------------------
>>> > This SF.Net email is sponsored by the Moblin
>>> Your Move Developer's challenge
>>> > Build the coolest Linux based applications
>>> with Moblin SDK & win great prizes
>>> > Grand prize is a trip for two to an Open Source event anywhere in the world
>>> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>> >
>>>
>>>
>>>
>>>--
>>>
>>>
>>>Andrés
>>>
>>>-------------------------------------------------------------------------
>>>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>>>Build the coolest Linux based applications with Moblin SDK & win great prizes
>>>Grand prize is a trip for two to an Open Source event anywhere in the world
>>>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>_______________________________________________
>>>Csound-devel mailing list
>>>Csound-devel@lists.sourceforge.net
>>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> Victor Lazzarini
>> Music Technology Laboratory
>> Music Department
>> National University of Ireland, Maynooth
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
>-- 
>
>
>Andrés
>
>-------------------------------------------------------------------------
>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>Build the coolest Linux based applications with Moblin SDK & win great prizes
>Grand prize is a trip for two to an Open Source event anywhere in the world
>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cso

Problem with varying block size is that some opcodes make calculations
at init time what assumes fixed ksmps.  Not investigated closely but I
would be suspicious.  This would be a major change, and makes my
worries about counting time in samples seem rather trivial.
==John ffitch

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I am wondering here whether we should start working on some
possible structural changes (Version 6?) alongside the upgrades
to Csound 5 (I am suggesting this because perhaps none here might
have the stomach for another 4 year freeze).

In other words: no major structural changes to Csound 5, but 
bugfixes, new opcodes,
minor changes with 2 -3 yearly releases, as we have been doing.

Alongside it, a 'bleeding edge' Csound 6.00 alpha, using only the new 
parser,  the
current opcodes, a minimal API and space for radical changes. Some of
us could then concentrate on that, while others work mostly on keeping
and upgrading 5.

Regards

Victor

At 09:34 21/10/2008, you wrote:
>Problem with varying block size is that some opcodes make calculations
>at init time what assumes fixed ksmps.  Not investigated closely but I
>would be suspicious.  This would be a major change, and makes my
>worries about counting time in samples seem rather trivial.
>==John ffitch
>
>-------------------------------------------------------------------------
>This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>Build the coolest Linux based applications with Moblin SDK & win great prizes
>Grand prize is a trip for two to an Open Source event anywhere in the world
>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net