Posts: 40
Threads: 15
Joined: Nov 2024
Reputation:
1
Read as my help in French and English about transmit tempo (BPM) in Midi equivalent.
https://forum.singularsound.com/t/how-to...ange/38156
It would be very useful to have a %miditempo% variable to transmit the midi equivalent of the current song's tempo. Furthermore, it would be wonderful to have an "internal" command able to send the right "Control Change" to a midi device. A command like "Tempo to Midi" would be really useful.
This command could be global, because it never happens to inform the MIDI that the tempo does not change if we change the song...
Thanks for reading
Posts: 14,093
Threads: 302
Joined: Apr 2012
Reputation:
264
I can add a new MIDI command type specific to the BeatBuddy (which would only be visible if Settings->MIDI Settings->MIDI Device Type was set to "BeatBuddy" which is something I would have to add), but it does not make sense to have a generic "Tempo to MIDI" command or anything of that nature, because the control change implementation used with the BeatBuddy is specific to the BeatBuddy. Every MIDI device can work differently and accept different messages.
I do not want to support a concept of "global" MIDI messages, as there are very few instances that I'm aware of where that makes sense or is useful in any way. I can consider adding an option specific to the BeatBuddy (something that can be set under Settings->MIDI Settings if MIDI Device Type is set to "BeatBuddy") to send a song's tempo when the song is loaded (if a tempo has been set for the song). I'm really going to need to hear from more BeatBuddy users though, because I have no idea how popular the BeatBuddy is or how many users utilize it.
Mike
Posts: 38
Threads: 6
Joined: Nov 2024
Reputation:
1
(12-18-2024, 05:05 AM)Zubersoft Wrote: I can add a new MIDI command type specific to the BeatBuddy (which would only be visible if Settings->MIDI Settings->MIDI Device Type was set to "BeatBuddy" which is something I would have to add), but it does not make sense to have a generic "Tempo to MIDI" command or anything of that nature, because the control change implementation used with the BeatBuddy is specific to the BeatBuddy. Every MIDI device can work differently and accept different messages.
I do not want to support a concept of "global" MIDI messages, as there are very few instances that I'm aware of where that makes sense or is useful in any way. I can consider adding an option specific to the BeatBuddy (something that can be set under Settings->MIDI Settings if MIDI Device Type is set to "BeatBuddy") to send a song's tempo when the song is loaded (if a tempo has been set for the song). I'm really going to need to hear from more BeatBuddy users though, because I have no idea how popular the BeatBuddy is or how many users utilize it.
Mike
Great, Better a little than nothing. The disadvantage of placing these commands in each song is that it must be done often whereas if a pedal or midi equipment is connected, there is no disadvantage in receiving the tempo information at each sound change... It would be easier. I don't think that "Beat Buddy" requires a special command, just the possibility of no longer calculating the BPM to MIDI conversion would be good, because the BOSS 500 is very popular and the command is different. So all that is needed is help with this conversion, then choosing the right Control Change is not difficult. Personally I would prefer a command not specific to BeatBuddy, but placed in the parameters or in a setlist command.
Posts: 40
Threads: 15
Joined: Nov 2024
Reputation:
1
Hello,
Do you plan to work on a better MIDI solution for tempo ?
In relation with song's tempo ?
Whe need it
Posts: 14,093
Threads: 302
Joined: Apr 2012
Reputation:
264
01-27-2025, 02:54 AM
(This post was last modified: 01-27-2025, 02:55 AM by Zubersoft.)
Eventually, sure, but I'm busy right now trying to finish other work that I started, and I have users waiting for other features that have been promised for a long time. What you are asking for is something that almost no other users are asking for or have requested, so I can't raise the priority on it.
Mike
Posts: 40
Threads: 15
Joined: Nov 2024
Reputation:
1
(01-27-2025, 02:54 AM)Zubersoft Wrote: Eventually, sure, but I'm busy right now trying to finish other work that I started, and I have users waiting for other features that have been promised for a long time. What you are asking for is something that almost no other users are asking for or have requested, so I can't raise the priority on it.
Mike
Yes, but imagine : the tempo could be sent to organ, tremolo, and also to à mixing table, looper etc, automatically, from Mobile Sheet. Probably people don't imagine possibilities
Posts: 38
Threads: 6
Joined: Nov 2024
Reputation:
1
And Midi 2.0 (Whifi and Ethernet) is comming soon : NAMM 2025
Posts: 40
Threads: 15
Joined: Nov 2024
Reputation:
1
03-16-2025, 10:38 PM
(This post was last modified: 03-16-2025, 10:39 PM by Jazzy Boomers.)
Hello,
We wait for a qind of %MidiTempo% variable, in relation with "Tempo" set for the song, useful for anny kind of Midi device receiving tempo or TapTempo synch (Drumer, Looper and now DELAY etc)
Would it be planed next times ?
Posts: 14,093
Threads: 302
Joined: Apr 2012
Reputation:
264
03-17-2025, 12:08 AM
(This post was last modified: 03-17-2025, 12:11 AM by Zubersoft.)
Every device may have a completely different mechanism to control the tempo (could be the MIDI timing clock message, a control change message, a system exclusive message, etc). Adding a way to insert the tempo as a value into any kind of MIDI command is not a trivial thing at all. The UI will not support that at all in its present state, and there is no where in the database for me to store that information at present. The MIDI logic is also not designed at the moment to pull values dynamically from other fields in a song (it expects constant values that were already assigned), so that would then require even more changes in the logic. I'm not even sure exactly how I would want to present that as an option to the user in the current UI, but even if I do make changes for that, then I have to make those UI changes on every platform and in the companion app. So this is not a small request that I can just slip into an update.
I should also add that inserting the tempo into a control change message requires splitting it up between the two fields, as they are limited to one byte (0-127). The implementation of that could also potentially be different with every MIDI device. I originally said I planned on adding something specifically for BeatBuddy, as I have documentation on what is expected with that device. Adding a solution that works for any device doesn't seem feasible to me unless they all use the exact same approach for setting the tempo.
Mike
Posts: 38
Threads: 6
Joined: Nov 2024
Reputation:
1
(03-17-2025, 12:08 AM)Zubersoft Wrote: ...
I should also add that inserting the tempo into a control change message requires splitting it up between the two fields, as they are limited to one byte (0-127). The implementation of that could also potentially be different with every MIDI device. I originally said I planned on adding something specifically for BeatBuddy, as I have documentation on what is expected with that device. Adding a solution that works for any device doesn't seem feasible to me unless they all use the exact same approach for setting the tempo.
Mike
Tempo implementation is all time the same : from 0-127 = 1 to 128 bpm, for the next, MIDI alwas use different CC command (Generally 0 and 1 2) to cover from 1 to 381 bpm...
Another solution is synchonise MIDI wit Mobilesheet, whitch is always the same command, for all devices...
Posts: 2,020
Threads: 314
Joined: Sep 2014
Reputation:
37
Please read again
"I'm busy right now trying to finish other work that I started, and I have users waiting for other features that have been promised for a long time. What you are asking for is something that almost no other users are asking for or have requested, so I can't raise the priority on it."
and stop nagging for an unimportant exotic feature.
Posts: 14,093
Threads: 302
Joined: Apr 2012
Reputation:
264
03-18-2025, 04:45 AM
(This post was last modified: 03-18-2025, 04:46 AM by Zubersoft.)
Tempo implementation is all time the same : from 0-127 = 1 to 128 bpm, for the next, MIDI alwas use different CC command (Generally 0 and 1 2) to cover from 1 to 381 bpm...
Please show me documentation from multiple devices that all have the same implementation for this. There is no "standard" for this with MIDI, and Control Change messages are device-specific in terms of what they do and how they are handled. Also, saying 0, 1, 2 means there is no standard way to do it for everything - i can't just "guess" which one might work for a given device, unless you are suggesting I start building information on every potential device out there that supports setting the tempo through MIDI.
Mike
Posts: 40
Threads: 15
Joined: Nov 2024
Reputation:
1
(03-18-2025, 04:45 AM)Zubersoft Wrote: Tempo implementation is all time the same : from 0-127 = 1 to 128 bpm, for the next, MIDI alwas use different CC command (Generally 0 and 1 2) to cover from 1 to 381 bpm...
Please show me documentation from multiple devices that all have the same implementation for this. There is no "standard" for this with MIDI, and Control Change messages are device-specific in terms of what they do and how they are handled. Also, saying 0, 1, 2 means there is no standard way to do it for everything - i can't just "guess" which one might work for a given device, unless you are suggesting I start building information on every potential device out there that supports setting the tempo through MIDI.
Mike
I'm not a specialist for Midi implementation but if I chain a Keyboard, a Midi looper and another synthetizer or a Midi Delay module, all have the same tempo. I have nothing to do...
It seems Midi receive synch information, for all...
Posts: 14,093
Threads: 302
Joined: Apr 2012
Reputation:
264
That's due to the MIDI clock being sent/transmitted ( http://midi.teragonaudio.com/tech/midispec/clock.htm), which MobileSheets already supports. That is completely separate from something like the BeatBuddy that requires the tempo to be set through a control change message. The BeatBuddy can already be controlled through the MIDI timing clock feature in MobileSheets if you change the metronome tempo. It just won't be as accurate as specifically setting the tempo you want (as there can be small variations depending on the type of device you have).
Mike
Posts: 40
Threads: 15
Joined: Nov 2024
Reputation:
1
(03-28-2025, 03:40 AM)Zubersoft Wrote: That's due to the MIDI clock being sent/transmitted (http://midi.teragonaudio.com/tech/midispec/clock.htm), which MobileSheets already supports. That is completely separate from something like the BeatBuddy that requires the tempo to be set through a control change message. The BeatBuddy can already be controlled through the MIDI timing clock feature in MobileSheets if you change the metronome tempo. It just won't be as accurate as specifically setting the tempo you want (as there can be small variations depending on the type of device you have).
Mike
Hi,
Accuracy isn't really the issue. I've tried many solutions, and your "Start Timer Using Metronome" command doesn't change anything on a Beat Buddy.
That's strange; other devices give the correct tempo...
Can you give an example of a command (in English) to synchronize your metronome with the Beat Buddy (even if the accuracy isn't absolute)?
Thanks
|