Something went wrong during the maintenance. Some of the profile icons might be missing. Please re-upload your profile icons if this is the case. Sorry for the inconvenience.
Hi.
I experienced the same today.
I’m using Bias AMP 2 on my iPad, connected through Bluetooth to my BIAS Head Processor, himself connected to my Alto TS 215.
I have choosed a patch on Tonecloud, tweak it, then save it to the head, and the sound was really different...
But after, I’ve choosed the same patch on Tonecloud, save it as it is on the head, tweak it and saved it again, then it was ok!
I was just comparing factory bass amps in Bias Amp 2 - iOS vs macOS.
I'm running the bass into an iConnectAudio4+ which splits the signal off into each device. Both are monitored at the headphone out of the ICA4+. The signal paths are identical - there are no effects.
iOS - AUM hosting Bias Amp 2 via IAA - sounds 'brighter' than macOS version
macOS - Ableton Live 10 hosting Bias Amp VST - sounds 'darker' than iOS version
These patches are identically programmed. I'm seriously wondering what makes the difference I'm hearing. FWIW, I prefer the iOS version -- it was also significantly cheaper than the desktop version. Thoughts?
@dawseeker : as I said in that thread, your GUI issue is not common, and points at an OS issue.
I tweak to get something that doesn't exist. But I think I've gotten close enough there with two amps, and will soon spend the half-hour individually deleting the other patches in B and BFX. Patches sound the same in standalone and within DAW over here. That they don't over there suggests an audio routing issue.
@pipelineaudio : I use the paraQ in B, and any of the Qs in BFX to set level. Input and output levels of each instance of either in the signal chain of each channel of your DAW will remain the same within the current project. Each new instance will be at default. Each new instance of B2 will ask for login - which you can skip if you don't need to be connected to Cloud.
@alderre I tried that before and I tried it again but it doesn't change anything.
And I think that option is not for enabling the internal speaker but selecting the type of output you are using. In the FAQ of Bias fx, it says
"3. If you are using external speakers, please select speaker mode in the Setting -> Output Selector -> Speaker."
https://help.positivegrid.com/hc/en-us/articles/115002726886-FAQ-BIAS-Amp-Mobile
Update to the serial vs parallel issue: I bought a Behringer FX2000. It can be switched to mono and in series and the mix can be adjusted. The main thing is that in bypass, the A/D conversion is so good that it does not affect the sound of the amp. However, it would still be good to have the option of series and parallel mode.
I just had a ticket for the same thing. I noticed this problem on all Fender products, not just the spring reverb but all the amps that can be downloaded from the cloud. Some funny going on with sample rates? Anyway, the fix says Bias please call FL support and play nice.
These and a lot of the issues in the plugins are really just quality of life issues. They have the means to fix them, but its hard for them to know exactly what it feels like to be the end user, so they focus on what seems to them to be higher priorities.
This is so much a parallel of when we were first making REAPER. There really wasn't a good liason between the studios who had to use the stuff for a living, and the developers of most DAWs who seem to never have been within 20 miles of a studio and just had no idea what it was we needed. I kept notes, and years later, REAPER was born. I would LOVE to do the same thing for Positive Grid, and I've offered.
@shiand2485 Tone will change but I honestly think thats to be expected. I created my patches at a very low volume, and when I played through a PA it shocked me how different they sounded. Minor tweaking though.
