...and has replaced the beta that was there

==John ff

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 --syntax-check-only commandline flag (exclusive with
                --i-only)
         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:
        pan2: Corrected so it agrees with documentation
        hilbert had its outputs reversed, now correct.
         works again according to the manual.
        Fixes in the { and } score looping statements.

new opcodes etc:
        image opcodes
        pvsbandp and pvsbandr: filters using spectral domain
        New opcodes powershape, polynomial, chebyshevpoly, pdclip,
                pdhalf, pdhalfy, and syncphasor. 
        New HRTF opcodes by Brian Carty: hrtfmove, hrtfmove2 and
                hrtfstat 
        jackTransport opcodes to control Jack from Csound

A number of internal changes

	gettext version
        pvsscale: Improved algorithm for SDFT case so no ampltitude variation
        partikkel: Internal changes to partikkel, interpolation of waveform 
                   read and windowing, allowing more precise pitch synchronous
                   granular synthesis. 

**end**

Ug(ur Güney wrote:
.. Altough the -m0 flag in the .csoundrc file blocks the
> warning messages printed in the command line, this warning dialogs (I
> attached a screenshot) keeps coming again and again (two of them)
> until I remove the csnd.dll and py.dll. 


This is a standard dialog put up by Windows, not Csound. Equally it 
means that so long as the named dll is on the system PATH somewhere, all 
will be well.

Richard Dobson

Installing this (the d version) on Windows Vista Business (32) results 
(after a few minutes) in the appearance of a notification balloon, 
stating that Windows has found a solution (say what???).

Clicking on the balloon results in the opening of a new window, the one 
that displays "solutions" to "problems". This time the "problem" is 
Csound itself, explaining that there is a "Program Compatibility Problem".

This is strange, because it happened with this installer for the first 
time - it did not happen with any of the installers for 5.07.

Thought that someone would like to know.

Panos


P.S. : It may be a good time to provide a reminder for how much i hate 
installers. Why (oh why) is there not a non-installer version for Csound 
anymore ?



jpff wrote:
> ...and has replaced the beta that was there
> 
> ==John ff
> 
> 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 --syntax-check-only commandline flag (exclusive with
>                 --i-only)
>          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:
>         pan2: Corrected so it agrees with documentation
>         hilbert had its outputs reversed, now correct.
>          works again according to the manual.
>         Fixes in the { and } score looping statements.
> 
> new opcodes etc:
>         image opcodes
>         pvsbandp and pvsbandr: filters using spectral domain
>         New opcodes powershape, polynomial, chebyshevpoly, pdclip,
>                 pdhalf, pdhalfy, and syncphasor. 
>         New HRTF opcodes by Brian Carty: hrtfmove, hrtfmove2 and
>                 hrtfstat 
>         jackTransport opcodes to control Jack from Csound
> 
> A number of internal changes
> 
> 	gettext version
>         pvsscale: Improved algorithm for SDFT case so no ampltitude variation
>         partikkel: Internal changes to partikkel, interpolation of waveform 
>                    read and windowing, allowing more precise pitch synchronous
>                    granular synthesis. 
> 
> **end**
> 
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I like both ideas.

- Dave

Steven Yi wrote:
> The python check has been so problematic, I'm wondering if we
> shouldn't change how the installer works to ask the user if they want
> to install the python opcodes with a note that Python is required.  If
> they say yes, install as usual, if no, copy them into a sub-folder
> which they can add to OPCODEDIR later if they want (also with a note
> about this shown during installer).  This places the installation
> burden on the user to decide what they want and makes them active in
> choosing.  They will basically get what they choose, rather than this
> situation where they get something completely unexpected.
> 
> As for .csoundrc, Anthony has mentioned that the Windows installer is
> the only installer of any OS that create a .csoundrc and that it
> defaults to values not shared by other csound distributables.  While
> we should definitely look into why things are awry with command
> processing order, it seems it would be prudent to default to
> installing a .csoundrc file that is completely commented out.  That
> way a user who may want to use it can find it later and have a
> template of what to do, but that keeps things set exactly as what is
> default for all the other platforms.
> 
> Thoughts on either proposal?
> 
> steven
> 
> 
> 
> 
> On Tue, Mar 18, 2008 at 1:00 AM, Uğur Güney  wrote:
>> # Hi,
>>  # I installed the new version. Thanks for your effort!
>>  # I want to report two things: 1) I am doubt about whether the "order
>>  of precedence" works correctly.
>>  http://www.csounds.com/manual/html/CommandTop.html#CommandOrder
>>  # I tested the -m0 commandline flag with some example files, but it
>>  did not work. All messages are printed. But when I changed the
>>  .csoundrc file then they are gone. This is why I think it is related
>>  to the command order thing.
>>  # And this is not true for -d flag or -b flag. Their assignment in the
>>  csoundrc file are overrided by the command line flags.
>>  # 2) Second issue is again about the warnings related to the missing
>>  python25.dll. Altough the -m0 flag in the .csoundrc file blocks the
>>  warning messages printed in the command line, this warning dialogs (I
>>  attached a screenshot) keeps coming again and again (two of them)
>>  until I remove the csnd.dll and py.dll. This was the problem I
>>  mentioned in my previous mail. But may be I have not well articulated
>>  myself.
>>  # For me warning messages in command line is not a big problem. But if
>>  have not used a python related opcode I will not expect a warning
>>  dialog/window pops up about them which stops the execution and wait
>>  for me to press enter.
>>  # Could the -m flag system adjusted to include these warning dialogs
>>  under Windows? Thanks!
>>  -ugur guney-
>>
>>  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"

My first two "full length" Csound works have been archived on the 
Sonus.ca web site. To listen, go to Sonus.ca and search for "mooney". 
The Csound pieces are at the end of the list, on the second screen: 
"A Little Noise Goes a Long Way," played last fall at Electronic 
Music Midwest, and "Olbum's Furniture," completed earlier this year. 
(The other works on Sonus were done with Kyma). Enjoy--

--David

David Mooney:  dmooney@city-net.com
Maxine Heller:  mheller@city-net.com
Opaque Melodies:  www.city-net.com/~moko/