The code says

int midiTempoOpcode(CSOUND *csound, MIDITEMPO *p)
{
    if (MIDIFILE == NULL)
      *(p->kResult) = FL(60.0) *csound->esr / (MYFLT)(csound->ibeatTime);
    else
      *(p->kResult) = (MYFLT) MF(currentTempo);
    return OK;
}

so in the case of no midi file and no t score opcode it should return
the sample rate -- which feels wrong.  Is that related to what you are
seeing?

==John ffitch

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

i get the same result 2880000 whether i give in the score t 0 60.0 or nothing
- in which case assumed is that t  = 60.
But there is a relation in that 2880000 / 60 = 48000. And that happens to be
my sample rate.

Perhaps i do not understand the use of the opcode correctly...



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

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

That makes sense if csound->ibeatTime is 1

I will look more closely at the code but it looks wrong-minded. 
I wonder if it works in the midi case.  The manual example seems to be 
missing the midi file

What value are you expecting?  It must differ from tempoval surely?


On Fri, 8 Feb 2019, Menno Knevel wrote:

> i get the same result 2880000 whether i give in the score t 0 60.0 or nothing
> - in which case assumed is that t  = 60.
> But there is a relation in that 2880000 / 60 = 48000. And that happens to be
> my sample rate.
>
> Perhaps i do not understand the use of the opcode correctly...
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
> 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

Reading the code csound->ibeatTime is 1 unless the -t option is used.   So 
that explains it all, except what it should do!

On Fri, 8 Feb 2019, Menno Knevel wrote:

> i get the same result 2880000 whether i give in the score t 0 60.0 or nothing
> - in which case assumed is that t  = 60.
> But there is a relation in that 2880000 / 60 = 48000. And that happens to be
> my sample rate.
>
> Perhaps i do not understand the use of the opcode correctly...
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
> 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

yes, the command line - t 60 was the solution! Now miditempo does work as
expected. 

The manual does not reflect this -t option. The example uses a midifile,
there is mention of the score as well but no mention of the command line -t
option.
(When i made or updated that example i never tried out miditempo together
with a score only, i guess...)

John, can you add in the manual that when using a score the command line -t
x should be set as well?

And: can the code from miditempo be modified so that it would accept the t
statement from the score also, leaving out the command line -t?  The t
statement from the score can vary, and miditempo could follow the changes.
Or is that another system?
 



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

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

Manual rweaked.  Problen wit making it work from the scoore t opcode is 
that in the score t can  vary over time and this adjusts the p2/p3 values 
and there is no recor of what the tempoisa any time.  So irt would require 
a great deal of additional work.


On Sat, 9 Feb 2019, Menno Knevel wrote:

> yes, the command line - t 60 was the solution! Now miditempo does work as
> expected.
>
> The manual does not reflect this -t option. The example uses a midifile,
> there is mention of the score as well but no mention of the command line -t
> option.
> (When i made or updated that example i never tried out miditempo together
> with a score only, i guess...)
>
> John, can you add in the manual that when using a score the command line -t
> x should be set as well?
>
> And: can the code from miditempo be modified so that it would accept the t
> statement from the score also, leaving out the command line -t?  The t
> statement from the score can vary, and miditempo could follow the changes.
> Or is that another system?
>
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
> 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