FM3 Firmware Version 4.00 beta 2

I believe this is the first time it's been brought to my attention. Is there a separate thread for this?
I writed even in the FM3 issue on cygnus tread , but in this tread there are some post with that issue illustrated . Agen you choose tap tempo or i believe some footswitch when the led Blink, there Is that issue
 
Hi, new around here,

a couple of days ago received my FM3, stellar sounds, truly amazing! It came with FW 3.0, updated to Cygnus beta 1 and had USB recording problems with my DAW, like it goes out of sync (not latency, it's the recorded audio with the grid that goes crazy) , updated to Cygnus beta 2, same problem, reverted back to FW 3.02 and it's all good!

Just wanted to chime in and let you know, I think I'll wait for the final version.
 
Hi, new around here,

a couple of days ago received my FM3, stellar sounds, truly amazing! It came with FW 3.0, updated to Cygnus beta 1 and had USB recording problems with my DAW, like it goes out of sync (not latency, it's the recorded audio with the grid that goes crazy) , updated to Cygnus beta 2, same problem, reverted back to FW 3.02 and it's all good!

Just wanted to chime in and let you know, I think I'll wait for the final version.
Welcome to the forum. I have not experienced any recording issues with the fm3. By any chance can you share a phone video or obs screen recording to demonstrate the issue?
 
Hi Edrod!, since I went back to FW 3.02 I'm not having any issues at the moment but if I do install Cygnus beta 1 or 2 again I'll make sure to post some samples of the problem, but basically after I recorded something it was like misaligned with the grid so the timing with drum tracks or the metronome was off. I tested this with Reaper, Studio One and Cakewalk, went back to 3.02 and all is good. Appreciate your disposition to help!

Maybe someone still on Cygnus beta1-2 can test this and see if it happens?.
 
Fan issue for me with beta 2 , only heard when I open my FM3 , but for for the first time I heard it when I was playing with beta 2 ,
 
Today, I tested the FM3 in a band context. Running through the Matrix 1000 into a 4x12 Engl Cab. I must say, that I'm impressed. That thing now easily cuts in the mix, retains a nice clarity and the sound is just spot on! the characters of the amps match, the sizzle, crackle, crunch, all is authentic! Thank you for that great work! Fan is still however spinning a bit more often than before.

One thing though, I'd say bothers me a lot is that some the impedance curve changes with the amp model change. There should be a way to chose to not reset it 😉 it's only because I have my own prefered one that just rocks with my cab and I'd like to stick to it.

Cheers!
 
  • Like
Reactions: MNG
One thing though, I'd say bothers me a lot is that some the impedance curve changes with the amp model change. There should be a way to chose to not reset it 😉 it's only because I have my own prefered one that just rocks with my cab and I'd like to stick to it.
To help work through those things that get reset I take a snapshot before doing the reset, then another afterwards. By doing that I can bounce between the original and the reset version to see what changed. As I tweak if it's a parameter I care about I'll note the value in the original and change the latest snapshot to match; I'll take continue that way, taking additional snapshots and comparing those to the original and when I'm happy I'll save.
 
Ok, so I've been playing with the beta .02 for the last 2 nights and discovered a few things, I apologize if I'm repeating things as I've been reading so much I forget where things left off with certain issues. My experience:

In each of my presets I have an Out1 and Out 2 block. I have my signal path split off before the cab block to go to Out2 to send to my Seymour Duncan PS 170 driving my on stage cab. Out1 goes to FOH. I noticed after I reset amp blocks, I level the preset for Out1 (most important) to unity 0db. In the previous firmware my Out2 levels would vary between -15db to -16db. Now the Out2 level fluctuates a lot more between presets even though Out1 all show 0db, but vary from -19db to -24db. Even with these lower levels, on the FM3 itself my Out2 Clip light flickers rather frequently. Having different Out2 levels I'm guessing would cause erratic stage volume between presets with this big of a fluctuation, so I rolled back to v3 pre Cygnus for my show tomorrow night. I can turn the level in the Out2 block down to get the Clip light to disappear, but then the Out2 level drops as one would expect. I have Copy Out1 to Out2 in global config, but I wasn't sure if that gets ignored or has any bearing if the Out2 block is in the grid.

Another observation, I had several presets where I had a TS808 OD drive block in front of an amp to juice it up a bit. After resetting the amp, changing settings on the drive did almost nothing. I changed to a different drive block as a test (Compulsion HP) and it worked as I would expect. Changed back to TS808 OD and still nada. I'm guessing this is user error, but I was happy with the new drive I chose anyway, so I moved on.

Most of the amp changes affected my presets quite a bit, even though it retained the tone controls. I had to tweak a bunch of my presets, but boy did everything sound great when I got them back to what I was used to! The one amp that changed dramatically for me was the Deluxe Tweed. After upgrading firmware, it changed the amp to Deluxe Tweed Jumped and the bottom end was so dark and distorted. Had to spend the most time getting that one dialed back in, but again, once I switched back to Deluxe Tweed and adjusted things, I got a tone that was great as well.

The last thing, I have some presets with a lot of blocks and get close to 80% cpu as you would expect. I nuked a couple of blocks I hardly use so I could turn on ultra res cabs. That said, I have a few presets with very limited number of blocks where the cpu was high where I couldn't turn on ultra res cabs, even though Reverb was set to economy. I forgot to note them before I rolled back, sorry, after the gig this weekend I'll reload the beta and mess with it again to upload the presets for examples. Just thought it was strange to have a pretty basic preset with high cpu (~80%) after the firmware upgrade, as they were at or under 70% pre upgrade.

Overall I loved the sound of the beta, but with the Out2 issue I had to roll back. With only 2 days of tweaking and practicing, I got used to the new firmware and am bummed I had to roll back for my gig. The old firmware/tones aren't bad by any stretch, but this is the first firmware for me where I could hear and tell what a significant difference Cygnus makes. Can't wait to get the kinks worked out. Keep going Fractal Team! I appreciate all the effort!
 
@BryantP, did you notice it ?

Just open the LAYOUT Utility , when the led is blinking under the TAP TEMPO button you can hear the click noise.


I writed even in the FM3 issue on cygnus tread , but in this tread there are some post with that issue illustrated . Agen you choose tap tempo or i believe some footswitch when the led Blink, there Is that issue
 
The link is working again now.
Hey Bryant - thanks.

If I may ask, are we going to see the next BETA -or- Release with the Axe 3 16.02 "engine" in the next day or so -or- is it still days/ weeks away ?

Thanks again,
Ben
 
Last edited:
Back
Top Bottom