Thanks oktronic, have rolled back firmware and all good now. Will wait for the fix…
Trying to start/stop the looper on Eventide H9 with BeatBuddy. MIDI start and stop from BeatBuddy to H9 works well when there is a recorded loop in the H9 (makes the loop play and stop), but the BeatBuddy start command does not trigger a recording action when the looper is empty. Is this a firmware issue? Or any other idea on how to solve it? Thanks a lot for any help.
(tried with Firmware 3.9.3 and 3.8.0)
Sounds to me like an issue with the H9 not the BB. The BB is obviously transmitting MIDI Start and Stop, but the H9 doesn’t recognise MIDI Start as a signal to start recording when the looper is empty. There is no way that the BB can tell whether the H9 has a recorded loop or whether it is empty.
@ajerni
The Midi specification states that the start midi message should begin playback of a slave device. This is what is happening when the H9 has a recorded loop, it is playing back the stored information. If there is no information it will not play. The start command does not start recording, you should use a midi CC command for this.
That would be CC 13 (value 127) to be sent to the H9. How can I send that along when I start the BeatBuddy? I have the MidiMaestro as well, so should be possible to do it on one “kick” somehow?
In the H9 Looper docs however it is stated, that MIDI start message should trigger recording. That is where my first question came from.
Thanks for your help.
Hi All!
Although this post concerns more looping (here) I’m reposting here because I think I may have experienced some bugs in the latest firmware 3.9.3,
I recently purchased the Boss RC-500 looper along with the MIDI cables/adaptors to connect this unit with the BB for syncing.
This ongoing process of studying/practicing the sync between the two units led me to a few preliminary conclusions, which require further investigation and confirmation.
Summary:
i) RC500 (sync master) and BB (sync slave) seems to work fine in terms of sync, but it’s not exactly the kind functionality that I’m looking for, mostly because RC500 as master doesn’t support the BB versatility, e.g. how intro, main rhythm, etc start/stop automatically.
Anyways, I think I didn’t explore this approach enough so requires more experimentation on my behalf to understand the possibilities.
ii) BB (sync master) and RC500 (sync slave) looses sync when the fill “part1-fill3” is triggered from the song “Pop1-16ths”. This raises a suspicion that there’s a problem in this specific drum fill (sounds like that ends with a syncope). Other users reported similar problems with other songs, which raises suspicion of the latest firmware 3.9.3 update, as all complaining users were using the 3.9.x version. This requires further confirmation/testing.
For these reasons I kept testing/debugging the settings with this song and haven’t tested properly others.
For the second ii) approach I set BB and RC500 with the following settings (the parameters that seem relevant at the moment):
– BB SETTINGS (Firmware 3.9.3)
1) BB -> Main Pedal -> MIDI Settings -> MIDI IN -> System Real Time ->
1.1) Sync: enable
1.2) Start: enable
1.3) Stop: enable
2) BB -> Main Pedal -> MIDI Settings -> MIDI IN ->
2.1) MIDI In Channel Number: 16 (related to RC500 parameter a.4)
2.2) Note On: disable
2.3) Control-Change: enable
2.4) Program-Change: disable
3) BB -> Main Pedal -> MIDI Settings -> MIDI OUT ->
3.1) Output Type: Midi-out
3.2) Channel: 10 (related to RC500 parameters a.1 and a.3)
3.3) Sync: Always-on (important to be sync master, sends out midi tempo clock)
3.4) Start: Main Beat
3.5) Stop: Pause and End
3.6) Notes: disable
3.7) Next Part: enable
3.8) Time signature: enable
4) BB -> Main Pedal ->
4.1) Mute Pause: Midi-activated (!!!automatic when BB acts as slave)
4.2) Cue Fill Period: Next-half-beat (!!!)
– RC500 SETTINGS (Firmware 1.02)
a) Menu -> MIDI ->
a.1) Rx CTL: 10
a.2) Omni: off
a.3) Rx Note CH: 10
a.4) Tx CH: 16
a.5) Sync Clock: MIDI (or AUTO)
a.6) Clock Out: off (to be sync slave)
a.7) Sync Start: All
a.8) PC Out: off
a.9) MIDI THRU: off
b) Memory -> REC ->
b.1) Quantize: off (I also tried ‘on’)
b.2) Loop Length: Auto
c) Memory -> PLAY ->
c.1) Play Mode: Multi
c.2) Single Change: Loop End
c.3) All Start: All
c.4) TRK Chain: Parallel
d) Memory -> RHYTHM ->
d.1) Var.Change: Measure
d.2) BEAT: 4/4
d.3) Start: Rec End
d.4) Stop: Loop Stop
–Other observations:
––The time signature information sent by BB is not supported by RC500 apparently, perhaps a feature request to Boss for future firmware revisions. I imagine this is important if quantize is activated in the RC500. There is a parameter to change time signature under ‘Rhythm’ menu, but to the best of my knowledge it’s not accessible through MIDI messages.
––You might wish to disable BB ‘intro’ when RC500 is sync master. At the end of loop recording the RC500 sends a ‘start’ message to BB, if ‘intro’ is enabled BB begins the loop with the intro drum fill and then after the goes to the main groove.
Please share your experience and thoughts, I will had update this post has I gather more info.
Thank you
1 Like
Hi,
I tried 3.9.3 and found it unstable in my rig and have gone back to 3.80.
Feature request:
I use Camelot Pro for managing my rig (scene changes, etc.).
The CC102 scheme where it sends out the part number is less than ideal for Camelot Pro, which has a “Next Scene” remote control option.
Could you add a configuration setting the sends a specific CC/value when the pedal is held to transition to the next part?
Thanks,
Dov
I have been playing with 3.9.3 for about a week now. Mostly it seems all ok but I find every now and then I’ll transition to the next part and the screen will display transition but then just stay on the same part. It is very random so doesn’t do it in the same places all the time. I’d consider myself pretty efficient in using the BB so I know it’s not when I’m pressing the button. I’m a little concerned that it is actually displaying it is transitioning but then just stays on the same song part.
As I said though, it’s very random. I have gone over and over songs where it’s happened and never got it to happen again. I will keep playing with it for now but might have to go back to 3.80 if it keeps happening.
2 Likes
Hi,
Is there some development with this upgrade ? Are we going to have an official release soon ?
Thanks!
We’re ironing out kinks with the paused state and receiving commands, this should be ready very soon!
3 Likes
BeatBuddy firmware version 3.9.9 has been posted above for download and the changelog has been updated!
7 Likes
It is not on the website 3.8 is the latest download there.
The download is located at the top of this thread. Scroll up.
Mini bug and a feature request.
When you Pause in an Intro or Outro, the display shows Part 1of 2 (or whatever). I’m not certain why someone would Pause in an Intro or Outro though, so it’s probably not very important to fix!
Can we have the old Pause behaviour back as an option (Pause then Stop stops the song even if it has an Outro). It was a good way to stop the drums cleanly if something went wrong.
Thanks
1 Like
You might want to pause in an intro or outro if the song is in OPB format. So, yes, if you want that as a option to operate the other way, I’m all for options.
Very nice job on the 3.9 manual! When this is out of beta, please be sure this gets posted to the Beat Buddy product page and then remove the separate out of date Midi Manual.
3 Likes
Assuming you have tried the new update already, can we not Stop the song silently after Pause? do we have to play the Outro if it exists?
As far as I know, with this update there is no way to Stop silently after Pause, if you also want to use Outros. (Unless you start using MIDI commands in OnSong or an external Midi pedal).
Hey there,
That is a small polish but thank you, we will look into that eventually.
Good news, to keep with the previous behavior when the footswitch pedal is set to outro and BB is paused and the BB stops immediately, we have added the option to set the External Footswitch/MIDI Outro command to split from the BB Outro setting if it is enabled and stop the song immediately like it did on 3.8.0. Simply go to Main Pedal > Unpause Behavior > External Unpause and set to Outro stops song. That external Footswitch must be set to send Outro while playing/paused.
^
Thanks, it’s a labor a of love and badly needed update!
2 Likes
Great. Thanks!