bolprocessor-devel — Bol Processor developer discussion list

Re: [bp-dev] A simple PHP environment to start with BP3

[Bernard B. <ber...@gm...>]

Dear Rainer,

If you really wish to try the original Bol Processor, then buy an Apple 
II… I might still have a floppy disk of the 6502 machine-code version. ;-)

Joke: it did not produce any sound!

I wouldn't recommend running the old BP2 under MacOS 9. When migrating 
to MacOS 10 — which took more than 3 months if my memory is correct — 
Anthony fixed a number of bugs. Today I have been running the last 
BP2.9.8 under MacOS 10.11.6 (El Capitan) which is almost bug-free. Once 
windows are pulled larger and spread over two screens, the old program 
becomes quite pleasant. The only very unpleasant aspect is that the 
editor does not recognize the mouse up/down scroll. I could enjoy again 
features that will take long to implement in the new environment… This 
leaves us an exciting agenda!

Another reason for running MacOS 10 is that you have access to "virtual" 
instruments activated by CoreMIDI whereas under MacOS you would need to 
hook an old physical instrument via an old MIDI interface.

Listening to all examples on piano is not very interesting. I started 
uploading MP3 files of examples designed to be played on "real instruments":

https://leti.lt/bolprocessor/

If you listen to "ShapesInRhythm" you will hear something utterly 
different than the piece on a single instrument. The Roland D50 synth 
produced unexpected Leslie effects due to the particular striking of 
"keys". The "Waves" example uses Harm Visser's synthesized saxophone; I 
liked the piano rendering as well. Piano pieces were recorded with PianoTeq.

I have just modified my PHP interface to automatically convert (to UTF8) 
and fix files encoded in MacOS Roman. So we can uses files 
simultaneously in both environments.

Bernard

Rainer Schütz wrote on 12/07/2020 23:10:
> Dear Bernard,
>
> I am - just for the fun of it - thinking of buying a “pre” intel Mac-Notebook… In order to get the “original” Bol Processor going, would I need Mac OS 9 or even older (?), or does it also run (fully) on the Powerbook G4 models with pre-intel OS X (like Tiger)? There are affordable ones on eBay (around 100$) with 1.67 GHz PowerPC 2GB ram and 80GB hdd - one could likely even fit in a ssd-stick with a cheap adaptor, which might make them rather fast with the original software.
>
> Best
> .r.
>
> PS: the 12 inch ones are little beauties, but they are comparatively pricey… And for BP it’s likely good to have some screen-estate, right?
>
>
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel

Re: [bp-dev] A simple PHP environment to start with BP3

[<rs...@ba...>]

Dear Bernard,

I am - just for the fun of it - thinking of buying a “pre” intel Mac-Notebook… In order to get the “original” Bol Processor going, would I need Mac OS 9 or even older (?), or does it also run (fully) on the Powerbook G4 models with pre-intel OS X (like Tiger)? There are affordable ones on eBay (around 100$) with 1.67 GHz PowerPC 2GB ram and 80GB hdd - one could likely even fit in a ssd-stick with a cheap adaptor, which might make them rather fast with the original software.

Best
.r.

PS: the 12 inch ones are little beauties, but they are comparatively pricey… And for BP it’s likely good to have some screen-estate, right?

[bp-dev] A simple PHP environment to start with BP3

[Bernard B. <ber...@gm...>]

Dear colleagues,

I have just seen a new commit by Anthony solving the problem of Csound 
output files. The work I am presenting here is anterior to this update, 
so it will require a small adjustment.

I developed a simple PHP environment to exploit (almost) all features of 
the new BP. My approach is to reproduce as much as possible the old 
operational model. This may be changed in the future, but I see more 
clear running the old and the new BP versions side by side.

The package is here:
https://leti.lt/bolprocessor/bolprocessor-php-v1.zip

It contains "bp" as I had recompiled it, which is good enough for the 
present demo.

After dezipping you will get a "bolprocessor" folder (don't rename it!) 
that should be placed in the htdocs folder of your local Apache server, 
presumably MAMP.

To run the program (after starting Apache in MAMP) just follow the link:

http://localhost/bolprocessor/php/

The "php" folder contains all required PHP files.

The display should be the directory of the bolprocessor folder, yet only 
folders and BP-relevant files. Grammar files are highlighted because 
they are the ones from which you start a "project".

I have put much more material than needed because I wanted to trace 
encoding mistakes: we're moving files from MacOS Roman to UTF8, which 
generates garbage on a few characters. When loading a file a few bugs 
are fixed. Others need to be fixed by hand, notably the '•' sign used 
for "period notation".

Move to the "ctest" folder and click “-gr.NotReich”. I am attaching a 
picture of the scene, so you can follow my explanation.

You can edit and save the grammar. At the bottom of the page two buttons 
are displayed for editing “-se.NotReich” and “-or.NotReich”. The 
“orchestra” file is a mapping of MIDI channels to GeneralMIDI 
instruments. Only useful when composing music for several instruments. 
Still, the format needs to be extended to more than 16 channels.

The “settings” file contains all settings. It also could be edited and 
saved but this is risky because we have no clue to the actual meaning of 
each parameter. My next work will be to extract all variables and 
display them in a comprehensive format.

Back to the grammar you can set up a folder that will receive all output 
files. By default it is named "output" but you can create new folders 
with different names, including subfolders such as "output/myitems". 
This a global saving managed by PHP and saved in a “_settings.php” file.

In the middle table you can set up the name of the output file, or no 
name if you want real-time MIDI. Then save the grammar to confirm the 
name. It will automatically append an extension or a prefix, depending 
on the type of file.

Here we have the CSOUND file format and the file will be called 
"out.sco". CSOUND file output is the only option that creates something 
with the current version of BP. Click "PRODUCE ITEM(s)" and you will 
land on a page that says:

cwd = /Applications/MAMP/htdocs/bolprocessor/php
root = /Applications/MAMP/htdocs/
dir = /Applications/MAMP/htdocs/bolprocessor/ctests/
output file = /Applications/MAMP/htdocs/bolprocessor/output/out.sco
command = /Applications/MAMP/htdocs/bolprocessor/bp -gr.NotReich -d 
--csoundout > /Applications/MAMP/htdocs/bolprocessor/output/out.sco

Well, absolute links are used to avoid mistakes on relative paths. After 
all, this is internal cuisine and I needed to make sure that BP would 
handle these absolute links. It does, except for the grammar because it 
checks its name is compliant with a BP grammar but it does it without 
removing the path. To go around this I did a chdir() in PHP that located 
the process in the same "ctest" folder containing the grammar.

Other absolute paths are in fact well-managed by the Linux command, and 
we get the "/output/out.sco" file as expected. Except that it contains a 
mixture of the score with computation messages as I had pointed out. For 
this reason, Anthony fixed the output option which I guess should fit 
with the new command:

command = /Applications/MAMP/htdocs/bolprocessor/bp -gr.NotReich -d 
--csoundout /Applications/MAMP/htdocs/bolprocessor/output/out.sco

Other commands produced by the PHP interface in compliance with 
BP2-Help, but which do not work, are:

command = /Applications/MAMP/htdocs/bolprocessor/bp -gr.NotReich -d --rtmidi
command = /Applications/MAMP/htdocs/bolprocessor/bp -gr.NotReich -d 
--midiout /Applications/MAMP/htdocs/bolprocessor/output/out.mid
command = /Applications/MAMP/htdocs/bolprocessor/bp -gr.NotReich -d -o 
/Applications/MAMP/htdocs/bolprocessor/output/-da.out

The last one complains that '-o' is not a valid option.
The first one is real-time MIDI which we will address later…

Maybe there should be a '-m' option (set by default) meaning that we 
don't want to see any of those messages that used to appear at the 
bottom line of the old BP. Their main purpose was to make the user aware 
that the machine is doing something and not stuck or looping. Now the 
machine is running so much faster that they don't make sense. If 
necessary we'll set up "Trace" in the settings.

Indeed, BP still reads “-se.NotReich” and it requires it for setting a 
few parameters required for the CSOUND output score. Once I have 
developed the interface for changing settings, we will be able to do 
things that otherwise would require many more options in the command line.

Take for instance “-gr.Mozart”. As shown on the video I sent a few days 
ago, it continuously creates new variations. This is a setting of 
“-se.Mozart”. If we don't change the setting and run the grammar to 
create a file, it will grow forever!

I tried to create that incident but it failed for another reason: the 
display of “-gr.Mozart” is perfect but its computation fails. You will 
find the list of errors in "output/Mozart.out". The same happens with 
the “Visser3_UTF8.bpgr” and both yield the same bizarre errors:

BP2 Console completed initialization.
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. GetTextChar(). pos out of range
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Compiling alphabet…
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. GetTextChar(). pos out of range
Looking for time patterns…
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. GetTextChar(). pos out of range
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Compiling subgrammar #1…
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'
Err. ReadLine(). c == '\n'

I tried to understand why a '\n' character was doing a mess and how to 
compensate it in the editor. Empty lines? No doubt it will make sense to 
Anthony! ;-)

I still have a lot of work to do on this minimal interface. I am using 
beginner's PHP: no session variable, no javascript, to make it easy to 
reconstruct in a different environment.

All the best, enjoy!

Bernard

Re: [bp-dev] Video demos of -gr.Mozart and -gr.koto3

[<rs...@ba...>]

> On 9. Jul 2020, at 16:53, Bernard Bel <ber...@gm...> wrote:
> 
> Yes Rainer, this is the version downloaded from https://sourceforge.net/projects/bolprocessor/ <https://sourceforge.net/projects/bolprocessor/>
> 
> It runs on recent MacOS versions except Catalina…

Ah, it’s 32-bit… They’ve closed the door, the bastards ;-)

As I’ve now seen the questionaire on Sourceforge: I think it would be great to have a command-line app that allows to translate texts/grammars into information that can be turned into sound by a third party (csound, core-midi or whatever, osc might be interesting). Frontend (text-editor or graphical) - command-line interpreter - audiogenerator is by now a pretty well established metaphor of music-composition or music-description, handled competently by semi-pro to pro “electronic musicians” or scholars/scientists. It’s not for the casual/non-technical user for sure, and not easy for interactive stuff, but it keeps the existing texts accessible and allows to create new ones. Of the three units the middle-piece is actually musically the most interesting one, I think. Factoring it out into an isolated console-map makes maintenance and broad platform-support a lot easier. The foundations that have already been laid are really wonderful!

I think one of the reasons why I lost track of BP is it’s “home” on SourceForge, which most people have been moving away from and which kind of got a negative reputation for excessive advertising and even data harvesting… Maybe moving to Github, or - not to last minute join a sinking ship again - Gitlab or something would be helpful for enhanced exposure ;-)

Best
.r.

Re: [bp-dev] Video demos of -gr.Mozart and -gr.koto3

[Bernard B. <ber...@gm...>]

Yes Rainer, this is the version downloaded from 
https://sourceforge.net/projects/bolprocessor/

It runs on recent MacOS versions except Catalina… The MIDI output is 
handled by standard Mac procedures. I send output to the IAC port and 
then connect to IAC the device for playing sounds. This can be the 
PianoTeq synthesizer or the (almost free) General MIDI Player. The 
latter gives access to several instruments that can be mapped to MIDI 
channels via the "orchestra" file.

A few years ago, Anthony explained the MIDI current setup in a discussion:

https://sourceforge.net/p/bolprocessor/discussion/555617/thread/f1a4fbdf/

I copied (enclosed files) "-gr.Mozart", "-se.Mozart", "-or.Mozart" and 
"-md.Mozart.bpmd" to the "ctests" folder which Anthony had sent us, 
switched on PianoTeq and tried to launch the command:

    ../bp -gr.Mozart --no-display

I did not include --rtmidi because it asked for a destination name and 
rejected "CoreMIDI"".

Running the command did load the grammar but wasn't able to compile it. 
Error messages suggest that there is a wrong interpretation of 
characters, perhaps improper linefeeds because we are now under Unix.

Normally it should produce sounds in this manner provided that 
"-md.Mozart.bpmd" sends MIDI to the proper port (IAC on my machine). 
Maybe the first interface page required will be the one for setting up 
"-md" files!

Below is the set of error messages:

Bol Processor console app
Version 2.9.8 (Jul 7 2020)
This is a beta version for evaluation...
Reading grammar file -gr.Mozart...
BP2 Console completed initialization.
Err. GetTextChar(). pos out of range
Compiling alphabet�
Err. GetTextChar(). pos out of range
Looking for time patterns�
Err. GetTextChar(). pos out of range
Compiling subgrammar #1�
Compiling subgrammar #2�
Compiling subgrammar #3�
Compiling subgrammar #4�
Compiling subgrammar #5�
Compiling subgrammar #6�
Compiling subgrammar #7�
Compiling subgrammar #8�
Compiling subgrammar #9�
Compiling subgrammar #10�
Compiling subgrammar #11�
Compiling subgrammar #12�
Compiling subgrammar #13�
Compiling subgrammar #14�
Compiling subgrammar #15�
Compiling subgrammar #16�
Compiling subgrammar #17�
Compiling subgrammar #18�
Errors: 164
ProduceItems() returned 0
New project memory use: 76320 [leaked: 0]
This session used 481 Kbytes maximum. 4428 handles created and released. 
[0 bytes leaked]

At least, 0 bytes leaked… ;-)

Bernard

Rainer Schütz wrote on 09/07/2020 15:54:
> Huh, you’re running this on your current Mac? I must admit I lost sight of BP a bit, I thought it hadn’t gotten to the state of actually playing on midi-instruments… Is that an easy setup, and for download somewhere?
>
> Best
> .r.
>
>
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel

Re: [bp-dev] Video demos of -gr.Mozart and -gr.koto3

[<rs...@ba...>]

Huh, you’re running this on your current Mac? I must admit I lost sight of BP a bit, I thought it hadn’t gotten to the state of actually playing on midi-instruments… Is that an easy setup, and for download somewhere?

Best
.r.

[bp-dev] Video demos of -gr.Mozart and -gr.koto3

[Bernard B. <ber...@gm...>]

I recorded 2 videos of the old BP2 for users who can't run it under 
recent MacOS.

These can be downloaded (for one week) from WeTransfer.com:

MOZART = https://tinyurl.com/yd4zn6am
KOTO = https://we.tl/t-yN9HCbWfy5

MOZART VIDEO

The Mozart demo shows how to "run" a grammar with a setup allowing 
continuous production, which means that new items are produced and 
played forever. To avoid a saturation of the MIDI buffer, BP2 measures 
the time T taken for producing an item and starts producing the next one 
only once playing the current one is about T before its end.

In the second part, I selected well-formed polymetric expressions and 
called "play selection" which use them as start strings and play their 
final derivations under current settings.

The Mozart score is piano-roll, by default when the "terminal 
vocabulary" is made of "simple notes" rather than complex sound-objects.

I have chosen this first example because its rendering on PianoTeq 
sounds nicely and it is a true instance of Mozart's musical dice game 
using the probabilities of numbers 2 to 12…

KOTO VIDEO

This one uses a "koto" sound produced by General MIDI Player, 
unfortunately quite bad compared with my old Roland D50 synth.

The process is the same: continuous production and sound output. 
However, items differ because they are produced by substitutions 
performed "in parallel" on an initial string. This is a simple 
unidimensional cellular automaton.

The output is "sound objects": a, b, c etc. with topological properties, 
e.g. forced continuity between certain objects that produces a natural 
flow instead of a strict metronom timing. Some objects such as <<f>> and 
<<chick> are "out-time", i.e. with null durations.

Bernard Bel

[bp-dev] Work on a very basic PHP interface

[Bernard B. <ber...@gm...>]

Dear colleagues,

I started designing PHP pages serving as a minimal interface for running 
BP. For the time being this setup will work in the MAMP environment 
(with a local Apache server) but later they could be moved to a real 
on-line environment (Anthony's proposal), at least for a small number of 
authorized users.

This interface will do its best to reproduce the old BP2 interface, at 
least its functionalities.

The initial version will have home page listing -gr, -da, -ho and -se 
files in a "data" folder. Clicking on the link will open one of these files.

A "-gr" file will be displayed as text on a simple form, thereby 
allowing editing/saving. It will have a "RUN" button to produce items as 
per its settings and options such as the type end location of output files.

A "-da" file will also be displayed in a form. It may have a "PLAY ALL" 
button calling the play-all command, but I also envisage using 
Javascript to play a selection (just like the old BP2)

A "-ho" file will only have a "SAVE" button as it cannot launch any action

A "-se" file will be displayed as a form with all options shown : 
input-output settings, computation settings etc. along with a "SAVE" 
button. This will take more time for the design because some settings 
are interrelated: for instance, in "USE MIDI in/out" is not set, then 
"Reset controllers" should be grayed out.

Indeed I also plan to include the definitions of Csound instruments and 
sound-objects as shown in the -gr.koto3 project.

I believe that this elementary work will contribute to remember all 
options that were available in the old version in order to implement 
them again, adapt them to the new environment, or abandon them.

Lot of work ;-)

Bernard Bel

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

It would be great to have a sort of "--outfile" option saving the 
production to some/.../path/the_file…

My first plan is to develop a minimum PHP environment loading a grammar 
and its associated text files to HTML forms with "save", "compile" and 
"run" buttons. Basically the commands we see on the old GUI. Then refine 
a little bit using a better editor, or do the same in a Wordpress 
environment… Ideas are coming! ;-)

I am also planning to investigate a MIDI real-time output such as:
https://www.smashingmagazine.com/2018/03/web-midi-api/

Not sure it is the one we need but it might teach us useful things…

Bernard

Anthony Kozar wrote on 07/07/2020 23:43:
> 
> I haven't implemented the functionality for sending output directly to a 
> file yet.  But, you're right, it shouldn't be too hard.  It might be as 
> simple as taking the next argument after --csoundout or --midiout, 
> opening the file, and setting the appropriate entry in gOutDestinations[].
> 
> My intention was not to leave stdout & stderr as the default 
> destinations for so many things.  I probably just hooked them up that 
> way to get BP console working quickly back in 2013 and haven't gotten 
> back to finishing what I had in mind.  (What I had in mind 7 years ago 
> might not be so clear now...)  I do remember that I was not just 
> thinking about the console version but looking ahead to developing the 
> "Bol Processor API" that will be used by GUI clients in the future. 
> Having many different destinations for output messages will allow 
> clients to handle each category of messages uniquely.
> 
> Maybe I can work on the output issues this weekend.  Until then you can 
> make whatever changes to your copy that you find helpful. :)  (If you 
> check the code out of the Sourceforge Git repository you can save your 
> changes on a local branch and switch back and forth between my version 
> and yours).
> 
> Anthony

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Anthony K. <mai...@an...>]

Yes. Remember that the console help is a "vision statement". ;)

I haven't implemented the functionality for sending output directly to a 
file yet.  But, you're right, it shouldn't be too hard.  It might be as 
simple as taking the next argument after --csoundout or --midiout, 
opening the file, and setting the appropriate entry in gOutDestinations[].

My intention was not to leave stdout & stderr as the default 
destinations for so many things.  I probably just hooked them up that 
way to get BP console working quickly back in 2013 and haven't gotten 
back to finishing what I had in mind.  (What I had in mind 7 years ago 
might not be so clear now...)  I do remember that I was not just 
thinking about the console version but looking ahead to developing the 
"Bol Processor API" that will be used by GUI clients in the future. 
Having many different destinations for output messages will allow 
clients to handle each category of messages uniquely.

Maybe I can work on the output issues this weekend.  Until then you can 
make whatever changes to your copy that you find helpful. :)  (If you 
check the code out of the Sourceforge Git repository you can save your 
changes on a local branch and switch back and forth between my version 
and yours).

Anthony


On 7/7/20, 10:46 AM, Bernard Bel wrote:
> This works!
>
> Except that if I run:
>
> chdir("ctests");
> $cmd = "../bp -gr.NotReich -d --csoundout > out.sco";
> exec($cmd,$o);
> for($i=0; $i < count($o); $i++) echo $o[$i]."<br />";
>
> nothing is displayed because the output is entirely stored in "out.sco"
> on top of the Csound lines.
>
> This means that we need an option to send the output to a file rather
> than redirect the standard output. We do have it, according to the help:
>
>   > --csoundout outfile write Csound score to file 'outfile' ('-' for stdout)
>
> So I tried:
>
> $cmd = "../bp -gr.NotReich -d --csoundout out.sco";
>
> but this yielded the following error:
>
>   > Unknown action 'out.sco'
>   > If 'out.sco' is an input file, indicate the file type (eg. -gr out.sco).
>
> Actually it is expecting an input file, not an output file, at this
> stage of the command. The problem is the same with --midiout:
>
> $cmd = "../bp -gr.NotReich -d --midiout out.mid";
>
>   > Unknown action 'out.mid'
>   > If 'out.mid' is an input file, indicate the file type (eg. -gr out.mid).
>
> I am confident it can easily be fixed. (No emergency!)
>
> Bernard
>
>
> Anthony Kozar wrote on 07/07/2020 11:46:
>> Aha!  Now I understand what the problem is.  I divided the output from
>> BP console between stderr and stdout.  My intention was to separate
>> "algorithm output" from other messages, warnings, etc.  Perhaps we need
>> to rethink that or provide an option to send all output to stdout.
>>
>> Look at the code in source/BP2/ConsoleMessages.[c/h] to see the current
>> behavior.  You can easily change all of the elements of the array
>> gOutDestinations[] to point to stdout in the function
>> ConsoleMessagesInit() so that you can continue your work.
>>
>> Anthony
>
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel
>

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

I meant SFTP, not plain FTP… Just because I've been using a text editor 
attached to Cyberduck that makes it easy to edit PHP files at distance 
and check immediate effects.

Still, this is not critical now that my MAMP configuration works. I will 
be able to do many trials at home before uploading the ones worth 
sharing. ;-)

Bernard


Rainer Schütz wrote on 07/07/2020 11:05:
>> This might be a very good option. Thus, PHP files created for various 
>> tests/demos could be shared by authorized contributors, and some of 
>> them arranged on a Wordpress site. I guess we would access this 
>> environment via FTP?
> 
> Nowadays the standard is ssh and scp for transfer of individual files. 
> With modern net-speeds ssh gives you a shell/console as if you were 
> sitting in front of your local workstation. If want to move large 
> amounts of files, sftp (or ftps) are available. Using ftp is a bit 
> faster, but allows every sniffer, and people with access to server logs, 
> to read your credentials in plain written language ;-)
> 
> Best
> .r.

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

This works!

Except that if I run:

chdir("ctests");
$cmd = "../bp -gr.NotReich -d --csoundout > out.sco";
exec($cmd,$o);
for($i=0; $i < count($o); $i++) echo $o[$i]."<br />";

nothing is displayed because the output is entirely stored in "out.sco" 
on top of the Csound lines.

This means that we need an option to send the output to a file rather 
than redirect the standard output. We do have it, according to the help:

 > --csoundout outfile write Csound score to file 'outfile' ('-' for stdout)

So I tried:

$cmd = "../bp -gr.NotReich -d --csoundout out.sco";

but this yielded the following error:

 > Unknown action 'out.sco'
 > If 'out.sco' is an input file, indicate the file type (eg. -gr out.sco).

Actually it is expecting an input file, not an output file, at this 
stage of the command. The problem is the same with --midiout:

$cmd = "../bp -gr.NotReich -d --midiout out.mid";

 > Unknown action 'out.mid'
 > If 'out.mid' is an input file, indicate the file type (eg. -gr out.mid).

I am confident it can easily be fixed. (No emergency!)

Bernard


Anthony Kozar wrote on 07/07/2020 11:46:
> Aha!  Now I understand what the problem is.  I divided the output from 
> BP console between stderr and stdout.  My intention was to separate 
> "algorithm output" from other messages, warnings, etc.  Perhaps we need 
> to rethink that or provide an option to send all output to stdout.
> 
> Look at the code in source/BP2/ConsoleMessages.[c/h] to see the current 
> behavior.  You can easily change all of the elements of the array 
> gOutDestinations[] to point to stdout in the function 
> ConsoleMessagesInit() so that you can continue your work.
> 
> Anthony

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Anthony K. <mai...@an...>]

Aha!  Now I understand what the problem is.  I divided the output from 
BP console between stderr and stdout.  My intention was to separate 
"algorithm output" from other messages, warnings, etc.  Perhaps we need 
to rethink that or provide an option to send all output to stdout.

Look at the code in source/BP2/ConsoleMessages.[c/h] to see the current 
behavior.  You can easily change all of the elements of the array 
gOutDestinations[] to point to stdout in the function 
ConsoleMessagesInit() so that you can continue your work.

Anthony


On 7/7/20, 3:56 AM, Bernard Bel wrote:

> Strangely, $cmd = "./bp --version" yieds no output, nor does $cmd =
> "./bp --version > try.txt" create a non-empty "try.txt" file. However
> they both generate apache errors which are the actual expected output.
> For instance apache error when calling "./bp --version" is:
>
> Bol Processor console app
> Version 2.9.8 (Jul  7 2020)
>
> In other words, the output of apache error is actually the output
> expected from BP. In reality BP runs properly. For instance this PHP
> sequence:
>
> chdir("ctests");
> $cmd = "../bp -gr.NotReich -d --csoundout > out.sco";
> exec($cmd,$o);
> print_r($o);
>
> creates the correct out.sco file while it sends the "console" output to
> apache_error.log:
>
> Bol Processor console app
> Version 2.9.8 (Jul  7 2020)
> This is a beta version for evaluation...
> Reading grammar file -gr.NotReich...
 > [...]

> In sum, the problem is not running BP but rather retrieving its "console
> output" somewhere else than apache_error.log. Unlike "hello.c" calling
> printf for the output:

Re: [bp-dev] A sneak peak at the future of Bol Processor

[<rs...@ba...>]

> On 7. Jul 2020, at 09:56, Bernard Bel <ber...@gm...> wrote:
> 
> creates the correct out.sco file while it sends the "console" output to apache_error.log:

The typical/expected interaction of a php-app would be to pipe output to the next web-page. 

> This might be a very good option. Thus, PHP files created for various tests/demos could be shared by authorized contributors, and some of them arranged on a Wordpress site. I guess we would access this environment via FTP?

Nowadays the standard is ssh and scp for transfer of individual files. With modern net-speeds ssh gives you a shell/console as if you were sitting in front of your local workstation. If want to move large amounts of files, sftp (or ftps) are available. Using ftp is a bit faster, but allows every sniffer, and people with access to server logs, to read your credentials in plain written language ;-)

Best
.r.

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

Anthony Kozar wrote on 06/07/2020 22:43:
> My web hosting service provides all of the standard Linux dev tools we 
> need (GCC, git, PHP, MySQL, and Apache).  If it would be helpful, I 
> can set up a sandbox environment for developing a BP web app and give 
> you access to it, Bernard.  The web front end would have to be 
> password-protected though since I don't think we can trust BP to not 
> be exploitable at this point.
This might be a very good option. Thus, PHP files created for various 
tests/demos could be shared by authorized contributors, and some of them 
arranged on a Wordpress site. I guess we would access this environment 
via FTP?
> Hmmm... strange that can't run a macOS binary on macOS just because it 
> is called from PHP.  I see that your script uses "./bp".  Are the PHP 
> script and bp in the same directory?  You might try using a full 
> pathname to bp.  Alternatively, try copying the bp binary to somewhere 
> on your path (or the web server's CGI bin folder?) and removing the 
> "./".  Also, "-v" is not a valid option for BP console.  I think you 
> want "--version".
In fact I can compile and run a simple "hello.c" program using the call 
"./hello".

Compiling "hello.c" created a warning in apache_error.log, claiming that 
since "stdio.h" is missing 'printf' will be interpreted implicitly. This 
gave me the idea of adding #include <stdio.h> to PrefixANSIDebug.h and 
run Makefile again. Yet BP remained silent when called by PHP.

Strangely, $cmd = "./bp --version" yieds no output, nor does $cmd = 
"./bp --version > try.txt" create a non-empty "try.txt" file. However 
they both generate apache errors which are the actual expected output. 
For instance apache error when calling "./bp --version" is:

Bol Processor console app
Version 2.9.8 (Jul  7 2020)

In other words, the output of apache error is actually the output 
expected from BP. In reality BP runs properly. For instance this PHP 
sequence:

chdir("ctests");
$cmd = "../bp -gr.NotReich -d --csoundout > out.sco";
exec($cmd,$o);
print_r($o);

creates the correct out.sco file while it sends the "console" output to 
apache_error.log:

Bol Processor console app
Version 2.9.8 (Jul  7 2020)
This is a beta version for evaluation...
Reading grammar file -gr.NotReich...
BP2 Console completed initialization.
seed 1 = 1594103353
seed 2 = 10475
Err. GetTextChar(). pos out of range
TextInsert(Trace):
Compiling alphabetÉ
Err. GetTextChar(). pos out of range
Looking for time patternsÉ
Err. GetTextChar(). pos out of range
Err. GetTextChar(). pos out of range
Compiling subgrammar #1É
Compiling subgrammar #2É
Err. GetTextChar(). pos out of range
Errors: 0
Producing item(s)É
Computing itemÉ
Subgrammar 1/2
Subgrammar 2/2
Buffer limit expanded to 1500
Buffer limit expanded to 2250
Buffer limit expanded to 3375
Buffer limit expanded to 5062
Interpreting structureÉ
etc.

In sum, the problem is not running BP but rather retrieving its "console 
output" somewhere else than apache_error.log. Unlike "hello.c" calling 
printf for the output:

#include <stdio.h>
int main() {
     printf("Hello! This is a test");
     return 0;
     }

When running PHP:

$cmd = "./hello";
exec($cmd,$o);
print_r($o);

The output is:

Array ( [0] => Hello! This is a test )

> Yes, the fact that it compiled on an ARM platform makes me think we 
> won't have much trouble compiling for Android either.  Imagine being 
> able to play with BP on your tablet or smartphone! :)
(Joke) I hardly use anything else than telephone, SMS, WhatsApp and the 
torch on my iPhone! ;-)
Nevertheless I can figure out extensions.

I am particularly keen to work with "sound-objects" (typically 
-gr.koto3). In reality, BP  handles "time-objects", the current ones 
containing either MIDI instructions, lines of Csound score or both. 
These time-objects have topological properties putting constraints on 
their actual time-setting. For instance, a certain object should not 
have its beginning mixed with other objects, so the algorithm may delay 
it if its is relocatable, otherwise move ahead the preceding object etc.

These time-objects could contain video sequences, bits of stories in a 
scenario. Producing object structures via grammars, polymetric 
representation and time-constraint solving would amount to fabricating 
"stories" mixing different sorts of material instead of just sounds.

Another great usage would be speech synthesis because the polymetric 
representation is probably the best tool for structuring prosodic units, 
thereby synthesizing speech at different speeds and taking care of 
co-articulation in fast speech.

As you guess there is still a very wide scope for development/research 
and this will be open to practice thanks to the command-line "engine"! I 
am certain that more developers will join once we have small demos of 
working with different sorts of time-objects. Imagine a grammar that 
creates variations of a scenario for a series including their clips, 
image sequences, music and synthetic background speech!
> I suspect the speedup is mostly due to the fact that BP console 
> doesn't have to poll for events like the Mac Classic & Carbon versions 
> did. Every time BP2 calls GetNextEvent(waitTime) creates a delay.
Indeed! For the time being we drop real-time interactions — e.g. 
controling improvisational processes via MIDI events.
> The low memory usage could be an advantage on mobile and embedded 
> devices though.  (One can imagine that, someday, someone might create 
> an interactive multimedia installation using BP on a Raspberry Pi or 
> even Arduino-like device).
This is an instance of the dream I described above. ;-)
> Well, on to far less interesting tasks for now. ;-)
No hurry! A few small steps at a time. :-)

Bernard

Re: [bp-dev] A sneak peak at the future of Bol Processor

[<rs...@ba...>]

> On 7. Jul 2020, at 00:37, Anthony Kozar <mai...@an...> wrote:
> 
> would probably tell you what the working directory of your script is when run under the web server.  (There's probably a better way to do it, but I didn't see any values specifically about it in the variables $_SERVER or $_ENV in some old tests I ran).

I like the idea of having the binary in the path (php e.g. uses compress-decompress binaries, or image utilities). Here user rights may come into play as well (apache configuration) - and I think there are different degrees of hardenedness of the php-configuration that determine how and from where binaries can be run. Security policies are the main issue here. I think the apache log (/var/log/apache/access or error) might tell you what went on.

Best
.r.

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Anthony K. <mai...@an...>]

<?php
   $cmd = "pwd";
   exec($cmd,$o);
   print_r($o);
?>

would probably tell you what the working directory of your script is 
when run under the web server.  (There's probably a better way to do it, 
but I didn't see any values specifically about it in the variables 
$_SERVER or $_ENV in some old tests I ran).

Anthony

On 7/6/20, 4:43 PM, Anthony Kozar wrote:

> On 7/6/20, 11:57 AM, Bernard Bel wrote:
>
>> After activating gcc I was able to compile an run a tiny program that
>> says "Hello". Then I compiled BP using the Makefile, and it did compile,
>> yielding "bp" or 875 Kb announced as "Unix executable file". It did not
>> work when called from PHP:
>>
>> <?php
>> $cmd = "./bp -v";
>> exec($cmd,$o);
>> print_r($o);
>> ?>
>>
>> "bp32" also did not run. However both run fine when called via Terminal.
>> This means that I have come as far as compiling a correct version of BP
>> under PHP on a MAMP server. Going beyond this step probably requires
>> working on MAMP setup - still a bit obscure to me. I'll manage it; :-)
>
> Hmmm... strange that can't run a macOS binary on macOS just because it
> is called from PHP.  I see that your script uses "./bp".  Are the PHP
> script and bp in the same directory?  You might try using a full
> pathname to bp.  Alternatively, try copying the bp binary to somewhere
> on your path (or the web server's CGI bin folder?) and removing the
> "./".  Also, "-v" is not a valid option for BP console.  I think you
> want "--version".

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Anthony K. <mai...@an...>]

Hello Bernard and Rainer,

It's wonderful to see the additional exciting developments this morning. 
  Thanks Rainer!  You beat me to compiling for Windows.  I have a 
cross-compiler installed on my Mac and was planning to try that out 
soon.  I'm so glad to hear that it worked for you!  This new portability 
is so amazing.  It motivates me to want to finish the work I started and 
make BP console truly usable for music-making!

Alas, I will be busy with other things for at least the next few days. :(

A few more comments below.

On 7/6/20, 11:57 AM, Bernard Bel wrote:

> You are probably right regarding OVH's limitations. I guess they'll
> suggest a dedicated server at a monthly price I can't afford. ;-)

My web hosting service provides all of the standard Linux dev tools we 
need (GCC, git, PHP, MySQL, and Apache).  If it would be helpful, I can 
set up a sandbox environment for developing a BP web app and give you 
access to it, Bernard.  The web front end would have to be 
password-protected though since I don't think we can trust BP to not be 
exploitable at this point.

> My motivation has been to take advantages of calling BP procedures via
> PHP instructions. In this way, part of the input could be prepared in
> advance — even using database storage — and the output could also be
> processed in various ways. For instance, Csound orchestras, definitions
> of sound-object prototypes etc., anything that contains more information
> that we can handle on a single line could be maintained in database
> tables. I admit that this motivation has been naively prompted by my
> current activity with databases and web.

I think a web interface to BP would be very helpful to allow curious 
individuals to try out some of BP's unique concepts before "committing" 
to installing it on their own machines.

> So, having little hope that OVH grants me superuser's rights on a shared
> hosting, I tried something else and it "almost" worked: using MAMP Pro
> on my personal computer.
>
> After activating gcc I was able to compile an run a tiny program that
> says "Hello". Then I compiled BP using the Makefile, and it did compile,
> yielding "bp" or 875 Kb announced as "Unix executable file". It did not
> work when called from PHP:
>
> <?php
> $cmd = "./bp -v";
> exec($cmd,$o);
> print_r($o);
> ?>
>
> "bp32" also did not run. However both run fine when called via Terminal.
> This means that I have come as far as compiling a correct version of BP
> under PHP on a MAMP server. Going beyond this step probably requires
> working on MAMP setup - still a bit obscure to me. I'll manage it; :-)

Hmmm... strange that can't run a macOS binary on macOS just because it 
is called from PHP.  I see that your script uses "./bp".  Are the PHP 
script and bp in the same directory?  You might try using a full 
pathname to bp.  Alternatively, try copying the bp binary to somewhere 
on your path (or the web server's CGI bin folder?) and removing the 
"./".  Also, "-v" is not a valid option for BP console.  I think you 
want "--version".

> It is an extremely pleasant surprise that this C code is really
> cross-platform. This is probably the effect of systematic programming
> when migrating BP through upgrades of MacOS. A major migration (which
> had taken me several months full time) was the one from 68K to PPC circa
> 1994. This forced me to clean-up many dependencies, unknowingly
> preparing the code for later upgrades, among which Anthony's migration
> to MacOS X which was also a big issue.

Yes, the fact that it compiled on an ARM platform makes me think we 
won't have much trouble compiling for Android either.  Imagine being 
able to play with BP on your tablet or smartphone! :)

> It's wonderful to hear that exec time is much smaller via command-line
> calls, even though large amounts of RAM may still be hired for storing
> items. This indicates that the strategy of minimizing memory usage that
> was so critical in the 1990s now pays off again. This is an advantage of
> poverty ;-)

I suspect the speedup is mostly due to the fact that BP console doesn't 
have to poll for events like the Mac Classic & Carbon versions did. 
Every time BP2 calls GetNextEvent(waitTime) creates a delay.

The low memory usage could be an advantage on mobile and embedded 
devices though.  (One can imagine that, someday, someone might create an 
interactive multimedia installation using BP on a Raspberry Pi or even 
Arduino-like device).

> I agree with the suggestion that building a standalone application BP4
> with its proper GUI should take full advantage of BP3's command-line
> features. This is a reason why I am looking for some way of storing
> large pieces of data. Once it works with a MySQL file it will be easy to
> translate the process to the standalone app. My understanding is that
> the GUI would be similar to the body of a car with a unique engine.
>
> Bernard

Well, on to far less interesting tasks for now. ;-)

Cheers for the progress we've made though!

Anthony

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

Hello Rainer,

You are probably right regarding OVH's limitations. I guess they'll 
suggest a dedicated server at a monthly price I can't afford. ;-)

My motivation has been to take advantages of calling BP procedures via 
PHP instructions. In this way, part of the input could be prepared in 
advance — even using database storage — and the output could also be 
processed in various ways. For instance, Csound orchestras, definitions 
of sound-object prototypes etc., anything that contains more information 
that we can handle on a single line could be maintained in database 
tables. I admit that this motivation has been naively prompted by my 
current activity with databases and web.

So, having little hope that OVH grants me superuser's rights on a shared 
hosting, I tried something else and it "almost" worked: using MAMP Pro 
on my personal computer.

After activating gcc I was able to compile an run a tiny program that 
says "Hello". Then I compiled BP using the Makefile, and it did compile, 
yielding "bp" or 875 Kb announced as "Unix executable file". It did not 
work when called from PHP:

<?php
$cmd = "./bp -v";
exec($cmd,$o);
print_r($o);
?>

"bp32" also did not run. However both run fine when called via Terminal. 
This means that I have come as far as compiling a correct version of BP 
under PHP on a MAMP server. Going beyond this step probably requires 
working on MAMP setup - still a bit obscure to me. I'll manage it; :-)

It is an extremely pleasant surprise that this C code is really 
cross-platform. This is probably the effect of systematic programming 
when migrating BP through upgrades of MacOS. A major migration (which 
had taken me several months full time) was the one from 68K to PPC circa 
1994. This forced me to clean-up many dependencies, unknowingly 
preparing the code for later upgrades, among which Anthony's migration 
to MacOS X which was also a big issue.

It's wonderful to hear that exec time is much smaller via command-line 
calls, even though large amounts of RAM may still be hired for storing 
items. This indicates that the strategy of minimizing memory usage that 
was so critical in the 1990s now pays off again. This is an advantage of 
poverty ;-)

I agree with the suggestion that building a standalone application BP4 
with its proper GUI should take full advantage of BP3's command-line 
features. This is a reason why I am looking for some way of storing 
large pieces of data. Once it works with a MySQL file it will be easy to 
translate the process to the standalone app. My understanding is that 
the GUI would be similar to the body of a car with a unique engine.

Bernard


Rainer Schütz wrote on 06/07/2020 16:25:
>> I tried both your and Anthony's suggestions without success… I should definitely wait for the reply of OVH support!
> Yea, I am not trying to push you, just make suggestions that might help.
>
>> Running “apt” without sudo yields the reply (my translation):
>>
>> E: Directory /var/cache/apt/archives/partial does not exist. - Acquire (13: Permission not granted)
>> E: Impossible to open the lock file /var/lib/dpkg/lock - open (13: Permission not granted)
>> E: Impossible to lock the admin directory (/var/lib/dpkg/). Do you have superuser's rights?
> Yea, I strongly suspect your account is not a full virtual server, but just a shared server. In that case they cannot give you root rights because you could take down the entire server including the 100 other accounts you share with;-). Their wording is ambivalent when it comes to describing a users capabilities with the account they provide.
>
>> For Anthony : echo $PATH returned expectedly:
>> /usr/local/php7.3/bin:/usr/local/bin:/usr/bin:/bin
>>
>> After all, I don't need superuser's rights. OVH folks should simply activate gcc and I would be able to run it!
> Build systems often require many dependencies, allowing gcc and not allowing apt access is rarely useful. They probably don’t offer that option. Gcc can also eat up a lot of system resources, another reason web-providers might not want to offer the option. And if they’d “just unlock” gcc, it would be in system-space, which would require root anyways.
>
>>  From a few (old) forum entries I see that "gcc" is the C compiler in OVH.
>>
>> I finally tried to upload and untar Anthony's compiled "bp". But running "bp" claims that "there is no such file" whereas trying to run "bp32" or "bp64" tells that "this binary file cannot be executed". Still, Unix rights are identical as shown below:
>>
>> -rwxr-xr-x+  1 letivbvp users 841072 juil.  5 04:34 bp
>> ...
>> -rwxr-xr-x+  1 letivbvp users 997260 juil. 26  2019 bp32
>> -rwxr-xr-x+  1 letivbvp users 964200 juil. 26  2019 bp64
> It’s not a user rights issue, Anthony’s bp32/bp64 only run on MacOS, I think. I am not aware of a file “bp” he provided. But if he sent you a linux-compiled file it is likely from his Ubuntu18.04  server, which might be incompatible with your Debian Jessie environment. You could try the binary I sentyesterday,  the one specifically for Debian Jessie (I can send it to your private email, if you can’t find it). But I don’t understand, why it doesn’t see the file at all...
>
>> ...
>> let...@ss...  (php/7.3/production/stable) ~/www/bolprocessor $ ./bp-ovh_ssh: ./bp: No file or directory of this type
>> let...@ss...  (php/7.3/production/stable) ~/www/bolprocessor $ ./bp32
>> -ovh_ssh: ./bp32: cannot execute binary file: Format error for exec()
>> let...@ss...  (php/7.3/production/stable) ~/www/bolprocessor $ ./bp64
>> -ovh_ssh: ./bp64: cannot execute binary file: Format error for exec()
> Sorry, no joy so far;-)  But as you said, it’s always the first steps that are the most thorny and frustrating. Once you have a working workflow, things will be smooth. After all Anthony’s ports based on your code are impressively widely applicable;-)
>
> Best
> .r.
>
> PS: I am not sure, why you want to do your stuff on a webserver. Are you ultimately after a website on which bolprocessor can be run, or is it just because it seems to be easy to use this kind of quasi-cloud to run your builds. Because I doubt web-providers actively support this use-case, it could be pretty demanding on the server…
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel

Re: [bp-dev] A sneak peak at the future of Bol Processor

[<rs...@ba...>]

> I tried both your and Anthony's suggestions without success… I should definitely wait for the reply of OVH support!

Yea, I am not trying to push you, just make suggestions that might help.

> Running “apt” without sudo yields the reply (my translation):
> 
> E: Directory /var/cache/apt/archives/partial does not exist. - Acquire (13: Permission not granted)
> E: Impossible to open the lock file /var/lib/dpkg/lock - open (13: Permission not granted)
> E: Impossible to lock the admin directory (/var/lib/dpkg/). Do you have superuser's rights?

Yea, I strongly suspect your account is not a full virtual server, but just a shared server. In that case they cannot give you root rights because you could take down the entire server including the 100 other accounts you share with ;-). Their wording is ambivalent when it comes to describing a users capabilities with the account they provide.

> For Anthony : echo $PATH returned expectedly:
> /usr/local/php7.3/bin:/usr/local/bin:/usr/bin:/bin
> 
> After all, I don't need superuser's rights. OVH folks should simply activate gcc and I would be able to run it!

Build systems often require many dependencies, allowing gcc and not allowing apt access is rarely useful. They probably don’t offer that option. Gcc can also eat up a lot of system resources, another reason web-providers might not want to offer the option. And if they’d “just unlock” gcc, it would be in system-space, which would require root anyways.

> From a few (old) forum entries I see that "gcc" is the C compiler in OVH.
> 
> I finally tried to upload and untar Anthony's compiled "bp". But running "bp" claims that "there is no such file" whereas trying to run "bp32" or "bp64" tells that "this binary file cannot be executed". Still, Unix rights are identical as shown below:
> 
> -rwxr-xr-x+  1 letivbvp users 841072 juil.  5 04:34 bp
> ...
> -rwxr-xr-x+  1 letivbvp users 997260 juil. 26  2019 bp32
> -rwxr-xr-x+  1 letivbvp users 964200 juil. 26  2019 bp64

It’s not a user rights issue, Anthony’s bp32/bp64 only run on MacOS, I think. I am not aware of a file “bp” he provided. But if he sent you a linux-compiled file it is likely from his Ubuntu 18.04 server, which might be incompatible with your Debian Jessie environment. You could try the binary I sent yesterday, the one specifically for Debian Jessie (I can send it to your private email, if you can’t find it). But I don’t understand, why it doesn’t see the file at all...

> ...
> let...@ss... (php/7.3/production/stable) ~/www/bolprocessor $ ./bp-ovh_ssh: ./bp: No file or directory of this type
> let...@ss... (php/7.3/production/stable) ~/www/bolprocessor $ ./bp32
> -ovh_ssh: ./bp32: cannot execute binary file: Format error for exec()
> let...@ss... (php/7.3/production/stable) ~/www/bolprocessor $ ./bp64
> -ovh_ssh: ./bp64: cannot execute binary file: Format error for exec()

Sorry, no joy so far ;-) But as you said, it’s always the first steps that are the most thorny and frustrating. Once you have a working workflow, things will be smooth. After all Anthony’s ports based on your code are impressively widely applicable ;-)

Best
.r.

PS: I am not sure, why you want to do your stuff on a webserver. Are you ultimately after a website on which bolprocessor can be run, or is it just because it seems to be easy to use this kind of quasi-cloud to run your builds. Because I doubt web-providers actively support this use-case, it could be pretty demanding on the server…

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

I tried both your and Anthony's suggestions without success… I should 
definitely wait for the reply of OVH support!

Running “apt” without sudo yields the reply (my translation):

E: Directory /var/cache/apt/archives/partial does not exist. - Acquire 
(13: Permission not granted)
E: Impossible to open the lock file /var/lib/dpkg/lock - open (13: 
Permission not granted)
E: Impossible to lock the admin directory (/var/lib/dpkg/). Do you have 
superuser's rights?

For Anthony : echo $PATH returned expectedly:
/usr/local/php7.3/bin:/usr/local/bin:/usr/bin:/bin

After all, I don't need superuser's rights. OVH folks should simply 
activate gcc and I would be able to run it!

 From a few (old) forum entries I see that "gcc" is the C compiler in OVH.

I finally tried to upload and untar Anthony's compiled "bp". But running 
"bp" claims that "there is no such file" whereas trying to run "bp32" or 
"bp64" tells that "this binary file cannot be executed". Still, Unix 
rights are identical as shown below:

-rwxr-xr-x+  1 letivbvp users 841072 juil.  5 04:34 bp
...
-rwxr-xr-x+  1 letivbvp users 997260 juil. 26  2019 bp32
-rwxr-xr-x+  1 letivbvp users 964200 juil. 26  2019 bp64
...
let...@ss... 
(php/7.3/production/stable) ~/www/bolprocessor $ ./bp-ovh_ssh: ./bp: No 
file or directory of this type
let...@ss... 
(php/7.3/production/stable) ~/www/bolprocessor $ ./bp32
-ovh_ssh: ./bp32: cannot execute binary file: Format error for exec()
let...@ss... 
(php/7.3/production/stable) ~/www/bolprocessor $ ./bp64
-ovh_ssh: ./bp64: cannot execute binary file: Format error for exec()

Bernard

==========

Rainer Schütz wrote on 05/07/2020 14:37:
> 
> You might be able to run “apt” without sudo?
> 
> If you have a “virtual server”, the say  "you get admin access to your 
> virtual server”. That could mean you get su/sudo, or it could mean you 
> can do stuff as “normal” user which usually only root can do… Just try 
> “apt install build-essential”, it’ll tell you if you can do it or not.
> 
> There is a way to configure su-access. So if apt complains without sudo. 
> You might be able to follow this (it’s for Ubuntu (another Distro like 
> Debian), but that’s based on Debian and very similar, so it should work):
> 
> https://www.digitalocean.com/community/tutorials/how-to-create-a-new-sudo-enabled-user-on-ubuntu-18-04-quickstart
> 

Re: [bp-dev] A sneak peak at the future of Bol Processor

[<rs...@ba...>]

For some reason a download-attempt on the gDrive seems to require another okay from me. That’s weird because my gDrive setting say “shared to anybody with the link”… maybe just a temporary thing. I’ll keep giving access to anybody who requests if this state continues, hopefully it won’t.
Best
.r.

Re: [bp-dev] A sneak peak at the future of Bol Processor

[<rs...@ba...>]

I am probably overstretching my ambitions to become the “top guinea pig” now ;-)  But as this opens up another world, hated in the past, but rather attractive as of lately, I find, and in many less-privileged parts of the world considered “the computer”, and often the only hardware/os-combo around: this can be built on Windows as well, and it seems to run flawlessly in the native shell without any additional dlls!!

The trick is to use sort of a posix shell emulation and build with Windows-gcc (“mingw”) as if you were on a unixy system, so that makefiles etc. can work. The hippest of these emulators these days is “msys2”, and I am happy to report, all works well. Once built, you can use the binary in the default Windows shell “cmd” and things just work, including the interaction with csound (installed from the official installer, I listened to the aiff via remote desktop, and it had a nice retro vibe ;-), one should ideally be playing SuperMario and smoke some weed while listening).

I attach the build-output and test results.

Re: [bp-dev] A sneak peak at the future of Bol Processor

[Bernard B. <ber...@gm...>]

I went through your messages with great excitment, as you would guess!

This morning I am helping a person on a much much simpler project… Then 
I will work and reply your suggestions.

Bernard


Anthony Kozar wrote on 05/07/2020 23:01:
> No problem.  Your helpfulness is greatly appreciated!
>
> I suspect 100K was the default limit set by Sourceforge and like I 
> said their system won't let me set higher than 999K.  (I thought 2 MB 
> would be reasonable).
>
> Fortunately, there are plenty of other ways to share things today.  
> And you can always try to email big files directly to me and Bernard 
> if that is more convenient.
>
> Anthony
>
>
> On 7/5/20, 4:36 PM, Rainer Schütz wrote:
>> Sorry, Anthony, for causing more hassle, I thought this would go 
>> through, the binary is 785 kb…
>> Best
>> .r.
>>
>> _______________________________________________
>> bolprocessor-devel mailing list
>> bol...@li...
>> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel
>>
>
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel

Re: [bp-dev] A sneak peak at the future of Bol Processor

[<rs...@ba...>]

Urning my "super guinea pig” medal (and even more excited!). The Raspi (model 4, Debian Buster, 32-bit) build works!

pi@bawor:~/Projects/bolprocessor $ ./bp --version
Bol Processor console app
Version 2.9.8 (Jul  5 2020)

pi@bawor:~/Projects/bolprocessor/ctests $ ../bp -da.acceleration
Bol Processor console app
Version 2.9.8 (Jul  5 2020)
This is a beta version for evaluation...
Reading data file -da.acceleration...
BP2 Console completed initialization.
seed 1 = 1593984101
seed 2 = 4979
TextInsert(Trace):
Compiling alphabet
Looking for time patterns
Producing item(s)
Computing item
TextInsert(Data): S
Ignoring DoKey(0xD)
New project memory use: 55167 [leaked: 0]
This session used 64 Kbytes maximum.  80 handles created and released. [0 bytes leaked]

pi@bawor:~/Projects/bolprocessor/ctests $ ../bp -gr.NotReich
Bol Processor console app
Version 2.9.8 (Jul  5 2020)
This is a beta version for evaluation...
Reading grammar file -gr.NotReich...
BP2 Console completed initialization.
seed 1 = 1593984166
seed 2 = 23084
Err. GetTextChar(). pos out of range
TextInsert(Trace):
Compiling alphabet
Err. GetTextChar(). pos out of range
Looking for time patterns
Err. GetTextChar(). pos out of range
Err. GetTextChar(). pos out of range
Compiling subgrammar #1
Compiling subgrammar #2
Err. GetTextChar(). pos out of range
Errors: 0
Producing item(s)
Computing item
Subgrammar 1/2
Subgrammar 2/2
Buffer limit expanded to 1500
Buffer limit expanded to 2250
Buffer limit expanded to 3375
Buffer limit expanded to 5062
TextInsert(Data): _chan(
TextInsert(Data): 1
TextInsert(Data): )
TextInsert(Data):
TextInsert(Data): _vel(
TextInsert(Data): 110
TextInsert(Data): )
TextInsert(Data):
TextInsert(Data): _volumecont
TextInsert(Data): _volume(
TextInsert(Data): 90
TextInsert(Data): )
…
TextInsert(Data):
TextInsert(Data): -
TextInsert(Data):
TextInsert(Data): F3
TextInsert(Data):
TextInsert(Data): G3
TextInsert(Data): ,
TextInsert(Data): A#5
TextInsert(Data): ,
TextInsert(Data): -
TextInsert(Data):
TextInsert(Data): D5
TextInsert(Data): }
TextInsert(Data):
TextInsert(Data): _volume(
TextInsert(Data): 0
TextInsert(Data): )
Ignoring DoKey(0xD)
New project memory use: 55449 [leaked: 0]
This session used 84 Kbytes maximum.  330 handles created and released. [0 bytes leaked]


pi@bawor:~/Projects/bolprocessor/ctests $ ../bp -gr.NotReich -d --csoundout
Bol Processor console app
Version 2.9.8 (Jul  5 2020)
This is a beta version for evaluation...
Reading grammar file -gr.NotReich...
BP2 Console completed initialization.
seed 1 = 1593984358
seed 2 = 23945
Err. GetTextChar(). pos out of range
TextInsert(Trace):
Compiling alphabet
Err. GetTextChar(). pos out of range
Looking for time patterns
Err. GetTextChar(). pos out of range
Err. GetTextChar(). pos out of range
Compiling subgrammar #1
Compiling subgrammar #2
Err. GetTextChar(). pos out of range
Errors: 0
Producing item(s)
Computing item
Subgrammar 1/2
Subgrammar 2/2
Buffer limit expanded to 1500
Buffer limit expanded to 2250
Buffer limit expanded to 3375
Buffer limit expanded to 5062
Interpreting structure
Expanding polymetric expression
Dur = 85 ticks  Prod = 6  [883 objects]  (no compression)
Expanded polymetric expression would contain 1207 symbols
Creating phase diagram.  (No compression)
Time-objects created: 50.  Estimated: 882
Time-objects created: 100.  Estimated: 882
Time-objects created: 150.  Estimated: 882
Time-objects created: 200.  Estimated: 882
…
i1 83.666 0.334 7.07 40.000 30.000 0.000 0.000 0.000 0.000 ; G3
i1 83.666 0.334 7.07 40.000 30.000 0.000 0.000 0.000 0.000 ; G3
858 objects done out of 870
i1 83.000 1.000 9.10 60.000 30.000 0.000 0.000 0.000 0.000 ; A#5
i1 83.000 1.000 9.10 60.000 30.000 0.000 0.000 0.000 0.000 ; A#5
i1 83.500 0.500 9.02 45.000 30.000 0.000 0.000 0.000 0.000 ; D5
i1 83.500 0.500 9.02 45.000 30.000 0.000 0.000 0.000 0.000 ; D5
i1 84.000 0.500 8.00 30.000 15.000 0.000 0.000 0.000 0.000 ; C4
i1 84.000 0.500 8.00 30.000 15.000 0.000 0.000 0.000 0.000 ; C4
i1 84.333 0.333 7.05 20.000 10.000 0.000 0.000 0.000 0.000 ; F3
i1 84.333 0.333 7.05 20.000 10.000 0.000 0.000 0.000 0.000 ; F3
i1 84.666 0.334 7.07 10.000 0.000 0.000 0.000 0.000 0.000 ; G3
i1 84.666 0.334 7.07 10.000 0.000 0.000 0.000 0.000 0.000 ; G3
i1 84.000 1.000 9.10 30.000 0.000 0.000 0.000 0.000 0.000 ; A#5
i1 84.000 1.000 9.10 30.000 0.000 0.000 0.000 0.000 0.000 ; A#5
i1 84.500 0.500 9.02 15.000 0.000 0.000 0.000 0.000 0.000 ; D5
i1 84.500 0.500 9.02 15.000 0.000 0.000 0.000 0.000 0.000 ; D5
870 objects done out of 870
s
New project memory use: 55449 [leaked: 0]
This session used 486 Kbytes maximum.  10933 handles created and released. [0 bytes leaked]
e
; this score was created by Bol Processor BP2 (version BP2.9.8) on Date: Sun, Jul 05, 2020 -- 11:25 PM
Closed Csound score file stdout




pi@bawor:~/Projects/bolprocessor/ctests $ csound -s -A -o out.aiff BP2test.orc out.sco                                                                                                            [350/9784]
time resolution is 1000.000 ns
0dBFS level = 32768.0
--Csound version 6.12 beta (double samples) 2019-03-21
[commit: none]
libsndfile-1.0.28
orchname:  BP2test.orc
rtaudio: ALSA module enabled
rtmidi: ALSA Raw MIDI module enabled
Elapsed time at end of orchestra compile: real: 0.006s, CPU: 0.006s
sorting score ...
        ... done
Elapsed time at end of score sort: real: 0.014s, CPU: 0.013s
graphics suppressed, ascii substituted
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
writing 512-byte blks of shorts to out.aiff (AIFF)
SECTION 1:
ftable 1:
ftable 1:       32768 points, scalemax 1.000
               _--'''''--_
            _-'           '-_
          _-                 -_
         .                     .
       _'                       '_
      -                           -
    _'                             '_
   .                                 .
  -                                   -
_'_____________________________________'________________________________________
                                        '_                                     .
                                          .                                   .
                                           -                                 -
                                            '_                             _'
                                              .                           -
                                               -_                       _'
                                                 .                     -
                                                  '.                 .'
                                                    '._           _-'
                                                       -.._____.-'
new alloc for instr 1:
new alloc for instr 1:
B  0.000 ..  0.333 T  0.333 TT  0.333 M:   4642.5
new alloc for instr 1:
B  0.333 ..  0.500 T  0.500 TT  0.500 M:   6931.6
B  0.500 ..  0.666 T  0.666 TT  0.666 M:   6953.1

…

B 79.000 .. 79.333 T 79.333 TT 79.333 M:   6914.3
B 79.333 .. 79.500 T 79.500 TT 79.500 M:   8910.6
B 79.500 .. 79.666 T 79.666 TT 79.666 M:   8895.3
B 79.666 .. 80.000 T 80.000 TT 80.000 M:   8201.5
B 80.000 .. 80.333 T 80.333 TT 80.333 M:   4642.5
B 80.333 .. 80.500 T 80.500 TT 80.500 M:   6931.6
B 80.500 .. 80.666 T 80.666 TT 80.666 M:   6953.1
B 80.666 .. 81.000 T 81.000 TT 81.000 M:   6960.3
B 81.000 .. 81.333 T 81.333 TT 81.333 M:   4642.5
B 81.333 .. 81.500 T 81.500 TT 81.500 M:   6931.6
B 81.500 .. 81.666 T 81.666 TT 81.666 M:   6953.1
B 81.666 .. 82.000 T 82.000 TT 82.000 M:   6960.3
B 82.000 .. 82.333 T 82.333 TT 82.333 M:   4619.2
B 82.333 .. 82.500 T 82.500 TT 82.500 M:   6139.1
B 82.500 .. 82.666 T 82.666 TT 82.666 M:   5568.4
B 82.666 .. 83.000 T 83.000 TT 83.000 M:   5406.0
B 83.000 .. 83.333 T 83.333 TT 83.333 M:   3078.1
B 83.333 .. 83.500 T 83.500 TT 83.500 M:   3828.5
B 83.500 .. 83.666 T 83.666 TT 83.666 M:   3250.7
B 83.666 .. 84.000 T 84.000 TT 84.000 M:   3085.9
B 84.000 .. 84.333 T 84.333 TT 84.333 M:   1537.0
B 84.333 .. 84.500 T 84.500 TT 84.500 M:   1518.0
B 84.500 .. 84.666 T 84.666 TT 84.666 M:    970.8
B 84.666 .. 85.000 T 85.000 TT 85.000 M:    765.8
end of section 1         sect peak amps:  13413.9
inactive allocs returned to freespace
SECTION 2:
end of section 2         sect peak amps:      0.0
Score finished in csoundPerform().
inactive allocs returned to freespace
end of score.              overall amps:  13413.9
           overall samples out of range:        0
0 errors in performance
Elapsed time at end of performance: real: 0.645s, CPU: 0.639s
256 512 sample blks of shorts written to out.aiff (AIFF)



pi@bawor:~/Projects/bolprocessor/ctests $  ../bp -gr.NotReich -d --midiout
Bol Processor console app
Version 2.9.8 (Jul  5 2020)
This is a beta version for evaluation...
Reading grammar file -gr.NotReich...
BP2 Console completed initialization.
seed 1 = 1593984807
seed 2 = 20588
Err. GetTextChar(). pos out of range
TextInsert(Trace):
Compiling alphabet
Err. GetTextChar(). pos out of range
Looking for time patterns
Err. GetTextChar(). pos out of range
Err. GetTextChar(). pos out of range
Compiling subgrammar #1
Compiling subgrammar #2
Err. GetTextChar(). pos out of range
Errors: 0
Producing item(s)
Computing item
Subgrammar 1/2
Subgrammar 2/2
Buffer limit expanded to 1500
Buffer limit expanded to 2250
Buffer limit expanded to 3375
Buffer limit expanded to 5062
Interpreting structure
Expanding polymetric expression
Dur = 85 ticks  Prod = 6  [883 objects]  (no compression)
Expanded polymetric expression would contain 1207 symbols
Creating phase diagram.  (No compression)
Time-objects created: 50.  Estimated: 882
Time-objects created: 100.  Estimated: 882
Time-objects created: 150.  Estimated: 882
Time-objects created: 200.  Estimated: 882
Time-objects created: 250.  Estimated: 882
Time-objects created: 300.  Estimated: 882
Time-objects created: 350.  Estimated: 882
Time-objects created: 400.  Estimated: 882
Time-objects created: 450.  Estimated: 882
Time-objects created: 500.  Estimated: 882
Time-objects created: 550.  Estimated: 882

…

434 objects done out of 870
426 objects done out of 870
438 objects done out of 870
446 objects done out of 870
465 objects done out of 870
477 objects done out of 870
479 objects done out of 870
493 objects done out of 870
500 objects done out of 870
534 objects done out of 870
532 objects done out of 870
555 objects done out of 870
549 objects done out of 870
560 objects done out of 870
569 objects done out of 870
582 objects done out of 870
594 objects done out of 870
607 objects done out of 870
617 objects done out of 870
628 objects done out of 870
633 objects done out of 870
647 objects done out of 870
654 objects done out of 870
669 objects done out of 870
677 objects done out of 870
699 objects done out of 870
711 objects done out of 870
713 objects done out of 870
728 objects done out of 870
743 objects done out of 870
746 objects done out of 870
757 objects done out of 870
769 objects done out of 870
780 objects done out of 870
793 objects done out of 870
808 objects done out of 870
813 objects done out of 870
825 objects done out of 870
837 objects done out of 870
846 objects done out of 870
858 objects done out of 870
870 objects done out of 870
New project memory use: 55449 [leaked: 0]
This session used 484 Kbytes maximum.  9190 handles created and released. [0 bytes leaked]



pi@bawor:~/Projects/bolprocessor/ctests $ ../bp -gr.NotReich -d --rtmidi
Bol Processor console app
Version 2.9.8 (Jul  5 2020)
This is a beta version for evaluation...
Reading grammar file -gr.NotReich...
BP2 Console completed initialization.
seed 1 = 1593984925
seed 2 = 16162
Err. GetTextChar(). pos out of range
TextInsert(Trace):
Compiling alphabet
Err. GetTextChar(). pos out of range
Looking for time patterns
Err. GetTextChar(). pos out of range
Err. GetTextChar(). pos out of range
Compiling subgrammar #1
Compiling subgrammar #2
Err. GetTextChar(). pos out of range
Errors: 0
FlushDriver(): null driver wrote 0 events.
Producing item(s)
Computing item
Subgrammar 1/2
Subgrammar 2/2
Buffer limit expanded to 1500
Buffer limit expanded to 2250
Buffer limit expanded to 3375
Buffer limit expanded to 5062
Interpreting structure
Expanding polymetric expression
Dur = 85 ticks  Prod = 6  [883 objects]  (no compression)
Expanded polymetric expression would contain 1207 symbols
Creating phase diagram.  (No compression)
Time-objects created: 50.  Estimated: 882
Time-objects created: 100.  Estimated: 882
Time-objects created: 150.  Estimated: 882
Time-objects created: 200.  Estimated: 882
Time-objects created: 250.  Estimated: 882
Time-objects created: 300.  Estimated: 882
Time-objects created: 350.  Estimated: 882
Time-objects created: 400.  Estimated: 882

…

Time-objects created: 800.  Estimated: 882
Time-objects created: 850.  Estimated: 882
Correction factor = 1.000
Setting time streaks
Positioning 870 sound-objects
870 objects. No compression.  Sequence 1/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 2/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 3/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 4/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 5/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 6/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 7/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
870 objects. No compression.  Sequence 8/8
Sizing objects
Setting limits
Placing objects
Solving constraints
Calculating global drift
Calculating legato/staccato
FlushDriver(): null driver wrote 1435 events.
New project memory use: 55449 [leaked: 0]
This session used 484 Kbytes maximum.  9190 handles created and released. [0 bytes leaked]


I am attaching the build-output, if you’re interested in the warnings/details. Sending a binary makes no sense, I think?