Same here. I always convert my IRs to ultrares since I have an AxeFx II also, but almost all of them showed up as standard res in the new firmware until I reimported them.I find I'm having to re-import IR files (YA mainly, but OH too) to get Ultrares working ok, anyone else?
1: if you’re using output 2 to copy output 1, then IMHO I would avoid the beta ..from my experience. I reverted then decided to switch some cables and use output 1 only and ignore out 2 for now and went back to 3.03...very nice.Quick question: if I use output 2, and need to control it, I’ll have a problem with 3.03?
Are us
QQ#2 do we know what causes the foot switch issue, and is there a workaround?
Reinstall 3.02I have blank mini displays - how do I fix that?
Ok, I don’t actually use the foot switching at the moment, so I’ll stay with the beta - was just curious if I was missing an obvious reset etc.Reinstall 3.02
As I said before, there is a bug.I generally hate flashing too, but if you mean the Preset Select flashing, you can disable this by setting your bank switches to load the first preset in the new bank.
The flashing otherwise is not gratuitous: it tells you that the FM3 is waiting for a selection.
Purple means cab is Ultra-Res. Green means cab is Standard.Can anybody clarify - does purple signify that the cab is able to be Ultra-Res and green is a cab that can’t?... if that makes sense?
It was noted earlier in the thread. There's an issue with FM3-Edit messing up the colors. Hopefully it'll be fixed in the next release: https://forum.fractalaudio.com/threads/fm3-firmware-version-3-03-beta-1.171881/post-2073720After checking the lists of cabs, I see the following distribution:
Is it correct that Factory 1 have only one Ultra-Res cab, and Factory 2 have no one?
- Factory 1: The first cab is Ultra-Res, the rest are Standard.
- Factory 2: All cabs are Standard.
- Legacy: There are a lot of Ultra-Res, and a lot of Standard.
On the AF3 white and pink noise use more CPU than the simpler waveforms. Sine seems to use the least CPU while pink noise uses the most (about 5% more). My guess is to generate a bunch of random frequencies/phases present in noise takes a bit of CPU.There’s something strange happening when adding a Synth block on my main preset and turning Track off. CPU usage was around 70% or less but after switching Track off in Synth block FM3 says ”CPU overload”. I deleted several blocks (2 drive blocks, 1 delay block) to add the Synth block for some temporary noise. Doesn’t happen with a new preset with CPU usage around 40%. Synth block type was at Pink noise.
Or does turning Track off in Synth block rise CPU with over 10 %? Not at my FM3, but can try to recreate this and post preset if needed.
Thanks Fractal and to everyone who worked on this one , the drive block is sounding great and all the new additions, the Horizon, Crunch Box, OCD and Voodoo drive are wicked
overall the whole block sounds much better and interacts with the amp models in a much more natural way
and the Ultra Res , thanks. so much for that , my York Audio mix Irs, finally sound like the way I remember them on my AX3
Even if the colors and italics are wrong, when you select a green one and turn it t Ultra Res, is it really UR sound or is it flat out broken?It was noted earlier in the thread. There's an issue with FM3-Edit messing up the colors. Hopefully it'll be fixed in the next release: https://forum.fractalaudio.com/threads/fm3-firmware-version-3-03-beta-1.171881/post-2073720
If it is the same as the Axe3 its a complete overhaul to the drive block new models but it also sounds an reacts quite differentlyWhat else is new about the drive block besides the new pedals? Is it improved sound on the original pedals?
If it is the same as the Axe3 its a complete overhaul to the drive block new models but it also sounds an reacts quite differently