c bon j'ai fait un refresh after new firmware. Désolé d'avoir posé la question aussi rapidement.Bonjour, est ce normal que dans le block drive j'ai dans "type" : legacy ou dynacab comme si c'était le bloc cab. j'ai fait la maj + utilitaires : maj preset. Pouvez vous m'aider svp ?
Always refresh after new firmware. It's the equivalent of this:c bon j'ai fait un refresh after new firmware. Désolé d'avoir posé la question aussi rapidement.
It's not a bug, it's never been advertised as a capability.Correct, seems like the perfect place to inquire about a bug that needs to be fixed, and whether that fix has been implemented in this latest firmware.
This FW 12.b2 seems to use roughly 2.5% more CPU on my FM3 mk1 than FW 12.b1 did, with 75% CPU still being the max before at minimum response to remote MIDI performance slows way down while audio is playing, as does editor response.Hello,
Any FM3 MK1 users tried this new beta ?
I'm curious to know if it takes more CPU and how many % more...
I got a few presets at 75% and hope I will still let them work without issue.
Thank you.
It's not a bug, it's never been advertised as a capability.
It was later added as a capability on Axe Fx III and FM9, which as already mentioned have a different USB implementation than the FM3.
It’s absolutely a bug. And it’s absolutely advertised as a ““extremely high quality 4×4 audio interface” on their product page. Feel free to check it out.
Where does it say that USB latency reporting is part of the functionality?It’s absolutely a bug. And it’s absolutely advertised as a ““extremely high quality 4×4 audio interface” on their product page. Feel free to check it out.
C´mon correct USB latency reporting is a crucial part of a extremely high quality 4×4 audio interface...Where does it say that USB latency reporting is part of the functionality?
All good here for me, have a 20year old RME Babyface sitting on my desk it does the trick for me.The FM3 does not report USB latency. This isn't a bug. It's lack of a feature (in the 3rd-party USB driver). Whether or not it disqualifies it as an "extremely high quality USB interface" is subjective.
At the moment all engineering resources are fully utilized. When/if we get some resource availability we can look into adding this functionality.

Thanks for clarifying the situation.The FM3 does not report USB latency. This isn't a bug. It's lack of a feature (in the 3rd-party USB driver). Whether or not it disqualifies it as an "extremely high quality USB interface" is subjective.
At the moment all engineering resources are fully utilized. When/if we get some resource availability we can look into adding this functionality.
C´mon correct USB latency reporting is a crucial part of a extremely high quality 4×4 audio interface...
Be nice.He knows, he just wants the brownie points.
You've already gotten the answer from the owner of the company (confirming exactly what I said).He knows, he just wants the brownie points.
Create a wish thread or see if one exists and add your voice. That's the right way to do it.I've had an FM3 for years and have been delighted with it in general but I come back to the forums every once in a while to see if the USB latency reporting has been addressed, or is on the roadmap in any way. Since it does seem to be a case of allocating engineering resources rather than a hardware limitation I'm guessing that the only way it will be worked on is if enough of the user base is vocal enough about it to make Fractal see it as a priority over the other things on the to-do list.
So I'm just adding my voice here in the hope of nudging us closer to whatever that critical mass is. For me, personally, a fix for this would be more meaningful update to the unit than anything else.
You can add your voice here: https://forum.fractalaudio.com/threads/usb-latency-fix.217256/I've had an FM3 for years and have been delighted with it in general but I come back to the forums every once in a while to see if the USB latency reporting has been addressed, or is on the roadmap in any way. Since it does seem to be a case of allocating engineering resources rather than a hardware limitation I'm guessing that the only way it will be worked on is if enough of the user base is vocal enough about it to make Fractal see it as a priority over the other things on the to-do list.
So I'm just adding my voice here in the hope of nudging us closer to whatever that critical mass is. For me, personally, a fix for this would be more meaningful update to the unit than anything else.
Create a wish thread or see if one exists and add your voice. That's the right way to do it.
Adding it here to a firmware release thread (especially a beta thread) isn't going to do much.
This thread is about this beta firmware release and will end up locked in the near future when the official firmware drops.
Who is "they"? Might be useful to add relevant quotes / links to that thread.We asked a lot of times in different threads but the main "reason" is that they assume that the FM3 main usage is for live performance and not studio recording and there are workarounds working.