Arturia Forums
Hardware Sequencers => BeatStep Pro => Beatstep Pro - Feature requests => Topic started by: wbonx on October 12, 2017, 08:47:42 pm
-
Come on guys... the BSP would be perfect with it.
Is a master feature, record a shift from the step equal to the timing the note is recorded. It is so frustrating to edit by hand the shift for the drum and other sequences. After a while is crap to hear only quantized sequences.
-
Umm, it's a step-sequencer, that is what they do, move the note being recorded in realtime to the nearest step.
-
Many sequencers allow unquantised recording and I wholeheartedly agree that adding this functionality would make it orders of magnitude better.
+1
-
My guess is that it wouldn't require any major work, the BSP has already the shift function and there would be no major load added to the hardware.
Not being able to have unQuantized recording is the major reason while a lot of people re selling their BSPs (reading around forums).
Is a major limit to the type of music that one can do.
If this made sense decades ago when people compensated with a different musicality the technical lack, in 2017 this is just frustrating.
I almost ended up going always back to record with a pad and a DAW, forced quantization is painful and breaks the workflow.
-
Would be great to hear from a developer.... I may move on to a different sequencer otherwise. Nothing against over quantizing everything... but this limitation would strongly impair my production. Shifting by hand nisn't an option, kills creativity nd the flow.
Love the BS otherwise!
-
I would love to see this feature too but probably best to not guess how hard something is if you didn't build it. Maybe it requires too much CPU to do it in real time (or enough of the CPU to mess up other things during live recording). As an example, and this is pure speculation on my part... The required ppqn resolution is going to be ~50X higher which is a lot of CPU cycles (1 possible spot per step vs 50 possible spots per step). Or, during recording, the code: "That note came in a little early. Should it be a negative offset or a positive offset on the previous step? First check if there was an event on the previous step... too much recursion..." All of this eats CPU.
Maybe they can drum up a way to store timestamps and defer calculating the offsets until you're back in play mode, who knows. Would love to see it too.
-
I would love to see this feature too but probably best to not guess how hard something is if you didn't build it. Maybe it requires too much CPU to do it in real time (or enough of the CPU to mess up other things during live recording). As an example, and this is pure speculation on my part... The required ppqn resolution is going to be ~50X higher which is a lot of CPU cycles (1 possible spot per step vs 50 possible spots per step). Or, during recording, the code: "That note came in a little early. Should it be a negative offset or a positive offset on the previous step? First check if there was an event on the previous step... too much recursion..." All of this eats CPU.
Maybe they can drum up a way to store timestamps and defer calculating the offsets until you're back in play mode, who knows. Would love to see it too.
My guesss is that is rather simple. the BSP does already soething similar or velocity, and the CPU speed isnt too bad, should be able to browse and set the offset x step while recording.
Would be nice to hear from a developer is they are planning the feature in teh next firmware... it is highly requested in the forums.
-
Many sequencers allow unquantised recording and I wholeheartedly agree that adding this functionality would make it orders of magnitude better.
+1
Bump. Come on dudes
-
Come on... users are asking this feature from years... it is all over on every single forum and you still don't spend a week coding in this feature in the next firmware?!
-
I'm praying for this feature. It is crucial. It is game-changing. It is awesome. Pleeease
-
I'm praying for this feature. It is crucial. It is game-changing. It is awesome. Pleeease
Then let's pray together bro. We are gonna make it happen, god be with us!
(And by the way... I need some Karma!!!!!!!!)
-
Yes!!! I'm in favor of unquantified recording!!
-
Yes!!! I'm in favor of unquantified recording!!
Then cross your fingers, heard a new update is coming out soon! ;)
-
Yes, it would truly be great if it were possible to do unquantized recordings, I keep my fingers crossed!
-
And look at my Karma bro... is sky rocketing from -8 to -1 !! :D
More thumbs up for UNQUANTIZED RECORDING !
:-*
-
the drum machines of arturia have it! let's port!
+1
-
This would be an awesome feature.
-
Me too for unquantized recording.... or at least more resolution.
-
Me too for unquantized recording.... or at least more resolution.
Seems they only care about releasing new average product... too bad, I'm going to sell my BSP
-
Yes me too. It's so sad. And I blame those YouTubers convinced me to buy it in the first place. And the gatekeepers on this forum: disgusting. The BSP is crap. It's a wonderful piece of hardware: knobs and pads are quality made but software.... There are so many controls and I find myself navigating through to access the control section. It's not for the live performance at all. Never gonna buy Arturia stuff again.
-
This, and the lack of Midi thru, is the main reason I wouldn't recommend Arturia gear to anyone.
I sent a support request to Arturia to ask how to record unquantized, not og it was possible.
Can someone recommend a decent sequencer?
Has anyone reverse engineered the firmware and fixed these major flaws?
Is there an unofficial forum somewhere whith download links to user-made firmware patches?
What other basic sequencer functions are missing from this so-called "pro" unit?
The last couple og days have been an endless nightmare of missing feature discovery. Now I doubt it can even fill my very amateur live performance requirements.
-
Guys!
It doesn't help to sell your Arturia gear. It just passes the problems and frustration to someone else.
To make a difference we should tell the world our meanings about the BSP in as many forums and gear review sites as possible.
-
So... does anyone know why this was never implemented? It is there in the drumbrute and impact, so obviously they heard people asking for it, but it was never added into the BSP, so I am guessing there is some firm/hardware limitation which prevents it... and before the guy comes back saying step sequencers aren't supposed to be unquantized, what people are really asking for is increased resolution > 8ppqn (32nd note resolution). Since you can nudge notes around by 50% in either direction, obviously there is some internal resolution used by the drum sequencer, and people just want to be able to record directly at that resolution without having to manually shift notes around... so why didn't this ever happen?
-
OK. SO, I have literally just registered for the sole purpose of saying that I REALLY, REALLY WANT UNQUANTIZED RECORDING! PLEASE PLEASE PLEASE.
Not having this feature, right now, is kind of a deal-breaker for me. I"m about to fall out of love with my BSP.
I've recently found myself wanting to make music, which focuses on groove and feel, and could really use being able to tap in a groove and BSP play it back the way I tapped.
Sure, it might be the case that BSP will have to say ignore a following/second hit if it falls also into the same grid segment. I totally fine with that...just please please implement this feature.
I don't want to have to go back to the PC to record unquantized MIDI.
P.S. I've searched this forum from Google and found multiple posts requesting this feature and on over half of them, there's this user "megamark" trying to be a smart-ass and criticising everyone who request this feature. This is not just unhelpful, but also really annoying.
Let's be adult about it. Some people want features, and some of those features are REALLLLY useful. The unquantized recording is one of the most useful features you can have in a sequencer. You don't have to use it you know? So, let's all chill the beans please :-)
-
Absolutely agree, this is an essential function that is sorely missing in a 2020 sequencer!