hey axel,

thanks for a great report.

the setscale bug is a good one. damn integer maths! i don't think
anyone has tried 64 steps per bar before. i will take a look at it
very soon because as you found out it's possible to crash the
sequencer with it.

version 1.1 of MRP does support midi sync reception. check out the
"midisync <portnumber>" command and let us know how it works for you.
works OK for me.

point taken on the long commands. i will put in appropriate
abbreviations in the next release. meanwhile you have full c-shell
type history, so you can type !ran to (for example) the last
randomise command you did.

tx
j



>hi, i really enjoy checking out mrp, it works fine on my ibookG4
>running Live5.2> MOTU
>MicroLite Midi interface> Access Virus.
>
>I quickly switched from the GUIed App to the commandline version,
>but only because the
>App doesnt offer MIDIsync yet which i found rather essential. I let
>Live generate the clock
>and send it to the IAC bus from where MRP picks it up. MRP triggers
>the virus which is
>then recorded by Live in perfect beats and bars. I really hope
>you'll include the MIDIsync it
>in the next version of the App as well.
>
>A problem i encounter using the commandline: entering "setscale 1
>64" and then "di"
>brings up an overview of 96 steps length - instead of 64. i also
>managed to produce a
>"Bus Error" by repeatedly doing setscale and di, but this happenend once only.
>
>If you plan to continue the commandline version as well, I'd like to
>suggest keeping the
>commands shorter ... commands like "randomvelocity" are just tooo
>long, how about
>"randvel" or better "rvel" ?
>
>also, i was about to suggest including sequencing MIDIcc, but i just
>read about your plans
>for 2.0, and saw you're gonna do it anyways which is great.
>
>thanks again for this fun app,
>axel