FM3 Firmware Version 10.0

[Chromatizm]

This is the first reproducible case I've seen reported.

I've reported a reproducible case a few pages back, and people reproduced it too.
There's something with compressor blocks in this fw.

 

[unix-guy]

Good idea to try it on other presets aswell !
result: yes, it happens on others aswell. I took a empty preset and just dropped a minimum blocks inside plus the compressor "VCA FB sustainer" and switched to knee type "hard" and it happened again. Coincedantly I had the meters page open and it looks like this in the moment of "crash"
View attachment 156089

View attachment 156090
Maybe that helps a bit ?

Tuner still works and also the meters in the "meters view" untill the compressor block, but after compressor all block meters remain red.

Yeah, that's a pretty convincing case for a Compressor block bug / crash.

 

[unix-guy]

I've reported a reproducible case a few pages back, and people reproduced it too.
There's something with compressor blocks in this fw.

So you did... Somehow I forgot.

 

[Chri B]

I'm unsure if this was happening with the beta release as I haven't rolled back, but I'm running into a really bothersome issue with the 10.0 release in the last couple days.

I have a preset where I'm using the scene controllers and it seems to be causing actual latency within the unit itself (regular FM3, not turbo). I can load it up on the default scene and get sound, but input monitoring and tuner on the unit will freeze, I can spin all of the controls as much as I want without affecting anything, try to change back to different presets, etc. and nothing will happen. Sometimes it will catch back up and go back and forth between changes of presets or scenes in the order I did them, other times nothing. All other presets are fine and work seamlessly, so I'm not sure how I caused this.

All of these issues happen within FM3 Edit as well. Have done RANF, and all of the usual troubleshooting ideas.

 

[Doogz]

I have a preset where I'm using the scene controllers and it seems to be causing actual latency within the unit itself

How many Scene Controllers are you running, and what is your CPU utilization?

Post a pic of the Grid, and if you're running at or around 80%, you should optimise the Preset to stay comfortably under the threshold.

You could try removing unneccessary shunts or blocks, lowering the reverb quality and/or density, tweaking the compressors.

Reverbs and Compressors in FW10 are CPU hungry, and I understand Scene Controllers can be too (happy to be corrected!).

 

[Chri B]

How many Scene Controllers are you running, and what is your CPU utilization?

Post a pic of the Grid, and if you're running at or around 80%, you should optimise the Preset to stay comfortably under the threshold.

You could try removing unneccessary shunts or blocks, lowering the reverb quality and/or density, tweaking the compressors.

Reverbs and Compressors in FW10 are CPU hungry, and I understand Scene Controllers can be too (happy to be corrected!).

That would make sense. I hadn’t realized that the scene controllers add directly to the CPU usage. I had already lowered the reverb block’s density in the beta, but noticed a slight performance increase last night when I set it another value lower before heading to bed last night. I was sitting right around 80-80.5% before adding the scene controllers and the displayed value never changed after the fact, so I didn’t put two and two together.

Only utilizing 2 controllers FWIW.

 

[Joel.Brown333]

I loaded up FW10 and was disappointed that I didn't play any better. I still did the same old cheezy riffs and made the same mistakes when playing the same old songs.

Actually, I didn't notice any difference, but I don't really use much in the FM3. It sounded great before; it sounds great now.

 

[Doogz]

That would make sense. I hadn’t realized that the scene controllers add directly to the CPU usage.

The CPU has to "listen out" for whether the Scene controller will be called upon to do something.

I understand that the CPU % shown is like a rolling average... sometimes it will be up a bit, sometimes it will be down a bit, depending what is pesent in the Scene, whether the FM3 is processing audio, what the GUI is doing.

I try staying under 80% wherever possible. Even removing unused shunts can save 1 or 2%

 

[Doogz]

I loaded up FW10 and was disappointed that I didn't play any better. I still did the same old cheezy riffs and made the same mistakes when playing the same old songs.

Perhaps you need an @Joel.Brown333 FW update?

 

[TimPRS66]

After being totally spoilt with the FW 10 release.

Can we hope for some of the goodies from FX3 28.07, would love the “Guardian Photon Speed” Danish Pete on Anderson’s TV used to rave about it.

 

[guitardoc]

Hi everybody,
I'm away from the machine, so some terms I use may not be correct but I hope I can make myself understood.
Just updated to FW10. My 30+ Presets have way too much output now (maxing out the output at +10!). Would you rather reduce the amp block level in each scene of each preset or reduce the overall output of the presets?
Thank you.

 

[Jens973]

There is no right or wrong really, but I prefer to have max output level when level knob on the unit is at max aswell. So I would adjust the amp block level. In this manner you avoid unwanted too high output levels by accident.

 

[unix-guy]

Hi everybody,
I'm away from the machine, so some terms I use may not be correct but I hope I can make myself understood.
Just updated to FW10. My 30+ Presets have way too much output now (maxing out the output at +10!). Would you rather reduce the amp block level in each scene of each preset or reduce the overall output of the presets?
Thank you.

Aside from Compressor block changes, I can't think of anything in the updates that would do much to levels.

What firmware did you update from?

Maybe you just changed the physical Level knob?

You should use the Leveling Tool to adjust your presets to be very close to 0 in the tool's VU meter.

Using they Amp block Level control is the recommended approach.

 

[guitardoc]

I had to turn down the physical level knob from 12 o'clock (my go to setting) to about 10 and the presets were still at +10 in VU meter. I came from 9.03.

 

[unix-guy]

I had to turn down the physical level knob from 12 o'clock (my go to setting) to about 10 and the presets were still at +10 in VU meter. I came from 9.03.

If your presets have a Compressor block you should definitely think about that as the source...

The physical level knob doesn't affect the VU meter in the Leveling Tool, if that's what you're referring to?

 

[guitardoc]

If your presets have a Compressor block you should definitely think about that as the source...

Oh yes, I do have compressors in my presets. Without having to read all the posts what is wrong with them?

 

[unix-guy]

Oh yes, I do have compressors in my presets. Without having to read all the posts what is wrong with them?

Nothing "wrong" but many were changed or replaced. I found I was getting a big level boost with my previous settings.

COMPRESSOR BLOCK UPDATES
● New Dynami-Comp algorithm with full control set and low-CPU version.
● New VCA Bus Compressor (replaces Studio FB Compressor).
● New Optical Compressor with doubly dynamic times and emphasis control.
● New JFET Compressor, perfect for grit and tone shaping.
● New JFET Pedal algorithm (replaces JFET Sustainer).
● New Rockguy Compressor Type.
● Updated Tube Compressor (now “Vari-Mu Tube Compressor”).

 

[guitardoc]

In this case I'll have to check all my presets. So much to do, so little time... Thanks for the help!

 

[FractalAudio]

today I played a bit with the VCA FB Sustainer. When switching to knee type "hard" the unit stops to output any audio signal - and no chance to recover - the unit stays alive and operable but no sound at all even after changing the preset. Only power cycle brings back sound.
This issue is reproducable. Each time I switch to knee type "hard" this happens.

Is this a confirmed bug? Or only on my unit/setup/preset?

This is a known issue and has already been fixed for the next firmware release.

 

[Boltneck Music]

Anyone else having this type of issue after doing an update. Before you ask, Firmware 10 update installed, dyna cabs, and factory presets as well. Refresh after Firmware performed three times. This is what I got, no value on many of the blocks and the unit freezes after a few minutes. Talking briefly with Fractal support via email. Sure wish someone from customer support would call and walk me through a fix. Any advise would help.