Arturia Forums
Hardware Sequencers => BeatStep Pro => BeatStep Pro - Technical Issues => Topic started by: Terrym on September 23, 2015, 04:50:51 pm
-
Hi , The latest firmware is out 1.2.0.6
http://www.arturia.com/beatstep-pro/resources
Terrym
-
I've been using several of these "new features" since getting the BSP several weeks ago.
------------------------
New features
Looper, Roller fully functional
Enter note with pad/external midi note by holding a step button
Directly select drum by pressing a pad
Sequence Transpose by pressing Sequencer button and a pad
Pressing pad in Sequencer mode send Midi Notes
Load/Sync sequences and settings with MIDI Control Center >= 1.2.0
-----------------------
Glad you are fixing bugs- what about the main defect in the BSP (in my opinion of course)- not finishing the current sequence when switching to another one. Is that going to be addressed? It's a huge shortcoming.
-
Hi
Most of them so called NEW features were already in the previous version ?
And when my Daw clock is set to 120bpm the BSP still does not display the correct tempo
it jumps about all over the place. So that has not been fixed. SO NO HUGE IMPROVMENT HERE
And when I startup the BSP the displays DO NOT SHOW THE FIRMWEAR REVISION
So for me this was NOT a upgrade per say. But mainly bug fixes for those that use cv and gate
Come on Arturia pull your finger out and stop with the lies
cheers
kev
what about the main defect in the BSP (in my opinion of course)- not finishing the current sequence when switching to another one. Is that going to be addressed? It's a huge shortcoming.
and also copy seq1 to seq 2 ? whats happened to that chestnut?
the two main updates people were asking for and nothing ????????
-
Are you serious?
-
Is who Serious ???
-
Hi kev, the firmware is shown in the sequencer displays going down 1
2
0
6 on start up
Also the tempo drift is normal for midi clock but arturia have improved this not to affect sync drift.
seq to change at the end of a pattern will be coming
copy pattern from s1 to s2 will also come
Terrym
-
Coming when?
Copy sequence is even in the manual, which must have been written a couple of months ago.
-
Good Evening MR T
thanks for the info on the firmware display
I await the new features with baited breath
But why did Arturia Make a splash about NEW FEATURES
when 99% of them were already included
it makes them look complete idiots
Rant over
i'm of to take a chill pill
goodnight from sunny Spain
-
I'm playing a gig on friday, should I wait to upgrade or is this version stable?
I'm interested in the upgrade because I've had a few bugs while practicing.
Once the unit just stopped sending MIDI through, also the roller sometimes mutes a pad in control mode.
-
I'm playing a gig on friday, should I wait to upgrade or is this version stable?
I'm interested in the upgrade because I've had a few bugs while practicing.
Once the unit just stopped sending MIDI through, also the roller sometimes mutes a pad in control mode.
This is a stable version on my mac no problem and there are loads of fixes even i was glade this update came as the last one was really buggy
-
Good Evening MR T
thanks for the info on the firmware display
I await the new features with baited breath
But why did Arturia Make a splash about NEW FEATURES
when 99% of them were already included
it makes them look complete idiots
This was an error kev and has been removed . there was meant to be another new feature but it still needs some work.
-
once again, afraid to install update and crash the few main features working fine on my BsP. Will wait for users feedback and see... arturia, is hard to believe you (like Volkswagen)
-
I think the "NEW FEATURES" that were at the bottom of the release notes were from the previous update, and they forgot to delete them (they're gone right now).
And what about the switching of the pattern at the end of the current pattern ? I read on this forum that this function was already -implemented in some beta firmware prior to the release of the BSP. If this function is already coded, seeing the number of people asking for it, why wasn't it included in this update ? I, for one, won't buy the BSP if this is not implemented in a timely manner, in spite of that I'd like to support a company from my native country. So, when is the next firmware scheduled ?
-
With this new release the PC version of MCC the sync button and function is not available. You can still recall from and store to but the live sync to the device is now broken. You can tell when you launch MCC the sync button appears for only a moment before disappearing. MIDI console shows no comms going to or from the BSP.
-
From the release notes:
Improvements:
BeatStep Pro Sync function was replaced by drag and drop between device memories and local templates.
Drag and drop Controller Map, Sequences, Drum Sequences separately from local templates to BeatStep Pro.
Set drum map range to [0,127] for BeatStep Pro
New features from KeyLab 88 version 1.1 are accessible
Bug Fixes:
BeatStep Pro Sequencer 1 Gate type and Sequencer 2 CV type were inverted
-
Really glad some work on the firmware has been released, but I'm unsure which bug fixes have been implemented with this revision?
And Terry, we know you're not responsible. Thanks for the heads up about the release, and clarity on what is or isn't happening with this release.
I hope Arturia have you on the payroll. You are their saving grace.
-
Ok I see the bug fix list
Looks like the midi din sequencing issues still aren't fixed.
I can't believe it is a companies policy to release a product that doesn't do what it says on the packaging. I also can't believe the beta testers and staff missed so many issues.
V 1.2.0.6
New Features
Huge improvement of external clock handling for higher internal resolution
Show firmware version on the four sequencer displays during startup
Fixed Bugs
Switching from CLK to INT sync while the sequencer plays would sometimes freeze the sequencer.
Looper would not behave correctly when sync is set to "CLK"
When slaved to a MIDI clock, the sent clock was half the tempo
On Sequencer 2, legato playing while in record mode would cut the CV output when releasing the first note
Displayed tempo and real tempo sometimes would not perfectly match
In some cases, metronome notes were not sent in time with the external clock sync
Control Map was not loaded properly from the MIDI Control Center
MIDI was not always transmitted correctly when synchronized to an external clock
No gate off messages were sent when synchronized to an external clock (1 pulse per step)
Playback would stop when saving a project
Tempo display was wrong when slaved to USB in some DAWs
DIN 24 sync was late
When synchronized to USB, BeatStep Pro does not transmit the MMC Play message back.
-
With this new release the PC version of MCC the sync button and function is not available. You can still recall from and store to but the live sync to the device is now broken. You can tell when you launch MCC the sync button appears for only a moment before disappearing. MIDI console shows no comms going to or from the BSP.
OK, that is terrifying. Anyone else confirm this? Also, if I do update the firmware and run into this sync issue, will MCC allow the BSP firmware to be rolled back using the 1.1.1.6 .LED file?
-
Hi Bleo,
We've removed the Sync option which wasn't really relevant. Now you have to store or drag and drop your control map (instead of do it in real time when synced). That's not so terrifying ;)
-
@Valentin why isn't the real-time info in the MIDI console being shown or the hits to the pads in control mode while it is connected to the PC over USB?
-
Hi Bleo,
We've removed the Sync option which wasn't really relevant. Now you have to store or drag and drop your control map (instead of do it in real time when synced). That's not so terrifying ;)
Why remove something that worked well? That's really frustrating. I liked the realtime Sync functionality.
This is really irresponsible programming and a bad business practice. To get bug fixes, I have to settle for losing functionality I previously had. So either way, the unit doesn't function the way it was advertised when I bought it. Not cool.
So as I previously asked, is it possible to downgrade the firmware? I'm open to trying the new firmware, but I'd also like to decide for myself if these fixes are worth losing Sync.
-
Can anyone who's used the new firmware confirm the midi slave/clk issue has been resolved. Thank you.
-
Really glad some work on the firmware has been released, but I'm unsure which bug fixes have been implemented with this revision?
And Terry, we know you're not responsible. Thanks for the heads up about the release, and clarity on what is or isn't happening with this release.
I hope Arturia have you on the payroll. You are their saving grace.
Thanks for the support! And no I'm not on the payroll...
regards
Terrym
-
Ok I see the bug fix list
Looks like the midi din sequencing issues still aren't fixed.
I can't believe it is a companies policy to release a product that doesn't do what it says on the packaging. I also can't believe the beta testers and staff missed so many issues.
Is it not working for you as I'm sure its fixed
-
Clock sync no longer functions at all for me on the new firmware.
I tested the signal from my CR5000, into the BSP, to my mixer so I could hear the pulse.
I select clock mode, hit play, nothing. No sound.
Roll back to the previous firmware, works without issue.
I was looking forward to this release hoping Arturia would fix the issue with syncing external analog clock to midi time code.
Now I kind of just want my money back. Is there an older firmware floating around that has this functionality? I don't really care about using it with a computer, so whatever updates the new firmware brings aren't terribly relevant to me.
-
Clock sync no longer functions at all for me on the new firmware.
I tested the signal from my CR5000, into the BSP, to my mixer so I could hear the pulse.
I select clock mode, hit play, nothing. No sound.
Roll back to the previous firmware, works without issue.
I was looking forward to this release hoping Arturia would fix the issue with syncing external analog clock to midi time code.
Now I kind of just want my money back. Is there an older firmware floating around that has this functionality? I don't really care about using it with a computer, so whatever updates the new firmware brings aren't terribly relevant to me.
Same problem here. New firmware will not run as a slave. I did successfully roll back to 1.1.1.6 in the MCC. Sounds like it has something to do with the disabling the real-time sync functionality described above. Very disappointing Arturia. :(
-
"Sync" in the MCC software is not related to clock sync- that was just how edited settings were sent to the hardware.
And I'm glad they changed it, I thought it was counterintuitive to the way I expected the software to work...
-
Now I'm getting a stuck, then non-functional pad #8 (far right bottom / high C) after the first hit. Wasn't there before. Other pads seem to work fine.
Update: It's literally hit or miss on this pad 8 lockup issue. Sometimes plays fine other times not so much. Tried clearing out all the patterns, reloaded firmware and same thing. Didn't exist in previous firmware.
Hopefully we won't have to wait another month for some fixes.
-
"Sync" in the MCC software is not related to clock sync- that was just how edited settings were sent to the hardware.
And I'm glad they changed it, I thought it was counterintuitive to the way I expected the software to work...
Hi,
As Zymos says MCC Sync (which is now removed) has nothing to do with External Synchronization (USB, MIDI, CLK).
The Sync option in the MCC was there to be able to :
-change Control Mode Pads and Knobs in real time
-check MIDI I/O with the MIDI console
-click on a project or template to recall/store it
Ext Sync is used to synchronized two devices, one as master, the other as slave. The Ext Sync is still available and you can run your BSP as USB, MIDI or CLK slave or master. We've made some improvements on this side and it's working.
@neurator : it's strange that you're able to run as slave with the previous FW but not this one. Have you set everything correctly ? If you prefer the previous versions of MCC and BSP FW, you can download them at http://www.arturia.com/beatstep-pro/resources (click on [show archive]).
-
1.2.0.6: instead of properly fixing the MMC Start issue they stopped sending MMC commands at all. So you can't use it BSP as a transport control anymore.
EDIT: previously, I wrote about the device losing the sync after a minute or so - the problem was in the faulty USB cable (a stock one). I replaced the cable with a quality one (a thick cable with two ferrite rings on both ends with good connectors) - my BSP now runs flawlessly with an external clock.
-
@ Valentin my setup is unchanged between the older firmware and the newer. It simply works with the old, not with the new.
Perhaps there is another step I'm missing with the new firmware to work as a clock slave?
In my test setup I'm sending the clock out to my mixer audio in to hear the clock pulse. I hear nothing with the new firmware, but pulse is properly amplified with the previous firmware.
-
I only use midi din and din sync with this device. Clocking from external midi. Until I get hard confirmation from a customer that this is working in the new firmware I'm not upgrading. This revision seems to have more problems than the last.
Perhaps Arturia could outsource the work to someone who has more experience?
-
Ext Sync is used to synchronized two devices, one as master, the other as slave. The Ext Sync is still available and you can run your BSP as USB, MIDI or CLK slave or master. We've made some improvements on this side and it's working.
@neurator : it's strange that you're able to run as slave with the previous FW but not this one. Have you set everything correctly ? If you prefer the previous versions of MCC and BSP FW, you can download them at http://www.arturia.com/beatstep-pro/resources (click on [show archive]).
External sync is NOT working here either, and everything is set correctly. Like I said earlier I rolled back to the previous firmware and have no sync issues. There is definitely something wrong with the new firmware when multiple users are complaining from the same issues. Please sort it out.
-
I only use midi din and din sync with this device. Clocking from external midi. Until I get hard confirmation from a customer that this is working in the new firmware I'm not upgrading. This revision seems to have more problems than the last.
Perhaps Arturia could outsource the work to someone who has more experience?
Exactly. I thought Arturia has some connections with Roland? In any case, Arturia please do not mess up you already -quostianable pro- reputation by letting BSP on low importance. this thing CAN be the next big thing, if you listen to your users.
-
Now I'm getting a stuck, then non-functional pad #8 (far right bottom / high C) after the first hit. Wasn't there before. Other pads seem to work fine.
Update: It's literally hit or miss on this pad 8 lockup issue. Sometimes plays fine other times not so much. Tried clearing out all the patterns, reloaded firmware and same thing. Didn't exist in previous firmware.
Hopefully we won't have to wait another month for some fixes.
Uh oh, I was worried about this turning out to be a manufacturing issue. Same thing happened to me. Pretty sure it's mechanical and only coincidence that it started after the firmware update. Here's video of it happening to me before v1.2.0.6 even came out.
https://www.youtube.com/watch?v=spZDizmVCrY
I returned it to the retailer and got a new one. No mechanical issues with the new one... yet! /me crosses fingers.
Also, good to know we can roll back firmware!
-
Hi teezdalien,
Could you describe your issue ? How is your set up ? I don't understand your issue. With my set up din sync works great.
-
Hi teezdalien,
Could you describe your issue ? How is your set up ? I don't understand your issue. With my set up din sync works great.
Sure. I'm not using din sync per se, I've been trying to run the BSP as a slave being clocked from my 4MS Quad clock distributor euro module in CLK mode. The clock is patched out from the QCD into the CLK IN on the BSP. When pressing the play button on the BSP the sequences don't play, ie: the white LED for the steps doesn't show and there's nothing coming out from the BSP at all. The other sync modes show this same (lack of) behaviour. The only mode that seems to play any sequences is the INT mode. All of the modes still play sequences with the previous firmware, which leads me to think it's not the hardware that's the problem. I can upload a video demonstrating this if it helps. Any help solving this would be really great.
I'm running the MCC on a Windows 10 64bit machine as well, in case it's platform related.
-
@teezdalien The BSP when ext synced (USB, MIDI or CLK) absolutly needs a clock to run. If it receive no clock (from USB, MIDI or clock) it can't sync and so pressing Play on the BSP will just lit the Button but nothing will be play. Could you check that you really send a clock ?
-
The sequencers still go out of synch when using alternate directions. In this clip I set sequencer 1 to control the pitch of the VCO and the gate of the ADSR, while sequencer 2's pitch modulates the cutoff of the filter. Sequencer two runs in alternate mode.
At the beginning of the clip the sequence has ran for a couple of minutes, and you hear it is all way out of synch. Restarting the sequence tightens it up considerably:
https://www.youtube.com/watch?v=AdmAMu0iVr8
-
@teezdalien The BSP when ext synced (USB, MIDI or CLK) absolutly needs a clock to run. If it receive no clock (from USB, MIDI or clock) it can't sync and so pressing Play on the BSP will just lit the Button but nothing will be play. Could you check that you really send a clock ?
I don't mean to be rude because it seems you're the only person actually taking any interest in this issue I have, but I know what I'm doing and know how to sync different devices. I tried to contact Arturia for support last week and still haven't heard anything back. Please watch this video if you have the time, I can't make it any clearer obviously.
https://www.youtube.com/watch?v=bisgYtHeatI&feature=youtu.be
-
@teezdalien
Ok I think I know where the issue comes from. We've implemented in the last FW the standard sync. This standard uses TRS/3 points jack connector.
T (Tip) = clock signal
R (Ring) = state signal : DC 3.3V(running) or 0V (not running)
S (Sleeve) = signal ground
If you use TS/2points jack to sync the BSP there will be a short cut between S (ground) and R (state). The state will be forced to 0V. The BSP will read that as a non-running/stopped sequence. It works with the previous FW because it wasn't implemented in the standard way before.
So if you use TS jack try TRS ones. Hope it will solve your issue.
-
@teezdalien
Ok I think I know where is the issue comes from. We've implemented in the last FW the standard sync. This standard uses symetric/TRS/3 points jack connector.
T (Tip) = clock signal
R (Ring) = state signal : DC 3.3V(running) or 0V (not running)
S (Sleeve) = signal ground
If you use asymetric/TS/2points jack to sync the BSP there will be a short cut between S (ground) and R (state). The state will be forced to 0V. The BSP will read that as a non-running/stopped sequence. It works with the previous FW because it wasn't implemented in the standard way before.
So if you use TS jack try TRS ones. Hope it will solve your issue.
Thanks for the helpful reply. That actually makes perfect sense, though frustratingly using a TRS cable hasn't resolved the issue either. I'm going to try and source another cable, but the one I used has been working. Another thing I'm going to try is to update the firmware with a different computer/OS to see if it makes any difference. I'm totally at a loss now, but it is behaving as if it's not receiving a clock in when it should be. ???
-
I'm afraid that your 4MS Quad clock doesn't deal with state signal. To make the BSP works as slave you need a DC 3.3V-5V on the Ring. We're thinking to implement the feature to choose if you want to use or not state signal but I don't know if we could implement it in the next release.
-
I'm afraid that your 4MS Quad clock doesn't deal with state signal. To make the BSP works as slave you need a DC 3.3V-5V on the Ring. We're thinking to implement the feature to choose if you want to use or not state signal but I don't know if we could implement it in the next release.
Wow, if that's the case then you guys have really dropped the ball on this one... ::)
-
We thought sequence and that's why we work with a state signal (a clock alone does not have sense for sequencing without a state), but we have forgotten other uses you can have like (why not?) sync your BSP with an LFO or clock . We will try to solve it for the next version.
-
I have a weird thing going on ever since the latest firmware update, my sequencer one (linked via midi to my volca keys) won't mute, it just keeps playing but on a different tone. Anybody else had the same issue? any suggestions? my sequencer 2 (via midi to my volca bass) works normal.
is it a midi thing, is it he firmware update, or is it hardware related?
-
We thought sequence and that's why we work with a state signal (a clock alone does not have sense for sequencing without a state), but we have forgotten other uses you can have like (why not?) sync your BSP with an LFO or clock . We will try to solve it for the next version.
I would like to point out that page 52 of the manual says you can use a ts cable for clock pulse only. If you read it before purchasing it implies that modular clock only signals will work with the bsp (one of the reasons i bought it)
-
I have a weird thing going on ever since the latest firmware update, my sequencer one (linked via midi to my volca keys) won't mute, it just keeps playing but on a different tone. Anybody else had the same issue? any suggestions? my sequencer 2 (via midi to my volca bass) works normal.
is it a midi thing, is it he firmware update, or is it hardware related?
Don't have an answer, sorry. I also use the Volca, keys and bass, with the BSP. But I slave the BSP using my ES-1. Wondering if you use your BSP as the master clock or not since my biggest issue has been midi slave failing. Looking for any suggestions.
-
It seems to me that the documentation/communication with customers on what's being changed, what will work and will not, is really not up to the level of detail needed for us to make this a working part of our studios.
This is an easy fix, technicians behind the firmware can write comprehensive release notes advising users of changes in function.
However, the lack of or slow response from Arturia, and the knee jerk "are you sure it's sending clock" responses only make this process even more frustrating.
Meanwhile I'm still not convinced I should be upgrading, does midi external did clock work? Are live performances being recorded and sequenced correctly?
I'm starting to see how sophisticated the volca internal sequencers are now, in that they "just work", they may have significantly fewer features, but it's a worlds more positive experience than either of the beat steps Arturia has put out where the attitude sometimes feels like
"if it's not working, it's probably the customers fault"
or
"you're required to help us fix our product to make it do what we said it would do when you paid us"
-
Massive ball drop on clock sync. Almost makes me feel like no one at arturia is actually using a current modular system.
Maybe arturia can argue that a lot of customers are using vintage analog gear that may use this system, but then why use mini jacks? Surely a nod to eurorack users?
Trs-3 is not the standard for clocking in eurorack. I'm actually struggling to find one clock or sequencer module that actually uses it? My 4ms doesn't, doepfer doesn't, I've just opened the box and faced this after updating and having to dig around on forums... A return for me I'm afraid :(
-
Yeah, what gear actually runs synch over a TRS minijack?
-
We thought sequence and that's why we work with a state signal (a clock alone does not have sense for sequencing without a state), but we have forgotten other uses you can have like (why not?) sync your BSP with an LFO or clock . We will try to solve it for the next version.
Any eta on next version? Will it be a similar wait to the last one :/
-
Massive ball drop on clock sync. Almost makes me feel like no one at arturia is actually using a current modular system.
Maybe arturia can argue that a lot of customers are using vintage analog gear that may use this system, but then why use mini jacks? Surely a nod to eurorack users?
Trs-3 is not the standard for clocking in eurorack. I'm actually struggling to find one clock or sequencer module that actually uses it? My 4ms doesn't, doepfer doesn't, I've just opened the box and faced this after updating and having to dig around on forums... A return for me I'm afraid :(
Hey !
If you roll back to the previous firmware version (1.1.1.6), you'll be able to use your clock modules. From what I understood, the ability to switch between the two clock standard will be implemented in a future firmware, so hang tight :)
-
Prev versions dont have 1-step clock in and seq cv out working though.
A temp workaround is to use a stereo splitter cable and send a constant voltage down one side along with the clock. Which sucks a bit because i'm wasting a mixer channel generating a constant voltage.
I noticed once i had it working that the stop button overrides a high incoming run signal, so imo the play button should also override a low run signal
-
A splitter is the way to connect to your modular :
https://drive.google.com/file/d/0B-1e9zXr5JIlb3F0TEpBOG12TzA/view?pli=1
-
Hey !
"If you roll back to the previous firmware version (1.1.1.6), you'll be able to use your clock modules. From what I understood, the ability to switch between the two clock standard will be implemented in a future firmware, so hang tight :)"
Some people are told to wait for the next fw release, others are told to roll back, for some of them v1.2.0.6 just does the job.... what about to release customized firmwares? I mean one dedicated release per user... come on arturia, you can do it!
-
A splitter is the way to connect to your modular :
https://drive.google.com/file/d/0B-1e9zXr5JIlb3F0TEpBOG12TzA/view?pli=1
Only covers clock out though. Not everyone will have a static voltage source to use as run signal, or realise it's necessary
Filterseducer- we get that your upset, i think you're crossing the line into trolling now though
-
think what u want buddy, you're so free as I am. Btw, who are the "we" that you represent?
-
Forum has a "buddy list", but no ignore list. Too bad....
-
yes, too bad for you buddy :P
-
A splitter is the way to connect to your modular :
https://drive.google.com/file/d/0B-1e9zXr5JIlb3F0TEpBOG12TzA/view?pli=1
Lol, so basically arturia forgot to put a cable in the box? managed to get din sync, midi In and out though ???
Anyway, The frustration comes from customers feeling the firmware updates are regressing, lets hope the next ones not to far away and moves this device forward not backwards.
-
This clock in fiasco is terrible. What do I need to do to sync the bsp to a trigger pulse from my 808?
-
only the clock?