Auria 1.06 Bugs

[SFAudio]

Thought I'd start this thread for us to collect information on bugs in the current 1.06 version.

I've only found one so far, so I'll start:

- IR Subfolders don't seem to be working (confirmed by other users too). IR files placed in subfolder to IR Files won't show up. They do show up if placed directly into IR Files folder

[DavePDX]

Hmmm, this works fine for me. The only issue I've found is that I move an IR file that is already used in a project, that project will crash when you try to open it. The only workaround I've found is to duplicate the IR, open the project, then reload the IR from the new location. A bit of a pain.

[Jus]

First of all this update is the absolute Biz. Rim you legend He He

Just noticed a little Bug when recording Jamup through Audiobus (which Rim Already knows about but as a reference )

There's just a little bit of lag on the recorded track

Cheers

[CEIsar]

i have the same problem with IR files but Rim already know about this issue.I have a nice collection of IR files and it would be great to sort them in folders.Who wants to scroll a list with 1000 entrys?

[Pointyhat]

Had a crash using audiobus and now get a crash occurred last time you started the application message every time I start auria.. Can click no on the crash report dialogue And everything works fine, but it is rather irritating to get the Message every time I start the app

[Rim]

That message will appear if you force close Auria while it's in Audiobus mode, or if you force-close it while background audio mode is enabled in Auria's settings. This is because force-closing Auria in this case is interpreted as a crash. In the next version, I'll see if I can exclude this type of "crash" if I can find a way of detecting it.

Rim

[Pointyhat]

Thanks Rim, so once the ' crash' condition has been set up is there away of making the 'error' start up behaviour stop? Tried disabling background audio and restarting Auria and still getting message.

[Rim]

Just don't force-close Auria, and you shouldn't get the error. As far as I can tell, it should only happen if you force-close it, not with a simple close.

Rim

[Pointyhat]

This does seem to be new behavoir in 1.06,I wasn't, experiencing this in previous releases.

[Rim]

The only reason I can think of that would make this new behavior in 1.06 is if you have Audiobus mode enabled in Auria's settings (or if Audiobus is running in the background).

Rim

[CEIsar]

1.if you disable the waveform view,the automation lane disappear as well.It's invisble but still possible to change it (by accident)when you want to drag and drop the automated region somewhere else.I was wondering first why i can't select/move certain regions.Until i got it that i still edit the automation lane in the backgound.

i'm not a fan at all that the automation lane disappear when i switch of the waveform view.I would prefer to have a seperate"hide/view automation" option in the edit menu.

2.It's not possible to access the "Sub 8" and "Master Fx"button if you switch of the CPU meter and open a song where the CPU meter is still visible.It overlays the buttons,not possible to scroll far enough to the left then.

[Rim]

Great, thanks. Those should be easy to fix.

Rim

[CEIsar]

Maybe I found another one.

Look at the volume automation on that pic.On the left side there's the original value but on the right side,after the last control point,it resets the value to zero (i mean lowest fader position,not db) no matter what i'm doing but it should stay at the original value imo.Happens with other automations as well (plugins...).Not sure if it's really a bug but definitely a bit annoying.



http://s1.directupload.net/file/d/3152/4yndg9ya_jpg.htm

[Rim]

Was this project imported from an AAF file originally? Aaf will do that distinctive point at the start of regions.

Rim

[CEIsar]

No,it's a project i started in Auria.