Amp block, not Drive block...Hello, you know if is important to reset the drive block with the cygnus firmware to have a better sound or only some drive models?
Cygnus is the name of the modeling algorithm... And it's "Cygnus" not "Cyngus"hello! tell me the difference in firmware 4 and cyngus. i am novice....
i have fm3 firmware 2.oo. i can update direct jumping to 4.0.?
again tell me shor history firmaware and cyngus beta etc... i am lost
thank you
polnareff27
Quoting myself to say, yes, I was confused... It's scanning presets and IRs.Interesting because Axe-Edit scans every time it starts up.
Actually, maybe it's only scanning IRs and I'm confused! I need to double check...
cyngus was released in fw4 beta 1 and updated another 4 times till beta 5, then once majority of defects were identified and fixed as well as bringing some of the effect and other blocks to save versions in AX3 it was released as FW4 (not a beta). people in the community were very excited to use the new beta so they could start trying and hearing Cygnus, (me included) I ran beta, 1,2 and 4,and now on version 4. there are other differences that others will most likely chime in on.hello! tell me the difference in firmware 4 and cyngus. i am novice....
i have fm3 firmware 2.oo. i can update direct jumping to 4.0.?
again tell me shor history firmaware and cyngus beta etc... i am lost
thank you
polnareff27
I've also noticed my FM3 not being recognized on the USB port (Windows 10) since FW4. I found an earlier suggestion to unplug the USB from the computer, restart the FM3, then plug it back in to the computer. Works every time for me and doesn't require restarting the computer.I thought that I did all of that, in that order? But that worked.. Back in business!
Thanks brother.
This is not normal behaviour. As others have said even when running in user mode this doesn’t happen except after doing a new install or upgrade. On subsequent invocations of the editor a quick scan is done but I infer it’s only to establish previous state and is so fast as to be imperceptible. I’d suggest there is something in the way you have Windows configured or the way in which you installed the editor that is causing this to happen.Quoting myself to say, yes, I was confused... It's scanning presets and IRs.
This IS normal behavior unless you disable it in editor preferences.This is not normal behaviour. As others have said even when running in user mode this doesn’t happen except after doing a new install or upgrade. On subsequent invocations of the editor a quick scan is done but I infer it’s only to establish previous state and is so fast as to be imperceptible. I’d suggest there is something in the way you have Windows configured or the way in which you installed the editor that is causing this to happen.
I’m pretty windows illiterate but in the hope that this will help you determine what is happening I’ll describe my setup. I have 2 accounts - Admin and NoPriv which is a user account with no privileges. I install the editor from NoPriv and use the Admin pw to install it. Under the main disc C: this is the directory structure:
C:>Users>NoPriv>AppData>Roaming>FractalAudioFM3-Edit
There are 5 files in the directory. I believe that the key is that the directory is R/W to NoPriv which allows FM3-Edit to save its state information.
I was under the impression that what you were saying was that reading the block definitions and factory cabs was normal. Happy you clarified. I don’t have the setting disabled in the editor and I guess by others’ lights I have a small number of user cabs, 50 or so. But even with moving things around and doing extensive editing on presets it takes less than a second for the editor to initialize.What's not normal is reading the block definitions (which is what I was thinking was happening).
Moving things and editing presets has no effect on starting the editor. Those things can't happen until after it's started and done scanningBut even with moving things around and doing extensive editing on presets it takes less than a second for the editor to initialize.
I have hundredsI have a small number of user cabs, 50 or so.
Sorry. Should have been clearer. The changes I was referring to - moving things, editing multiple presets, etc. - all done using the on-device editor. So the state of the device and the FM3-Edit cache are going to be out of sync. This is where I would expect to see the editor initialization taking longer. But it’s still on the order of a second or so. Just out of curiosity how long is the editor initialization taking when you start it. Maybe the difference lies in the FM3 vs the Axe Fx-III.Moving things and editing presets has no effect on starting the editor. Those things can't happen until after it's started and done scanning
It reads all presets every time. I don't think that part really matters.Sorry. Should have been clearer. The changes I was referring to - moving things, editing multiple presets, etc. - all done using the on-device editor. So the state of the device and the FM3-Edit cache are going to be out of sync. This is where I would expect to see the editor initialization taking longer. But it’s still on the order of a second or so. Just out of curiosity how long is the editor initialization taking when you start it. Maybe the difference lies in the FM3 vs the Axe Fx-III.
Ok... It takes about 15 seconds from launch until scanning is done.It reads all presets every time. I don't think that part really matters.
It doesn't take super long but long enough that I have to wait...
Probably less than 30 seconds. I'll try to time it next time.
Also it may depend on the CPU load of the current preset as I know some other things are affected by that... For example, backups are faster on an empty preset.
From launch from the taskbar 4 seconds. From the time the application window is visible, slightly less than 2 seconds. This may all smack of navel gazing but hopefully the combined numbers provide somewhat of a baseline for what to expect in terms of launch timesOk... It takes about 15 seconds from launch until scanning is done.
Short history: There was Ares. Now there's Cygnus. The end... Until the next chapter.
I said that because the diferent drive modeling. Now is the same that the fx3 as said FAS ar the begining of the post. I reset the chanel of a drive block, and then i put the same tone and drive than before and it sounds diferent. With some models is more notable in my fm3Amp block, not Drive block...