- #Tracking with uad plugins inside daw drivers
- #Tracking with uad plugins inside daw software
- #Tracking with uad plugins inside daw windows
#Tracking with uad plugins inside daw software
Instead of struggling with inserts, why not just route all tracks/busses out (you would, of course, need to have sufficient I/O) and just use hardware monitoring? Even if you don't have hardware mixer, a lot of software (like RME) allows you to route inputs and outputs out to your monitor port. I'm game for doing whatever is needed to help straighten this out (At least I think I am.) A reboot doesn't seem to have any impact on whether it will or won't act up. Sometimes when it happens.I can't get Reaper to work at all.Sometimes it gets over it quick and the next open everything is fine. Both AMD powered, XP-64, and I've been using the same audio hardware (MOTU PCI-424 with latest drivers). Two different computers I've had this happen on. Open up the error report and all it says is "Hungapp."
#Tracking with uad plugins inside daw windows
Force Reaper closed, Windows terminates it and gives me an option to send off an error report. Only it kinda forgets to actually play.Īfter I took the 3.31 update.I opened this exact project up, hit play, and the message of death happened. Looks like it is doing exactly what it says.Buffering. It pegs a CPU and memory starts increasing at about 2-3MB a second. With just that right there, I can get Reaper to go out to lunch with in the transport bar. Track 13 Tom crush (ReaInsert, Gate, send to OH verb)Ħ ReaInserts, several sends, a folder to sum it all and a parallel compressor on the folder.
![tracking with uad plugins inside daw tracking with uad plugins inside daw](https://help.uaudio.com/hc/article_attachments/360053814052/assigning-cues.png)
Track 9-12 T1-4 (Gate ReaEQ send to Track 13) Track 8 Snare crush (ReaInsert, Gate, send to snare verb) Track 4 Kick sample (Reagate, Reasamplomatic) Track 3 Kick inside mic (Gate, ReaInsert, ReaEQ, 2 Sends, one to Track 4 one to OH Verb) Track 2 (folder) Drum submix (two plugs and a send to Track 1 Track 1 Drum Crush (ReaInsert hardware compressor) You obviously wouldn't have all of my outboard.But you can see what I've got going on. My newer dual, dual-core Opteron 8220 system seems to handle it alright, but I'm concerned how it's going to work in a complex project. However, at that latency level I pretty much dedicate a whole CPU core to just running a 10 track drum mix.įor the record, this would've been completely impossible on my dual-Opteron 142 system. With this setup I can't duplicate my previous issue listed above.
![tracking with uad plugins inside daw tracking with uad plugins inside daw](http://indierecordingdepot.com/uploads/default/optimized/2X/b/bd7ef60d094ac60c950682521aff4d5d37d34276_2_1380x776.jpg)
Overall ASIO latency reported in Reaper, 1.8ms or something like that.
#Tracking with uad plugins inside daw drivers
I want to play with it some more before I get too excited about it though.Įverything at my place runs at 24bit/48k and I'm using MOTU ASIO drivers as they are the only driver model that even seems to remotely work in Reaper (How the hell do you get all of your audio I/O with WDM in Reaper?) I have my ASIO buffers set to 64 samples, ReaInsert latency is around 220-240 samples (depending on which of the three different MOTU interfaces I'm using). Sorry for hijacking your thread.I'm just frustrated and feel that my issues are relevant.ĭstructs thread is over a year old and not once did a dev even comment on it.įor the record, I think I might've minimized my issues by turning down my soundcard latency. I might be a more intensive user of ReaInsert than most, I have 6 ReaInserts just for drums with three different latencies. My other issue with ReaInsert is that Reaper will occasionally get stuck in a state when starting playback, either by jumping position or simply starting playback. The first two passes will be in-sync, the third pass will lose sync and stay un-synch'd until I stop playback or otherwise mute/unmute the parallel compressor track (which only "fixes" sync for a loop or two if it even fixes it at all.) Track 2 is like my drum buss and has a couple of plugs.
![tracking with uad plugins inside daw tracking with uad plugins inside daw](https://d29rinwu2hi5i3.cloudfront.net/article_media/2f573f30-a5ec-4fc5-af65-efac90b8feec/friedman_ds_40.jpg)
In my case, track 3 is a kick track with a gate plug and a hardware comp/eq chain via Reainsert. Track 3 is a "child" track under the folder with a ReaInsert on it. Track 2 is a "folder" track with a send to track 1. Track 1 is a "parallel" compressor with ReaInsert It might just be my setup with multiple interfaces (read: latencies) but then again, you hard-code the latency in ReaInsert. My most recent is that Reaper seems to lose track of PDC when looping with ReaInsert. I've got multiple issues with ReaInsert (which is the MAIN reason I even BOUGHT Reaper) which have gotten absolutely NO attention.