It seems strange that it changed for the update -and then only for some users of 218. And now for Peters Finger seq- that is a shame. Seems buggy…
My Finger does this and I’ve never noticed until now
I’m starting to wonder if its a case of ‘visual semantics’ -it depends on how you look at it. And it may of done this all along.
I asked my friend over the phone (who is also new to OP-1) to check the old OS for Pattern and he didn’t think it behaved as most of us are seeing in this thread- so my check of both OS’s wasn’t 100% thorough.
(Maybe TEs way of looking at it is… once an impact has happened it is after the event so the drum won’t sound until marker moves off the beat. It seems more logical with finger the way we move about and edit the steps).
Andrew and millbastard, thanks for your response!Would you mind recording your OP-1 screen when playing back a pattern at 40bpm?
I’ve tried this right down at 40 bpm and I seem to be getting the same results as everyone else. IMHO it does not look as bad on mine as the videos but maybe that’s to be expected with the recording.
I am not sure it’s even consistent, but it certainly seems to be sounding as the image shows the marker leaves the beat.
Firmware 218
I was thinking about why this might actually not be a bug as much as just a fringe case. The emphasis should be that the sound happens in time with what is expected. So the priority will be to play the sound, then to increment the image. If you incremented the image first and then the sound, then you might end up with the sound behind the beat as expected. So perhaps at low BPM, the timing just works out to a very perceivable difference, but at higher tempo you no longer perceive the difference.
i have experience programming sequencers so from a programming perspective i can see what has happened. the count for the playhead position has simply been miscoded and needs to be fixed thats all. move playhead forward function is being called too soon, discounting the first step in both finger and pattern sequencers. it really should not be hard for them to fix. they prob just need to change a count variable from 1 to a 0.
On the bright side - it does display the playhead properly for one use case - when the white knob is used to reduce the number of steps to 1.
As someone said before: You could chalk this down to semantics as well…
As someone said before: You could chalk this down to semantics as well...
give it up… its called “hold” because technically you are HOLDING a key. The fact it starts at all when turning the knob is just an added bonus. Look at them like arpegiators. You HOLD down a key to play the pattern, you turn the knob to “hold” it…
Hold on to your hat for this one: If you like every other sequencer better, why not play those? Complaining that the OP1 is not like every other instrument is missing the point of the OP1 explicitly trying not to be like every other instrument.
You HOLD down a key to play the pattern, you turn the knob to "hold" it....except, im not holding any keys. so the logic fails.
Hold on to your hat for this one: If you like every other sequencer better, why not play those? Complaining that the OP1 is not like every other instrument is missing the point of the OP1 explicitly trying not to be like every other instrument.
im not complaining that it is not like every other sequencer. im complaining that there is a programming error. everyone in design knows “do not go against expectations”. they simply made a mistake in the programming – it was not a design feature to have the playhead in the wrong spot.
We are all autistic arent we? :)at least i am! :). And so are you.
The hold reminds me of the Roland juno 6 arpeggio, hold button to simulate finger hold ?
We are all autistic arent we? :)at least i am! :). And so are you. The hold reminds me of the Roland juno 6 arpeggio, hold button to simulate finger hold ?
We are all autistic arent we? :)at least i am! :). And so are you. The hold reminds me of the Roland juno 6 arpeggio, hold button to simulate finger hold ?
personally i find it offensive to be called autistic. a friend of my mine has aspergers and im sure he wouldnt appreciate it either.
im an industrial designer amongst other things. things should be done correctly.
i cant explain my point any more times.
You HOLD down a key to play the pattern, you turn the knob to "hold" it....except, im not holding any keys. so the logic fails.
What are you talking about? You don’t have to hold any keys because you turned the hold knob…? … logic does not fail. There is no other way to start a sequencer other than pressing a key(or turning the knob), the knob is keeping it held for you. Which is why hold makes sense …The reason you aren’t actually holding a key like you said is because you turned the hold knob. You must be trolling . They are like arpeggiators that need a key pressed to work. Press can be replaced with hold. Hold is what the knob is doing doing for you. I’m sorry but You continue to sound ignorant on the subject, I don’t get it…
Peter rabbit said: personally i find it offensive to be called autistic. a friend of my mine has aspergers and im sure he wouldnt appreciate it either.
Well i am classical autistic, so im allowed to say it
And your topics remind me of my own mindfarts. Make something out of nothing,
The fact that you find it offensive to be called autistic, proves my point, thank you :).
And i should be offended by you being offended by being called autistic, but i dont mind. Autism can be of use in the arts.
Can we just close this thread? It’s getting unproductive.
Yes please
“it’s a feature not a bug.”- every developer ever. it still works in time if you program it properly and go according to the way the sound it produced. Not just a graphical representation of it. Listen to the beauty of the sound. The thing thats cool about music is that when you hear music, it makes you feel.
+1 for closing the thread