Hi list,

I can't get these  two opcodes working on my system (cvs csound on Ubuntu
9.10)

I include a short csd and its render wav to show that. 

tempoval gives always zero for kval
and i can't understand why the output wav is like that (2 notes overlaps)

Please note that the tempo manual say to add the -t flag in the command line
but the example given on the same page don't include it.


http://old.nabble.com/file/p26483590/tempo_tempoval.csd tempo_tempoval.csd 
http://old.nabble.com/file/p26483590/tempo-tempoval.wav tempo-tempoval.wav 

Best,
René
-- 
View this message in context: http://old.nabble.com/Problem-with-tempo-and-tempoval-opcodes-on-Linux-tp26483590p26483590.html
Sent from the Csound - General mailing list archive at Nabble.com.



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I ran your csd on os x, and also got zeros. In my experience, the
tempo opcodes don't really work all that well. I wrote some test
scripts back in the day, and the results led me to believe that there
are a lot of bugs with tempo and tempoval. It is possible that some of
these issues have been addressed, as this was a couple of years ago.

Best,
Jake
-- 
The Csound Blog - http://csound.noisepages.com/



On Mon, Nov 23, 2009 at 10:36 AM, Djack  wrote:
>
> Hi list,
>
> I can't get these  two opcodes working on my system (cvs csound on Ubuntu
> 9.10)
>
> I include a short csd and its render wav to show that.
>
> tempoval gives always zero for kval
> and i can't understand why the output wav is like that (2 notes overlaps)
>
> Please note that the tempo manual say to add the -t flag in the command line
> but the example given on the same page don't include it.
>
>
> http://old.nabble.com/file/p26483590/tempo_tempoval.csd tempo_tempoval.csd
> http://old.nabble.com/file/p26483590/tempo-tempoval.wav tempo-tempoval.wav
>
> Best,
> René


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I believe I am the author iod the ipcode to read the tempo -- I think it
as requested as I never use that stuff.

the tempo opcode is ancient -- it is in v3.30 and does not look new there.
 I think it is Barry's original code.

==John

> Not sure. Who is the author of tempo and tempoval? If they are broken,
> they need to be fixed.
> I was not aware of this, because I don't use them, but if no one with
> more expertise offers to do it,
> I can take a look for the next release.
>
> A CSD with the errors and an idea of what you're supposed to be
> getting will also help.
>
> Victor
>
> On 24 Nov 2009, at 08:54, Rene Djack wrote:
>
>> Hi,
>> Thanks Jacob.
>>
>> I am not an expert in csound, neither in software and neither in
>> English language !!
>> But i like to play with this wonderful csound.
>>
>> Before sending a message to the list i test and retest and i ask
>> myself a lot of questions:
>>
>> Is it Linux?
>> Is it Ubuntu?
>> Is it csound csv last release?
>> Is it my compilation? scons version, python version......etc
>> Is it the csd?
>>
>> IS IT ME???
>>
>> and after i post to the list to know if others have the same problem
>> as me.
>>
>> For tempo and tempoval opcodes,
>> I found in the manual for -t or --tempo flag the line: WARNING: this
>> mode of operation is experimental and may be unreliable.
>>
>> I think this line should be also included in the tempo and tempoval
>> opcodes manual pages.
>>
>> And why to keep unreliable opcode(s) and flag(s) in csound?
>>
>> Best,
>> René
>>
>>
>>
>>
>>
>> 2009/11/24 Jacob Joaquin 
>> I ran your csd on os x, and also got zeros. In my experience, the
>> tempo opcodes don't really work all that well. I wrote some test
>> scripts back in the day, and the results led me to believe that there
>> are a lot of bugs with tempo and tempoval. It is possible that some of
>> these issues have been addressed, as this was a couple of years ago.
>>
>> Best,
>> Jake
>> --
>> The Csound Blog - http://csound.noisepages.com/
>>
>>
>>
>> On Mon, Nov 23, 2009 at 10:36 AM, Djack  wrote:
>> >
>> > Hi list,
>> >
>> > I can't get these  two opcodes working on my system (cvs csound on
>> Ubuntu
>> > 9.10)
>> >
>> > I include a short csd and its render wav to show that.
>> >
>> > tempoval gives always zero for kval
>> > and i can't understand why the output wav is like that (2 notes
>> overlaps)
>> >
>> > Please note that the tempo manual say to add the -t flag in the
>> command line
>> > but the example given on the same page don't include it.
>> >
>> >
>> > http://old.nabble.com/file/p26483590/tempo_tempoval.csd
>> tempo_tempoval.csd
>> > http://old.nabble.com/file/p26483590/tempo-tempoval.wav tempo-
>> tempoval.wav
>> >
>> > Best,
>> > René
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> "unsubscribe csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Once features are in csound we are obliged to keep them in case people have made pieces with them.

Mkg

On Nov 24, 2009 3:54 AM, "Rene Djack" <rene.djack@gmail.com> wrote:

Hi,
Thanks Jacob.

I am not an expert in csound, neither in software and neither in English language !!
But i like to play with this wonderful csound.

Before sending a message to the list i test and retest and i ask myself a lot of questions:

Is it Linux?
Is it Ubuntu?
Is it csound csv last release?
Is it my compilation? scons version, python version......etc
Is it the csd?

IS IT ME???

and after i post to the list to know if others have the same problem as me.

For tempo and tempoval opcodes,
I found in the manual for -t or --tempo flag the line: WARNING: this mode of operation is experimental and may be unreliable.

I think this line should be also included in the tempo and tempoval opcodes manual pages.

And why to keep unreliable opcode(s) and flag(s) in csound?

Best,
René

2009/11/24 Jacob Joaquin <jacobjoaquin@gmail.com>

> > I ran your csd on os x, and also got zeros. In my experience, the > tempo opcodes don't really ...