|
From: Anthony K. <mai...@an...> - 2020-07-23 22:22:43
|
On 7/23/20, 5:25 PM, Bernard Bel wrote: > I also found out that we get an error message with an empty Trace file > when there is a mistake in the command, which is not the case here. I > got a mistake trying to run a grammar whose name contains a space… This > is now fixed by putting spaced names or paths between quotes. Yes, quoting or escaping spaces and some other characters like *? is necessary when constructing command lines. I'm not sure of all of the rules myself. Any online shell tutorial/reference should be able to clarify problems that come up. > I also completed the reformat_grammar() procedure after checking all > reserved words on BP2.9.8, many of which I had forgotten as they date > back to modelling drum improvisation! > > The files I modified are attached. They are also in > https://leti.lt/bolprocessor/ I'll check it out when I get a chance. > Indeed the crash log tells something but I am unable to make sense of > it! It might be difficult to trace the process on such a complicated > grammar. I use it only because it contains a great diversity of > instructions. So the error may just be stored on the to-do list. If I'm lucky, when I run this example in Xcode with the debugger it will just show me which line of code the segmentation fault occurs on. Then I can set an earlier breakpoint if necessary to understand how it got there. -gr.ShapesInRhythm does seem like a good test. :) > [...] Probably a few script commands will be used by the PHP > interface, e.g. load a file, produce x items etc. and executed via > command lines. I think a few of the planned command line "actions" were inspired by script commands: produce-items N, play-item N, expand-item N, etc. > At some point we may need to find a method for waiting for a mouseclick > or any human action triggering the performance of an item that has been > prepared. This and other custom or scripted "workflows" will be very easy to implement in client programs once the API is available (i.e. "BP4"). If it is needed before then, we can consider alternatives. > I am now tempted to work on the import of MIDI files into sound object > prototypes, and converting MIDI sequences to Csound. Looking at the C > code should make it easy. These operations might be good to implement as actions in BP console. That way we can use the existing code instead of "reinventing the wheel". Anthony |
