Well, at the default ksmps, you'd be maximally only 10 samples out of the exact start time (whatever 'exact' in this case means), which is

10/44100 = 0.227 ms. Can't you live with that?

Victor

On 21 May 2011, at 22:00, Alex Weiss wrote:

Yes, that would certainly be a possibility, but I was hoping there would be a more elegant solution. And even then, the question remains how I would obtain a sample-accurate start time from that; it is my understanding that score times are not "evaluated" at the sample rate but instead at the control rate. So simply multiplying the start time by sr would give an inaccurate result.

What I'm trying to do is sync csound with video, using csound->icurTime as the reference time. The sample-accurate start time of the instrument would then be the offset that I can subtract from icurTime.

On Sat, May 21, 2011 at 9:57 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

why don't you have an i-rate input where the start time can be fed
into? Then an instrument can use time to do it.

Victor

On 21 May 2011, at 20:44, Alex Weiss wrote:

> Hi,
>
> what is the easiest way to get a sample-accurate start time of the
> instrument event that calls my opcode? Should I simply read p2 from
> INSDS and multiply by the sample rate?
>
> Thanks

> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie




------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Dr Victor Lazzarini

Senior Lecturer

Dept. of Music

NUI Maynooth Ireland

tel.: +353 1 708 3545

Victor dot Lazzarini AT nuim dot ie

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Hi,

You'd also need to calculate video latency to get it completely in
sync... our best bet is to choose certain times and make sure your
events are triggered at that time. Then when you render the file, it
will sync up.

Cheers,
Andres

On Sun, May 22, 2011 at 11:46 AM, Alex Weiss <alexweiss86@gmail.com> wrote:
> You're right, that is quite low. I was just curious. But I also just
> realized something else: I've completely forgotten to take the latency of
> the output device into account, which would be necessary for accurate sync.
> I don't suppose there is any way for an opcode to obtain such information or
> calculate it?
>
> On Sat, May 21, 2011 at 11:23 PM, Victor Lazzarini
> <Victor.Lazzarini@nuim.ie> wrote:
>>
>> Well, at the default ksmps, you'd be maximally only 10 samples out of the
>> exact start time (whatever 'exact' in this case means), which is
>> 10/44100 = 0.227 ms. Can't you live with that?
>> Victor
>>
>> On 21 May 2011, at 22:00, Alex Weiss wrote:
>>
>> Yes, that would certainly be a possibility, but I was hoping there would
>> be a more elegant solution. And even then, the question remains how I would
>> obtain a sample-accurate start time from that; it is my understanding that
>> score times are not "evaluated" at the sample rate but instead at the
>> control rate. So simply multiplying the start time by sr would give an
>> inaccurate result.
>> What I'm trying to do is sync csound with video, using csound->icurTime as
>> the reference time. The sample-accurate start time of the instrument would
>> then be the offset that I can subtract from icurTime.
>>
>> On Sat, May 21, 2011 at 9:57 PM, Victor Lazzarini
>> <Victor.Lazzarini@nuim.ie> wrote:
>>>
>>> why don't you have an i-rate input where the start time can be fed
>>> into? Then an instrument can use time to do it.
>>>
>>> Victor
>>> On 21 May 2011, at 20:44, Alex Weiss wrote:
>>>
>>> > Hi,
>>> >
>>> > what is the easiest way to get a sample-accurate start time of the
>>> > instrument event that calls my opcode? Should I simply read p2 from
>>> > INSDS and multiply by the sample rate?
>>> >
>>> > Thanks
>>> >
>>> > ------------------------------------------------------------------------------
>>> > What Every C/C++ and Fortran developer Should Know!
>>> > Read this article and learn how Intel has extended the reach of its
>>> > next-generation tools to help Windows* and Linux* C/C++ and Fortran
>>> > developers boost performance applications - including clusters.
>>> >
>>> > http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> Dr Victor Lazzarini
>>> Senior Lecturer
>>> Dept. of Music
>>> NUI Maynooth Ireland
>>> tel.: +353 1 708 3545
>>> Victor dot Lazzarini AT nuim dot ie
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> What Every C/C++ and Fortran developer Should Know!
>>> Read this article and learn how Intel has extended the reach of its
>>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>>> developers boost performance applications - including clusters.
>>> http://p.sf.net/sfu/intel-dev2devmay
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>>
>> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> Dr Victor Lazzarini
>> Senior Lecturer
>> Dept. of Music
>> NUI Maynooth Ireland
>> tel.: +353 1 708 3545
>> Victor dot Lazzarini AT nuim dot ie
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> What Every C/C++ and Fortran developer Should Know!
>> Read this article and learn how Intel has extended the reach of its
>> next-generation tools to help Windows* and Linux* C/C++ and Fortran
>> developers boost performance applications - including clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel