FX2 - Any way to disable the "modifications will be lost without saving" alert?
-
I would like to use Bias FX2 in a live setting, and would like to switch back and forth between a lead tone preset with a wah pedal and a normal rhythm tone. I would love to use the wah pedal, but whenever I touch it, the tone becomes "edited" and when want to switch back to my rhythm tone, this message blocks any way of me changing presets whatsoever: "Alert: Modifications will be lost without saving. Save the current preset?"
It annoys the living hell out of me and I would like to be able to have full control over which preset I choose and when, regardless of what modifications I made, like using a wah/volume pedal (which shouldn't be considered modifications in general).
Please fix this issue by either
- Removing that pop-up compelitely
- Don't consider using the Wah/volume pedal a "modification" that causes your tone to get an "Edited" status
- Giving pople the option to remove this pop-up.
Thanks in advance and I hope there's a way to get what I need out of this software. I hope more people feel the same way about this.
-
@luca-matioc Please write to us at https://help.positivegrid.com/hc/en-us/requests/new we will create an official bug report to track. Thx
-
@luca-matioc good eye, also anything like toggling of the FX on/off through instant access switching causes the preset to be " *Edited " and the same prompt to save or ignore before allowing you to change presets follows... unfortunately this is not an improvement over BFX1 - was this new feature even needed, asked for, or worth the effort to code in? won't be missed if it's gone and it is not "professional" it is a step backward (like a safety blanket)
spoken plainly this is a Small Bug that will need addressing (removal) - it renders it unusable for live
it appears to be an attempt to make an idiot proof edit mode, my word they really felt this is needed for people to know how to save a preset they make before switching to a different one? we play guitar and use computers we're not complete idiots (most times) and a feature like this is a mistake so can this one get fixed soon please
I'd guess 2-3 quick builds down the road most issues will get addressed - these guys work hard to make it happen and I am sure it will get fixed next
cheers
-
+1 on this. It effectively removes the ability to change presets via foot pedal.
-
@Felix FWIW, TH-U handles this with a performance mode vs editing mode. When 'performing' program changes do not prompt to save even if they have been edited.
-
Thats how! I swear I thought PG already had this on the iOS version of BFX1, maybe it was tonestack
-
@felix today's update:
6.3.2019
Changes in BIAS FX 2 Desktop 2.1.1.4655
Bug Fixes
Fixed the "Toggle Automation reset issue in DAWs" Fixed "IR Loader in BIAS FX 2 Causes Audio Engine to Crash" Fixed "MIDI CC won't be saved when assigning MIDI for BIAS Pedal FX the first time " Fixed "BIAS FX2 closes shortly after opening (without Internet Connection)"
How can this preset switching issue "not be addressed" yet? when it comes to field testing this thing this issue outweighs all of the above imho
-
@PG obviously this will get fixed but this is honestly a crazy huge error that should never have made it public
With any unit that has presets for decades "performance mode" is a Default Concept (I mean 35+ years even) and when you want to make changes you need to save you always entered "edit mode" - such a basic concept as the wheel and does not need reinventing just needs implementation as it should be (if you were real lucky you could even compare the changes with the original before saving...)
Thank you for the effort thus far - keep it coming
-
Man that toggle vs actually on/off for the individual pedals is a SERIOUS issue, I wonder if thats how they adressed it.
It MUST have a on/off, not just toggle...If you have to give up one, please give up toggle! This is a pretty serious issue
-
@pipelineaudio It did... Both the iOS and PC version of Bias FX1 didn't have this alert, and allowed you to change presets after using wah, volume, or toggling effects on/off.
-
Bias FX 1 certainly had the toggle problem though, they are toggle only for most functions, which can lead to serious logic errors
-
@tafkad FX2 V4655 is a hot fix version that mainly focused on IR crash issue.
The preset-switching issue has been addressed before and will be implemented in the next version. -
@pipelineaudio Totally agree with the toggle problem that’s in both Bias FX 1 & 2... That REALLY needs to be addressed. An on/off seems a much better option, and less prone to glitches. An example of this... When using my wah auto-engage scripts in Gig Performer (PC) or MidiFire (iOS)... If the wah pedal isn’t shut off before I switch programs, the wah on/off gets reversed! This results in the wah being ON in the 0 position, and OFF when being used.
My last post was about the “alert” issue every time you try to change presets after you’ve used the wah or volume or turned on/off any effects via MIDI. Bias FX1 did allow you to change presets without that alert popping up.
-
@guitarkite said in FX2 - Any way to disable the "modifications will be lost without saving" alert?:
@pipelineaudio Totally agree with the toggle problem that’s in both Bias FX 1 & 2... That REALLY needs to be addressed. An on/off seems a much better option, and less prone to glitches. An example of this... When using my wah auto-engage scripts in Gig Performer (PC) or MidiFire (iOS)... If the wah pedal isn’t shut off before I switch programs, the wah on/off gets reversed! This results in the wah being ON in the 0 position, and OFF when being used.
My last post was about the “alert” issue every time you try to change presets after you’ve used the wah or volume or turned on/off any effects via MIDI. Bias FX1 did allow you to change presets without that alert popping up.
That's exactly the kind of logic error I'm talking about
-
@felix said in FX2 - Any way to disable the "modifications will be lost without saving" alert?:
@tafkad FX2 V4655 is a hot fix version that mainly focused on IR crash issue.
The preset-switching issue has been addressed before and will be implemented in the next version.Ooooh! Awesome!!! That was one that was kicking my but! I'll be testing tonight when I get back to work
-
@felix said in FX2 - Any way to disable the "modifications will be lost without saving" alert?:
The preset-switching issue has been addressed before and will be implemented in the next version.
Thank you sir we need this fix asap ~ cheers
-
Hey all, got a question..
I just got my midi commander foot pedal and started encountering this scenario when switching presets (60s Love Song / A Strat in London) after a pedal (within the preset) got toggled (i.e. delay/reverb).
Seems it doesn't matter if the pedal went back to its initial state, the popup appears regardless...is there a fix on the roadmap for this or am I missing something?
-
This post is deleted! -
@greystoque said in FX2 - Any way to disable the "modifications will be lost without saving" alert?:
Hey all, got a question..
I just got my midi commander foot pedal and started encountering this scenario when switching presets (60s Love Song / A Strat in London) after a pedal (within the preset) got toggled (i.e. delay/reverb).
Seems it doesn't matter if the pedal went back to its initial state, the popup appears regardless...is there a fix on the roadmap for this or am I missing something?
Nevermind! found the Preset Save Alert toggle in the menu, that did it. =)
-
I know this topic is quite old, but I ran into this exact issue; I found the option in the menu to prevent the alert to pop-up, but if I switch from a preset to another, I lose the changes I did.
For example, I have this preset with a Dumble 50, with a Drive and a Delay that are Off by default, and I turn them On when needed (with a MIDI footswitch); now, let's suppose that I turn them both On, and then I switch to a different preset, and after a while I go back to this Dumble preset, those two pedals that I left On, went back to their original setting, so they're Off.
My question is, is it possible to simply let them be in the state we leave them, On or Off, even if the preset originally would be different?
Maybe it's just a silly request, but it would be helpful for me.
Thank you, kind regards