Arturia Forums
Hardware Sequencers => BeatStep Pro => BeatStep Pro - Technical Issues => Topic started by: guidewire on June 24, 2017, 08:35:48 pm
-
I got the newest firmware installed last night and was playing around with things. At one point I turned on the "global tempo" while bsp was playing and then switched to a new Project. I poking around with the other "control mode" toggles before switching over. I think it got to the end of the first new pattern and locked the whole device up. I couldn't select any of the tracks and none of the buttons functioned. I turned it off and back on and it ran fine after that. I've never had a lock up like that before. I'm not sure I can provide any more info on what was happening when it locked.
-
Hi guidewire,
I'm really sorry to hear about that.
Could you please give more infos ?
When the bug happens did the sequencer was still running ?
Do you remember if "wait to load pattern" was on ?
Did you change "wait to load project" option in MCC ?
Best
-
When the bug happened the sequence seemed to get stuck on the last note.
I didn't edit anything from the MCC and I'm fairly sure the "wait to load pattern" was off.
I'll try to recreate what I did tonight and see if I can make the same thing happen.
-
Did you use the touch strip ?
-
I was trying alot of things and could have. I can't say for sure. The clearest detail was me changing from one project to another. I tried recreating it last night to no "success".
-
I got the newest firmware installed last night and was playing around with things. At one point I turned on the "global tempo" while bsp was playing and then switched to a new Project. I poking around with the other "control mode" toggles before switching over. I think it got to the end of the first new pattern and locked the whole device up. I couldn't select any of the tracks and none of the buttons functioned. I turned it off and back on and it ran fine after that. I've never had a lock up like that before. I'm not sure I can provide any more info on what was happening when it locked.
+1. I have had two total lockups (all the lights that were on when the lockup happened frozen but no response from any buttons) in the last 2 days. Latest firmware installed. First time, I was using MIDI out to play notes on a Korg Monologue and the second time CV pitch and gate from Seq 1 to a Makenoise 0-Coast. Also, the first time was using the internal clock and the second was syncing to a Drumbrute via clock out.
This is not good - I've had the BSP for about 5 days. That is not a good crash rate. It needs addressing urgently as I'm very tempted to return it.
-
Hi could you save all your projects in the mcc and try a hard reset by pressing PRST <<>> LST STEP buttons and turning on the bsp . also do you have the latest FW .Remember all projects will be lost if you do not save them first to the mcc.
Terrym
-
Thanks. Done that and have had no problems yet...Not really fully tested, but as I say, good so far. Fingers crossed.
I really hope it stays working because apart from that, it's a pretty brilliant unit. :)
-
I got the newest firmware installed last night and was playing around with things. At one point I turned on the "global tempo" while bsp was playing and then switched to a new Project. I poking around with the other "control mode" toggles before switching over. I think it got to the end of the first new pattern and locked the whole device up. I couldn't select any of the tracks and none of the buttons functioned. I turned it off and back on and it ran fine after that. I've never had a lock up like that before. I'm not sure I can provide any more info on what was happening when it locked.
+1. I have had two total lockups (all the lights that were on when the lockup happened frozen but no response from any buttons) in the last 2 days. Latest firmware installed. First time, I was using MIDI out to play notes on a Korg Monologue and the second time CV pitch and gate from Seq 1 to a Makenoise 0-Coast. Also, the first time was using the internal clock and the second was syncing to a Drumbrute via clock out.
This is not good - I've had the BSP for about 5 days. That is not a good crash rate. It needs addressing urgently as I'm very tempted to return it.
+2. I have had 5 consecutive lockups in less than two hours. I updated to the latest firmware yesterday and was happy with the added functionality.
Today I was running the beatstep pro in internal sync mode, powered by usb, not connected to a PC.
I was sequencing:
- System-1m with sequencer 1 pitch and gate outs
- Modular synth with sequencer 2 pitch and gate outs
- TR-09 through midi out
,
Everything was working fine until I pushed the button to advance to the next pattern on sequencer 1, and the whole thing locked up. The lights that were on stayed lit, and all signals to the synths stopped. No response to any button press or combination of buttons pressed. Upon restarting the beatstep pro, everything went back to normal. I fooled around a bit more, and after about 15 minutes of constant playing, the same thing happened, this time while I was pressing the "pattern advance" buttons on both sequencer 1 and sequencer 2 simultaneously. I was able to replicate this "freeze" 3 more times, always after pressing a button in the green and/or yellow sequencer sections. Before a freeze happens, I can press buttons in these areas as quickly as I like, in any pattern or combination.
I've never experienced a lockup like this before, and have used the beatstep pro regularly for at least 4 months.
I hope this info helps and that the error is on my end. Any help is appreciated.
[edit] I executed the hard reset and haven't been able to replicate the lockup. Hopefully this fixed it.
-
Hi Efadis,
That's a very strange behavior. I've been testing it here and I didn't reproduce it.
Could you please tell me :
- What was the previous Firmware on your BSP before updating ?
- Do you have polyrythm pattern on drum sequencers ?
- What was your pattern direction, time division ?
- Are you in wait to load pattern mode ? (shift + step 14)
If you don't reproduce after a reset factory it could mean that the problem comes from the last firmware you had on the machine...
-
Had three lockups too after using the touch strip. :'(
polyrythm on, swing 67%
-
Hi Efadis,
That's a very strange behavior. I've been testing it here and I didn't reproduce it.
Could you please tell me :
- What was the previous Firmware on your BSP before updating ?
- Do you have polyrythm pattern on drum sequencers ?
- What was your pattern direction, time division ?
- Are you in wait to load pattern mode ? (shift + step 14)
If you don't reproduce after a reset factory it could mean that the problem comes from the last firmware you had on the machine...
Hi ben arturia, thanks for the response!
I just reproduced the lockup today after fooling around with a project. It happened after about 15 minutes again. It seems to occur when I am editing and saving patterns on the fly while changing patterns on the sequencer 1, sequencer 2, and drums. It works great, and then it just locks up while I'm doing the exact same thing that I was doing 20 seconds before.
In response to your questions:
-I don't know what firmware I was running before updating to 2.0, as I had never connected it to a PC before doing the 2.0 update. So whatever it shipped with is what it was running.
-At the time of my first post, I did have polyrhythm mode turned on, although today I don't, and was able to reproduce the lock up. Something to note though, on sequencer 2, my first two patterns have last step set at 6. I was frequently (every 2-10 seconds, sometimes skipping from pattern1 to pattern 5 as quickly as i could) changing through the patterns. So, going from last step 6, to last step 16, last step 64 very quickly, and many times. I don't know if the beatstep pro handles polyrhythms the same as "last steps", but seeing as I feel that the lockup happens while switching through patterns, this might help someone replicate it.
-Pattern direction is always forward and time division is always 1/16
-I am not in wait to load pattern mode, and have never toggled it to my knowledge
I will try to factory reset it and see if I can reproduce the lockup again. I'd like to solve this, as I am looking at using the beatstep pro in some live settings soon and I've really enjoyed using it so far, especially after 2.0
-
Updated and played around with it last night. I did not try any new features. But I used the Drum sequencer using midi and the midi control center to change the instruments for the pads on the BSP (linked to an RX-5) and as a result lost every sequence I programmed in before on sequencer 1 and 2. I did not back them up (as I had never had any issues before). It was like it had reverted to factory settings.
Today, I just turned it on and this happened. Pressing any button did nothing. I turned it off and on twice afterwards before it powered up normally.
(http://i67.tinypic.com/wvzevm.jpg)
I just played around with the tempo speeding it up and slowing it down and whilst doing so, the BSP froze. Pressing buttons changed noting. I had to turn it off and on.
-
Y'all are scaring the shit out of me. I've not updated my firmware to 2.0x yet and I think I'm gonna wait until they fix the bugs before I do so.
Could different build date for the hardware make any difference to the firmware? I have a BSP from the first run (well I assume it is since I pre-ordered and received mine from the first distribution run in this country).
-
Y'all are scaring the shit out of me. I've not updated my firmware to 2.0x yet and I think I'm gonna wait until they fix the bugs before I do so.
Could different build date for the hardware make any difference to the firmware? I have a BSP from the first run (well I assume it is since I pre-ordered and received mine from the first distribution run in this country).
If you really want to try 2.0 just make sure you backup your projects, just in case anything crazy happens. Otherwise you can always revert back to your stable version of the firmware that you're running now. I'm confident that there will be a quick fix for all these issues.
Peace.
-
If you really want to try 2.0 just make sure you backup your projects, just in case anything crazy happens. Otherwise you can always revert back to your stable version of the firmware that you're running now. I'm confident that there will be a quick fix for all these issues.
Peace.
Cheers for the reply and the gentle prod to move forward! I know I want to, just last post about it breaking the machine really worries me....
Your user name is a palindrome!
-
Hi Guy,
I'm really sorry to hear about those issues.
I think that the bug comes from the previous firmware and not from the 2.0.
What you can try is :
- Back up all your project with the MidiControlCenter
- Reset you BeatStepPro to factory default.
=> Press PRST LINK/<</>>/LST STEP while booting the BSP
- Store your projects back
Please please let me know if it fix your problem.
-
Hi all,
Did you update your MCC?
When you perform the firmware update, the last MCC version is MANDATORY! Otherwise, your sequences are corrupted due to former MCC not knowing polyrhythm for instance.
Best,
Y.
-
Could different build date for the hardware make any difference to the firmware?
-> no.
-
One more thing, if you are in the case you did:
- No MCC update
- An update to FW v2.0.0.2
- Backup sequences into the MCC
- Reset factory
- Recall of your sequences from the MCC
You are going into troubles...
Please be sure perform the MCC update. Then do a reset factory. Then call back again your sequences from the last MCC.
Hope this help.
Y.
-
I used the MCC and shut it down then restarted the BSP and got this (see video below) until I unplugged the USB cable from my macbookpro.
Then the BSP booted normally, but everything was wiped. But the drum map was the same as the one I set up earlier.
https://flic.kr/p/W6rFZY
I just tried the same procedure again (although for ten minutes as opposed to an hour) and it functioned normally when rebooted.