I’ve found it gets past the boot screen quicker and gets me to the interface, but takes a few seconds to load the project and samples still before it’s playing smoothly. Where as before it would sit on the boot page longer but load perfectly.
Never had an issue once it’s loaded though
How did you guys update your devices? Might worth a try to do the opposite procedure as in browser or via manual download/file transfer to check if that helps with the startup problems.
PN sent
I have over 6gb of samples, always updating via file download. No boot lag at all. I didn’t check sample browser lag yet.
iam most likely - pro firmware updates but with the XY it’s a thing that’s between ongoing development with a lot of hope that some workflow things and features reach the dev. the missing link is the direct communication and with 1.15 up to 1.18 it should‘ve been in the shelves for 2 weeks longer and then drop as 1.20 all the fixes + drum synthesizer + comb filter.
this is some anxious state inbetween updates and that leads to searching the bugs because things get fixed but as long as the lfos haven‘t been rewritten for each track behavior (names + functions) or the step components holding some value twice on the keyboard which could be more complex, with settings per component etc it’s a non necessary looong stretch for feature requests. 
these daily hotfixes need to get merged and idk a newsletter with upcoming features and a realease date to celebrate that day would be more in line these days. it’s the waiting that sucks I guess 
comb filter would negate the need for insert fx I reckon. would be mega.
I also wish -
per track distortion parameter, like elektron digis/tv.
instant pattern reload, or Temp button like on torso S4. would make jamming way more fun.
shortcut for scene change [arr + number]
I’ve updated firmware both ways, boot loader and midi utiliy…makes no difference, same boot lag bug either way.
I find that it passes the boot screen faster as well, and lands on the main screen faster than it did in 1.1.14, but then freezes almost immediately, for 45 or more seconds. For just a second or two it seems to try to load a sample (meaning the empty sample image on screen has a cursor that runs back and forth horizontally, as if it’s searching for a sample to load) until it freezes…every-single-time I load a project.
I also have at least 5gb of content on my unit. Most of it is bought packs that I’ve collected over the past year and a half, and loaded on my unit one at a time. ….which all ran perfectly on 1.1.14 and prior. It’s mostly preset folders from content developers. In fact I have only a small collection of user samples in my sample folder. I’m loathed to try to rebuild all of my packs and content. What a time consuming PITA, which may all be for nothing if it doesn’t fix the issue. So I backed up my projects/presets/samples folders to my computer….done factory resets….and then loaded all my content back on….all to no avail….unit still freezes on boot up…
I think we have to expect it will have some loading time, whether that’s on a boot screen or visible on the interface doesn’t matter to me personally
Edit: don’t realise it was freezing for some people. Does it not unfreeze after a few seconds?
Sounds like I was right to not update before finishing my summer gigs. But looking forward to trying the update in the autumn!
Holy guacamole. My dude, if you can fathom adding a drum synthesizer and comb filter if they wait an additional 2 weeks, you should apply to TE stat.
And Sweden is known for great furniture so you will have the most comfy armchair to design from.
I still agree though. Really should have been a more robust beta stage. Or even any? I’m not sure if ran one or if they typically do.
Only if 75 seconds is “a few”. And then when you load/start a new project, it happens again.
I haven’t gine past 1.15 yet as I’m not experiencing any bugs (so far at least… minimal usage as I’m on holiday with my family).
But I have noticed if I go into the settings menu and tap “ctrl” (M2 or M3…. can’t recall offhand) It gets stuck. The only fix is to reboot. Is this a known issue or am I missing something?
press shift + com
Your situation is identical to mine. I have a 5GB sample library and I am experiencing the exact same behavior. However, I just downgraded back down to 1.1.3 and everything went back to normal. Maybe try some of those earlier ones to see if that fixes it. I’d hate for you to have to rebuild your packs and content.
I submitted a ticket to TE (#267282, thank you so much @MichaalHell!) and they just asked me to upgrade to 1.1.18, but the issue still persists. 
That’s rule #1! Don’t ever update your gear if you’re in the middle of a project, especially live gigs. We shouldn’t have to be so cautious, but things slip through.
Thanks for that info! I did jump back to 1.1.14, but the boot up lag persisted to my surprise, because it was always fine on 1.1.14 before I updated to 1.1.15 or later. With your experience you’ve shared, I’ll try jumping to 1.1.13 as soon as I’m home from work. Here’s hoping!!!
TE needs to get this one sorted!
Edit: I just submitted a ticket (#267427) to TE with a comprehensive explanation.
i’m recording stems to my daw (soloing one track at a time) and am wondering if anyone knows if there is a way to isolate the tape track?
i guess what i need is essentially a pre-fader send to the tape track.