I’ve run mine in that mode since day 1 and not had issue. Think it might still be the IR’s
thanks.
Most of my issues began when I imported impulse responses. that's my workflow. I am totally fine with the FAS sounds but they all revolve around IRs. That's my preference. I want to give L6 my business so if I can get presets on the Stadium to sound close with the same IRs then I am good with it, but it has to be a stable system.
Perhaps it's the underlying conversion engine on Stadium or perhaps the topology of scanning IRs on boot but there are definitely some lingering things going on.
- when importing large amounts of IRs in nested folders, boot times are much longer, boot stalls, full on boot freezes at the banner screen, and overall sluggishness even after boot
- I removed the nested folders and put 2000 IRs in a flat file system, still issues, sluggish at times. Boot times were better but not as quick as an empty device
- with all IRs installed, I changed stomp mode from default (stompA/preset) to (stompA/Snapshot) from then on, most boots failed to activate the footswitch lighting and their functionality. I attempted to toggle it back to default but the encoders seemed sluggish or unresponsive, IMO there is something going on in the background that is bogging it down
- when putting it back to StompA/preset and rebooting it still randomly boots with or without footswitch functionality
- it seems to freeze up momentarily at random times.
Like I said all of this started when I imported IRs but those are important to me so I'm letting L6 attempt to remedy things. I do not plan on removing them unless there are a few that are problematic. Are some impulses corrupt? Was there an error in conversion for some? Is there a lingering background process still spooling causing other processes to struggle? Perhaps
On a positive note: The L6 support team put my image on 1.2.1 (like mine) and were able to reproduce my issues. They then put it on a soon to be released fw version and they stated it seems to be good/fixed.