For general questions or discussion of Auria.
5 posts • Page 1 of 1
I can confirm this load problem your having. I have reported the problem to Positive Grid to correct. But to get around this problem, before you select Final Touch in AuriaPro or Auria, simply load Final Touch so that it is working as a standalone and them load it into AuriaPro or Auria while its open in the background, Works with either listing of Final Touch. I reported to Positive Grid the two listings of the app in the app list back when I was first beta testing the app for them, They still have not fixed that as it only shows up as doubles in Auria and not any other daw. Cheers.
Note that Bias Amp, Bias FX, Jamup Pro (but not standard Jamup paid version), and both the paid and free versions of Amplitube do this as well. Tonestack, Tonestack GO, Ampkit, SampleTank, Fiblicator and others do not display these doubled listings though. Odd. I've noted that if the first of the "doubles" is selected, there is feedback due to the mic of the device acting as channel input (even if it's a midi designated channel within Auria). But, if you select the second of the "double" listing it works as intended as an insert effect. This is the case in all the above noted double listing apps. Also note that when the second of the double entry is selected that the red banner can be seen (when tapped takes you back to Auria) but when the first of the double entries is selected (the one that creates the mic feedback) there is no red banner. Again this is the case with all the above listed apps.Anthony Alves wrote:They still have not fixed that as it only shows up as doubles in Auria and not any other daw. Cheers.
Considering this phenomena is occurring in multiple developer apps within Auria and not other DAW (that I have anyway) it leads me to believe this double entry effect is a PSP ChannelStrip issue. Until the cause is determined select the second of the double listings in the ChannelStrip and all is ok.
that is correct. Using the second in the listing is the working one. As I said this was reported here and to the developer years ago. I don't know the cause but weird things seem to happen in iOS audio land. I guess in the end were masters at getting around these problems. Thats why so many Auria users are happy ones because they get the answers they need to keep on going. Thanks to everyone who contributes and helps here. Good job everyone. Cheers.
Who is online
Users browsing this forum: djanton73 and 4 guests