MIDI clock and start fixes
Hello everyone,
We have greatly improved the handling of MIDI clocks and fixed a MIDI Start problem.
It works very nice so far.
Available in BeatMaker 2.5 soon !
Cheers,
Mathieu.
We have greatly improved the handling of MIDI clocks and fixed a MIDI Start problem.
It works very nice so far.
Available in BeatMaker 2.5 soon !
Cheers,
Mathieu.
Comments
When I open new Project and after work I decide to "Save Ass", write name and continue to work on it, need that the Project now save the "AutoSave" on my new name of the Project and No on "Last Session", because for two times I change with New Project and they save on my project and I lose it....
I think that the solution is that every time you open BM2 he ask you to make a "New Project" with new name (like Logic or ProTools) for continue to "AutoSave" any project on his name...
Please....I have lost great tracks
I want to use BM live as master sequencer, combining external MIDI hardware with BM instruments, but I encounter a delay on the outbound clock and midi events that makes it unviable.
Even with an 'acceptably perfect' MIDI sync (Funkbox…) the receiving devices can introduce unpredictable latencies, so I think it is essential to have a manual *negative* latency adjustment, so that the clock and events go ahead of main time to external devices.
By the way, currently I see no effect when I try to use the *positive* latency adjustment in the MIDI settings.
Perhaps the solution is already there, but for some reason does not work or I did not make it work.
As of 2.5, leaving the MIDI latency to 0 will provide best results in most conditions.
I'll wait hopefully for 2.5
Anyway, could you tell me if the MIDI latency adjustment is working properly, and what could I be doing wrong in that case?
If you're connecting apps locally, then you don't really need to induce latency, so you can set it to 0. If you are using MIDI hardware via the CCK or device dock connector, 5 to 20 ms seems appropriate.
If you are using MIDI-over-WiFi, 25 to 50 ms will work in most case, but I'd suggest using a ad-hoc WiFi connection (1 peer connected to 1 peer) to reduce the latency. As you might already know, WiFi is subject to interferences, which leads to packet drops, latency peaks; this is really not optimal to achieve perfect synchronization !
The 2.5 update will really tighten the overall MIDI synchronization via clock and sequencer messages. We'll communicate on the update pretty soon !
Best,
Mathieu.
As I said, I use MIDI hardware via iODock, but I don't noticed any effect when I tried to use the latency adjustment before.
Don't know exact milliseconds, but is around 1/48 at 120 BPM, far more than 20 ms, I think, and clearly audible.
I'll try again, while wait for the 2.5 version.
By the way, congratulations for your great product and thanks for keep working on it.