v1.151 submitted to Apple today
v1.151 submitted to Apple today
This will fix the following issues:
- Fixed issue with Delete Automation on Track
- Fixed issue with Auria muting output when using audiobus with an Aux or Subgroup output
- Fixed issue with freezing mono tracks when an IAA plugin is inserted
- Fixed import issue when importing audio for video
- Fixed Apple Loops issue and timestrecthing when importing loops
- Fixed issue with international characters causing problems with Audio Copy/Paste
- Fixed issue with removing an IAA plugin and the previous plugin getting re-enabled
- Fixed IAA issue with mono tracks when closing the plugin outside of Auria.
Rim
- Fixed issue with Delete Automation on Track
- Fixed issue with Auria muting output when using audiobus with an Aux or Subgroup output
- Fixed issue with freezing mono tracks when an IAA plugin is inserted
- Fixed import issue when importing audio for video
- Fixed Apple Loops issue and timestrecthing when importing loops
- Fixed issue with international characters causing problems with Audio Copy/Paste
- Fixed issue with removing an IAA plugin and the previous plugin getting re-enabled
- Fixed IAA issue with mono tracks when closing the plugin outside of Auria.
Rim
Re: v1.151 submitted to Apple today
Thank you
-
- Member
- Posts: 10
- Joined: Thu Jan 16, 2014 4:51 pm
Re: v1.151 submitted to Apple today
Thanks, Rim.
Re: v1.151 submitted to Apple today
Thank you so much, Rim! Better & better....
Best regards,
Mike E. Dee
Best regards,
Mike E. Dee
-
- Expert
- Posts: 210
- Joined: Tue Nov 27, 2012 2:35 pm
Re: v1.151 submitted to Apple today
Thanks Rim.
Assuming (perhaps incorrectly) that this is the last of the bug-fix updates before the big new update with extra features, is there any chance that you can arrange for users to have BOTH the old 1.151 and the new 1.2/2.0 version installed? I realise this isn't how iOS normally works, but when I was Beta testing MT DAW, I was able to have two versions installed. Maybe there would have to be some clever 'Restore Purchase' feature on Auria 2.0 to allow both old and new to be working side by side.
I'd love to try out the new features of the new version, but in reality, there will be some teething problems as there always are with new features. In the mean time I'd like to keep the excellent, stable and bug-free 1.151 running for day to day work. With a PC or Mac, this is easy. For iOS, the implication is that it's impossible, but is it really? Your thoughts would be appreciated. It would be a big step forward for the iOS world if you could somehow manage this.
Dominic
Assuming (perhaps incorrectly) that this is the last of the bug-fix updates before the big new update with extra features, is there any chance that you can arrange for users to have BOTH the old 1.151 and the new 1.2/2.0 version installed? I realise this isn't how iOS normally works, but when I was Beta testing MT DAW, I was able to have two versions installed. Maybe there would have to be some clever 'Restore Purchase' feature on Auria 2.0 to allow both old and new to be working side by side.
I'd love to try out the new features of the new version, but in reality, there will be some teething problems as there always are with new features. In the mean time I'd like to keep the excellent, stable and bug-free 1.151 running for day to day work. With a PC or Mac, this is easy. For iOS, the implication is that it's impossible, but is it really? Your thoughts would be appreciated. It would be a big step forward for the iOS world if you could somehow manage this.
Dominic
- Anthony Alves
- Expert
- Posts: 1444
- Joined: Sat Mar 10, 2012 9:52 am
Re: v1.151 submitted to Apple today
From my Beta testing experience I believe the difference is that the Beta you tested for MTDaw was not from apples app store but rather sent through a beta channel like Test Flight. At least that is my understanding. If there is something different that Rim knows than that would be cool to keep working versions while trying out the new one. Cheers.~~_/)~~~*
Re: v1.151 submitted to Apple today
There's no way to do this in iOS and still keep an upgrade path from one version to the next. Would be nice, but only beta systems like test flight/ hockeyapp permit what you're describing.
Rim
Rim
Re: v1.151 submitted to Apple today
What about the master strip automation issues? Did those get in the release?
Gary
Gary
Who is online
Users browsing this forum: No registered users and 4 guests