I have been further modifying your work because I myself am doing research for a Chance Music Piece to generate original readable notation in real-time for perfomance based off of things the computer has "learned" by analysis of people whom have previously played the "Mother" instrument. I have a Disklavier Upright Player Piano that has midi capabilities that will be used to "teach" it(This is the Mother instrument). I have accomplished Key Signature Modification and Time Signature, all of which were a real pain, so I am starting to second guess the process. Max Objects like coll and sprintf, possibly text though I have not tested yet, all use backslashes to indicate either escaping or "insertions", similar to the whole \r issue. Past that, the comma also has significance to max also, so when dealing with lilypond syntax(\relative c,,) it becomes cumbersome. I will keep investigating also, and try some your suggestions. I have been meaning to pick up Ruby, but never had a use for it in the stuff I do, but with this awesome little object you made, I now have an excuse. I will keep you up to date with my progress, maybe we can work out something fun and useful. This has lots of potential, and is a big hole in max IMHO, that needs to be filled.
Re: escaping backslashes
I have been further modifying your work because I myself am doing research for a Chance Music Piece to generate original readable notation in real-time for perfomance based off of things the computer has "learned" by analysis of people whom have previously played the "Mother" instrument. I have a Disklavier Upright Player Piano that has midi capabilities that will be used to "teach" it(This is the Mother instrument). I have accomplished Key Signature Modification and Time Signature, all of which were a real pain, so I am starting to second guess the process. Max Objects like coll and sprintf, possibly text though I have not tested yet, all use backslashes to indicate either escaping or "insertions", similar to the whole \r issue. Past that, the comma also has significance to max also, so when dealing with lilypond syntax(\relative c,,) it becomes cumbersome. I will keep investigating also, and try some your suggestions. I have been meaning to pick up Ruby, but never had a use for it in the stuff I do, but with this awesome little object you made, I now have an excuse. I will keep you up to date with my progress, maybe we can work out something fun and useful. This has lots of potential, and is a big hole in max IMHO, that needs to be filled.