Surprised there isn’t a shortcut to delete all step conditions without clearing the notes. I think there’s a clear for motion record in the bar settings menu, which feels random- but not step conditions.
I’m noticing other random things that feel like bugs. As of right now, this instrument reminds me a bit of the norand mono- a completely unique and incredible instrument that’s got some flaws and probably always will. I’ll never sell the mono(s) and I don’t see myself ever selling this.
All I did here was save a preset on the EP engine and change its name. Boom locked up
But this time I actually saved it as a snapshot in the ‘categories’ area, not as a preset in the ‘engines’ area.
Just tried it again and it locks up every time, replicable every time I try it
Did you factory reset after the firmware update?
I did a factory reset after the firmware update yeah, is that the issue?
I actually did the firmware a while back but the factory reset today to see if maybe it would correct the pitch bend issue (after hearing the above about a calibration coming soon)
@MichaalHell relying on you for this one:
Up until now I haven’t tried to record pitchbend because mine causes the synth engines to be out of tune. But I said fuck it on the tuning, I want to see how it works. And… it’s not working. Pitch bend is bending the pitch but the sequencer plays it back straight without any pitchbend data recorded. I Looked at the settings and don’t see what I could be doing wrong.
By messing around with the pitch bend a lot I figured out that if I press downwards (left side of pad) I can actually leave it in a state where it stays in tune and doesn’t affect the engines. But if I press upwards, it sticks slightly above middle thus throwing the engines out of tune, which is further accentuated by the pitch bend range setting (the higher the range the further it is out of tune)
It’s not so cut and dry, it requires some finessing to get it right. Which is just as detracting as just setting the engine to no pitch bend range.
SO! It’s not entirely broken I guess, just sticks to one side. I’m really hoping that the pitch bend calibration that is potentially in the next firmware helps address this and that it maybe, hopefully isn’t a hardware issue.
Send it to support, then they can much quicker identify the problem with that code.
If you press BAR
, do you see a blue line ascending or decending where the note data is? If not then it might be a hardware malfunction of your pitchbend pad. There is a pitch calibration setting inbound, but that only fixes tolerance issues with the PB pad and not actual hardware malfunction.
If you don’t see a blue line the. It’s not recording the pitch bend data, which it always is whether or not you have bend range set or PB mod set
It’s definitely recording what I played in, but it’s not playing it back with that (and it’s a massive 1 octave pb, so it should be pretty noticeable, it was very noticeable while playing it)
Same. This exists on the OP-Z right?
Yeah although the combo is hard to remember.
I just reinstalled the firmware, still throwing this issue.
I can avoid it if I dont turn an encoder after saving the preset, and instead just exit the preset screen and go elsewhere. When I go back, it’s still all black, but then I can turn the encoder and it comes back. funky 
I think you’re right. It’s a shame, I’d love to use the xy’s clock but also use the cv/gate.
That’s really strange. As long as you have PB range set there shouldn’t be any other settings that is needed to change
I was playing around with the multisampler a lot yesterday. It’s awesome when it works, but it seems to be a little picky about what samples you feed it. I put some mellotron, rhodes, and wurlitzer single note samples in seperate folders within the “samples” folder on the OP-XY. About 21 - 24 samples for each instrument. Some were fine to create multisampler patches with, but the OP-XY seems to have some problems with some samples, but I couldn’t find a pattern or replicate the issue on what went wrong. For example, I created a wurlitzer multisampler patch and saved it. When I load this patch to one of the tracks, some samples just won’t load for whatever reason. If I go shift+sample button to assign a sample to the problematic note, it shows that it should have the correct sample allocated to the key, but it’s just silent and no waveform is drawn on the screen. I’ll try to figure out the problem after a factory reset, but I just wanted to chime in here if anyone experienced similar issues with the multisampler?
Have you tried applying PB to a synth setting in the MOD settings just to see if it affects any synth parameters
I fully agree. It’s an incredible instrument and there is so much to love about it. But yeah, there’s still quite a few bugs and inconsistencies that need to be ironed out and I hope TE will concentrate on fixing those for the coming weeks and months.
For clearing the step components, there’s still some room in the UI with BAR+3 and it would be consistent with the rest of the delete functions.
Don´t know, if this video was already posted…
Do you have an idea, how the patch could look like?
In the infos under the video Pierre writes he uses the step components system for this generative approach.
I think this is what got me! Thanks a lot for getting back to me. Seems like I need to truncate a few very long, low samples and try again.
It sounds like its not really much generative in this piece.
It sounds like there is some step component use on the Punch in FX and TAPE, mainly Step component trig random, so these functions randomly trigger.
