Arturia Forums
Hardware Sequencers => BeatStep Pro => Beatstep Pro - General Discussions => Topic started by: nectarios on July 18, 2015, 12:29:57 pm
-
Hello,
Got a Beatstep Pro a few days ago.
First impression is very good. I've already made a tune using just that and my modular and there is nothing better than something that inspires and makes things so precise and fun. A real game changer this thing is.
I am having some problems with it though.
For starters I am on Snow Leopard (10.6.8) so no joy using the software as its not compatible with Snow Leopard which I do not want to upgrade to a newer OS as its the most stable from my experience.
So my first problem is that the clock in/out is not working. It is but its sending some very fast clock out. Clock does nothing when I send clock via Make Noise Maths.
One way that I've found around this is to use one of the 8 drum triggers and make 16th trigger sequence and use the Beatstep as clock is this way and clock Maths, Rene...everything.
That works but not always, which brings me to my second problem.
Another problem is that does not happen very often but happens on every session is that after a while (over an hour) Beatstep sends random CV/Gate values, so random notes from VCOs, random triggers/clocks from the drum sequencer. I have to stop and run Logic Pro 9 and hope it might work but most times I have to switch it off and on until luck helps and it starts working as expected.
The SHIFT and >> does not copy patters from the first 16 steps to the available beats to easily get a 64 steps.
I also had ground noise but a 6 USB charger did the trick.
Note that I am using the USB connection to connect to my mac.
I will try using MIDI to sync it to Logic Pro, to make sure that its not Snow Leopard and Beatstep Pro issue when connecting via USB.
Is there a chance of making a Snow Leopard version of the Beatstep Pro software? That would be great.
Build quality is great. Love the lights and interface, so great job on making this.
Nectarios.
-
I wonder whether the previous posters issues with CV are also being replicated via MIDI as I have a similar sounding problem :-
Every now again a sequence on either channel will either skip a note, there is a very brief pause or no note off is sent to the sound module and a note sustains longer than normal.
It is a very irregular occurrence and I don't seem to be able to induce it but it happens regularly.
Sync is internal, it isn't connected to a PC and it happens with a direct connection to a modules MIDI in port - ie no thru box.
So reducing it down to the simplest set up ie MIDI out BSP to a single sound module and issue persists. Either sequence channel.
Just now a stuck note required a transport stop and start to clear it.
-
I am not sure what is wrong withe the BSP.
I use it in ableton and it has its own mind.
I create an empty pattern and every now and then it plays a note..
I fill the pattern and every x cycle it changes the pattern a little bit an restarting the pattern helps a bit.
No, i do not have any swing or randomness values set.
There is a small clip named ghost sends that someone made, that is a bit alike my problem...
https://www.youtube.com/watch?v=JNObwTheUA4
Yes, firmware is up to date.
It is like it is already said above: great build quality, crappy software...
I hope this will be fixed or someone enlightens me, what I am doing wrong...
-
Sounds like I am not alone...
Very disappointing.
Arturia - is this a known issue or some defective units?
And if a known issue when do we get aa fix?
-
For the moment I only use it to record the built sequences immediatly into ableton.. not exactly the best usage.
At least this is fine and the gernerating of patterns is very simple and elegant.
As I do not use CV Devices it is ok for me...
But I hope and in a way I am shure about this arturia will provide a general fix soon..
Not that this is more than hope :)
-
Hi all as mentioned in other threads have you been clearing all pattens after your first firmware update .even if theres nothing in the pattern please clear all by pressing shift and clear ptn on all 3 sections as i found the firmware corrupts anything stored .
i have 2 bsp and cannot repeat your problems i have one setup on cv equipment and one on midi /daw work.
There is a firmware update coming very soon.
hope this helps
Terrym
-
OK, will try that.
Thank you for support..
I must have overlooked that advice
-
Hi all as mentioned in other threads have you been clearing all pattens after your first firmware update .even if theres nothing in the pattern please clear all by pressing shift and clear ptn on all 3 sections as i found the firmware corrupts anything stored .
i have 2 bsp and cannot repeat your problems i have one setup on cv equipment and one on midi /daw work.
There is a firmware update coming very soon.
hope this helps
Terrym
I haven't done any firmware update, I just used it straight out of the box. Do I still need to clear all sequences on all three sequencers and try to build sequences with no sequences stored what so ever?
Is there a way to see what firmware I am on without using the software that is not compatible on my OS?
-
I wonder whether the previous posters issues with CV are also being replicated via MIDI as I have a similar sounding problem :-
Every now again a sequence on either channel will either skip a note, there is a very brief pause or no note off is sent to the sound module and a note sustains longer than normal.
It is a very irregular occurrence and I don't seem to be able to induce it but it happens regularly.
Sync is internal, it isn't connected to a PC and it happens with a direct connection to a modules MIDI in port - ie no thru box.
So reducing it down to the simplest set up ie MIDI out BSP to a single sound module and issue persists. Either sequence channel.
Just now a stuck note required a transport stop and start to clear it.
Same here, MIDI hasn't made things any better. The OCT pads don't change octaves, so its actually worse. Timing is not tight, it wasn't with USB either...
I am in standalone mode right now and still get the same problems...drum sequencer has all 16 steps on yet occasionally drops triggers...
-
Ok, the clearing pattern bit works, everything seems to work fine. So I clear patterns every time and start a fresh until there is a new firmware that remedies the patterns that are saved in memory?
-
Hi, you must update the firmware as soon as possible as the factory firmware had many bug. Even if you have not used the bsp I would go through all seq and clear the patterns .
As regards to the change OCT you must press the seq button then the OCT button + -.
regards
Terrym
-
Ok, the clearing pattern bit works, everything seems to work fine. So I clear patterns every time and start a fresh until there is a new firmware that remedies the patterns that are saved in memory?
if you save your patterns to the mcc thats fine .but just incase its not fixed on the next firmware just clear all patterns then load or add your patterns
some people have been adding steps then turning them off then starting a new pattern and getting ghost notes so its best to start afresh and clear the pattern first.
regards
terrym
-
Do you know if there is going to be a Snow Leopard compatible, software? Is there a way to update firmware whilst on Snow Leopard?
-
Hi all as mentioned in other threads have you been clearing all pattens after your first firmware update .even if theres nothing in the pattern please clear all by pressing shift and clear ptn on all 3 sections as i found the firmware corrupts anything stored .
i have 2 bsp and cannot repeat your problems i have one setup on cv equipment and one on midi /daw work.
There is a firmware update coming very soon.
hope this helps
Terrym
Hi,
And thanks for your reply and advice which I have just seen.
No, I hadn't heard about clearing parts after an update and will try this tomorrow morning. I really hope it is similarly effective.
It seems odd that "ghost notes" appear so occasionally and inconsistently though...
Would be delighted to see this fix this issue.
Thanks again and will report.
-
I cleared the patterns, but
the ghost notes still appear, even in an empty new ableton set with nothing else init but the BSP track.
Strange is that they don't follow a pattern, some cycyles it seems so and the it starts to drift and alter...
After fiddling around with the tempo knob, I run BSP as an ableton slave via usb, the ghost disappear...
I have to include this tempo knob fiddling in my workflow as it seems to help for the moment...
Oliver
-
Yep, I did a Pattern Clear from first switch on, put in a simple 6 note sequence and on about repeat number 30 there was another stray event (sounded like missing note off).
The "ghost notes" don't seem to be the issue here. :(
And like others here, I am only hearing these additional / corrupted / missing events over MIDI - if I seq a VST in Live cant see a problem.
So, firmware or hardware??? (firmware - please get it fixed ASAP but if harware it is going back to the retailer because personally I need to be able to rely on a predictable output).
-
HI, I have 2 bsp here and can not repeat the odd behaviour you have . so it only happens in standalone right? what is your set up what are you using.
Terrym
-
OK, Terry, thanks for your continued interest....
BSP standalone - usb PSU, single MIDI out directly in to either a Voyager or a Access Virus (or anything... any synth responds similarly). If I chain the MIDI in thru the first hardware synth the event (or absence thereof) is replicated via MIDI thru to the next synth.
I am not sure how I can reduce it down further? Any ideas?
-
OK, Terry, thanks for your continued interest....
BSP standalone - usb PSU, single MIDI out directly in to either a Voyager or a Access Virus (or anything... any synth responds similarly). If I chain the MIDI in thru the first hardware synth the event (or absence thereof) is replicated via MIDI thru to the next synth.
I am not sure how I can reduce it down further? Any ideas?
OK, Terry, thanks for your continued interest....
BSP standalone - usb PSU, single MIDI out directly in to either a Voyager or a Access Virus (or anything... any synth responds similarly). If I chain the MIDI in thru the first hardware synth the event (or absence thereof) is replicated via MIDI thru to the next synth.
I am not sure how I can reduce it down further? Any ideas?
ADDITIONALLY - this is definitely just events sent over 5 pin MIDI - had it running in parallel into Live driving a single VST , missing note off's evident on hardware attached synth and NOT on VST which stayed 100% stable.
-
HI, I have 2 bsp here and can not repeat the odd behaviour you have . so it only happens in standalone right? what is your set up what are you using.
Terrym
No, I have the abletin with ghost notes = playing notes without having ones entered also within ableton.
I use an internal sond or a vst and even an empty track in ableton and an emtpy track within BSP produces notes...
BSP is usb connected and ableton is master.
BUT if I turn the tempo knob on the BSP even if it is a slave the "ghost" notes disappear...
-
To add to my missing MIDI events issue -
The missing MIDI events (entire notes or more typically just a Note Off) occurs irrespective of how the BSP is clocked - so internally or remotely from Live via usb.
Problem is occurring regularly and is a pain.
-
So apart from missing MIDI events I now have.....
I am now also getting "ghost notes" - irregular events that occur sporadically, normally in the same place but not on every Seq pattern repeat - they will not clear with a "Shift-Sequencer 1- Clear Ptn" . USB cable connected to PC but no DAW running - Internal clock only. These ghost notes are transmitted over both MIDI and CV/gate. The only way I have found to clear them is power the BSP off then back on a again.
I still have sync out issues to a Korg SQ-1 (irregular clock that skips notes)- kind of gave up on that...
And I cant seem to get the BSP to config to Hz/V on either sequencer.
This device is not working out well for me - do I have a defective unit???
Is there an absolute factory reset command available?
-
@ sbDigisound
Have you done a firmware update?
-
First thing I did before trying anything else at all.
-
Hi,
Don't you have some Randomness or Probability ? A value of 1 can do this kind of thing.
-
Hi,
Don't you have some Randomness or Probability ? A value of 1 can do this kind of thing.
Nope, both set to zero.
But if that were the issue then the same deviation (randomness) would be present on cv/ gate and usb - and it isn't.
It is just the 5 pin DIN output that is affected.
-
Hi I am also getting ghost notes playing every now and then
the only way for me to stop them is to disconnect the power from the BSP
then all is well again
Just reset the BSP and I am getting random ghost notes playing
but I notice that the random and probability knobs are set to 50
if I turn them to 0 then the ghost notes go away
I think this is a bug in the firmwear
cheers
kev
-
Its a known problem kev
terrym
-
Cheers
Mr T
this is most likely tied up with the same issue
but I just made a little sequence then turned all the steps of and I was again getting random notes
playing until I turned the rand and prob knobs to 0
Hasta Leuago boy o boy is my Spanish coming along good
only lived here 12 years LOL
-
My issue seems to be the only one where midi events are actually missing rather than experiencing additional notes.
Arturia support seem to have lost interest in this specific issue but are hopefully rewriting the firm ware to deal with ghost notes (amongst other things....)
-
Clear pattern isn't working on mine?
I'm getting the same problem with sequencing CV and gate - it plays for a bar or 2, then misses a couple of bars, then kicks back in again, its awful.
Ive cleared patterns before, but now when i do it, it clears the pattern, then i go to a pattern2, if i then go back to pattern 1 it is there still?!?!?!
Any ideas?
-
Clear pattern isn't working on mine?
I'm getting the same problem with sequencing CV and gate - it plays for a bar or 2, then misses a couple of bars, then kicks back in again, its awful.
Ive cleared patterns before, but now when i do it, it clears the pattern, then i go to a pattern2, if i then go back to pattern 1 it is there still?!?!?!
Any ideas?
You need to save the pattern once you have edited it, it does say this in the manual. I think it is even in bold print, so any changes you make need to be saved or you will lose them when you switch pattern.
-
Did OP get solution to clock sending far too fast? When I try to send clock to a volca it is far too quick. I have ensured the clock speed is set to 1 through MIDI Control Centre, but it's still incredibly fast (approx 500bpm)
-
there's a couple things that might cause dodgy volca clocking:
- the clock signal is too hot for volcas, fix by attenuating the signal
- volcas work with 1 clock pulse for every 2 steps, so if you send 1:1 then it'll be double speed. a solution is to use a drum track with every other step lit
-
For the record....
I still have the same issue with the BSP occasionally not sending MIDI data via 5 pin DIN - most often this is missed note off's.
I have now tried 2 units and both exhibit the same basic flaw.
The CV / Gate & USB data is NOT affected so if you are using anything other than 5 pin DIN this wont be an issue.
Annoying. Hope it's a firmware issue.
(And yes, Probability & Randomness = 0)
-
Hi are you using midi leads or 5pin din leads as these are wired differently and to make sure your using clock out only for machines that use clock and use midi out for midi clock
Terrym
-
Hi are you using midi leads or 5pin din leads as these are wired differently and to make sure your using clock out only for machines that use clock and use midi out for midi clock
Terrym
Thank you for your reply.
I have tried several 5 pin MIDI leads.
I am not certain what you mean about Clocking. The BSP is using Int sync and outputting Clock data on the same MIDI cable that is connecting to my hardware synths that are occasionally not receiving MIDI messages from the BSP.
-
Yeah there's definite dodginess. I'm using the three volcas by midi, using the quadra midi thru to send signal. The BSP is all over the place. Total mess.
-
how does one volca with direct midi perform?
-
I'm not here to beta test for random community members. this is a finished product and should have a definitive solution.
-
I don't have a Volca, but that's not the issue. Using any hardware synth directly connected by 5 pin MIDI and the fault (missing MIDI event messages) will occur.
With or without any intermediate thru box the 5 pin MIDI out drops event data on an occasional but very annoying basis. I tried 2 separate units, swapped cables and the problem always persists.
Link by CV/gate or USB MIDI the problem does not happen.
-
I'm not here to beta test for random community members. this is a finished product and should have a definitive solution.
Great attitude bro'- all the whining with no helpfulness towards anyone else.... :-\
-
A - I'm not whining. I'm trying to describe a very confusing and inconsistent problem. Including video documentation. That not helpful enough?
B - I'm not a beta tester. I paid money for this. I'm not pulling my studio apart while I'm sick in bed to satisfy the curiosity of others who cant be bothered to test it themselves.
C- you assume my gender. Great attitude, bro.
-
I've got MIDI Din out from BSP directly to MIDI Din in of Volca Beats and it works fine.
-
Gender is a useless societal construct, but sorry if I assumed anything about your sex organs by using the term "bro".
Still think shooting down another user on a discussion forum for asking a simple question is a pretty shitty thing to do.
-
https://www.youtube.com/watch?v=owWN-WfIK98
volca beats/bass/keys using quadra thru midi din. record button changes character of volca keys (even with direct midi line) misses notes, sometimes wont clear pattern, sometimes switches two octaves down, then turns all gates down to 1.
https://www.youtube.com/watch?v=DZqTZiuxwvM
midi direct to sub 37, sometimes doesn't record notes, doesnt like second pass recording.
basically useless.
-
I'm not here to beta test for random community members. this is a finished product and should have a definitive solution.
actually, I was asking as a method to try and debug your problem. The quadra thru is not externally powered, ie it draws power from the midi port. It was possible the beatstep doesn't like power being drawn to send 4 sets of midi signals.
-
Sorry, I shouldn't have gotten so annoyed, it just reminded me of telephone help desk staff asking if I'd tried a different cable, a different unit, had I tried turning it on or off.
I've reported to arturia, hopefully they'll provide some concrete answers. I find it hard to believe that they didn't bother getting midi din working well before release. I have read in the far that the internal clock for midi is useless and to use external clock which isn't promising.
Also the BSP will only play the sounds of the volcas when the record button is on, but the sub 37 can be played from the pads any time. Also the roller interrupts the beat completely. It's like the original beat step all over again.
The sub 37 is a bit more stable and less velocity volatile, but still misses information in live recording.
It's disappointing. I want to use my BSP to sequence the volcas and two of my vintage synths which I got upgraded to midi specifically for sequencing. Now I will have to reassess the market and look for something else.
I have low hopes of arturia fixing these issues, they don't seem to have the technical capability.
-
Last weekend i played a show, and was using the BSP to sequence my Juno-1. Well, about half way through, it just stopped sending note data to the Juno. I couldn't get it to start sending again either, so i had to can the Juno for the remainder of my set. I wasn't real pleased. So this whole notes randomly not sending issue needs to be fixed ASAP! can't be having these failures in a live setting.
-
All interesting.
There is definitely something unreliable about 5 pin MIDI output.
Arturia told me to replace my BSP - so I did. The new one does exactly the same thing.
Something so fundamental (if you use 5 pin MIDI) needs to be reliable and right now it is not.
Just hope there is firmware that can fix this....
-
I own two BSPs they both do this.
-
Hi all , i had a look at this and think i know where your going wrong . if you start with a blank sequence just press shift then sequence number step just to clear any problems . then say you want 64 steps change this with lst step and press where you want it to finish when you have done this . press save and the pattern your using before recording . then you are ready to record .
this fixed the problem with weird recordings.
give it a go and let me know.
also there is a problem with the latest FW 1.1.1.6 and sync
so I'm using 1.1.1.4 below. please note this is not a released FW
hope this helps
terrym
-
I'm still on firmware 4 not 6.
And I don't think it's the user that's wrong for not saving the sequence as 64 steps before putting notes in.
That's a design fault. Needs fixing ASAP.
Because every time you clear a pattern it just goes back to 16 anyway. So... You're just adding archaic steps to the process.
No response from Arturia to me. And to the other user, they say "oh get a different unit" when, both my units do this.
I find this all even more concerning.
I'm holding out for some fix very soon. But currently the product is not fit for purpose and the longer I wait to return both my units, the more issues there will be with the retailer.
-
Hi . I do see your point and its not the best i think the next Fw is next month . they way the memory allocation is in bsp is the default is 1 bar /16 steps
if you increase the step count and do not save this the bsp has not allocated memory but if you save your step amount the memory is allocated .
it has worked for me here . i will email arturia and ask about this .
Please remember i don't work for arturia and only remote test for them so I'm in the same boat as everyone else.
please try this method and let me know how you get on.
Terrym
-
I just want to do simple stuff without PC or USB. A simple 8 note riff repeating with robotic precision like my doepfer sequencers.
Switched on, cleared sequence 1,input 16 note sequence with gate on odd numbers only. Firmware 1.1.1.6
This is using the midi out to a Boomstar 4075 - seems OK on CV and GATE but midi falls over after a random time.
I made a very short video of the fault:
https://youtu.be/j_OLUFpJC9I
-
Did you try the method above even with 16 steps
I know the latest fw has a sync issue
Terrym
-
I just want to do simple stuff without PC or USB. A simple 8 note riff repeating with robotic precision like my doepfer sequencers.
I made a very short video of the fault:
https://youtu.be/j_OLUFpJC9I
Sam sort of thing I am getting (on 2 units) Typically with a mono hardware synth I will just here a random lengthened release.
-
Did you try the method above even with 16 steps
I know the latest fw has a sync issue
Terrym
Hmmm. Well seems to me all 3 official firmware releases have sync issues (not tried .4).
Arturia really need to sort this out ASAP.
-
Yes when I set all 16 steps to trigger ( internal sync ) it will, after a short while randomly start triggering what sounds like 2 gates per note as if the roller looper is being used and just missing out other random notes. I don't know why the roller looper was made touch sensitive like it is - I would have preferred standard push buttons or the ability to disable it. If it wouldn't cancel the warranty I would unplug the internal connector to see if that was causing this.
-
Thanks for the explanation terry at least it feels like getting closer to the issue.
I would like to hear from Arturia though. I don't think it's right to leave all this to beta testers.
-
also there is a problem with the latest FW 1.1.1.6 and sync
so I'm using 1.1.1.4 below. please note this is not a released FW
Thank you for the firmware.
1.1.1.6 not only haas sync bugs, but has broken Hz/Volt mode as well, so my MS-20 did only microtonal stuff.
With your firmware it works as it should, in a plain old 12-tone scale. Oh yeah! ;)
However, sync stuff is broken in the 1.1.1.4 as well.
I posted my detailed findings here: http://forum.arturia.com/index.php?topic=85368.0
-
I got my BeatStep Pro last week. I updated to firmware ending in 6. Prior to the firmware update the Midi Controller software on my PC didn't recognise the unit properly - it does now and seems to work fine. With the device itself I am primarily running it hooked up to an Arturia Origin module. Some of the issues I'm having are when a sequence is first started the first few notes can go weird - wrong notes, doubled notes - even sliding notes where there shouldn't be any. The second time through the sequence plays fine as does any other sequence I select after the first one. This doesn't happen every single time I hit the play button but pretty often - 1 in 3 maybe. Another thing I've observed is the longer I have sequences running the more likely I am to pick up sustained notes. If I just stop the device the held notes keep going and the only way to end them is to select a different patch on the Origin. At first I thought this was a gate setting issue but it still occurs even in patterns where my gate times are 25 or less.
Looking forward to the next firmware update - maybe some of these things will be corrected.
Edit: I also meant to say that the way this thing behaves at the moment I wouldn't use it live - too unreliable. Which is sad because I haven't had so much fun with a new gadget since I got a TB 303 in the 80s. Arturia needs to make fixing the issues with this device a priority because it could be a classic.
-
...........Another thing I've observed is the longer I have sequences running the more likely I am to pick up sustained notes. If I just stop the device the held notes keep going and the only way to end them is to select a different patch on the Origin. At first I thought this was a gate setting issue but it still occurs even in patterns where my gate times are 25 or less.
This is exactly what I have been experiencing - on two separate units.
Sincerely hope Arturia take note here as it wrecks an otherwise great bit of equipment.
-
...........Another thing I've observed is the longer I have sequences running the more likely I am to pick up sustained notes. If I just stop the device the held notes keep going and the only way to end them is to select a different patch on the Origin. At first I thought this was a gate setting issue but it still occurs even in patterns where my gate times are 25 or less.
This is exactly what I have been experiencing - on two separate units.
Sincerely hope Arturia take note here as it wrecks an otherwise great bit of equipment.
this issue is known by many users, including me:
Notes Being Held Open:
http://forum.arturia.com/index.php?topic=84950.0
could Arturia get this fixed PLEASE?
Or at least, let us know if fixing is in progress, so we donīt have to return our units...
-
...........Another thing I've observed is the longer I have sequences running the more likely I am to pick up sustained notes. If I just stop the device the held notes keep going and the only way to end them is to select a different patch on the Origin. At first I thought this was a gate setting issue but it still occurs even in patterns where my gate times are 25 or less.
This is exactly what I have been experiencing - on two separate units.
Sincerely hope Arturia take note here as it wrecks an otherwise great bit of equipment.
this issue is known by many users, including me:
Notes Being Held Open:
http://forum.arturia.com/index.php?topic=84950.0
could Arturia get this fixed PLEASE?
Or at least, let us know if fixing is in progress, so we donīt have to return our units...
Thanks for making me aware of this - hadn't seen this thread. So thus far I have returned one unit and got exactly the same problem with it's replacement. Massive waste of time & money all round.
Arturia - if you have a problem at least admit it (you told me to return it BTW) or better still fix it.
This is such a fundamental flaw it should be top of your list.
-
when a sequence is first started the first few notes can go weird - wrong notes, doubled notes - even sliding notes where there shouldn't be any. The second time through the sequence plays fine as does any other sequence I select after the first one. .... Another thing I've observed is the longer I have sequences running the more likely I am to pick up sustained notes
Not good form to quote yourself but I have to confess I'm no longer convinced the BeatStep Pro is the source of these problems. The weird notes at the beginning I've now determined is the inbuilt delay in the Origin trying to sync to the BeatStep Pro clock. I've turned off the Origin's delay sync and manually set the delay to where I want and it doesn't happen any more. As far as the sustained notes go I tried hooking the BSP up to a microKorg and I never once got this happening. I've also not had it happen when I had the BSP connected to my desktop pc. Seems like the Arturia Beatstep Pro and the Arturia Origin module don't play nice with each other - which is both disappointing and ironic. If other people are having the sustained note problem what gear are you using your BSP with?
-
when a sequence is first started the first few notes can go weird - wrong notes, doubled notes - even sliding notes where there shouldn't be any. The second time through the sequence plays fine as does any other sequence I select after the first one. .... Another thing I've observed is the longer I have sequences running the more likely I am to pick up sustained notes
Not good form to quote yourself but I have to confess I'm no longer convinced the BeatStep Pro is the source of these problems. The weird notes at the beginning I've now determined is the inbuilt delay in the Origin trying to sync to the BeatStep Pro clock. I've turned off the Origin's delay sync and manually set the delay to where I want and it doesn't happen any more. As far as the sustained notes go I tried hooking the BSP up to a microKorg and I never once got this happening. I've also not had it happen when I had the BSP connected to my desktop pc. Seems like the Arturia Beatstep Pro and the Arturia Origin module don't play nice with each other - which is both disappointing and ironic. If other people are having the sustained note problem what gear are you using your BSP with?
I have this exact same issue which presents with any hardware synth connected (directly) to the BSP 5 pin MIDI output..
I have used a Voyager, a Mopho and Supernova and all demonstrate these occasional hanging / sustained notes.
I have other sequencers (eg SQ-1) that never do this.
The fault is coming from the BSP.
-
The product has a rough start, i agree, but please stop being dicks to each other over little bugs.
On the other hand, i would wish for stronger moderation from Arturias side.
Both technically and to calm the Kindergarten.
-
The product has a rough start, i agree, but please stop being dicks to each other over little bugs.
On the other hand, i would wish for stronger moderation from Arturias side.
Both technically and to calm the Kindergarten.
Wow!....Can't say I've noticed anyone being overly aggressive or abusive here so I'm not quite sure what you are reacting to but the problem of unwanted held notes is not a "little bug" it renders this device unusable for live work as far as I am concerned. Having said that I LOVE the BSP. I want it to work right and giving Arturia feedback through the forums is one way of encouraging them and pointing them in the right direction.
Edit: BTW I tested the BSP with a little Pittsburgh modular system (that had a midi in converter so I didn't need to use the cv/gate) and it picked up held notes confirming this is pretty widespread. I'll try with the cv/gate when I get my next chance.
-
I'm not saying it's not happening to the people who are saying it is, but I've used this thing for many hours by now, controlling hardware and software synths through both USB and 5 pin MIDI, and I haven't experienced this issue a single time.
-
That's good Zymos you are confirming it isn't a universal problem. Like I said earlier it is an issue with the Arturia Origin module which is the device I mainly wanted to use it with. However, I've had no problems with soft synths and it worked fine the evening I had it hooked up to a microKorg. What I have been wondering is whether there is any continuity of experience across a group of users. Is there someone else using the gear I have mentioned with a BSP? - is their experience different or the same as mine?
-
I hadn't encountered the bug either after several hours use, but I decided to let one pattern play continuously for about 40 minutes while I did something else- and yep I noticed a couple of skipped notes. a couple times within that period, nothing as catastrophic as midi cutting out completely as someone else has experienced.
-
I hadn't encountered the bug either after several hours use, but I decided to let one pattern play continuously for about 40 minutes while I did something else- and yep I noticed a couple of skipped notes. a couple times within that period, nothing as catastrophic as midi cutting out completely as someone else has experienced.
Yes, this is my experience exactly. Either skipped notes or missing note off's resulting in sustained notes. Were you connected via 5 pin MIDI?
It is possible that the same issue goes unnoticed by other owners as the effect is so intermittent and can be masked by the nature of the sound being generated (eg - staccato where audio is closed off by the synthesis engine rather than a MIDI event).
Arturia - we would appreciate a fix ASAP lplease.
-
Hooray - recognition at last.
Hopefully a fix before too long - make the product what it was supposed to be.
HEllo simon,
This is now a referenced bug, Bug Ticket : 122048
I sent this problem to the appropriate developer, know that a newer version will come in some time to solve this issue.
You will be contacted at that time to download.
Please accept our apologies for the inconvenience.
Feel free to get back to us in order to have news about this subject.
Yours,
Arturia Technical Team.
--
Distributors
distributors.support@arturia.com
-
I'm not sure if anyone else has highlighted this issue,
Basically i'm using the beatstep pro seq 1 cv gate out to an sh101, it is set correctly for v-octave and v-trig in the midi control centre and works fine.
I then set sequencer 2 to Hz and S-trig to control an ms 20 and it works fine, however it completely stops the cv gate on sequencer 1.
I tried switching back and forth with hz and s-trig on either sequencer to the ms 20 and it works on both. As soon as I switch one to v-octave it cancels it out.
I then reset the machine and it did it again as soon as I switch to hz-S-trig in the MCC.
I reset it again and it then mysteriously started working with both hz and v-octave.
I'm sending the BSP midi from a TR 707 and also have an sh 32 via midi out and it also plays the pattern from sequencer 1 but after several cycles of the pattern, suddenly adds in some notes to the pattern then removes them after a few bars. (it actually sounds good but is still undesired) the random and probability are set to zero.
Several other issues like notes double triggering on input but I see they have been mentioned many times already.
Please give us any update on when you intend to resolve these issues as I am considering returning the unit while I still can. However it has the potential to be great and I'd be prepared to stick with it if you could provide basic updates on resolving the bugs.
-
Buggy unit here too, updated to the last firmware, all of the described above plus Drum Sequencer skipping triggers via Midi every once in a while (seems to happen while editing steps more often)
-
Clear all patterns and still with the issue, it behaves like if randomness was activated but it's actually not. Is there going to be any fix for this? maybe some hardware issue? it is great but i don't honestly have the time to deal with this issues, already thinking to return it
-
Buggy unit here too, updated to the last firmware, all of the described above plus Drum Sequencer skipping triggers via Midi every once in a while (seems to happen while editing steps more often)
Yes, that will be the same issue as hanging notes / skipping notes on an occasional basis. I think that when note events are missed that all 3 sequencer outputs are affected on the 5 pin MIDI output.
Arturia acknowledged this as a bug so I guess we should realistically expect a fix before too long.
For me this has really taken the edge of a theoretically excellent product and price point but I will wait it out.
-
Agreed.
And it's definitely not the unit.
I just hope the firmware is well on its way.
-
you can add a Rate knob that doesn't work to this growing list...
-
Then add shift taking not effect on sequence, i need to save then restart, then it works again, not always, but almost.
Have to admit one of the main things for me was the Drum seq over midi, to sequence my beloved Airbase99 of course cvīs and extra sequences was a big plus, but like this is like having a brick. It's not a minor thing though, midi is too one of it's main features, it seems it hasn't been even tested, if not you would never put out a product like this.
-
Returned mine, good luck guys!
-
unless I get a respone to my ticket soon I'll be doing the same (for a replacement though). bummer.
-
Just confirm that the random MIDI out bugs are still happening with firmware 1206.
This short video shows the glitch after 25 seconds
https://www.youtube.com/watch?v=LJNV_8Xo0Os&feature=em-upload_owner
-
Just confirm that the random MIDI out bugs are still happening with firmware 1206.
www.youtube.com/watch?v=LMxWYo9IurY
bummer, i'd really like to buy one, but as long users will report critical bugs like this i surely won't!
-
buy it after summer 2016, i'm sure some bugs will be ironed
-
1.2.0.6 and it keeps losing the USB clock... Looks like a sloppy programming on Arturia part. Are there no good real-time device programmers nowadays?
-
A bug: Setting ControlMode pads/encoders to output only to MIDI out makes no effect - the events still come through the USB.
Reported to Arturia.
-
A bug: Setting ControlMode pads/encoders to output only to MIDI out makes no effect - the events still come through the USB.
Reported to Arturia.
Well I thought my system was immune to this usb dropping issue but experienced while programming and jamming on a project. Tried changing from hub to the only free slot i have but found the same issue after a while even though was a different project.
I'm switching to midi until a fix comes.
-
A bug: Setting ControlMode pads/encoders to output only to MIDI out makes no effect - the events still come through the USB.
Reported to Arturia.
Hi dm13,
Are you using the last firmware (1.2.0.6) and the last Midi Control Center version (1.2.1.346) ? Make your settings, save them in the MCC and then drag and drop control map from Project Browser to Device project. It should work fine.
-
Hi Valentin,
Yeah, this works. A bit counterintuitive, but I'll adapt.
Thank you!
-
Ok, live recording midi din beat step pro. With long notes.
What are the steps to do this successfully, why am I still getting hits and misses?
What will BSP do if two notes overlap momentarily in the live recording? It seems, it means the new note will not be recorded at all, where in all my other mono devices it will take over from the last note.
Can we turn off some features like cv, USB so that it will work more reliably? I'm primarily only using midi din sequencing and clock in/out, and din sync clock out.
-
When I clear a running sequence, I will sometimes get a hung note as a note off message hasn't been set. It would be great ti have an all notes off sent on the channel when you clear a sequence.
-
Since updating to firmware 1.2.0.6 when I start playback the first note of the pattern is dropped on the CV out (DIN MIDI output is OK).
With regard to the stuck note problem, I have never had a stuck note at home, but when I took the same equipment to my practice space and set it up identically I had a lot of stuck note problems with DIN MIDI. I wonder if it's a power issue of some kind, since the only major difference was that when I got stuck notes it was on the same circuit as a couple of high wattage tube amps.
-
Updated to OS 10.10.5 so that I can use the MIDI Control Centre.
Things are actually worse...So...still loads of problems.
Most annoying, BSP freezes, it does so everyday and more than once. I have to switch off and on for it to work.
When recording MIDI notes in Logic X, using the BSP, it records double notes. There is a note layered on top of the one that I recorded, same length and velocity.
Clock out is not tight, even when using a negative delay off set patterns in order to make up for latency, the clock out is still not tight. This is also very annoying.
When using the BSP sequencer to record a pattern and trigger a step, I often get long notes that play over more than just the step I enabled and yes, the gate length is short.
I am on firmware 1.2.0.6 using OS 10.10.5
Anyone knows if there is a firmware update that addresses these issues?
The freezing and loose clock have started to become an issue now.
-
Hi,
Here comes my list of errors and malfunctions of an otherwise marvellous piece of hardware.
First of all, I have updated the firmware to its latest version. Before, the BSP was simply unusable,
which is strange for a company that is known for complex software. Also, a bit annoying because
it seems unlikely, that those MAJOR errors were unobserved/unknown for the final product. Its like
selling a car with random gear changes, and ohh sorry, we just added two wheels, we thought you wouldn't notice..
Errors:
(1) occasional, beats are dropped despite Rnd/Prob set to 0 (esp. for the drum sequencer)
(2) when connected to Roland HD-1 Drum set via Midi (just for midi-thru), notes will be dropped
(3) project save seems to forget to save the midi channel for the drum sequencer
(4) strange error I got in the drum sequencer: suddenly, each step was active for 2 instruments ???
and various other errors, like octaves are not saved, etc pp
Some day, after fixing the bugs, I would love to see at least one sequencer
to be truly polyphone.
So long
-
I've encounter the hung midi-note issue a couple of times, but not really recently until last night. I was using patterns of long held notes that were each slid to the next note and found when I muted the sequence, the last note sounding would hang. So I went through and set the gate time of the last step of the pattern to 99. This silenced the hung note even though the sequence was muted. I was happy to find a work around, but it does mean if I slide (or tie) an entire pattern, including the last note of the pattern, it'll always hang. Unfortunate as I did want to slide the entire note loop including the last note into the first....
Is that fixable?
-
in EVERY session i using the BSP, held notes issue is happening repeatedly!
This will kill EVERY live situation, so if Arturia want BSP to be a Live Tool, this is a MAJOR bug!
Please fix this ASAP, Arturia
-
Downloaded latest MCC and Firmware a couple of weeks ago. Installed MCC first then update the firmware and after a few attempts it burned the new FW on the hardware.
Crashed only once so far but the clock (and gate triggers) are drifting still after a while. I've tested this on USB and MIDI to see if one works better.
I am not alone in this, facebook forum has other people reporting the same, along with one of your testers.
I understand the new features are a selling point, but what is the point of a step sequencer that does not do the most basic task, that is play on time?
Please, please, PLEASE fix the most important things that do not work as advertized before adding more things.
-
Please, please, PLEASE fix the most important things that do not work as advertized before adding more things.
Absolutely!
New functions would be a great thing on a bug-free fundament.
- notes being held open issue-> Fixed
- rock solid clock
- edit-begin of pattern function
then weīre ready to go :)
-
Same here... Sad :'(.... Very disappointed :-[, PLEASE fix IT >:(
Or give me a way to refund this Beatstuck Pro.
-
- notes being held open issue-> Fixed
So there is no "hanging/stuck notes bug" in latest firmware 1.3.0.23?
-
True - thankfully! I haven't heard any hangs since that firmware .
Main complaints are sloppy timing and the way sequences change direction immediately vrather than at the end.
I have found it difficult to be enthusiastic about this inherently buggy device.
-
Hi you can change the way sequences change direction in the MCC
1. straight away
2. wait till end
cheers
kev
-
Hi you can change the way sequences change direction in the MCC
1. straight away
2. wait till end
cheers
kev
Hi,
And thanks for this. Just hunted round MCC and dont see this option. Where can I find it please?
Thanks.
-
Hi, did you down load the latest mcc ? its in the righthand column .
regards
Terrym
-
I don't think that's what they are asking about.
Say you have a sequence playing normally (forward)- it could immediately go backwards at the moment you hit the reverse button, or it could play until the last step, and then go backwards.
-
I don't think that's what they are asking about.
Say you have a sequence playing normally (forward)- it could immediately go backwards at the moment you hit the reverse button, or it could play until the last step, and then go backwards.
I was hoping that an option to wait till sequence end before actioning a direction change.
Maybe someday....
-
there is already an option in the MCC to do this
wait till sequence end
look in the MCC down the right hand side
cheers
kev
-
there is already an option in the MCC to do this
wait till sequence end
look in the MCC down the right hand side
cheers
kev
I have looked & do not see this. What is it called?
I am on the most recent MCC ? firmware BTW (1.2.2.429)
-
Are you sure that changing immediate vs. wait for end has an effect when changing direction, or is it only when changing to a different pattern?
I had thought the latter, I'll give it a try later.
sbD- are you at least seeing the pattern change behavior setting in MCC?
-
True - thankfully! I haven't heard any hangs since that firmware .
stuck notes are still a problem with the newest firmware, with no solution at the time.
http://forum.arturia.com/index.php?topic=84950.30
So... it's 1:1 :-/ Is there anybode else who has experience with firmware 1.3.0.23?
-
So yeah, no...
Direction changes happen immediately, regardless of whether the pattern is set to wait or not.
It would be REALLY great if they could add that setting to MCC too....!
-
Er, slightly confused here but....
I don't see a setting in the MCC that could change the behaviour of when direction would be changed. What is it labeled?
Still not getting hung notes though but odd that isn't consistent with other users of the same firmware.
-
It doesn't exist. That's what I'd thought all along, and have now confirmed.
People saying it does were not reading what you were actually asking about, only what they already thought you were asking about...
-
OK.
Thanks for clearing that up.
cheers.
-
Hi sorry about my answer , your right what you want to do does not exist
but as a work around
you could copy the pattern and make the second copy play backwards
then with the wait till patter end selected
you would get the required effect
if I understand you right ?
cheers
kev
-
So... it's 1:1 :-/ Is there anybode else who has experience with firmware 1.3.0.23?
Many people seem to have this problem with different gear, even with other Arturia products like Microbrute, Minibrute and Origin:
http://forum.arturia.com/index.php?topic=85383.0
or with synths from other brands:
https://www.youtube.com/watch?v=CzeshbZIE2c
(see vid description)
"I got some hanging moments i can tell why, so just a reset helped"
So it should not be a problem to reproduce this issue, using Midi Out only and under controlled conditions
-
True - thankfully! I haven't heard any hangs since that firmware .
stuck notes are still a problem with the newest firmware, with no solution at the time.
http://forum.arturia.com/index.php?topic=84950.30
So... it's 1:1 :-/ Is there anybode else who has experience with firmware 1.3.0.23?
Cancel that sigh of relief on the stuck notes issue - it's still here.
These bugs & shortcomings are just too distracting to work around. I'll set it aside and try the next firmware as & when.
-
Midi timing is hasn't stopped swinging like a drunken jazz drummer yet. New firmware might fix that I'm hoping. Really would like solid timing.
I'm syncing a delay using a trig clocked from the BSP midi clock and it's already got modulation.........
-
Thats it.
Due to all the bugs & problems, but especially because of the problems with random held/stuck notes, i will sell my BSP units.
I will go for a Squarp pyramid Sequencer, as soon as i got the bucks.
Sorry Arturia, this took way too long for fixing your buggy BSP Firmware.
Itīs a shame, because i had a good feeling about the Design and Hardware.
-
And I have at least temporarily abandoned my BSP for the same reasons.
I bought a BCR2000 with Zaquencer firmware and find it far more creative and infinity more reliable.
-
Thats it.
Due to all the bugs & problems, but especially because of the problems with random held/stuck notes, i will sell my BSP units.
I will go for a Squarp pyramid Sequencer, as soon as i got the bucks.
Sorry Arturia, this took way too long for fixing your buggy BSP Firmware.
Itīs a shame, because i had a good feeling about the Design and Hardware.
When you sell it, are you going to inform the buyer that you think it is broken and buggy?
Seems kind of shitty to pass it off on someone else if that's your opinion of it....
-
When you sell it, are you going to inform the buyer that you think it is broken and buggy?
Seems kind of shitty to pass it off on someone else if that's your opinion of it....
I never wanted to beta-test BSP units for free, so everyone has to make his own experiences with it.
I think i.e. modular people who use the CV-Outs of the BSP only, will have fun times with it.
But dare you using the Midi Out....
i have made my best to make people aware of possible issues here, everyone can read something about the pro & cons of the BSP on the forums, in reviews or even in ratings on onlinestores; before buying it. So, no reason to play the gooseberry here :P
At least; Did Arturia cares about such things ??
-
Yep, MIDI Out - that is where all my BSP pain comes from.
It's too much grief to work round - for me.
-
New member here.
I had an old Yamaha RM1x that had a tight midi timming, I'm not expecting less from my next sequencer.
I'm willing to buy the BSP but before that I would like to see the mentioned midi "gremlings"/timming/sync issues solved.
So, Arturia team: Is there a timetable to launch the firmware with these issues solved? Obvious is the fact that I wil only buy it if the reviews show this to be fixed.
-
New member here.
I had an old Yamaha RM1x that had a tight midi timming, I'm not expecting less from my next sequencer.
I'm willing to buy the BSP but before that I would like to see the mentioned midi "gremlings"/timming/sync issues solved.
So, Arturia team: Is there a timetable to launch the firmware with these issues solved? Obvious is the fact that I wil only buy it if the reviews show this to be fixed.
... I wish there were. I had Arturia acknowledge and open a ticket for the issue but here we still are. Dont hold your breath! I have owned my BSP for over 6 months and despite 3 firmware revs have now abandoned it for a Zaquencer.
Shame - nearly but not quite.
-
I have both the Zaquencer and BSP- they really are different from each other. To me, it's way easier to see what's going on with the BSP, I just don't have the same flow with the Zaq. But, it has some features missing from the BSP.
I'm using the BSP pretty much exclusively with CV these days, and though I do have a MIDI to CV module, I'm using it for keyboard input. So, for my personal situation, it's harder to integrate the Zaquencer into my system.
Both are great, but not really interchangable.