BIAS FX 2 v2.1.9.4865 Beta
-
Dear BIAS FX 2 users,
Please feel free to try BIAS FX 2 v2.1.9.4865 Beta below, any feedback is welcome!
Windows
Mac
BIAS FX 2 v2.1.9.4865 Standalone
Release Notes
Fixed "Guitar Match inconsistent on/off status in DAWs"
Fixed several Scene Bugs
Fixed "preset edited status is not correct"
Fixed "Can not save amp knob settings in certain scenarios"
Fixed "MIDI errors in Scene mode"
Fixed "Uni-Vibe pedal reverts back to default after relaunching"
Fixed "Looper Metronome issue"
Fixed "Can't read Amp2 license in presets"
Improved Effect Pedal/Rack sequence in the effect menu
Fixed "iCloud sync crash issue" (Mac only)
Fixed "User banks are not selectable"
Added two new Guitar Match models
Added "Backing Track" feature in Looper
Fixed "license inconsistency issue between ToneCloud and the app"You can also contact us here
-
This post is deleted!
-
@feeb13x Sorry it's corrected
-
@mike On the guitar match, isn't the body on the YJM signature suppose to be Alder, not Basswood?
-
@tylmay said in BIAS FX 2 v2.1.9.4865 Beta:
On the guitar match, isn't the body on the YJM signature suppose to be Alder, not Basswood?
It's a Japanese model!
-
Missing the most important thing. PERFORMANCE IMPROVEMENTS. This works fine in stand alone. Terrible when trying to use in a DAW for recording. Enough with the gimmicks. Less CPU use should be priority number 1. I have elite and I'm pretty disappointed. I have no problems with other amp software and can run and record with MANY synths.
-
@thievedletter There is zero difference for me between cpu/memory usage on standalone vs. inside a DAW using vst. (I'm using the Windows version). If the difference is that stark for you in your DAW, it's the way with which your specific DAW is handling the plugins.
Keep in mind, this is a premium virtual amp/fx module, and as such it takes up a lots of resources. There are ways to limit this, such switching from Dual to Single routing, using other less CPU intensive sources of IR's etc., but if you insist on Dual amps and cabs with intensive IR's and a lot of effects, and you want it to sound great, you're going to have to use a lot of resources to make it happen.
-
@myxolydian said in BIAS FX 2 v2.1.9.4865 Beta:
@thievedletter There is zero difference for me between cpu/memory usage on standalone vs. inside a DAW using vst. (I'm using the Windows version). If the difference is that stark for you in your DAW, it's the way with which your specific DAW is handling the plugins.
Keep in mind, this is a premium virtual amp/fx module, and as such it takes up a lots of resources. There are ways to limit this, such switching from Dual to Single routing.
Calling something "premimum" is not an excuse for it to run terribly. In Studio One and Pro Tools, I have the same issues. If I have a project with several instances of Bias FX 2, when I load the project, I have to open each instance of Bias FX 2 for them to even pass audio. I have hundreds of other plugins and this is the ONLY software that acts this way. I have ZERO issues with other company's guitar plugins (Amplitube, Overloud etc.) Bias simply will not pass audio when armed for recording. Customer support was VERY unhelpful and basically said "well it works for us"
-
@thievedletter I have heard a lot about cpu/memory issues in the past. But to be honest, I have never had an issue with Reaper not being able to handle 5-6 issues of bfx2 with some 10 other tracks wtih vst instruments etc... if thing do get a little slow/chonky, I just render the stem and continue. IMHO, I agree with Mix... this is a pretty complete signal path simulator... got to expect high cpu use. But I also suppose different DAWS handle things differently.
-
@mike Always good news when a beta is available :-)
-
@thievedletter said in BIAS FX 2 v2.1.9.4865 Beta:
Missing the most important thing. PERFORMANCE IMPROVEMENTS. This works fine in stand alone. Terrible when trying to use in a DAW for recording. Enough with the gimmicks. Less CPU use should be priority number 1. I have elite and I'm pretty disappointed. I have no problems with other amp software and can run and record with MANY synths.
Are you RSMcGuitar from the Cakewalk forums?
Anyway I never had any of the issues that you are having either in the quoted post or your subsequent post. I don't use PT, but I do use Studio One and I never found BFX2 to be CPU intensive, I could use all the instances that I require and not even have to think about it, the other issue you speak of is also foreign to me, always worked fine. Your problem may lie elsewhere?
I no longer use PG products (I keep an eye on it), but it certainly wasn't due to performance issues, but more 'quality of life' issues, omissions of basic stuff that have been missing in ALL PG products since day 1 which are available and considered 'standard', 'required' in practically every other amp sim or plugin out there, and even though people have brought it up again and again over the years, PG has never bothered to implement, from things like 'usable' value readouts to their pathetic preset management and on and on it goes.
Totally agree on the 'Premium' thing.
-
Found a bug. Going to the backing track selector and loading a track: the file explorer window does not show files based on the pre selected filter. I have to use . to show the audio files.
-
I've downloaded the 2.1.9 Beta
I'm using Reason. I open a saved song that uses Bias FX2 and UniVibe. Yes, the settings come in as what I've saved instead of the defualt.
But the problem is that I have to load a Preset from my Bank 1 to get that to happen.
Every song that I open defaults to American Dream Bias FX 2 initial setting. That's not helpful.I need the saved information with the song to come back. That isn't happening.
I've saved the install to all the same default places.
When I saved a song in Reason before it would not require anything more than the song save to recall what Bias FX settings I wanted. Now it seems that all those setting have been lost.
Even when I pull a Combinator setting it reverts back to American Dream, not what I saved.
This is a step backward in the settings, even with the one step forward with the UniVibe.
Not HAPPY!
Ben
-
@estm8ben said in BIAS FX 2 v2.1.9.4865 Beta:
Every song that I open defaults to American Dream Bias FX 2 initial setting. That's not helpful.
We'll look into this, thank you for your feedback!
-
@mike said in BIAS FX 2 v2.1.9.4865 Beta:
@estm8ben said in BIAS FX 2 v2.1.9.4865 Beta:
Every song that I open defaults to American Dream Bias FX 2 initial setting. That's not helpful.
We'll look into this, thank you for your feedback!
It's the same here, Mike. I've verified in ALK2, GigPerformer 3.6, and Cubase 9.5. (Win64 version)No matter which preset you save within the DAW, FX2 always re-loads as American Dream now.
-
@myxolydian I also see this in reaper. Interestingly, if I have a project with multiple BFX2 instances. The first one to load has the correct preset. The later ones have an incorrect preset AND ask me to log in to tone cloud again. On some occasions the American dream is not the right configuration. It SAYS american dream, but the amps and effects are incorrect.
-
@myxolydian said in BIAS FX 2 v2.1.9.4865 Beta:
@mike said in BIAS FX 2 v2.1.9.4865 Beta:
@estm8ben said in BIAS FX 2 v2.1.9.4865 Beta:
Every song that I open defaults to American Dream Bias FX 2 initial setting. That's not helpful.
We'll look into this, thank you for your feedback!
I just reverted (clean install) to .4840, and the problem goes away, so it's definitely something new with the .4865 Beta version.
-
@myxolydian Thank you all, we've fixed it from here and will get back to you with another beta later, thanks!
-
@Myxolydian @paul-jones32 @estm8ben
Please try this version to see if the issue is resolved, thank you.
-
@mike
I tested .4880 in the above mentioned DAW's from my previous post and the issue was resolved in all 3.
Thanks, Mike!
