Been a while so It's time to check in.
Have read the mail, including that midi file bug posted earlier,
but have not read it for a few days. Will read after sending this...
Grab these commits (as always, in the muse CVS REL07 branch).
See the ChangLog for more...
Take a look at the new midi sync editor.
Read the tooltips and What's This for detailed explanations.
*** In particular, I want everyone out there to open the
sync editor, and tell me if the 'Sync Input Detect' lights
STAY on when your external devices are NOT playing.
In other words, do your devices transmit midi clock even when
stopped? (The lights should, of course, come on when playing).
If the consensus is yes, I may turn clock off in muse when stopped.
There seems to be some differences out there in the way some
software/hardware does it.
Note that I have not investigated or worked on MMC or MTC yet.
Observed problems with midi sync clock input - wandering or even
reversing direction song cursor ! If saved like that, .med file is
unplayable after reopening (tempomap->fix is negative !). Trying to fix...
You know, midi sync clock input actually works pretty good if you don't
fool around with the external tempo.
I had fun with two instances of muse. One sync'd to external, and the
other sync'd to the first muse instance. The external keyboard, and
the two instances of muse, kept step pretty good.
Anyways, still tweaking the code, pardon the messy comments in places.
Pardon the slight bug when loading a song with midi controller values
which you had set, not being applied to the device upon load.
And all the other stuff I was working on... I'm a workin' on it...
Now to actually read the last few days' mail...
Am Freitag, den 27. März 2009 um 21:31:23 Uhr (-0400) schrieb Tim:
> Hi there.
> Been a while so It's time to check in.
> Have read the mail, including that midi file bug posted earlier,
> but have not read it for a few days. Will read after sending this...
if this is related to my previous post: I have checked into it
again. The problems I had boil down to two issues:
1. The time signature is coded with length 2 which seems to be non
conformant to the Standard.
2. There is a Meta Message (Hex Code "FF 0F" IIRC), which isn't
documented in the standard. It seems to be used by Muse for the
comment of a Midi Track.
Maybe the second could be fixed by using the Text Meta Message (Hex
"FF 03") instead, as the Format of the Muse Export seems to be
equivalent to it anyway (ASCII characters).
I contacted the developer of common music and we agreed upon a flag
":non-strict" within cm to allow importing of non standard MIDI files,
so for me the files exported by Muse aren't problematic anymore, but
since it's a trivial fix I just wanted to let you know.