- Oct 7, 2000
- 18,619
- 38,939
- Disclosures
- Endorsing artist: Musicman basses
The BeatBuddy Manager has arrived!
You can download it here:
http://mybeatbuddy.com/forum/viewtopic.php?f=16&t=374&p=1452#p1452
Sweet!
TalkBass has been independent since 1998. Add your voice.
Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
Join free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
The BeatBuddy Manager has arrived!
You can download it here:
http://mybeatbuddy.com/forum/viewtopic.php?f=16&t=374&p=1452#p1452
Is anybody else using this thing with a looper? My MIDI experience has been hit or miss. At first, it seemed like there was some drift when I put the Beat Buddy third in a MIDI chain with my looper after that. So I just hooked the Beat Buddy right up to my Infinity (using the BB for master tempo) and it seemed to improve dramatically. However, after rewiring my board (not suggesting a connection, that's just what happened), it seems like I'm getting just a bit of drift, and also using the start/stop footswitch function, the Beat Buddy will play a full measure before the loop restarts. Any ideas?
@Adamixoye
(1)Will the Beat Buddy pass MIDI THRU in addition to what it outputs? (So will it do THRU while also adding its own MIDI output or start/stop/clock?)
The BeatBuddy is not MIDI THRU because we output custom data from the Beatbuddy. The concept of a MIDI THRU is to send the same data that comes from the MIDI IN. We could add an option to change output between “Beatbuddy Midi out data” and MIDI THRU that would resend every data from the midi in. Would that be useful to you?
(2) What channel(s) is the Beat Buddy operating on for input and output (1-16/OMNI)?
There is no official channel for the Beatbuddy since the signal used are the “System Real-Time Messages” signals. Those signals don’t have specific operating channel since they are made to be use by all the channels (instrument) at the same time.
(3) What control codes (CC#s) and values control start/stop/tempo?
We don’t use control codes (CC#s) to control start and stop. We only use “System Real-Time Messages” signals. Controlling the tempo, like sending a command to set the tempo to 134 bpm, would be a little bit difficult since standard MIDI CCs control values range from 0 to 127. We need to use relative midi signals.
@Adamixoye -- we will have the THRU option for the next firmware update (coming very soon).
Seems like you figured out that the issue is that the infinity waits a full measure to implement the 'start' command after it is sent. This is something that needs to be fixed by Pigtronix. I'll let them know.
For everyone else, here is the thread discussing this issue: http://mybeatbuddy.com/forum/viewtopic.php?f=18&t=823&start=10