Is there a known issue using BIAS FX 2 as a plug-in within Ableton Live 11 Suite?
-
Re: "Can't delete undo.cfg" in Ableton Live
Hi all,
Is there a known issue using BIAS FX 2 as a plug-in within Ableton Live 11 Suite?
Whenver I use the plug-in within an Ableton project, upon closing the project I see...
"C:\Users\Dave\AppData\Roaming\Ableton\Live 11.0.1\Preferences\Undo" cannot be deleted.And it crashes out with the message;
Failed to access the Undo history file. Switching to memory based undo etc, etcYou then have to recover the project when you next open it?
-
@draven-morose
FWIW, I'm using BiasFX2 with Ableton Live 11 on Mac OSX (BigSur) without problems. -
Thanks for the info wilmarboer :) I should have said I am running 64bit everything on windows 10...
-
Hi
I've having this problem with Live 10 on Windows 10 64-bit.Undo.cfg can't be deleted on exit and Live asks if I want to recover on re-opening. I've been considering upgrading to Live 11 just to solve this; won't be doing that if it won't help!
Please post any solution you find.
John
-
27/10/2021 I came back to this after a few months hoping for software patches all round to have fixed the issue. lol. Same as before.
A work around I am playing with is to ensure the plug-in (BIAS FX 2 in this case) is deleted from its track before I quit Ableton.
So in my project I have a track which records directly from my guitar. This sends to a track which contains the BIAS FX 2 plug in. From here I record to other tracks to get my different guitar tones. When I am done playing with the BIAS plug in, I save my project, DELETE THE PLUG-IN FROM THE TRACK, and then quit (ignore the prompt to save again).
Not ideal, but it lets me do what I want to at this stage. I guess I won't bother with that new Hendrix pack lol!
-
@gary_hutchings Hi there, Thanks for that but it didn't work for me. The computer said no...
-
@gary_hutchings Sorry, I wasn't clear... I can run as administrator a-ok. It just doesn't solve the problem :) I have already logged the problem with support... Months ago
As an aside, I had a play with my install of Reaper and the plug-ins work fine.
-
@draven-morose Hi, Missed this post till now, but thanks for the work-around.
It's a pain, but if I remember to save the current set up as a preset, it's viable.
This kind of thing is really bad for Positive Grid's image as other posters have noted. I'm in the market for a practice amp, but I wouldn't touch the Spark, because it has all the hallmarks of a similar pain in the arse! -
@draven-morose New user of BIAS FX here, but ran into the same problem as soon as I started with it. Your workaround does stop the error, but a complete pain!
I've tried VST2 and VST3 plugins with exactly the same error. I've tried all the suggestions on the Ableton forum to no avail. I've got many other VST plugins, but this is the only one that causes this problem.
-
The Problem here is the same now 2023 after the big May Update.Please Fix
-
@draven-morose This plug in has never worked well with Ableton Live on windows. I find these threads in all kinds of forums that date back years with no real solution and no patch has addressed it. I've been able to somewhat get around these issues, but it takes time. You can delete that folder to get rid of the error, but it will come back
-
I have contacted the Positive Grid support and they confirmed it. They are saying it's Ableton Live's fault. That Live isn't closing the plugin properly and that's why it's happening.
The Ableton support is saying that they are still investigating it.I blame Positive Grid more, since it's their plugin which has issues in a DAW they claim to be supported. It's also pathetic that they marked the support tickets concerning this as "Solved".
Since it's been years now, I seriously urge anyone using Ableton Live not to buy BIAS FX2, since it is not usable.