Bug reports for the OP-1 Beta OS (2016)


#41

Not sure if this is exclusive to the Beta OS, but the tempo when pitching down the tape seems to be wrong. I’m working on something at 120 bpm pitched down -1, which the tempo display says is 113.3 bpm, but after a long time trying to figure out why Ableton kept going out of sync I recorded the OP-1 loops in and worked out that they are at 112.5 bpm.


So it seems -1 on the tape is actually -1.12 semitones, meaning that all my other instruments are slightly out of tune.

If anyone could try replicating this it would be much appreciated!



#42

I installed the beta only about a week ago; the first thing I noticed was the new presets sounded quite muddy and distorted… almost like there was too much gain on them. Then when I was making new sounds, the notes started to latch. I had to switch the op-1 off.


#43
Not sure if this is exclusive to the Beta OS, but the tempo when pitching down the tape seems to be wrong. I'm working on something at 120 bpm pitched down -1, which the tempo display says is 113.3 bpm, but after a long time trying to figure out why Ableton kept going out of sync I recorded the OP-1 loops in and worked out that they are at 112.5 bpm.

So it seems -1 on the tape is actually -1.12 semitones, meaning that all my other instruments are slightly out of tune.

If anyone could try replicating this it would be much appreciated!


This is big. I had exactly the same issue a while back - the reported BPM isn’t what it runs at. Really strange because I was of the opinion that it gradually drifts out of sync, then the next time I ran it at 0, no pitch adjustment, it kept a stable BPM at the expense of graphics lag, and whatever I threw at it, would still keep stable BPM. As I said, this is a big find, hope TE work this out in time.


#44


Not sure if this is exclusive to the Beta OS, but the tempo when pitching down the tape seems to be wrong. I’m working on something at 120 bpm pitched down -1, which the tempo display says is 113.3 bpm, but after a long time trying to figure out why Ableton kept going out of sync I recorded the OP-1 loops in and worked out that they are at 112.5 bpm.

So it seems -1 on the tape is actually -1.12 semitones, meaning that all my other instruments are slightly out of tune.

If anyone could try replicating this it would be much appreciated!


This is big. I had exactly the same issue a while back - the reported BPM isn’t what it runs at. Really strange because I was of the opinion that it gradually drifts out of sync, then the next time I ran it at 0, no pitch adjustment, it kept a stable BPM at the expense of graphics lag, and whatever I threw at it, would still keep stable BPM. As I said, this is a big find, hope TE work this out in time.

The workaround, in the meantime, is to use the OP-1 as master when using sync


#45

Not sure if this is exclusive to the Beta OS, but the tempo when pitching down the tape seems to be wrong. I'm working on something at 120 bpm pitched down -1, which the tempo display says is 113.3 bpm, but after a long time trying to figure out why Ableton kept going out of sync I recorded the OP-1 loops in and worked out that they are at 112.5 bpm.

So it seems -1 on the tape is actually -1.12 semitones, meaning that all my other instruments are slightly out of tune.

If anyone could try replicating this it would be much appreciated!


This is big. I had exactly the same issue a while back - the reported BPM isn’t what it runs at. Really strange because I was of the opinion that it gradually drifts out of sync, then the next time I ran it at 0, no pitch adjustment, it kept a stable BPM at the expense of graphics lag, and whatever I threw at it, would still keep stable BPM. As I said, this is a big find, hope TE work this out in time.

The workaround, in the meantime, is to use the OP-1 as master when using sync

no go, as it sends the wrong song position data on anything other than very start of tape, and from there it can’t loop backwards because of declick algo


#46

Recording problems. It would omit / lose audio in spots in initial recording. I had to do a couple takes, and it seemed the culprit was the effects?? I’m not sure. When I went to effects screen during recording and tweaked parameters that’s when problem seem to occur. I tried to turn off effects in certain spots, and make sure instrument effects were off and sequencers were off. I can’t really tell if it helped. Never had this problem before until using the BETA. Any advice? As far as I know people reported lost visuals but I didn’t experience that. But, lost audio is worse! Also, I do have very slow tape speed when erasing tape.


#47

@Trilobyte: I used to have random drop-outs near the start of my recordings. I don’t know if this is the same as you, but in my case it was user error: I was on the tape screen, started recording, then I wanted to change to the fx page so I’d hit “3”… but the on tape screen that mutes the current recording (unless you’re recording to track 3). Then I’d realize my mistake, press “mixer” and THEN “3”, and then later wonder why I had gaps near the start of recording.


#48
@Trilobyte: I used to have random drop-outs near the start of my recordings. I don't know if this is the same as you, but in my case it was user error: I was on the tape screen, started recording, then I wanted to change to the fx page so I'd hit "3".. but the on tape screen that mutes the current recording (unless you're recording to track 3). Then I'd realize my mistake, press "mixer" and THEN "3", and then later wonder why I had gaps near the start of recording.

Hey Raigan, I don’t think that’s what I did…but I may have been tired or distracted. I did also consider that. I will try to recreate the scenario and see if it’s indeed my own sloppiness or if it’s OS error. Thanks!


#49

OP1-BUG

Crash on Arpeggio activation

#50

@futil: do a factory reset or drive format in the bootloader. (Always the thing to do before up- or downgrading)


#51
@futil: do a factory reset or drive format in the bootloader. (Always the thing to do before up- or downgrading)

Thanks <a href=“https://www.operator-1.com/index.php?p=/profile/530/TabascoEye” class=“Username” style=“margin: 0px; padding: 0px; border: 0px; outline: 0px; font-weight: bold; font-size: 15px; font-family: “lucida grande”, “Lucida Sans Unicode”, tahoma, sans-serif; vertical-align: baseline; text-decoration: none; color: rgb(1, 115, 198); background-color: rgb(252, 252, 255);”>TabascoEye<span style=“color: rgb(37, 38, 30); font-family: “lucida grande”, “Lucida Sans Unicode”, tahoma, sans-serif; font-size: 13px; background-color: rgb(252, 252, 255);”> It did the trick !


#52

<span class=“fbPhotosPhotoCaption” tabindex=“0” data-ft="{“tn”:“K”}" id=“fbPhotoSnowliftCaption”>(first time poster, long time lurker - hi everybody)
I hope that’s the correct thread to post that.

REV 218; 8.1.11.1
DNA synth, poly mode, no portamento, piano-like ADSR, random LFO, spring effect as per photo.

I was playing long notes and it happened the first time on the low
register and the second time on the high one.
It freezes emitting a
medium high pitched tone (always the same in both cases).

My OP1 worked always flawlessly. I factory reset it few hours this occurred, and there was nothing on it except for its presets. No other files whatsoever, plenty of space too.

Is that error a stack overflow of some sort? Is it related to some extreme settings on spring or DNA? Maybe they’re relying on some feedback to generate sound and with some settings the software can’t cope with that. I’m more curious than worried.