Amazing work!
I compiled and ran the new version (creating a Csound score).
Messages on the console were perfect. The out.sco and NotReich.bpda look
good. Double-clicking "NotReich.bpda" even opened it in BP2.9.8 (with
just an expected garbage sign at the end) and it played it on the piano!
"Zero byte(s) leaked". My favourite message. :-)
Today I will adjust the PHP interface to the new syntax and share it.
I spent 3 days on the sound-object prototype (‘-mi’ file) editor. So
many parameters requiring to be checked one by one to avoid any
confusion. An error might take a while to be detected! In addition, the
interface must check the consistency of some combinations as the old
good BP2.9.8 was doing…
When time permits (no emergency) you might update BP2.9.8 to read at
least ‘-se’ and ‘-mi’ files with the Unix line endings. This would make
it possible to check changes via the sound output. Don’t bother about
the saving format that can remain MacOS Roman, since it is automatically
converted by the PHP interface.
Probably my next work on the interface will be the edition of ‘-cs’
Csound orchestra files.
We're moving forward nicely :-)
Bernard
Anthony Kozar wrote on 20/07/2020 20:49:
> Hello everyone,
>
> I've uploaded a new snapshot of my development folder to my website.
> Just download and unzip the file "bpconsole-2020-07-20.zip" from
>
> http://www.anthonykozar.net/files/BolProcessor/
>
> Inside the "bolprocessor" folder you will find (amongst other things):
>
> bp 64-bit console app built with the Makefile
> bp32 32-bit console app built with Xcode (has debug info)
> bp64 64-bit console app built with Xcode (has debug info)
>
> BP2-ANSI.xc82.xcodeproj current Xcode project file
>
> ctests/ folder full of test files and output files from tests
>
> source/BP2/ the folder containing all of the source for this version
>
> I haven't tested building this version yet under Linux or Windows. I
> expect it to build fine with the Makefile. On any platform (including
> MacOS), just try the command "make" from the "bolprocessor" folder to
> build.
>
> Changes in this version
> -----------------------
> • Makefile included
> • the action argument is now required on the command line; all actions
> listed in the command line help are recognized but only these actions
> work: compile, produce, produce-all, templates
> • the --csoundout option now works as advertised. It requires a file
> name for the output score or "-" to print to stdout.
> • a default f-table statement is now written into the score file.
> • --midiout now requires an argument but a Midi file is still not produced.
> • implemented -o option for writing produced items to a file
> • new option --seed [num] for setting the random number seed
> • new options --show-production and --trace-production
> • all messages are now directed to standard output by default instead of
> standard error
> • new options -e or --use-stderr redirect messages to standard error,
> allowing you to get just the "algorithmic output" on standard out
> • new option '--traceout [filename]' for routing compilation errors and
> trace outputs to a trace file
> • console output has been cleaned up a lot
> • can read input files with any line ending convention (please let me
> know if this doesn't always work)
> • changed the version number to "2.999..."
>
> The --traceout option is recommended right now for viewing compilation
> errors, the output of the "templates" action, or when --show-production
> & --trace-production are used. Currently, the output of all of these
> processes still contain carriage returns and will not display properly
> in a terminal. --traceout will route them to a file which you can then
> open in a text editor that is "CR-aware".
>
> Example command lines
> --------------------
>
> Here are some examples to try from the "ctests" folder (you can use
> "bp32" or "bp" instead of "bp64"):
>
> ../bp64 --version
> ../bp64 --help
>
> ../bp64 produce -gr.NotReich
> ../bp64 produce -gr.NotReich -o NotReich.bpda
> ../bp32 produce -gr.NotReich -d --csoundout -
> ../bp32 produce -gr.NotReich -d --csoundout out.sco
>
> ../bp64 templates -gr.checktemplates --traceout trace.txt
>
> // the next command will generate some compilation errors
> ../bp64 compile symbols.bpgr --traceout trace.txt
>
> // adding the alphabet file fixes them
> ../bp64 compile symbols.bpgr symbols.bpho --traceout trace.txt
> ../bp64 produce symbols.bpgr symbols.bpho
>
> // type this all on one line
> ../bp64 produce symbols.bpgr symbols.bpho -o out.txt --traceout
> trace.txt --show-production
>
> // type this all on one line
> ../bp64 produce symbols.bpgr symbols.bpho -o out.txt --traceout
> trace.txt --trace-production
>
> ../bp64 produce produce-all.bpgr
> ../bp64 produce-all produce-all.bpgr
> ../bp64 produce produce-all.bpgr -d --midiout out.mid
>
> // this command will also generate some compilation errors
> ../bp64 compile -gr.Nadaka --traceout Nadaka-errors.txt
>
> // adding the --indian option fixes them
> ../bp64 compile --indian -gr.Nadaka
> ../bp64 produce --indian -gr.Nadaka
> ../bp64 produce --indian -gr.Nadaka -d --rtmidi
>
>
> Updating to the latest code
> ---------------------------
>
> The "bolprocessor" folder contains a Git repository. Before you can
> download changes from Sourceforge you will need to reconfigure the
> remote settings because they are set up to use my username. You can do
> so with these commands:
>
> git remote remove origin
> git remote add -f origin git://git.code.sf.net/p/bolprocessor/git
> git branch --set-upstream-to=origin/ANSI-branch ANSI-branch
>
> After that, you can update to the latest code on Sourceforge anytime
> with just the command
>
> git pull
>
> If you have made changes to the source code, it is safer to do
>
> git fetch
>
> and examine any non-local changes first!
>
> --------
>
> I hope that this snapshot works for all of you. Inquire here on the
> developer list if you have problems.
>
> Anthony
>
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel
|