I added "massign 0,0". There was no difference compared to the earlier behaviour. All the events were read and printed correctly
but without any time-delays between events.
If i have a real midi-connection and events come after every 2s, then printing happens also at 2s interval.
Now when the midi-file includes exactly the same events with the same 2s time-intervals, shouldn't printing then also happen after every 2s ?

So actually it's the question of how csd get's the midi-events in. The manual says that -F behaves the same way as the real-connections.
However the manual doesn't say exactly what happens to the event time-stamps in the midi-file. So if the -F is identical to the real midi-input, it would mean
also that timing of the events will happen before they reach the active code.

Is there still something else that is needed to preserve the time-stamps from the midi-file ?
By the way i also tried the "opposite", "massign 1,1". Also that didn't help.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

No, because you are not running in realtime. You are running as fast the computer can run. You need to add a -odac to slow it down to realtime.

Prof. Victor Lazzarini
Maynooth University
Ireland

> On 20 Mar 2024, at 21:33, Risto Kuusisto  wrote:
>
> I added "massign 0,0". There was no difference compared to the earlier behaviour. All the events were read and printed correctly
> but without any time-delays between events.
> If i have a real midi-connection and events come after every 2s, then printing happens also at 2s interval.
> Now when the midi-file includes exactly the same events with the same 2s time-intervals, shouldn't printing then also happen after every 2s ?
>
> So actually it's the question of how csd get's the midi-events in. The manual says that -F behaves the same way as the real-connections.
> However the manual doesn't say exactly what happens to the event time-stamps in the midi-file. So if the -F is identical to the real midi-input, it would mean
> also that timing of the events will happen before they reach the active code.
>
> Is there still something else that is needed to preserve the time-stamps from the midi-file ?
> By the way i also tried the "opposite", "massign 1,1". Also that didn't help.
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here