Tagged: midi multiboard golf
January 26, 2015 at 6:25 am #2831
First I want to say it´s a great piece of hardware and super fun and easy for music making, (multiboard, golf firmware)
The problem I got is sync with other gear.
When I try to sequence my OP-1 using the groovesizer as master clock and sequencer I get clock drift +- 2 bpm back and forth according to the OP-1. The reading in the first place is not even correct, if I set the bpm to 120 on the groovesizer the OP-1 gets a tempo of 118-119.
If I use an external clock source which is relatively stable (old tr 626), the groovesizer instead refuses to respond to midi start command in a constant manner, it is on beat the very fist step and then rushes to the next step, getting out of sync immediately, it then keeps going more or less offbeat until stopped.
Very frustrating and limits the usefulness a lot.
Is this software related or is it a limitation in the arduino that causes this behavior?
Otherwise it got great functionality and is loads of fun.
/bbkJanuary 26, 2015 at 1:33 pm #2832
It’s a combination of factors – my inexperience being not the least of them! I’ve not been able to get reliable start on the Atmega328 based Groovesizers. On the faster Arduino Due based TB2, responding to start is not a problem. I think the issue with the MB and RED is that my relatively long loop and slower processor delay the response to the start command. As soon as I find time, I’ll try and make a short loop while the instrument is waiting for sync to see if that helps.January 26, 2015 at 2:13 pm #2833
As for the unreliable BPM when outputting clock signals: these were my first implementations where I’m basically asking the processor to send clock signals please when it finds time and if it’s not too busy. It means other processes can have a higher priority, leading to inaccuracy in the clock. Starting with the Bravo firmware, the clock output is on an interrupt, meaning it fires exactly on time every time. I definitely need to update the clock on the Golf!January 29, 2015 at 6:28 am #2844
it would be very nice if it is possible to solve the sync and the bpm problem, then its possible to jam in sync with other machines.
also, if the mb golf is synced to an external device and after i use the reverse pattern function the position jumps always to the first step and not to the actual step like it is when the mb is not synced externally. so it also gets out of sync.
i like the mb concept, and its very nice to sequence the volca beats (or other drumcomputers) and make it swing.
jonathanJanuary 29, 2015 at 9:59 am #2846
Thanks for your feedback. I’m hard at work overhauling the sequencer of the Golf firmware and it should be ready in the coming days. I’ve implemented an interrupt-based internal clock, so that Golf’s sequencer and master clock output are rock-solid.
I’ve also implemented a short loop whilst waiting for MIDI clock so it should start reliably every time.
I’m almost there – now I just have to see about fixing the new bugs I introduced while implementing the updated clock ;^/February 1, 2015 at 3:54 am #2860
I really appreciate how you put effort in the MB although you got plenty of new projects going..
This made my day!
/bbkFebruary 3, 2015 at 3:27 pm #2876
Please try out the V026 firmware for the Golf. I think you’ll find it’s a big improvement.February 3, 2015 at 6:35 pm #2877
Yay! will do ASAP when I get back from work!
/MartinFebruary 4, 2015 at 3:32 am #2878
hello moshang, thanks, thats great news.
when i try to install the new firmware i get this error message:
“This report would have more information with
“Show verbose output during compilation”
enabled in File > Preferences.
Arduino: 1.0.6 (Windows 7), Board: “Arduino Mini w/ ATmega328″
HelperFunctions.ino: In function ‘void bpmChange(byte)’:
HelperFunctions:113: error: ‘Timer1’ was not declared in this scope
Setup.ino: In function ‘void setup()’:
Setup:7: error: ‘Timer1’ was not declared in this scope
with the same sett”
perhaps i missed something because i dont know that much about arduino.
but with the same settings i can install the old golf version.
jonathanFebruary 4, 2015 at 3:33 am #2879
“‘Timer1′ was not declared in this scope” is the main error message i think.
February 4, 2015 at 9:05 am #2883
- This reply was modified 2 years, 5 months ago by Tanoan.
Sorry, I forgot to add that you now need the Timer1 library installed for the firmware to compile. It makes it easier to work with the interrupts we need for the sequencer. I’ve reuploaded V026 with the library included in the Required Libraries folder.February 4, 2015 at 9:34 am #2884
thanks again, now its in sync. and the implemented time division is great. and even after playing a reverse pattern the sequencer jumps to the right position.February 4, 2015 at 9:39 am #2885
Great! Let me know if you run into issues.
You must be logged in to reply to this topic.