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

As @candygarage pointed out, we should have a separate thread for bug reports. I will post as soon as I have time to reproduce the things I've noticed so far. Feel free to report bugs if you like.

[Beta OS ENGINE/FEATURE]

[PROBLEM]

[STEPS TO REPRODUCE]
«1

Comments

  • Nice one :)

    I haven't encountered any beta OS bugs yet except for graphics becoming sluggish in certain situations when there's a lot going on in OP.
  • after using the usb drive feature, it's possible to lock the encoders by randomly turning and clicking blue&green. encoders won't return to function until the op1 is restarted, but the unit won't turn off until it's unplugged from usb. 

  • Tape chop effect: Not in time. Still bugs on loop points.

    I had a bug when i switched from one sound to another and played a sequence but don't know exactly why.

    And the following is a bug that came with the sketch sequencer and will not be fixed in the next time. (i asked TE)
    If you used the help button in the sketch or pattern sequencer a note will no longer just trigger a sound, it will trigger the sequence. You have to switch to another screen and go back to the sequencer.
  • edited May 2016
    One time i had this message during start up:

    SEQSTAT 0x21 : RETX 0
    ADDR 0x15ce3ac : STATUS 0
    0xffa00420
    0xffa03418
    0x109abf0
    0x109b406
    0xffa0b578
    0xffa08c0e
    0076

    (USB Cable was connected to the Computer during the start, but this message showed up only one time. Before and after not anymore for now...)
  • inconsistent naming -> DRWAVE -> DR WAVE
  • - when playing the ARP from an external keyboard, you can only use the current range of the OP-1 keyboard
    - you can "overload" the ARP, this leads to hanging notes (missing note-off events).

    i.e.:

    Try creating a fake string-orchestra: 
    - Preset CSTRINGS
    - ARP-Settings: 1/16, Note-Length: 64
    - play some chords
    -> after a short time one note will play continuously and can only be stopped by stopping the arp and playing that note on the keyboard.
  • below error received on startup. not plugged in to anything. probably anywhere between the 5th and 15th time i've powered it on since upgrading. upon first glance appears to be same error as amidis. so far has only happened once
    image
  • drybones said:

    below error received on startup. not plugged in to anything. probably anywhere between the 5th and 15th time i've powered it on since upgrading. upon first glance appears to be same error as amidis. so far has only happened once
    image

    Same as i posted above.

    AND next bug:

    This error came up as i was in the REC window and pressed radio tuning. After a few presses i frozze and this message came up.

    c55a63a558582a528f84f7581cb56c4b.jpg
    1552 x 873 - 128K
  • when I have the OP synced via MIDI (send clock to op-1, select SYNC on tempo page), the loop markers drift here and there on the beta OS. not on the official one. It's way noticeable, after 10 loops of a 1 bar section on the op-1 tape, it's very very off sync.
  • Same as you for sync
  • Hmm, not seeing that sync issue here, pretty rock solid after 10 minutes still. Might be useful to know what other gear is involved, I was using Oplab and Elektron Rytm slaved to Roland SBX1 at 120BPM OP1 connected to Oplab USB port 1.
  • got sync problem, too
  • Iconnectmidi4+ here. MIDI from Cirklon.
  • usb to laptop here. seems to be the same issue that had been fixed a while ago.
  • Wondering if this sync issue might be related to the click reduction on loop boundaries fix? On the example that I tested I just used a drum pattern from the finger seq recorded to tape, so perhaps there was no click correction going on, but if something is hand played then maybe the OP1 moves the loop marker to zero crossing to avoid the clicks, therby throwing off the sync? Just a theory, anyone care to add/dispel/comment?
  • I don't really know what I'm taking about but seems to be more than zero-crossings going on with the loop pop fix. The way it sometimes takes a few passes before the pop goes etc... think maybe some kind of copy/paste section of start to end and vice versa and short fade applied or something maybe. Pretty clever whatever it is. though slightly unpredictable in its consistency still on the beta.
  • @darenager, I was thinking about that as well. I'll try to test it tonight.
  • Yeah. I still get pops, but it's easy to work around one or two. Before the beta, the struggle was real.
  • Can someone verfy that sequenzers / arps are not turned off? (even when you turned it off?)
    it seems that tombola still tomble around even when i switched it off.
  • amidis said:

    Can someone verfy that sequenzers / arps are not turned off? (even when you turned it off?)
    it seems that tombola still tomble around even when i switched it off.

    how do you know? 
  • Well i turn of the ARP / SEQ  and then back in Tape Mode for example i Press a Key and the ARP / SEQ noodles again and i thought "huh?! i turned it off right before!" so maybe this is a new bug i think.
  • edited June 2016
    amidis said:

    Well i turn of the ARP / SEQ  and then back in Tape Mode for example i Press a Key and the ARP / SEQ noodles again and i thought "huh?! i turned it off right before!" so maybe this is a new bug i think.

    I haven't noticed this problem here at all. Is this happening on all sequencer types? You're deactivating sequencer before you exit the sequencer page right?

    If yes to all of the above then I think you might have a hardware problem? My OP initially had a problem where sequencer would occasionally activate by itself or a patch would switch by itself. I had to send it back for repair.

    You didn't have this problem before updating to beta tho right? That's the weird part, as it would normally indicate that the problem isn't hardware..


  • edited June 2016
    Pattern sequencer doesn't play sequence when filling it. Forced to go to the sequencers menu selection, to select it back and be able to play the sequence again. I didn't try with the other SEQ


  • I haven't noticed this problem here at all. Is this happening on all sequencer types? You're deactivating sequencer before you exit the sequencer page right?

    If yes to all of the above then I think you might have a hardware problem? My OP initially had a problem where sequencer would occasionally activate by itself or a patch would switch by itself. I had to send it back for repair.

    You didn't have this problem before updating to beta tho right? That's the weird part, as it would normally indicate that the problem isn't hardware..


    Well now it seems all works as it should work..... maybe i put it back on accidently as i played and messed it up.
  • I don't know if this should be considered a bug, but it annoys me a bit.. The preset in Sampler called "RMK2 NOTE" is tuned a full note up. If you want to play  a C, you have to press A.
  • edited August 2016
    bug in click-smoothing i think - 

     - record from very start of tape for a couple of bars
     - then play in reverse and loop
     - expected: once it reaches the start of tape (start of loop), it should keep playing in reverse from the end of the loop
     - actual: once it reaches the start of the tape it makes a buzzing noise without moving to the end of the loop

    ps: recording from some time into the tape (e.g. half a second in) makes the issue disappear.

  • After installing the beta my Sound 1 key has become dodgy and unresponsive, it takes multiple presses to get it to register at all. I assumed the obvious "fuck my button is going out!" but to my surprise upon running the function test the key actually registers 100% so it seems to be software related. Now the messed up part is I reverted to 14203 which crashed due to the addition of the new files "error arpeggiator.cpp found" or something like that so I factory reset it, but the problem persists.
  • After installing the beta my Sound 1 key has become dodgy and unresponsive, it takes multiple presses to get it to register at all. I assumed the obvious "fuck my button is going out!" but to my surprise upon running the function test the key actually registers 100% so it seems to be software related. Now the messed up part is I reverted to 14203 which crashed due to the addition of the new files "error arpeggiator.cpp found" or something like that so I factory reset it, but the problem persists.

    Haven't noticed this on the beta here so it's prob good idea to contact TE mate.
  • After installing the beta my Sound 1 key has become dodgy and unresponsive, it takes multiple presses to get it to register at all. I assumed the obvious "fuck my button is going out!" but to my surprise upon running the function test the key actually registers 100% so it seems to be software related.

    Could be due to your key having issue before and the new firmware having a different debouncing algorithm. So it might still be HW related but just exposed/amplified by the new FW.

    Now the messed up part is I reverted to 14203 which crashed due to the addition of the new files "error arpeggiator.cpp found" or something like that so I factory reset it, but the problem persists.

    Sounds like you might still have the ARP engaged in either Synth or Drum mode. Try going back to the Beta, explicitly setting the Sequencer to Endless first and then disabling it. Do this for both the Synth and the Drum engine, then revert back to R14203. Report back the outcome in any case :)
Sign In or Register to comment.