<br><br><div class="gmail_quote">On Sat, Feb 11, 2012 at 10:25 AM, Rafał Cieślak <span dir="ltr"><<a href="mailto:rafalcieslak256@gmail.com">rafalcieslak256@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Though I like Fons' suggestion concerning jumping to the nearest bar,<br>
that seems a reasonable solution, will try to implement that once.<br>
</blockquote><div>That would be great: Currently there is a bit of drift between the programs, I reckon its in my own code<br>as the current transport / beat system is pretty basic and untested. It will be rewritten at some point to<br>
include JACK transport & BBT, but its not high on the priorites list :)<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Maybe I wasn't clear about the tags - these have nothing to do with<br>
OSC's own tags, and are indeed predefined, so that harmonySEQ will<br>
react the same manner each time.<br></blockquote><div>Yes, get you know. I meant consistent across different HarmonySeq projects,<br>but I realize now that's not possible due to the configurable nature. Basically<br>
the user will need to tell harmonySeq what it needs to do per scene of Luppp.<br><br>That's the best way to go for now. It works so I'm happy with that! If we could implement<br>Fons' beat sync idea (just for beats, sending BPM is no problem) that would be great :)<br>
-Harry<br></div></div>