FM3 Firmware Version 12.0

The new FW sounds good. Howbeit, what used to sound like early breakup now more or less has become distortion, nice but beyond compression. I guess that I'll need to push a bit less the compressor block in front of my main amp (Vibrolux and D30) but wondered if other users have the same experience and how you coped with that.
 
The new FW sounds good. Howbeit, what used to sound like early breakup now more or less has become distortion, nice but beyond compression. I guess that I'll need to push a bit less the compressor block in front of my main amp (Vibrolux and D30) but wondered if other users have the same experience and how you coped with that.
Are you noticing it on all presets or just ones you've built? I'm still getting nice edge of breakup, but I tend to use factory presets as a template.
 
With v12, I just can't get a good clean anymore. Everything seems to be distorted now and the only fix for me was to revert back to v11. Hoping that I can get along with further releases but I just can't get along with v12.
 
Are you noticing it on all presets or just ones you've built? I'm still getting nice edge of breakup, but I tend to use factory presets as a template.
My own stuff. I turned down compresser mix to 30% and the input drive of the amps. Sounds better but need to spend some more time on this.
 
With v12, I just can't get a good clean anymore. Everything seems to be distorted now and the only fix for me was to revert back to v11. Hoping that I can get along with further releases but I just can't get along with v12.
I do get good clean sounds, it's just that this FW obviously needs a bit more attention for retweaking light distorted sounds. But the amps react very nicely to my P90's.
 
Olá, todos bem? Espero que sim!

Na parte de PREAMP na opção switch de Saturation, não está alterando o som quando está em (on), antes essa opção alterava o som e tinha diferença entre a on e a on Ideal. Sei que a opção on ideal compensa o volume. A opção (on) foi ignorada nessa atualização?
 
Olá, todos bem? Espero que sim!

Na parte de PREAMP na opção switch de Saturation, não está alterando o som quando está em (on), antes essa opção alterava o som e tinha diferença entre a on e a on Ideal. Sei que a opção on ideal compensa o volume. A opção (on) foi ignorada nessa atualização?
Fiz o teste aqui na FM3 Firmware Version 12, switch Off (aumenta o volume e um pouco do brilho), On (abaixa o volume um pouco e o timbre fica velado), e On Ideal (volume e brilho mais alto que em Off). Nunca alterei esta função. Espero que tenha ajudado.
 
Olá, todos bem? Espero que sim!

Na parte de PREAMP na opção switch de Saturation, não está alterando o som quando está em (on), antes essa opção alterava o som e tinha diferença entre a on e a on Ideal. Sei que a opção on ideal compensa o volume. A opção (on) foi ignorada nessa atualização?
Qual é a versão de FW que estás a usar? Eu estou na 11 ainda, isso acontece-te na 11 ou na 12?
 
I wonder if the next FM3 FW will have the oversampling "fix" in it (?)

On the A3 forum is seems some people are reporting quite a bit higher CPU use when its engaged - which is to be expected.

I thinking it may (?) be doable on the FM9 but maybe the FM3 just doesn't have the grunt (?) -or- the CPU hit is just going to be too high (?)
 
I wonder if the next FM3 FW will have the oversampling "fix" in it (?)

On the A3 forum is seems some people are reporting quite a bit higher CPU use when its engaged - which is to be expected.

I thinking it may (?) be doable on the FM9 but maybe the FM3 just doesn't have the grunt (?) -or- the CPU hit is just going to be too high (?)
I hope they try and include it, even if there’s a significant hit to the cpu. Always good to have the option to build a more basic preset with something like this included.
 
I wonder if the next FM3 FW will have the oversampling "fix" in it (?)

On the A3 forum is seems some people are reporting quite a bit higher CPU use when its engaged - which is to be expected.

I thinking it may (?) be doable on the FM9 but maybe the FM3 just doesn't have the grunt (?) -or- the CPU hit is just going to be too high (?)
If I read the FX3 forum correctly there is choice whether to apply it or not. So presets that are maxed could be an issue. But I would want the choice. I believe it will be added just for “specmanship” as @FractalAudio put it.
 
I wonder if the next FM3 FW will have the oversampling "fix" in it (?)

On the A3 forum is seems some people are reporting quite a bit higher CPU use when its engaged - which is to be expected.

I thinking it may (?) be doable on the FM9 but maybe the FM3 just doesn't have the grunt (?) -or- the CPU hit is just going to be too high (?)
I am sure it will be included - I read somewhere the aliasing issue is a new bug and apparently only found in the latest FW across all products.
 
I am sure it will be included - I read somewhere the aliasing issue is a new bug and apparently only found in the latest FW across all products.

Those are 2 separate things.

Yes and yes.

But what I'm getting at is .... absolutely it is fixable and has been fixed in the A3 with some high'ish degree of CPU trade-off's .... I'm guessing the same may also be doable for the FM9 albeit with an even higher degree of CPU trade-off.

My out-loud thinking is that even if it does come to the FM3, the additional CPU unit may make it a potentially massive /problematic CPU Tradeoff - fine in minimal block presets, but effectively un-selectable when you are [already] running projects in the %70 <->%75 range which is very easy to hit on the FM3

Its not a criticism of FAS .... they have responded ultra-quick as they always do.

Just a potential practical reality if/when it does come to the FM3 which from memory has something like 1/3 to 1/4 of the total juice that the A3 has.

Time will tell.
 
But what I'm getting at is .... absolutely it is fixable and has been fixed in the A3 with some high'ish degree of CPU trade-off's .... I'm guessing the same may also be doable for the FM9 albeit with an even higher degree of CPU trade-off.
No... The "fix" was in the Amp block. There's no mention of additional CPU.

The updated Drive block is an enhancement, not a bug fix, and that is what incurs additional CPU.
 
Back
Top Bottom