Hey Dave, not sure there every was a (public) reply to this, so...
On 10.02.2014 04:15, Dave wrote: > I've been looking for a software system that will let me do more of the song > sequencing (and even sound design) via a text file interface. I've just > found Beast, and it looks like it should support this mode of working. > > I've looked at a .bse file and most of it makes sense, but already I can > tell that I'll need to be able to find the details on some of the functions > in them (e.g. insert-notes). Does anyone know any pointers on how to get > into the details of this? Hm, what you're really asking for here is a formal description of the file saving format Beast has. Atm, noone has attempted to create that, it's actually encoded in bsestorage.cc and in the store_*/restore_* methods of the various Bse* classes. > Ultimately, I'd like to be able to use a mixture of guile code and commands > entered in the REPL to setup and audition sounds/songs. I've noticed that > Beast provides bsescm, but I'm not sure how to use it to invoke functions > provided by Beast itself (I'm a Guile/lisp newbie but I intend to learn). > Again, any pointers on how to proceed in this direction? Hm, Beast has scripts that fiddle with notes already, e.g. ./library/scripts/part-harmonic-transposer.scm But honestly, long-term I'd like to see bsescm replaced by a shell and scripts in Python. > Thanks, > Dave -- Yours sincerely, Tim Janik https://testbit.eu/timj/ Free software author and speaker. _______________________________________________ beast mailing list [email protected] https://mail.gnome.org/mailman/listinfo/beast
