thats interesting wonder if their is a beta out where they are trying to implement the Ultrares and level out the cab block
I know some have faced a similar issue on the Axe Fx III where Axe-Edit seems to be confused about the IRs. There's a tool somewhere in the editor to rescan/refresh the cabs and that corrects the display. Maybe try to do that?
Same here.I've tested the Archeon Bright Amp and no Audio dropout when turning on or off the FAT switch (also waited 10 or more seconds).
With FM-Edit and at device directly tested.
Not needed blocks bypassed - amp-cab- IN and OUT..
But strange behaviour with the FAT switch.
Turning ON makes the AMP asunding "thin" and turning OFF it sounds "FAT".
May this could be a hint for the staff to find the cause of Audio drops with the FAT switch.
It is working vice versa on my device but no dropsouts.
I imagine they would mention something that big in the release notes if it were in the beta.Randall dude...how can we know if Ultra Res is implemented?
Randall dude...how can we know if Ultra Res is implemented?
lol i am not sure Teddis it was more just wishful thinking maybe
Here is my thoughts they are going through alphabetically block by block and trying to match them up
they started with Amp, Chorus Compressor , Cab block would be next then Drive
again probably wrong but that could be the system they are using To keep organized
or I had too much jack daniels
Sounds logical ......I am also buying an extra lottery ticket for tonightlol i am not sure Teddis it was more just wishful thinking maybe
Here is my thoughts they are going through alphabetically block by block and trying to match them up
they started with Amp, Chorus Compressor , Cab block would be next then Drive
again probably wrong but that could be the system they are using To keep organized
or I had too much jack daniels
I had the same exactly issue. It was frozen at the very end of the bar (FM3 logo). Did the emergency load 1.06 and ok. Re-downloaded the beta version, tried again without success (frozen at the same point)...Any thoughts??EDIT:
Re-downloaded firmware, and it installed properly.
Having 1 issue when loading the new firmware. It seems to load, and after waiting 5 seconds and restarting, it gets to the Fractal logo, with the bar creeping across the screen. It stops at the very end.
And just stays there (at least for 1/2 hour, haven't tested longer).
I can emergency load 1.06, which works & loads normally, so I can at least use it.
I am sure this can be worked out, but I just wanted to document my experience in case someone else has the same issue.
Plugged directly to the computer and just disable Windows 10 power management as per your instructions. No change. Still frozen in the end of FM3 logo progress bar. I really can’t understand how it can update on some units and other don’t. Never had any similar issues with Fractal products.If you're having USB issues ensure you are plugged directly to the computer and not a hub, powered or otherwise. Secondly, disable Windows 10 USB power management.
Here is my thoughts they are going through alphabetically block by block and trying to match them up
or I had too much jack daniels
I applied the update and installed the new FM3 edit. Install went fine.
I have a probleem in FM3 Edit, for the Amp block I cannot select a type. The field is empty and the list of amps doesn't come up when I click it.
View attachment 75650
When I select a Reverb block I can select the different reverbs. If I select the Amp block again, the type field for the amp is now filled with values form the Reverb block:
View attachment 75651
Same if I select the Drive or the Wah block, when I select the Amp block the type field is populated with the options from the previously selected block.
Actually the same happens with the Compressor block. When I first select the Compressor block I can't select a Compressor type, the list is empty. When I select another block type and then select the Compressor again, the type field is populated with the type options form the previously selected block.
. View attachment 75652
I did full reboots of both FM3 as well as my MacBook several times, nothing changes.