Hi,

What's new in version 5.08?

Cheers,
Andrés



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://

Command line and Top level changes:
        Added --csd-line-nums= option.
        Major changes to score error reporting; now accurately reports
                the line numbers for the chain of inputs for most errors. 
        Change to gettext localisation; French and Columbian-Spanish
                translations available.
        Messages about loading opcode plugins modified so can be suppressed
        New "no-carry" operator (!) for score language that prevents
                implicit carrying of p-fields in i-statements. 
        Added --check-syntax-only commandline flag (exclusive with
                --i-only)
        
Bug fixes:
        pan2: Corrected so it agrees with documentation

new opcodes etc:
        image opcodes
        pvsbandp and pvsbandr: filters using spectral domain
        New opcodes powershape, polynomial, chebyshevpoly, pdclip,
                pdhalf, pdhalfy, and syncphasor. 

A number of internal changes

	gettext version
        pvsscale: Improved algorithm for SDFT case so no ampltitude variation


==John ffitch

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Andres,

If everybody agree - and since you're updating the manual for the new 
version - I would like to see a notice in the pages about the 'm' and 
'n' score statements, which says that, at the moment, they're broken.

BTW, I know that fewer and fewer are making music writing plain old 
score by hand, but I would love to see them fixed. I, for one, would 
like to use these statements every now and then to test new ideas.

Best,

-c.

Andres Cabrera wrote:
> Hi,
>
> What's new in version 5.08?
>
> Cheers,
> Andrés
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>   


-- 
www.cesaremarilungo.com 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound

Cesare,

I have added "try to fix m and n" to my list of things to do for Csound
5.09.  In the meantime, you might be interested to know that the { and }
score statements for creating loops without starting a new section have been
fixed.  (This may be the first time that they have worked in Canonical
Csound -- Gab originally added them to CsoundAV).  Macros are of course a
good substitute for m and n too.

I will be adding some documentation to the manual for these statements
before the beta is released.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

Cesare Marilungo wrote on 1/29/08 6:12 AM:

> If everybody agree - and since you're updating the manual for the new
> version - I would like to see a notice in the pages about the 'm' and
> 'n' score statements, which says that, at the moment, they're broken.
> 
> BTW, I know that fewer and fewer are making music writing plain old
> score by hand, but I would love to see them fixed. I, for one, would
> like to use these statements every now and then to test new ideas.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Note the new flag for syntax checking is --syntax-check-only, not
--check-syntax-only.  I got it wrong in the ChangeLog, but it should be
correct everywhere else.

I would also add...

Improvements:
 is accepted as an alternative to 
Line numbers of errors in CSDs are now reported using the CSD line numbers
  instead of the temporary ORC and SCO line numbers *unless* the
  --csd-line-nums=0 option is given.

Bug fixes:
 works again according to the manual.
Fixed the { and } score looping statements.

Manual changes:
The following long-existing, but undocumented features have been documented:
  { and } score statements
  ~, &, |, and # operators in score expressions
   tag for CSDs

----------------------------
(I have not finished adding all of these changes to the manual but I hope to
get that done today and tomorrow ...)

Anthony

Oeyvind Brandtsegg wrote on 1/29/08 3:35 AM:

> Manual changes:
> Updated examples for partikkel
> 
> Oeyvind
> 
> 2008/1/29, jpff :
>> Command line and Top level changes:
>> Added --csd-line-nums= option.
>> Major changes to score error reporting; now accurately reports
>> the line numbers for the chain of inputs for most errors.
>> Change to gettext localisation; French and Columbian-Spanish
>> translations available.
>> Messages about loading opcode plugins modified so can be suppressed
>> New "no-carry" operator (!) for score language that prevents
>> implicit carrying of p-fields in i-statements.
>> Added --check-syntax-only commandline flag (exclusive with
>> --i-only)
>> 
>> Bug fixes:
>> pan2: Corrected so it agrees with documentation
>> 
>> new opcodes etc:
>> image opcodes
>> pvsbandp and pvsbandr: filters using spectral domain
>> New opcodes powershape, polynomial, chebyshevpoly, pdclip,
>> pdhalf, pdhalfy, and syncphasor.
>> 
>> A number of internal changes
>> 
>> gettext version
>> pvsscale: Improved algorithm for SDFT case so no ampltitude variation


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net