Yes please!! without this, browsing the presets is very painful when using an actual Amp and cab
1 Like
Bump on this one. Would love to see this feature included in a future update.
I ran my Kemper this way, and it made everything super simple routing wise.
Sure I could use an fx block, or run a split. But as mentioned by others here I would then loose my post effects (delay, verb ect ect ect).
Being able to split a capture to amp/cab would be very nice too.
1 Like
Thats a muĂt have in furtureupdates.
I came from fractal and it´s so easy so disable the cabsim global.
To dis/enable it on the output you want is a great way i think.
Hope it`s coming soon 
This would be so amazing! Hoping this comes in an update soon!
1 Like
Youâve got my vote. I also used this feature on the Kemper. If youâre monitoring though a physical amp/cab while also sending to FOH, this is almost a no brainer. It made all the difference in the world for my bass rig.
2 Likes
why are people so interested in this? you can literally do this with an fx loop block before your cab block
If it can be implemented outside of the lanes, it saves a block.
It would be nice if there was a Button to deactivate alls speaker Simulations.
So if you switch the Preset the speaker is deactivated on all Presets.
If you play your QuadCortex through an power amp with an Classical 4x12 or sth like That you donât have to deactivate all sims while switching the preset.
I suggested this and specially for outputs 3/4 only a few times here and there.
For some that may not fully understand and to add another reason.
I like my post effects after my cab/ i.r. when going to front of house.
1 Like
it shouldnât actually matter whether your FX (time based FX) are before or after a cab block. cab blocks are just a form of EQ
Exactly, i dont want that eq affecting my signal chain in that way. Itâs just a preference thing, i completely understand that it doesnt make a difference in terms of functionality for the effects themselves. A many of Axe users place a cab block at the end of their chain to go FOH with a split right before to go to their real cabs. Surely, if its fine for them and the engineers that run their sound, than it cant be too bad. Again, its just a personal preference. Gun to my head, A/B comparison, i have to pick one, Iâm gonna choose post effects after the cab block. This also is because i feel that gain structure and reactive nature of the amp tone is better this way. YMMV
Yeah - what I mean is it wonât have any effect at all on most FX because the cab block / IR doesnât interact with the amp the way a real cab does and the cab doesnât have any nonlinear components like a real cab. Not to say thereâs no reason youâd want to do it, but it shouldnât be affecting the tone either way
For sure the difference is negligible, some just prefer after. For me its the difference that the cab block acts like a filter so any delay and reverb will have automatic high cuts for example or possibly more emphasized lows. Another thing to point out i thought of early is how most fixed signal path multi effects units will be layed out in the same way by having the cab block somewhere near the middle and all other post effects after. I suppose, this is more akin to like a live rack system where after the cab is micâd it then sends the mic to a series of post rack effects or even in studio settings where basically the same thing takes place plus or minus plugins these days. Although in most regular setups, all post effects are in the amps loop anyways. So in this way, its more like youâre saying I think, where it doesnât really matter that much because it mirrors most modern real life stage applications.
I guess Iâm just used to doing it this way and can be classified as a bougie neurotic gear nerd guitarist and dammit! I want my i.r. before my delay and reverb cake and have my none i.r. signal easily bypassed with a one press button and eat it too! 
Can you not set output rows to the multi out, then set which outputs you want to have cab bypassed? You can also use panning to reduce outputs to just one side as well?
That was my interpretation/plan at least:
- Row 3+4 both set to multi out, cab bypass set on outputs 3/4.
- 1/2 become main FOH outs, 3/4 can go to stage power amp.
I can then pan everything on row 3 one way so that outputs 1+3 are for that row, then do the opposite on row 4 and have that in output 2+4.
Yes you could do it this way but you require separate paths/rows for FOH and stage monitor. That sort of defeats at least one of the primary purposes in my estimation for having global cab/IR bypass. To my way of looking at it the whole point to having this is not requiring additional split/merge blocks or separate paths and output blocks for FOH and stage monitor. You should be able to set global bypass with an option of which physical output to bypass the cab/IR to.
That way you can have, for example, one long four row serial path that takes up four rows and terminates in an output block set to âMulti Outâ. Plug your feed to FOH in outputs 1&2 (XLR) and your feed with (no QC cab/IR) to your amp/cab in outputs 3&4 (1/4"). No fuss, no muss, maximum flexibility. That is how I read this request. I think it covers the most common use case in the most elegant implementation.
I would keep the row-by-row global cab/IR bypass option, 'cos well, itâs already here. Adding what I think should have been the most important feature, output based global bypass would make this feature extremely flexible and be a boon to performers. Super useful for flipping back and forth between studio, rehearsal, stage, jams sessions, or whatever. One preset to rule them all, regardless of what destination equipment is being connected.
Last but not least maintaining one pair of rows for FOH (e.g. 1&2) and one pair (e.g. 3&4) for stage monitor means having to keep all your block modifications for each row pair (FOH and monitor) in synch. Perhaps I am not properly understanding the routing scenario you are describing.
1 Like
Ah, just gone back and rechecked the video, I missed that it was per row, not per output 
Yea, thatâs basically useless for what I wanted to do and is only really useful for those that switch between an actual cab and just DI.