As it says in the FM3 manual, the "third party audio interface" setup isn't suitable for re-amping. Not only that, it adds latency and noise due to the additional D/A/D conversions. It also adds complications with level calibration since it's not enough to adjust your levels in the FM3.I’d be interested in reading any comparisons between options 4/5 and the “third party audio interface” option described in the FM3 owner‘s manual. Up until now, I’ve only used my FM3 with headphones, but plan to buy a pair of studio monitors, which I would like to use to monitor my DAW with or without the FM3 powered on.
Only thing I can mention about your situation (been using Cubase since 2006 but I don't leave computer on) is to recover your I/O settings, you can save them, making that process quite a bit easier (you may know this already)! I like having my Tascam Model 12 properly assigned and if a template I want to use does not have things set right, the I/O is easily populated by recalling that saved I/O preset. It is a drop down along the top edge of the I/O channels section. Best of luck in resolving your issue and I would definitely say do any future testing with Axe started before you fire up Cubase!Thanks for the reply. I could've sworn I tried that and it didn't work: the Axe was on at the time, and Audio/MIDI setup was showing it as available as a separate device but not part of the aggregate device I'd previously associated it with. It was almost as if the Axe was registering itself using some sort of different UDID than it had previously, but that doesn't seem likely. It seemed more likely due to not powering things up in the proper order. My computer is always on, the Axe considerably less so, with Cubase somewhere in between (again, with various interfaces).
Probably what would best address it is to always use the aggregate device (regardless of whether I plan to use it), and always ensure the Axe is on before launching Cubase.
That's a good idea: Whenever finishing any edits in Audio Connections, I always save a preset in case I need to restore it later. However, I think SeasonOfPain may be talking about the port names in Studio Setup. Cubase is pretty good about automatically mapping the ports in Audio Connections, so those should be ok when switching to a replacement aggregate. But you lose the port names when switching your audio device.Only thing I can mention about your situation (been using Cubase since 2006 but I don't leave computer on) is to recover your I/O settings, you can save them, making that process quite a bit easier (you may know this already)! I like having my Tascam Model 12 properly assigned and if a template I want to use does not have things set right, the I/O is easily populated by recalling that saved I/O preset. It is a drop down along the top edge of the I/O channels section. Best of luck in resolving your issue and I would definitely say do any future testing with Axe started before you fire up Cubase!
Can't speak on the Apple side, I am constantly looking through Windows! I will try to remember to test later when I fire up the system!!That's a good idea: Whenever finishing any edits in Audio Connections, I always save a preset in case I need to restore it later. However, I think SeasonOfPain may be talking about the port names in Studio Setup. Cubase is pretty good about automatically mapping the ports in Audio Connections, so those should be ok when switching to a replacement aggregate. But you lose the port names when switching your audio device.
I've been trying to corrupt an aggregate for the past few minutes by launching cubase with and without the axe-fx on, but I'm not having any luck making the problem happen. The Axe-FX channels are simply unavailable until I turn it back on. At that point, everything works fine. I seem to remember seeing that happen though. Maybe the problem happened with an older version of MacOS? I'm running Big Sur.
I think SeasonOfPain may be talking about the port names in Studio Setup. Cubase is pretty good about automatically mapping the ports in Audio Connections, so those should be ok when switching to a replacement aggregate. But you lose the port names when switching your audio device.
I've been trying to corrupt an aggregate for the past few minutes by launching cubase with and without the axe-fx on, but I'm not having any luck making the problem happen. The Axe-FX channels are simply unavailable until I turn it back on. At that point, everything works fine. I seem to remember seeing that happen though. Maybe the problem happened with an older version of MacOS? I'm running Big Sur.
So what to do if i have an FM3?
Is there any info that is fm3 specific?
Note I'm using "Axe-FX" to refer to the Axe-FX, FM3 and FM9. If there are specific exceptions to this below, I'll mention them.
Yes i read that. I updated both USB drivers. Maybe its Reaper. There is a lot though that doesn't pertain to Fm3. Maybe the 6.00 beta3 will gitr done. Are there people that are using the Fm3 as an interface and recording multiple tracks and it is working for them?Almost all of it applies to the FM3 and aneptions to this are called out. Near the begining of the guide it says:
What is behind the recommendation for -6dB?Change the output of your “DI” track to Axe-Fx III Output 5/6. Set its output level to –6.0 dB.
Thanks for that confirmation (and all your great doc in this thread). I've not had issues with re-amping, but I'm putting together some benchmark preset recordings so I can make adjustments across firmware updates in volume / tone for gigging presets that are already tightly leveled in for a band mix, so I'm being extra meticulous in the recording process.Yeah, the Axe-FX manual is not right. I should do a re-amping tutorial video.