Auria Discussion Board

I agree with Tarekith. Get the levels right first. Then EQ. Then try compression. Mixing is all about levels.

mixing vocals is probably the most difficult part in a mix. If you succeed, the mix has good chances to become good. Difficult to give advices. Maybe just try again and again. Doubling is a good idea already. EQ and compression should be familiar for an engineer, and if you're not familiar with it, ...

sorry for being not clear, with DAW I meant Auria. In general it is recommended to have Auria (or any other DAW, be it on a tablet or on a computer) as master clock, and all synths/sequencers as clock slave.

It is normal that the slave starts automatically.

syncing in iOS can indeed be very difficult. Often it simply doesn't work at all. See also this topic:

http://auriaapp.com/forum/viewtopic.php?f=19&t=11950

both devices send MIDI clock, which is not the same as MIDI Time Code (MTC). If you set Auria to receive MIDI clock it should work in theory, but in iOS there's no guarantee. Furthermore, there may be sync, but no start/stop. Generally it is better to have the DAW as master clock, there's more chanc...

that is correct. I have another interface that has a fixed sampling rate of 44.1 kHz, and with that one I can only do Auria project at 44.1 kHz. Which is enough for common line-in and middle-class microphones.

Phil, Have you tried a 96K project with all audio interfaces unplugged? This seems to be an issue with iOS7.1 Rim no. I have heard of problems without interface, so I did not try. 44.1 and 96 kHz projects with interface is fine, that's all I can say, sorry. Maybe I should add that I don't see any s...

did a short test and could not find any difference to 7.0.4. Everything is working perfectly well as it should, not worse, not better (graphics). iPad4 with Apogee Duet 2.

since I have only iPads v.2 and 4, I cannot comment from own experience. But from what I've heard, the v.3 is the worst in performance. It has the so-called retina display, and not enough RAM and CPU to support a fluent performance. It seems a well known problem with v.3, I'm afraid to say. Use the ...

I was thinking more along the lines of that it would look clearer and also display nicely in retina displays, rather than pixellated like currently. Just a suggestion :) ah, I see. I wasn't even aware that one can see pixels, I guess I only look at the meters and try to hit the right button when wo...

I guess the bitmap graphics take a couple of kilobytes of memory - no big deal. I could be wrong, but I think vector graphics won't improve performance remarkably. Just a tiny bit more free RAM is the only advantage. The same with other apps (synths, sequencers, DAW's), they all use bitmaps.

instinctive wrote:There's really only one single thing missing to make Auria the first complete, professional all-round DAW for iPad. But, I'll shut up now. The last thing Rim needs now is (perceived) pressure

I share this opinion, too.

unplugging the lightning cable while the Maestro app is running, and plugging it again solved all issues with my Duet 2. It's not ideal, but as long as it works ... Don't know if that is of any use for you.

if it can take up to 8 seconds to lock, I think you should forget about wifi and connect the iPad and the DAW with wired MIDI. MTC or MIDI clock over wifi seems adventurous anyway. Such things should always be done with wires. Strangely it works very good at my place using wifi. With Auria only, whe...

my experience is that Cubase and Auria are completely in sync (using both metronomes for quick check), but it takes a moment until Auria locks to MTC. What you are describing appears not possible to me: either it locks and is in sync, or it doesn't lock and doesn't even run. I don't know if this hel...