Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> 
wrote:
>
> --- In bc2000@yahoogroups.com, "islandgroove2002"
> <islandgroove2002@> wrote:
> > Anyone know how or if it is or would be possible to convert the 
> > snapshot received by BC Manager into a Standard midi file that 
could be 
> > played in my host (via iac bus) in order to transmit all 
parameters to 
> > mapped controls when the midi clip was triggered?
> 
> What exactly would you want to be able to save to a standard MIDI 
file?:
> 
> Messages recorded in the "MIDI input messages" window?
> 
> Or "custom output" messages? Such a conversion would be limited in 
the
> sense that custom output may contain items other than MIDI bytes,
> which of course cannot be saved to a MIDI file. And of course 
snapshot
> MIDI messages converted to custom output have lost any timing
> information, so their timing values would all have to be set to zero
> in the MIDI file.
> 
> To summarize: saving actual MIDI messages from the "MIDI input
> messages" window to a standard MIDI file is a lot more 
straightforward
> to implement, but it depends on your situation whether that suffices
> your needs.
> 
> Mark.
>
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.
I don't think timing information would have any relevance, I am 
looking to capture a set of constant values in the form of a midi 
file that in turn could be played back into my sequencer that 
would "trick" the externally mapped controls within my sequencer into 
thinking every fader, rotary and button on the Behringers had just 
sent a "current position" signal.

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.

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 could send you a midi file from Ableton Live containing the 
supposed snapshot from the Behringer if that would be usefull?

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.