If you were willing to upgrade to 1.30b again and see if the problem came back that would definitely help narrow down whether it’s a bug in the firmware itself or something that went wrong with the update process on some machines, but I definitely get why you wouldn’t want to go through the hassle of that.
For those with UI NOT TESTED issue, I’d be interested to know which OS update method they used: BIN or SYSEX?
BIN here!
1 Like
BIN here, no problems.
1 Like
Just hit my first 1.30b bug. I won’t have time to try to replicate it and submit a ticket until next week.
I brought the OT and Tanzmus along for the holiday so I could practice with the Tanzmaus and get my default project reorganized so it would be fully integrated into the live setup by my next practice on Tuesday. So the only thing hooked up to the OT right now is the Tanzmaus. Right not I’ve got about half a dozen patterns and scenes and two parts that load up by default as a starting point for the live duo I’ve been working on. I don’t use parts much these days, I’ve basically got part 1 geared toward more rhythmic stuff using a couple external synths with thru and neighbor machines processing them, and part 4 is mostly flex machines and is mainly for more ambient stuff, with just three thru machines for the external synths and Tanzmaus I’ll be using live. I spent about 45 minutes jsut now jamming with the Tanzmaus and internal sounds, with som patterns using part 1 and some using part 4 and everything worked fine, but a couple minutes ago I manually switched parts with the sequencer running and this happened:
The buttons all worked still and the display was fine and the sequencer kept running, but all audio and midi output stopped (I was only sending clock and transport to the tanzmaus, but I suspect MIDI notes weren’t being output either, I jsut don’t have the synths that would have been receiving them with me), and the LEDs for inputs C and D (what the Tanzmaus was connected to) got stuck on yellow and stayed yellow even if I physically unplugged the patch cables from them. The only way to get it back to normal was to restart the OT, and after that it worked fine but I didn’t mess with it much and came here to post this instead, while the details were still fresh in my mind.
If avoiding it happening is just a matter of not manually switching parts manually while the sequencer is running that’s OK for the short run for me since that’s not important to my workflow right now anyhow, but if it happened live it would be a big problem, especially since the OT is the master clock for the other guy’s entire Eurorack system too. And also obviously it’s not a bug I’d want to have to worry about avoiding permanently, so hopefully it will get fixed in an update soon along with the rest of them!
I should be able t really sit down and figure out how to replicate it next Wednesday, and I’ll post more details once I’ve done that and submitted a formal bug report to Elektron.
I was thinking it could be related but the symptoms are different so it’s hard to say. For me, everything is still responding like it should but the audio and MIDI i/o seemed to be frozen so nothing would go in or out and the input LEDs were stuck on. But all of the controls I tried before I restarted responded in terms of ebing able to change screens, change scene, change parts, tweak parameters and having the screen and front panel LEDs (except the input meters) act like they should - there was just nothing actually coming in or out of it. Like the interface was working but the audio and MIDI engine was frozen.
New Os OT 1.30C, bug fix release, for those interested!https:
//www.elektron.se/support/?connection=octatrack#resources
2 Likes
Nice, I’ll install that and mess with it tomorrow. Doesn’t seem to apply to the issue I had but at least I shouldn’t have to worry about the UI Not Tested bug showing up now.
List of changes from Octatrack DPS-1 OS 1.30B to 1.30C
Bug fixes
Fader position would sometimes not be stable on some MKII devices.
The device would sometimes report ``UI NOT TESTED’’ at startup, and then respond incorrectly to keystrokes. Does not apply to MKII devices.
Fader position is still a little out of sync for me on my MKII. While in scene A, if I change the rate of a sample in scene B the OT will adjust the pitch of the sample in scene A slightly. Leads me to believe that the fader isn’t able to move 100% into scene A, which is an issue.
1 Like
Did you do crossfader calibration in test mode ?
2 Likes
Thank you! I was not aware of test mode. The crossfader was off slightly. I reset it and everything’s working as it should now. Phew.
3 Likes
So the other day I was working on a project that had one bank using three parts. At one point I copied and pasted some of the older patterns into different locations in the bank, always playing them back to confirm that I had pasted the right one before clearing the source I copied from, and then spent some time working on a few new patterns. About ten minutes later, I went to select a different pattern to work on and discovered:
-ALL of the older patterns that I had moved earlier were now gone
-I was now working in bank 2 not bank 1
-Two of the three parts were now back to their default settings and names (the currently selected one hadn’t changed, though).
-Bank 1 now had two patterns and two parts that were from a completely different project I haven’t opened in at least a month
-Even though I hadn’t saved since these changes showed up, reloading the current project didn’t revert them to the last saved version
-Today, I tried reloading the project from the card and I get a parse error
This is the second or third time I’ve gotten parse errors when reloading a project but I’ve never had the actual contents of the project get jumbled up. I’m using a SanDisk Extreme 64gb card but the first time it happened was with the factory card, and it has happened with OS versions 1.25h, 1.30b and now 1.30c.
Any ideas? I wouldn’t even begin to know how to replicate it for a support ticket.
EDIT: in the mean time I’m going to reformat the card and copy my files back on, just to be on the safe side.
I’ve noticed when switching banks there’s always card activity, like only the current one is stored in ram and the OT needs to read the next bank from the card, and I imagine save the one your switching from…
If your getting parse errors and missing a bank, it leads me to think corrupt cf card issues…
That’s my train of though and speculation…
That’s the weird thing, I wasn’t missing a bank, the changes I made since booting it up had somehow jumped to a new bank, all previous editing done before that session were gone, and the bank I had been working in before whatever happened happened was replaced with a bank from an entirely different project. And all of this happened without stopping the sequencer or interrupting my workflow in any way.
The last time I had a parse error(about 6 months ago) it seemed to actually be propagating from the project in working memory, not the saved version, in that it was fully working but when I saved to card, any saved versions were corrupted, but the one in memory was still fine. Only saved copies of it were corrupt.
Also, just checked the log and the specific file that was generating the error in this case was the .work file for bank 12 (which I didn’t use at all) so it’s definitely something weird going on with banks. Looking at old logs, the previous times I had the problem last summer were the .work files for bank 12 and bank 9, neither of which I had edited at all.
That’s super weird and scary… My OT’s never flinched, it’s been a rock on 1.25H and I’ve never had a parse error or anything weird with the card, it’s never frozen, and I’ve never lost anything…
Being kinda ocd, if I started getting parse errors or something, I’d probably trash the project, get a new card, empty reset, and build it back, but I’m a bit of a must make sure everything is perfect with minimal chances of future failure type…
All of this may have nothing to do with the new OS, it’s probably card stuff, but from reading this and some other funny business on here I think I’m gonna hold out for the D version…
1 Like
Yeah, I have no idea how I could have done it accidentally. I bet it’s the card but I hope not, because it’s only a few months old and these things aren’t cheap. If it happens again I’ll swap the factory card back in.
1 Like
Didn’t use the OT for about 10 days over the holidays. Turned it on today and a lot of the record setup setting were different than when saved. Record sources that had been assigned to inputs, main and cue are no assigned to other tracks, mostly tracks 7 or 8, or have no source selected. The track that had the source set to Input CD last time I used the OT is now set to Input B. Reloading the project didn’t fix anything. Loading the template version of the project (same as the working version but with some effect parameters set differently and the patterns empty except for the trigs needed to activate thru machines and a couple other things) didn’t fix anything - the record setup settings didn’t change.
I’ve got no explanation for why this happened. The files on card don’t appear to be corrupt (at least they aen’t generating errors), the setting shave just changed since the last time the OT was on. Very, very strange. I’m thinking it’s time to do another full backup of my card and then wipe the card itself (maybe do a full diagnostic and low level format from a computer before formatting it in the OT, just to be sure) and start from scratch.
This is a 6 month old Sandisk Exteme 64gb 120mbps UDMA 7
Can’t afford to get a second one to rule out a bad card, right now unfortunately.
Yeah, so the OT is completely messed up. I’m randomly losing data in the record buffers, files will come back corrupted from the card regularly, sometimes the track recorders won’t record from inputs C and D, old projects have their record parameters scrambled, different effects assigned or different flex slots assigned compared to when they were saved, XLV no longer works correctly, resampling sometimes (but not always) results in a feedback loop, even though the settings are the same in either case, it spits a bunch of junk MIDI CC data out when I first play a newly loaded project, sometimes (but not always) the lights on inputs C and D flicker even when there’s no input. I wouldn’t even know where to begin a bug report. It was working perfectly two weeks ago and now it’s completely unusable and the only thing that happened in the interim is that I didn’t use it. I’ve got no idea where to even start.
Anyone have any ideas what might be wrong? I’ve got a show coming up in a couple of weeks and this is a huge problem.