BIAS FX 2 MIDI control
-
True. I was hoping "mid April" meant sometime this week!
-
Hi All, We're still working on the MIDI feature and it will be implemented in the next update release, the ETA is around 4/20 - 4/25.
Really Sorry for the inconvenience,
Thank you for your understanding
-
@mike Thanks Mike... clearly it is the must have people are Jonesing for. :-)
-
?MIDI? ???
-
Hi All, the next update release might be postponed again to early-May, we're working on some fixes for the issues reported and we want to include as many fixes as possible in this release. We're sorry for the inconvenience again and thank you for all your understanding.
-
REALLY?!?! This is becoming ridiculous. I didn’t spend $$$ on a program because I have nothing better to do than waste money... I’m a regular working musician who spent several hundred dollars on a piece of gear with the intention of actually USING that gear!
To be clear - MIDI control is not just some nifty little add-on toy that I’m not allowed to play with yet... It is an INTEGRAL PART of the FUNCTIONALITY of the program. Without it, the program is effectively USELESS!
Now I t would be ONE thing if there was a delay in releasing the program... But it’s quite another thing to release the program, take people’s money, only to have them discover afterwards that (despite your advertisement) the program is essentially non-functional. And then to, not once, not twice, but three times, promise to fix, then subsequently break that promise! In the mean-time, for over a month, you guys have had all of our hard earned cash, and we have... yet another promise. Really can’t express how disappointed and irritated I am.
-
Bought in to Bias and have pro versions of both Bias FX and Bias AMP 2. One of my main problems with Bias is the really poor midi support, resulting in the inability to use it for live purposes. Was anxiously awaiting the release of Bias FX2 with it's heralded upgraded MIDI capabilities, and was fortunate enough to wait for the first comments relative to the "MIDI experience" prior to buying. Now on the verge of going over to TH-U, as this option offers a very easy MIDI setup and use. So does Revalver (a 2013 !!! program), Amplitube (a bit more effort, but in the end totally workable), and virtually all other options available on the market. I would say to Positive Grid; better hurry up and make sure that the next release incorporates proper MIDI support.
-
Let's give PG some time to work on this functionality so that it is an actual enhancement from the Bias FX 1 (quite basic) experience...
-
Shame on you, PG
-
I don't understand the hate. When I upgraded, I was fully aware of the lack of a full feature set. I welcomed the opportunity to get the software early to contribute to bug-squishing as well as having time to learn the interface etc. I still use BFX1 daily, but am working on porting my presets to BFX2.
I see this model being used a lot now, where developers are releasing 90% done software to the greater customer base with the intent of getting an "extended beta test".
I think we just need patience. Which is certainly not encouraged in the interTubes.
-
Hello,
Although I respect the work of PG, I do not understand either how MIDI has been set aside from the very first version.
As many posts I read, this is a major feature, and it worked fine in Bias FX. Even if we may have expected more implementation of MIDI, the one in FX was OK so far.
And the software bricks were probably available in house at PG, as it was available in FX...And postponing all the time to undefinite date is not project managed...
I feel not considered as a customer, who paid for every version...
-
@mike I WANT MY MONEY BACK.
-
What a garbage company. Never buying another product again. Never been treated so horribly as a customer. Ive literally been robbed.
-
@paul-jones32 The problem is NOT that there is limited functionality... The problem is a glaring lack of an interface that makes using or even assessing the software impossible. How do you check if the looper is functional in a real world environment? Or use the wah? Or change a program? We’re not even to the stage where we can check for bugs!
Furthermore, it was NOT marketed as a “beta test” product... It was sold under the guise of being an fully functioning product (like EVERY SINGLE other piece of software they had released prior to this.) with this SPECIFIC feature as an advertised selling point!
I said it before... It’s like selling a car, but forgetting to put in the gas pedal. Who cares if the car has a fancy interior, if you can’t actually DRIVE it?
-
If I recall correctly, and I usually do, it was the same when BIAS FX (1) was released, no midi, had to wait, so nothing has really changed, just another release debacle, business as usual for PG, the BIAS Amp 2 release was also a mess, promised/advertised presets not ready, other stuff not ready, if memory serves me correct you couldn't even integrate it with BIAS FX for some time, same old same old. It would be much better if they released products FULLY FUNCTIONAL as other developers do, but considering all the stuff that other developers include right off the bat as standard and basic features, a lot of which PG hasn't even implemented in any of their products EVER, (decent preset management, visual/at a glance readouts, and on and on it goes, the list is so long and has been mentioned many times before), I don't think that is going to ever happen.
I'm glad I missed the circus this time around, after being onboard since BIAS Amp (1) I sold my PG account some months ago, as I realized they would never add the stuff that other developers consider required and basic, a lot of which makes using a product so much easier and enjoyable, not to mention more efficient. They just don't seem to have a clue, and judging by there business practices, it's all about the $$$$.
I still check in to see if they will ever get their act together lol, but it appears not, same old same old, release a product that isn't ready, with promised and advertised features absent, much talked about and requested omissions ignored as per usual, it's business as usual here at PG lol
Do yourself a favor, there are other products out there that give you everything that PG doesn't and more, and they sound just as good, and arguably more realistic, more 'amp like' than any PG product.
-
This MIDI issue with PG is confusing to me...
First - Why would MIDI be so low on the priority list for them? They are after all, emulating FOOT PEDALS that are traditionally controlled with FEET and would therefore necessitate the use of a MIDI foot controller. Figuring THAT out should’ve been done right after getting the audio interface block done... Well before messing around with “Guitar Matching” or “Loopers”.
Secondly - MIDI is not new or complicated... Why should this pose such a challenge to the programmers? MIDI has been around since the 80’s and is a well established protocol. Furthermore, it is laughably simplistic when compared to “modeling” and the other vastly more complex and cutting edge technologies in Bias FX. I’m perplexed why THIS is the area they’re having difficulty with.
-
I am stoked. But like I said, earlier, I want it done right, so I am willing to wait for it. PG can be slow sometimes but they always do listen and improve things over time. I guess I would be more upset if I had a project hinging on this but I have the app and FX1 in the meantime plus a zillion other plugs. And hardware. LOL.
-
PG claiming they want to wait until they can get all the fixes in shows a very dated approach to software management. More and more developers are moving towards regular smaller releases as a way to get product out quickly and not making users wait 6 months for a patch. They could have released MIDI first, seeing how it's a MAJOR priority for their users and then had subsequent releases afterwards to fix additional bugs.
Also the whole business of always one guy has to be the apologist for the company. Look PG messed up and have now three times gave their user community FALSE and misleading information. There is no excuse for that. That just show poor issue and community management,.
-
Interesting discussion.
I've been a long term user of Bias FX on the desktop and to a lesser extent Bias FX mobile.
I recently made a decision to commit to these software based simulations. I sold all my pedals and purchased iRig Stomp IO.
I've been an even longer term owner of Amplitude desktop and mobile but found myself gravitating to Bias FX due to the what I found to be overall better sound quality, ease of use and flexibility. I also really like the idea that presets made on the desktop version were easily transferable to the mobile version and vice versa. And then several months ago something changed. I'm not sure if the driver was an update to my Mac OS or maybe and update to Bias FX but suddenly it was taking extended periods of time for Bias FX load. It was frustrating and my fix was to fire up Amplitube which fired up instantaneously.
I entered a support request but it was never resolved. Suddenly version 2 was there and when I installed it the loading was back to how the original version worked. So good, but where I go from here depends on a couple of things.
-
Midi implementation. It shouldn't be surprising that the iRig Stomp IO works seamlessly with Amplitube on both desktop and iPad. I just plug it and it works. I have yet to get either the desktop or iPad version of Bias FX to work consistently with the Stomp IO. I had a period of maybe 5 minutes where it seemed to be working as expected then it just kind of stopped. No idea why and I haven't been able to get it working again. So I just go back to Amplitube. Why? because it just works.
-
How tight is the integration between desktop and mobile versions. This is something that the current and the original versions of Bias FX did really well. I could set up a preset on the desktop version and use it on the iPad version. I haven't spent any time comparing how the new desktop version of will integrate with the mobile version.
So where does this leave. If Positive Grid can adequately address the two items I will likely make the investment and buy version 2. If either item is left unaddressed than I think I'm moving back to Amplitube full time. While I'm not sure sound quality is as good the need for midi integration is fundamental and how close they can get to the seamless integration I see with Amplitube and Stomp IO will determine whether or not I stay or go. For me they have to get the midi implementation right and I am prepared to wait.
-
-
Given that Amplitube's VST version MIDI is croaked since at least 2015, I guess we can grumble a bit less, but this MIDI thing sure is frustrating. I have super high hopes that it will be done right, in a way that even Amplitube hasn't yet, so I'm crossing my fingers.
PG is being blamed a lot for violating the rule of much lesser and less friendly and less honest companies where one the the number one rules about software development is "Never say ANYTHING about when". Because they care about us, they violated that rule, and because we're so passionate about their product, we get upset at them.
A regular company would just say "it'll come out when it comes out"