L
luke
Guest
…
Last edited by a moderator:
How about a screenshot of your III patch for those of us in the back?Can we discuss this a bit more please?
If I were to get down to one cab block by merging the two cabinets in Cab B (via Cablab I suppose) and placing them in second slot of Cab A, and changed out MTD2 for say the Plex Delay in the FM9, would that suffice?
Shunts on the FX3 use about .12%.I don't know if it would make any difference, but that's a ton of shunts, on the FM3 deleting those extra spaces can be helpful.
(6.5-4.8)/14=0.1214
.(15.1-12.8)/12=0.1916
.Mmm... The perverse joy of refactoring...Out of perverse curiosity, I refactored the preset to remove extraneous shunts and took it from 36 to 11. The original has several empty slots in the cabs so I filled those with quick grabs from the factory IRs just so I could get output on several of the scenes, and, after refactoring the scenes sound the same in the before and after versions. The CPU utilization went from about 73% to about 69%.
View attachment 87868
Doing this reminded me of the days when a co-worker would hand me a pile of spaghetti code and I'd start refactoring to try to wrangle some order from the chaos.
You bet. It's a discussion forum.Can we discuss this a bit more please?
I don't think so. But I can do a quick refactor in the FM9 and tell you for sure later tonight. I think you need to consider getting down to one chorus block as well. The delays and time based effects on that return loop are using a lot of CPU for a single scene that looks like it's a super special effect/sound scene.If I were to get down to one cab block by merging the two cabinets in Cab B (via Cablab I suppose) and placing them in second slot of Cab A, and changed out MTD2 for say the Plex Delay in the FM9, would that suffice?
Oh, the MTD2 is never used so removing it will drop CPU usage by 4-ish %.Out of perverse curiosity, I refactored the preset to remove extraneous shunts and took it from 36 to 11. The original has several empty slots in the cabs so I filled those with quick grabs from the factory IRs just so I could get output on several of the scenes, and, after refactoring the scenes sound the same in the before and after versions. The CPU utilization went from about 73% to about 69%.
View attachment 87868
Doing this reminded me of the days when a co-worker would hand me a pile of spaghetti code and I'd start refactoring to try to wrangle some order from the chaos.
Do you only use the named scenes in the preset?Yes, but original music.
Do a pitch harmonic while playing the A note (2nd fret) on the G string and press your bar down. You need to turn on the scene EXACTLY as you pinch.
Ok. So you can straight up lose:
They're not completely free. I threw one in to check and the preset went to 82% which is danger zone.Thank you so much.
I believe the FM9 can work for me then.
Just to be clear, adding back in two reverbs would be a non-factor since they are on a different chip correct?