Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "islandgroove2002"
<islandgroove2002@...> wrote:
> I am assuming that what I would want to save to a midi file would be 
> the result of the "receive snapshot" function that opens the midi 
> messages window and displays what I assume is the "current state" of 
> the behringer device.

In that case, I could simply use the timing stored in the MIDI
messages window (possibly subtracting the first message's timing value
from all timing values so that the file's first message has a timing
value of 0).

> I don't think timing information would have any relevance,

Well, there might still be pitfalls here. E.g. does a program
correctly process a MIDI file in which all messages have a timing
value of zero? (A program might wrongly reorder the messages, based on
class or so...)

> Ableton Live already attempts to be able to record this information 
> directly into "midi clips", but for some reason the "Accuracy" of 
> Ableton captures from my Behringers "snapshot send" seem very erratic.

Hmm, this MIGHT be related to the point I've just made, but in
concrete terms I have no idea what goes wrong.

> The idea is that I can use cc messages from another device to 
> remotely trigger midi clips loaded in Live that will relay 
> my "snapshot" out to the IAC midi bus and back into Live as "current 
> value" remote control information which will set all of my mix 
> parameters in the Live set to exactly the way they were when I 
> capture the snapshot..
> 
> The problem that I "might" be having with Live capturing the snapshot 
> is how fast the Behringer sends the data.Therefore it might be a good 
> idea if the resulting midi had some length of the "current value" 
> controller information within it.Of course this might be what you are 
> talking about when you mention the lack of timing information in a 
> resulting midi file?

I'm not sure if I understand things completely, but it does look at
least possible that there is a timing issue here.

> I could send you a midi file from Ableton Live containing the 
> supposed snapshot from the Behringer if that would be usefull?

Go ahead. (Assuming the file isn't 10 megabytes long!)

> I also can't assure you that implementing this feature into your 
> program would solve my problem.It is possible that Live or the IAC 
> bus (midi yoke) is not relaying back the messages properly.

Yes indeed: if the problem doesn't lie with the MIDI file (in
particular the timing bytes), it wouldn't help.

But if it IS a timing problem, I can of course implement any scheme in
BC Manager, e.g.:
a. set all times to zero
b. have the times increment by a fixed amount
c. base the times on the original ones received in the MIDI message window

I'll see what I can do.

Mark.