Posts: 14,109
Threads: 302
Joined: Apr 2012
Reputation:
265
03-29-2025, 04:48 AM
(This post was last modified: 03-29-2025, 04:49 AM by Zubersoft.)
That was discussed in this thread: https://www.zubersoft.com/mobilesheets/f...-8905.html
Another user posted this:
Rather than using "Start Sending Timing Clock" as the midi command in MobileSheetsPro to send a tempo command to BeatBuddy, you are able to do the same with Control Change (CC) commands. The benefit of using CC is the tempo command is sent only once to BeatBuddy rather than continuously using the timing clock. This means during the song or when you exit the song, the tempo on the BeatBuddy can be changed manually. To set a tempo of 109bpm, the CC commands are CC106 0 and CC107 109. Please refer to the BeatBuddy manual under Tempo Control for more information.
That user was controlling the tempo on the BeatBuddy using the "Start Sending Timing Clock" message in MobileSheets, but found it was better to set the tempo through control change messages.
Mike
Posts: 42
Threads: 15
Joined: Nov 2024
Reputation:
1
03-29-2025, 09:39 PM
(This post was last modified: 03-30-2025, 12:22 AM by Jazzy Boomers.)
(03-29-2025, 04:48 AM)Zubersoft Wrote: That was discussed in this thread: https://www.zubersoft.com/mobilesheets/f...-8905.html
Another user posted this:
Rather than using "Start Sending Timing Clock" as the midi command in MobileSheetsPro to send a tempo command to BeatBuddy, you are able to do the same with Control Change (CC) commands. The benefit of using CC is the tempo command is sent only once to BeatBuddy rather than continuously using the timing clock. This means during the song or when you exit the song, the tempo on the BeatBuddy can be changed manually. To set a tempo of 109bpm, the CC commands are CC106 0 and CC107 109. Please refer to the BeatBuddy manual under Tempo Control for more information.
That user was controlling the tempo on the BeatBuddy using the "Start Sending Timing Clock" message in MobileSheets, but found it was better to set the tempo through control change messages.
Mike
Yes I know that solution, but you have to change command line each time the tempo is set on Mobile Sheet, twice...
Other devices are set by Master Midi
It is what we need : Mobile Sheet have to be the Master for song change AND for tempo setup.
Depite "Accuracy excuse", why Midi sychro time do not work on Mobile Sheet ?
See below what AI said about BeatBuddy tempo control :
The BeatBuddy drum machine can be controlled with MIDI to change its tempo using INC/DEC messages or the MSB/LSB system. You can also use a MIDI clock to sync the BeatBuddy with other MIDI devices.
INC/DEC messages
- Adjust the tempo up or down by 1 BPM
MSB/LSB system
- Skip directly to a specific tempo BPM
- Use the “NRPN Register” (Non-Registered Parameter Number) to control tempo
MIDI clock
- A signal that is sent over MIDI to sync several devices together
- Allows you to set two or more MIDI devices to one tempo
Posts: 14,109
Threads: 302
Joined: Apr 2012
Reputation:
265
03-30-2025, 04:51 AM
(This post was last modified: 03-30-2025, 04:54 AM by Zubersoft.)
"Accuracy excuse"? I just said that the accuracy is not perfect when using the MIDI time clock, not that you can't use the time clock. I really don't appreciate the tone you are taking. I already said I will consider adding a way to control the BeatBuddy tempo through a separate MIDI message when I can, but it's not the highest priority right now, and you don't get to push through your requests over the requests of others that having been asking for features patiently for far longer than you. You are going to have to be patient. Only you and swiss1000 have asked for something related to the BeatBuddy. I am getting requests for other features far more, so those are going to be higher priority.
I don't know why you are unable to get the MIDI clock to work for your setup - as mentioned, the other user had it working perfectly fine, so it seems to me like you have something misconfigured.
Mike
Posts: 42
Threads: 15
Joined: Nov 2024
Reputation:
1
OK, sorry for term of "excuse", but I found no exemple to link Mobile Sheet tempo via MIDI.
Do you have an exemple ?
Using windows version, I only obtain 59Bpm, wenever the tempo Mobiel Sheet si set to another value...
Posts: 14,109
Threads: 302
Joined: Apr 2012
Reputation:
265
This is what worked for me when I tested it both with my keyboard and with a metronome app:
1) Long press a song in MobileSheets to select it on the library screen, then tap edit song
2) Go to the MIDI tab, add a MIDI command and select "Start sending midi timing clock". Tap OK to create the command, and tap OK to save the changes
3) Load that song, open the metronome and adjust the tempo to 120 (or some other value)
After doing that, I see the tempo adjusted on the keyboard (or metronome app, depending on what I'm testing). I've also tested this with MIDI OX which is a MIDI testing tool which shows the proper tempo being driven by MobileSheets. The BeatBuddy should work in the exact same way as all these other things.
Mike
Posts: 42
Threads: 15
Joined: Nov 2024
Reputation:
1
If I set it below the tempo (like 45), it works roughly; the pedal displays 43 bpm.
If I set it to 60 bpm, the pedal syncs to 53 bpm.
If I set it to 120, the pedal locks to 79 bpm.
For 200 bpm, I get 152...
In my opinion, MS transmits a value but not an equivalent of the song's BPM.
Posts: 14,109
Threads: 302
Joined: Apr 2012
Reputation:
265
04-01-2025, 05:56 AM
(This post was last modified: 04-01-2025, 06:00 AM by Zubersoft.)
The MIDI beat clock can't be sent as a single fixed value. If you read up on it, you will see that: "Clock events are sent at a rate of 24 pulses per quarter note". So MobileSheets has to generate a significant number of MIDI messages in a very short span of time to drive faster tempos. If your device can't handle this, and falls behind on the timing, the tempo on the receiving device wil be incorrect. This can be especially noticeable over bluetooth, as bluetooth is not a particularly reliable protocol to use for high-speed messaging. That's why USB and wifi generally work better for things like this. To be clear, this is generally a hardware issue, not a software issue, especially when it comes to the timing with bluetooth. This is also why it's better to use a control change message with the BeatBuddy to drive the tempo, so that it's exactly what you want without any variation. If you find that MobileSheets is not handling the bluetooth messaging for the tempo as well as you would like, but you have another application on your device that does handle the messaging better, and supports virtual ports, you could send the message out of MobileSheets using a virtual MIDI port (with an application like loopMIDI), and then that other application can be the one communicating with the BeatBuddy. So check to see if another application on your device can use bluetooth to accurately drive the tempo on the BeatBuddy.
Mike
Posts: 42
Threads: 15
Joined: Nov 2024
Reputation:
1
04-01-2025, 08:38 PM
(This post was last modified: 04-02-2025, 01:37 AM by Jazzy Boomers.)
The connexion is USB, cable. And it works well from other devices (other than MS). One idea : Beat buddy keep last BPM synchronisation. Would it need longer time to "understand" transmission ?
If I use BB Manager, tempo is perfectly understant, even if I use Midi OX (Tool)
Another prolem : If a I send a MIDI STOP SYNCHRO the Beat Buddy climb and climb as reaching 300BPM (the max possible)
In addition :
I just performed a test with Ableton 12 : Tap tempo AND MIDI synch work. They is a difference of 1BMP sometime, never more. It seem having a bug in MS.
I also performed on Ableton the folowing test :
1 Lunch Albleton, start synch wit a xxx BPM (different eache tiME)
2 Stop Ableton
The tempo is set, stay in place until I luch Ableton again.
It is the same with other tools.
In use, it is not significant to have 59 or 60 BPM, or 119 in place of 120... Nevertheless if tempo is 59, stop change frome 59 to 60. MS works differently : the tempo is wrong (20-30% below)
Couldn't you suspend all process, sens a synch command and stop them after a second of time ?
With a Ipad (MAC) and a blutehoot (Yamaha) the midi solution appear relatively not correc : instead of 180 I have from 175 to 184...
Posts: 14,109
Threads: 302
Joined: Apr 2012
Reputation:
265
04-02-2025, 06:14 AM
(This post was last modified: 04-02-2025, 06:35 AM by Zubersoft.)
I found code for a high resolution timer for the Windows version, and it seems to have resolved all the accuracy issues. This will be included with the next update.
On a side note, I also tested this on Android - I used the USB connection for MIDI, hooked up MIDI-OX on my PC to the port that shows up, then synchronized the tempo. It was 100% accurate. If I set 218 on the Android device, it's 218 in MIDI-OX.
Mike
Posts: 42
Threads: 6
Joined: Nov 2024
Reputation:
1
04-03-2025, 12:30 AM
(This post was last modified: 04-03-2025, 12:31 AM by Swiss1000.)
BRAVO !
Posts: 42
Threads: 15
Joined: Nov 2024
Reputation:
1
Tank you, great reactivity.
By the way, you should explore possibility to "Synch and release", no necessity to maintain.
I tryed to place "Start Synchro" and just after "Stop synchro" to release ressources, but it is pobabily to fast behind, it do not works.
Posts: 14,109
Threads: 302
Joined: Apr 2012
Reputation:
265
Add a pause in between the two. So start the MIDI timing clock, pause for at least a second, then stop the MIDI timing clock. The pause command is something I added for situations like this.
Mike
Posts: 42
Threads: 15
Joined: Nov 2024
Reputation:
1
Thanks, hope you add "MIDI propagation", Have now 180 songs tu update
|