Manual examples

[francibal]

Dear all,
i'm trying all the examples of the manual. Can be useful for You if i will make a report (as possible for me) of not working examples? I would like to be helpful for You, but i have not ability! I'm not a programmer, i'm not an expert in csound ... I have only some free time.
If i can be useful let me know, if not, don't worry, i'll be always here to ask You for some help.

Always thanks for Your time, work and help,

Your black beast
fran.

[jpff-2]

>
> Dear all,
> i'm trying all the examples of the manual. Can be useful for You if i will
> make a report (as possible for me) of not working examples? I would like
> to
> be helpful for You, but i have not ability! I'm not a programmer, i'm not
> an
> expert in csound ... I have only some free time.
> If i can be useful let me know, if not, don't worry, i'll be always here
> to
> ask You for some help.
>

Sure; all examples worked at one time byut things drift.  Knowing of ANY
problems in the manual or the system is good; which is not a promise to
fix everything....  but we do try to fix stuff whenever it turns up.

==John ff





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

[csounder]

It will be very useful to have a beginner run and test all the manuals  
examples and make suggestions.

Thanks for offering to do this Fran.

Keep us posted.

-dr.B.


On Jul 4, 2009, at 7:59 AM, francibal wrote:

>
> Dear all,
> i'm trying all the examples of the manual. Can be useful for You if  
> i will
> make a report (as possible for me) of not working examples? I would  
> like to
> be helpful for You, but i have not ability! I'm not a programmer,  
> i'm not an
> expert in csound ... I have only some free time.
> If i can be useful let me know, if not, don't worry, i'll be always  
> here to
> ask You for some help.
>
> Always thanks for Your time, work and help,
>
> Your black beast
> fran.
> --
> View this message in context: http://www.nabble.com/Manual-examples-tp24333983p24333983.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body  
> "unsubscribe csound"

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

[Jacob Joaquin]

Not sure if this has already been done or not.  Perhaps we should consider writing test-cases for each example in the manual, and use a script to run all the tests prior to the release of a new version of Csound.  This would help smooth things out for beginners, as they are less likely to run into buggy examples. This might even help catch bigs introduced into Csound during the development process.

I might have time to do this myself sometime in the next few months.  If anyone is interested in starting a dialog about how to tackle this, no better time than the present.

Best,
Jake

jpff-2 wrote:

>
> Dear all,
> i'm trying all the examples of the manual. Can be useful for You if i will
> make a report (as possible for me) of not working examples? I would like
> to
> be helpful for You, but i have not ability! I'm not a programmer, i'm not
> an
> expert in csound ... I have only some free time.
> If i can be useful let me know, if not, don't worry, i'll be always here
> to
> ask You for some help.
>

Sure; all examples worked at one time byut things drift.  Knowing of ANY
problems in the manual or the system is good; which is not a promise to
fix everything....  but we do try to fix stuff whenever it turns up.

==John ff





Send bugs reports to this list.
To unsubscribe, send email [e-mail] with body "unsubscribe csound"

[Mark Van Peteghem-2]

I'm a firm proponent of automated tests, so I can only agree. Perhaps
you could have a wavefile for every example (rendered with one version
of CSound), and write automated tests that check whether it is almost
the same for the double and float versions, and for different values of
kr and sr. Although some opcodes give drastic differences by design.

Jacob Joaquin wrote:

> Not sure if this has already been done or not.  Perhaps we should consider
> writing test-cases for each example in the manual, and use a script to run
> all the tests prior to the release of a new version of Csound.  This would
> help smooth things out for beginners, as they are less likely to run into
> buggy examples. This might even help catch bigs introduced into Csound
> during the development process.
>
> I might have time to do this myself sometime in the next few months.  If
> anyone is interested in starting a dialog about how to tackle this, no
> better time than the present.
>
> Best,
> Jake
>
>
>
> jpff-2 wrote:
>  
>>> Dear all,
>>> i'm trying all the examples of the manual. Can be useful for You if i
>>> will
>>> make a report (as possible for me) of not working examples? I would like
>>> to
>>> be helpful for You, but i have not ability! I'm not a programmer, i'm not
>>> an
>>> expert in csound ... I have only some free time.
>>> If i can be useful let me know, if not, don't worry, i'll be always here
>>> to
>>> ask You for some help.
>>>
>>>      
>> Sure; all examples worked at one time byut things drift.  Knowing of ANY
>> problems in the manual or the system is good; which is not a promise to
>> fix everything....  but we do try to fix stuff whenever it turns up.
>>
>> ==John ff
>>
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>>
>>    
>
>  

--
  Mark
  _________________________________________
  When you get lemons, you make lemonade.
  When you get hardware, you make software.



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

[jpff-2]

> I'm a firm proponent of automated tests, so I can only agree. Perhaps
> you could have a wavefile for every example (rendered with one version
> of CSound), and write automated tests that check whether it is almost
> the same for the double and float versions, and for different values of
> kr and sr. Although some opcodes give drastic differences by design.
>

There is of course the tests directory and the script that runs them and
compares the md5 signature of the binary audio files.  This is not perfect
and as far as I am aware I am the only one that uses it.  It is not
comprehensive but does catch stuff.  Could do with someone looking over it
and extending it.

On the other hand, if it renders "Trapped..." then it is clearly working.....

==John ff



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

[francibal]

Ciao,
i make this test manually, using CsoundGUI, WinXound and console, because is the only way i'm able to do it. Today i've tried ALL examples and now i'm repeating the test writings some helpful (i hope) notes. Tomorrow i will do a first report (I feel like a buisnessman!).
First note: in CsoundGUI do not work ctr-c, ctr-v that was ok in 5.09, and often crashing.

thanks and ciao,

fran.

[francibal]

and ...
this is really strange (at least to me). I've try the 4 examples of butter filter (bp, br, hp, lp).
Are ok, but butterhp only with csoundgui! If i use console or Winxound i have this message - isfinit: cannot open dac -. Wow.

fran.

[francibal]

First instalment:

REPORT_01.txt

I'm using a notebook with Windows Vista, csound 5.10 double, and internal pc audio.
This is my basic setting, and, for now, i have not try midi opcode examples. Next step it will be testing that too with my external (cheap) audio-midi interface.

Hope helpful at least for someone,

ciao,

fran.

[jpff-2]

>
> First instalment:
>
wgbrass

Is it all right? To me play really bad.

No; it only worls at 22050 sample rate and I do not know why. Have spend
way too many hours on thios opcode with no positive results

==John ff

(looking at th eothers)



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

[Mark Van Peteghem-2]

jpff@... wrote:

>> I'm a firm proponent of automated tests, so I can only agree. Perhaps
>> you could have a wavefile for every example (rendered with one version
>> of CSound), and write automated tests that check whether it is almost
>> the same for the double and float versions, and for different values of
>> kr and sr. Although some opcodes give drastic differences by design.
>>    
>
> There is of course the tests directory and the script that runs them and
> compares the md5 signature of the binary audio files.  This is not perfect
> and as far as I am aware I am the only one that uses it.  It is not
> comprehensive but does catch stuff.  Could do with someone looking over it
> and extending it.
>  

I suppose that an improvement in an opcode may change some bits, so I
guess using md5, which demands no change at all, it isn't perfect
indeed. If I had the time I would love to help, but alas I don't.

--
  Mark
  _________________________________________
  When you get lemons, you make lemonade.
  When you get hardware, you make software.



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

[francibal]

About butterhp.csd, there is wrong option -idac instead -iadc, then give an error message
isfinit: cannot open dac.

ciao,

fran.

[francibal]

also these have wrong -idac instead of -iadc :

BUTTERHP
EXPCURVE
LOGCURVE
GAINSLIDER

ciao,

fran.

francibal wrote:

About butterhp.csd, there is wrong option -idac instead -iadc, then give an error message
isfinit: cannot open dac.

ciao,

fran.

[menno]

This discussion along with the one: http://www.nabble.com/Interpolating-between-waveforms...-tt23407590.html#a23470672
, would it be a good idea to set up a page (a wiki?) where we could all dump problems found with the examples in the manual?
I personally do not know how to do this, but i am willing to report faulty examples (and help to get working ones if i can). Thing is, i believe, that at the moment these reports are too fragmented in this mailing list and tend to get lost. Even when someone is coming up with a good example in this mailing list  it does not seem to find its way in the manual and will get lost very easily. A special corner for this would help focus on the problem and obtain in the near future a manual with simple, working examples. Also it should help to understand why an opcode was invented anyway!? This would help to reveal the unique character of this opcode.

Menno

csounder wrote:

It will be very useful to have a beginner run and test all the manuals  
examples and make suggestions.

Thanks for offering to do this Fran.

Keep us posted.

-dr.B.


On Jul 4, 2009, at 7:59 AM, francibal wrote:

>
> Dear all,
> i'm trying all the examples of the manual. Can be useful for You if  
> i will
> make a report (as possible for me) of not working examples? I would  
> like to
> be helpful for You, but i have not ability! I'm not a programmer,  
> i'm not an
> expert in csound ... I have only some free time.
> If i can be useful let me know, if not, don't worry, i'll be always  
> here to
> ask You for some help.
>
> Always thanks for Your time, work and help,
>
> Your black beast
> fran.
> --
> View this message in context: http://www.nabble.com/Manual-examples-tp24333983p24333983.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email [e-mail] with body  
> "unsubscribe csound"



Send bugs reports to this list.
To unsubscribe, send email [e-mail] with body "unsubscribe csound"

[francibal]

Ciao all,
one more micro step: tempo.csd and tempoval.csd examples needs -t.. in options, and i have added that, but tempoval print only 0.0 value. Can Someone tell me what's wrong ?

many thanks,
ciao,
fran.

[francibal]

Dear Mr Andrés (and all others),
only for report: examples tablewa.csd and tablewk.csd are inverted, also in manual pages, and, anyway, are wrong.
vtablewa (i.e. real vtablewk), when corrected audio file (.wav, in my folder, and not .aiff), it work BUT with horrible audio.
vtablewk (i.e. real vtablewa), is missing part of code (or it seems so to me).

Again, i'm not expert but are all theese table opcodes really necessary?

Hope a little more help for Your work.
Ciao,
fran

[francibal]

Hi All,

only another little report on opcodes.

loopseg and lpshold cannot take time0 parameter of type k (as in manual), but only of type i.
I think it's obvious, but ...

Hope not annoy
(so fussy)

ciao,
fran

[Andres Cabrera]

Hi francibal,

It's been a while, but I finally had a look at your report, thanks.
These reports are very useful, as it takes a lot of time to revise
each example. See below for all comments.
If you want, next time send the corrected files, which makes it quicker to fix.

Cheers,
Andrés




I'm using a notebook with Windows Vista, csound 5.10 double, and
internal audio of pc.

CsoundGui often crashes, especially when csd had diskin opcode.


Yes... Csound5Gui is no longer maintained, and the diskin opcode
crashes, use the diskin2 opcode instead


Here is my first report (not yet complete):


adsyn bad audio output, and amplitude exaggerated.



The output amp for me is (using 0dbfs= 1):
end of score.   overall amps:  0.41790



bformenc deprecated, use bformenc1. But ...


Added comment


bformenc1

error:  too many input args, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
error:  input arg 'kord2' of type k not allowed when expecting i, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
error:  input arg 'kord1' of type k not allowed when expecting i, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
error:  input arg 'kord0' of type k not allowed when expecting i, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
4 syntax errors in orchestra.  compilation invalid


Fixed.


biquad-2

error:  input arg 'irpole12' used before defined, line 51:
    irpole2 = irpole12
error:  input arg 'irpole13' used before defined, line 52:
    irpole3 = irpole13
error:  input arg 'irpole14' used before defined, line 53:
    irpole4 = irpole14
error:  input arg 'irpole15' used before defined, line 54:
    irpole5 = irpole15
error:  input arg 'irpole16' used before defined, line 55:
    irpole6 = irpole16
5 syntax errors in orchestra.  compilation invalid


Fixed.


checkbox

error:  no legal opcode, line 25:
  k1 checkbox 1
error:  input arg 'k1' used before defined, line 28:
  k2 = (k1 == 0 ? 440 : 880)
2 syntax errors in orchestra.  compilation invalid


checkbox is not available on the standard windows distribution. That's
why it shows "no legal opcode". You can use fltk widgets or a frontend
like QuteCsound or Blue for this.



cross2

It seems not working. But is ahh.aiff file like a single tick ?


Fixed


diskin

Csound tidy up: Segmentation violation. Change kpitch parameter to +1,
instead -1, and work, but same message.


Have marked diskin as deprecated and recommended usage of diskin2


expcurve

Imported csd with bad tag. </CsOptions> is not in right place, missing
new line char.
Moreover don't work if command line had RT parameters (-odac, -idac).


Improved the example.


flashtxt

error:  no legal opcode, line 24:
  flashtxt 1, "Instr 1 live"


Same problem as checkbox


FLbutton

Instable. It crashes with rew/fwd button.



Does work for me on Linux properly, but FLTK widgets have threading
issues when using the API, so they're not recommended if you are using
a front end.


FLpanel-sensekey, FLpanel-sensekey2

Don't print the value.

You're right they're not working, but this is a problem with Csound,
not the manual.




FLslidBnk2Setk

Csd had white line after "\" that get error in reading opcode
parameters. (Sorry i can say in a better language, i hope it is clear
anyway).

gainslider

There is not "soundin.aiff" in directory, and there are some others errors ...


Fixed.


hrtfmove, hrtfmove2, hrtfstat

Data files (hrtf.dat) are in a different directory. When indicated
right path they work well.


The path is platform dependent, so it can't be hardcoded. What's the
path for Windows?



hvs1, hvs2

Same of FLslidBnk2Setk, white line into opcode.


I don't understand what you mean...



imageopcodes, imageopcodesdemo2

Can't load .png files, but i believe that is a my system problem.


I've added a note. The image opcodes can only load png images.



logcurve

Same of expcurve, wrong imported csd.


Fixed and improved


mute

Accept only strings as argument. It seems that it works only with
named instrument. Changing instr 2 with any name it works.


I've improved the example, but the opcode is working properly.



nestedap

Only in console mode.


What do you mean? It's working fine here.



polynomial

Only it works without RT parameters in command line.


Yes, that's the way it's set up.



poscil3-file

It miss last parameters in ftgen opcode. Putting this (0) it works.


It's working here. What do you mean?



tbvcf

Amplitude vs. infinity �  It needs some adjustments.



Fixed.



vtablewa

It use �beats.aiff�, but there is only �beats.wav�. Correcting this resolve.


Fixed


vtablewk


examples were switched. fixed.


vcopy
error:  insufficient required arguments, line 22:
vtablewa ar

vtablewa is a very strange opcode. I need to have a look at this...




wgbrass

Is it all right? To me play really bad.


Now it's better (not great, but better...)


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

[francibal]

Dear Mr. Andrés,
many thanks. I know that actually You (and others developers) are really busy for next release, then again thanks for Your work.
My report is old, because You had corrected many examples near a months ago, and i sent You my csds with micro corrections (if You not remember that don't worry, You are only aged!). Anyway i'm really happy if my micro work helped just a little bit.

For who like me use pre-build distributions, all these improved examples will be available for next release. But i looked at cvs ... (impatient waiting next release)

ciao,
fran.

Only next 3 are notable

htrfmove :

"C:\Program Files\csoundBase\samples\hrtf-44100-left.dat"
normally on windows the path is "C:\Program Files\csound\samples\hrtf-44100-left.dat"
Also in new release by Mr. Gogins.

cross2 :

comment lines say - use beats.wav - but it uses fox.wav

mute :

there is a problem in opcodes that accept only string argument. Seems it was correct by Mr. Ffitch, and then in next release it will be ok.


Remains are now corrected, and then only for record.

adsyn :

Corrected. Before it had wrong output arguments.

FLbutton :

The problem was diskin, now it uses diskin2 and it's all ok.

FLslidBnk2Setk, hvs1, hvs2 :

Corrected. Problem was that there was a blank line after the \ in opcode line, then, i think, it was a parsing error.

nestedap :

Corrected. It was diskin problem, now it uses diskin2.

polynomial :

Corrected. It was sr = 10 that reported errors, also if is not important. Now with sr = 44100 it works ok.

poscil3-file :

Corrected.

Andres Cabrera wrote:

Hi francibal,

It's been a while, but I finally had a look at your report, thanks.
These reports are very useful, as it takes a lot of time to revise
each example. See below for all comments.
If you want, next time send the corrected files, which makes it quicker to fix.

Cheers,
Andrés




I'm using a notebook with Windows Vista, csound 5.10 double, and
internal audio of pc.

CsoundGui often crashes, especially when csd had diskin opcode.


Yes... Csound5Gui is no longer maintained, and the diskin opcode
crashes, use the diskin2 opcode instead


Here is my first report (not yet complete):


adsyn bad audio output, and amplitude exaggerated.



The output amp for me is (using 0dbfs= 1):
end of score.   overall amps:  0.41790



bformenc deprecated, use bformenc1. But ...


Added comment


bformenc1

error:  too many input args, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
error:  input arg 'kord2' of type k not allowed when expecting i, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
error:  input arg 'kord1' of type k not allowed when expecting i, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
error:  input arg 'kord0' of type k not allowed when expecting i, line 35:
        aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
kbeta, kord0, kord1, kord2
4 syntax errors in orchestra.  compilation invalid


Fixed.


biquad-2

error:  input arg 'irpole12' used before defined, line 51:
    irpole2 = irpole12
error:  input arg 'irpole13' used before defined, line 52:
    irpole3 = irpole13
error:  input arg 'irpole14' used before defined, line 53:
    irpole4 = irpole14
error:  input arg 'irpole15' used before defined, line 54:
    irpole5 = irpole15
error:  input arg 'irpole16' used before defined, line 55:
    irpole6 = irpole16
5 syntax errors in orchestra.  compilation invalid


Fixed.


checkbox

error:  no legal opcode, line 25:
  k1 checkbox 1
error:  input arg 'k1' used before defined, line 28:
  k2 = (k1 == 0 ? 440 : 880)
2 syntax errors in orchestra.  compilation invalid


checkbox is not available on the standard windows distribution. That's
why it shows "no legal opcode". You can use fltk widgets or a frontend
like QuteCsound or Blue for this.



cross2

It seems not working. But is ahh.aiff file like a single tick ?


Fixed


diskin

Csound tidy up: Segmentation violation. Change kpitch parameter to +1,
instead -1, and work, but same message.


Have marked diskin as deprecated and recommended usage of diskin2


expcurve

Imported csd with bad tag. </CsOptions> is not in right place, missing
new line char.
Moreover don't work if command line had RT parameters (-odac, -idac).


Improved the example.


flashtxt

error:  no legal opcode, line 24:
  flashtxt 1, "Instr 1 live"


Same problem as checkbox


FLbutton

Instable. It crashes with rew/fwd button.



Does work for me on Linux properly, but FLTK widgets have threading
issues when using the API, so they're not recommended if you are using
a front end.


FLpanel-sensekey, FLpanel-sensekey2

Don't print the value.

You're right they're not working, but this is a problem with Csound,
not the manual.




FLslidBnk2Setk

Csd had white line after "\" that get error in reading opcode
parameters. (Sorry i can say in a better language, i hope it is clear
anyway).

gainslider

There is not "soundin.aiff" in directory, and there are some others errors ...


Fixed.


hrtfmove, hrtfmove2, hrtfstat

Data files (hrtf.dat) are in a different directory. When indicated
right path they work well.


The path is platform dependent, so it can't be hardcoded. What's the
path for Windows?



hvs1, hvs2

Same of FLslidBnk2Setk, white line into opcode.


I don't understand what you mean...



imageopcodes, imageopcodesdemo2

Can't load .png files, but i believe that is a my system problem.


I've added a note. The image opcodes can only load png images.



logcurve

Same of expcurve, wrong imported csd.


Fixed and improved


mute

Accept only strings as argument. It seems that it works only with
named instrument. Changing instr 2 with any name it works.


I've improved the example, but the opcode is working properly.



nestedap

Only in console mode.


What do you mean? It's working fine here.



polynomial

Only it works without RT parameters in command line.


Yes, that's the way it's set up.



poscil3-file

It miss last parameters in ftgen opcode. Putting this (0) it works.


It's working here. What do you mean?



tbvcf

Amplitude vs. infinity �  It needs some adjustments.



Fixed.



vtablewa

It use �beats.aiff�, but there is only �beats.wav�. Correcting this resolve.


Fixed


vtablewk


examples were switched. fixed.


vcopy
error:  insufficient required arguments, line 22:
vtablewa ar

vtablewa is a very strange opcode. I need to have a look at this...




wgbrass

Is it all right? To me play really bad.


Now it's better (not great, but better...)


Send bugs reports to this list.
To unsubscribe, send email [e-mail] with body "unsubscribe csound"

[Andres Cabrera]

Hi fran,


Thanks, I've now fixed according to your suggestions. They are small
issues, but do give a nice polish to the manual.

On Sun, Aug 16, 2009 at 7:59 AM, francibal<ilterzouomo@...> wrote:
>
> Dear Mr. Andrés,
> many thanks. I know that actually You (and others developers) are really
> busy for next release, then again thanks for Your work.

Not only on the next release =)

> My report is old, because You had corrected many examples near a months ago,
> and i sent You my csds with micro corrections (if You not remember that
> don't worry, You are only aged!). Anyway i'm really happy if my micro work
> helped just a little bit.
>
> For who like me use pre-build distributions, all these improved examples
> will be available for next release. But i looked at cvs ... (impatient
> waiting next release)
>
> ciao,
> fran.
>
> Only next 3 are notable
>
> htrfmove :
>
> "C:\Program Files\csoundBase\samples\hrtf-44100-left.dat"
> normally on windows the path is "C:\Program
> Files\csound\samples\hrtf-44100-left.dat"
> Also in new release by Mr. Gogins.
>

Done.

> cross2 :
>
> comment lines say - use beats.wav - but it uses fox.wav
>

Done.

> mute :
>
> there is a problem in opcodes that accept only string argument. Seems it was
> correct by Mr. Ffitch, and then in next release it will be ok.
>

Yes, it's working here from csound cvs, so I supposed it's been fixed.


Cheers,
Andrés

>
> Remains are now corrected, and then only for record.
>
> adsyn :
>
> Corrected. Before it had wrong output arguments.
>
> FLbutton :
>
> The problem was diskin, now it uses diskin2 and it's all ok.
>
> FLslidBnk2Setk, hvs1, hvs2 :
>
> Corrected. Problem was that there was a blank line after the \ in opcode
> line, then, i think, it was a parsing error.
>
> nestedap :
>
> Corrected. It was diskin problem, now it uses diskin2.
>
> polynomial :
>
> Corrected. It was sr = 10 that reported errors, also if is not important.
> Now with sr = 44100 it works ok.
>
> poscil3-file :
>
> Corrected.
>
>
>
>
> Andres Cabrera wrote:
>>
>> Hi francibal,
>>
>> It's been a while, but I finally had a look at your report, thanks.
>> These reports are very useful, as it takes a lot of time to revise
>> each example. See below for all comments.
>> If you want, next time send the corrected files, which makes it quicker to
>> fix.
>>
>> Cheers,
>> Andrés
>>
>>
>>
>>
>> I'm using a notebook with Windows Vista, csound 5.10 double, and
>> internal audio of pc.
>>
>> CsoundGui often crashes, especially when csd had diskin opcode.
>>
>>
>> Yes... Csound5Gui is no longer maintained, and the diskin opcode
>> crashes, use the diskin2 opcode instead
>>
>>
>> Here is my first report (not yet complete):
>>
>>
>> adsyn                 bad audio output, and amplitude exaggerated.
>>
>>
>>
>> The output amp for me is (using 0dbfs= 1):
>> end of score.            overall amps:  0.41790
>>
>>
>>
>> bformenc              deprecated, use bformenc1. But ...
>>
>>
>> Added comment
>>
>>
>> bformenc1
>>
>> error:  too many input args, line 35:
>>         aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
>> kbeta, kord0, kord1, kord2
>> error:  input arg 'kord2' of type k not allowed when expecting i, line 35:
>>         aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
>> kbeta, kord0, kord1, kord2
>> error:  input arg 'kord1' of type k not allowed when expecting i, line 35:
>>         aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
>> kbeta, kord0, kord1, kord2
>> error:  input arg 'kord0' of type k not allowed when expecting i, line 35:
>>         aw, ax, ay, az, ar, as, at, au, av bformenc1 anoise, kalpha,
>> kbeta, kord0, kord1, kord2
>> 4 syntax errors in orchestra.  compilation invalid
>>
>>
>> Fixed.
>>
>>
>> biquad-2
>>
>> error:  input arg 'irpole12' used before defined, line 51:
>>     irpole2 = irpole12
>> error:  input arg 'irpole13' used before defined, line 52:
>>     irpole3 = irpole13
>> error:  input arg 'irpole14' used before defined, line 53:
>>     irpole4 = irpole14
>> error:  input arg 'irpole15' used before defined, line 54:
>>     irpole5 = irpole15
>> error:  input arg 'irpole16' used before defined, line 55:
>>     irpole6 = irpole16
>> 5 syntax errors in orchestra.  compilation invalid
>>
>>
>> Fixed.
>>
>>
>> checkbox
>>
>> error:  no legal opcode, line 25:
>>   k1 checkbox 1
>> error:  input arg 'k1' used before defined, line 28:
>>   k2 = (k1 == 0 ? 440 : 880)
>> 2 syntax errors in orchestra.  compilation invalid
>>
>>
>> checkbox is not available on the standard windows distribution. That's
>> why it shows "no legal opcode". You can use fltk widgets or a frontend
>> like QuteCsound or Blue for this.
>>
>>
>>
>> cross2
>>
>> It seems not working. But is ahh.aiff file like a single tick ?
>>
>>
>> Fixed
>>
>>
>> diskin
>>
>> Csound tidy up: Segmentation violation. Change kpitch parameter to +1,
>> instead -1, and work, but same message.
>>
>>
>> Have marked diskin as deprecated and recommended usage of diskin2
>>
>>
>> expcurve
>>
>> Imported csd with bad tag. </CsOptions> is not in right place, missing
>> new line char.
>> Moreover don't work if command line had RT parameters (-odac, -idac).
>>
>>
>> Improved the example.
>>
>>
>> flashtxt
>>
>> error:  no legal opcode, line 24:
>>   flashtxt 1, "Instr 1 live"
>>
>>
>> Same problem as checkbox
>>
>>
>> FLbutton
>>
>> Instable. It crashes with rew/fwd button.
>>
>>
>>
>> Does work for me on Linux properly, but FLTK widgets have threading
>> issues when using the API, so they're not recommended if you are using
>> a front end.
>>
>>
>> FLpanel-sensekey, FLpanel-sensekey2
>>
>> Don't print the value.
>>
>> You're right they're not working, but this is a problem with Csound,
>> not the manual.
>>
>>
>>
>>
>> FLslidBnk2Setk
>>
>> Csd had white line after "\" that get error in reading opcode
>> parameters. (Sorry i can say in a better language, i hope it is clear
>> anyway).
>>
>> gainslider
>>
>> There is not "soundin.aiff" in directory, and there are some others errors
>> ...
>>
>>
>> Fixed.
>>
>>
>> hrtfmove, hrtfmove2, hrtfstat
>>
>> Data files (hrtf.dat) are in a different directory. When indicated
>> right path they work well.
>>
>>
>> The path is platform dependent, so it can't be hardcoded. What's the
>> path for Windows?
>>
>>
>>
>> hvs1, hvs2
>>
>> Same of FLslidBnk2Setk, white line into opcode.
>>
>>
>> I don't understand what you mean...
>>
>>
>>
>> imageopcodes, imageopcodesdemo2
>>
>> Can't load .png files, but i believe that is a my system problem.
>>
>>
>> I've added a note. The image opcodes can only load png images.
>>
>>
>>
>> logcurve
>>
>> Same of expcurve, wrong imported csd.
>>
>>
>> Fixed and improved
>>
>>
>> mute
>>
>> Accept only strings as argument. It seems that it works only with
>> named instrument. Changing instr 2 with any name it works.
>>
>>
>> I've improved the example, but the opcode is working properly.
>>
>>
>>
>> nestedap
>>
>> Only in console mode.
>>
>>
>> What do you mean? It's working fine here.
>>
>>
>>
>> polynomial
>>
>> Only it works without RT parameters in command line.
>>
>>
>> Yes, that's the way it's set up.
>>
>>
>>
>> poscil3-file
>>
>> It miss last parameters in ftgen opcode. Putting this (0) it works.
>>
>>
>> It's working here. What do you mean?
>>
>>
>>
>> tbvcf
>>
>> Amplitude vs. infinity �  It needs some adjustments.
>>
>>
>>
>> Fixed.
>>
>>
>>
>> vtablewa
>>
>> It use �beats.aiff�, but there is only �beats.wav�. Correcting this
>> resolve.
>>
>>
>> Fixed
>>
>>
>> vtablewk
>>
>>
>> examples were switched. fixed.
>>
>>
>> vcopy
>> error:  insufficient required arguments, line 22:
>> vtablewa ar
>>
>> vtablewa is a very strange opcode. I need to have a look at this...
>>
>>
>>
>>
>> wgbrass
>>
>> Is it all right? To me play really bad.
>>
>>
>> Now it's better (not great, but better...)
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>
> --
> View this message in context: http://www.nabble.com/Manual-examples-tp24333983p24993272.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

--


Andrés


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