|
Post by indiehouse on Nov 19, 2016 12:54:28 GMT -6
I use Reaper (user since 1.85) and the hardware insert engine is pretty much a thing of beauty for me on my system. I use an RME HDSP9652 with 24 channels. Hmm the only time I have an issue with delay compensation is when I have my Total Mix cue mixer set to send signal from a returning input back to the output I'm using for ReaInsert. So if you had some weird feedback loop going in your digital cue mix (pretty sure the Apollo has monitoring software) then you might want to check to see if your cue mix is interfering with your ability to ping properly. Did you have any tracking sessions recently? Punch a part over? Replace a syllable? Food for thought. Good luck. Thanks -L. Yeah, I checked that. Usually, that will double my signal and give me a weird slap back echo thing. This is straight up latency. I'm about to go fire up a session and check it out today. Got sucked into a college football game.
|
|
|
Post by ChaseUTB on Nov 19, 2016 13:41:58 GMT -6
|
|
|
Post by indiehouse on Nov 19, 2016 14:16:37 GMT -6
Thanks man. I've been running outboard off an Apollo for a few years now, so I've got a good grasp of the ins and outs of it, pun intended. I did restart PT and my computer, but I didn't power cycle the Apollo.
|
|
|
Post by drbill on Nov 19, 2016 14:24:25 GMT -6
I don't know if this is a : General PT hate thread, a Cubase/Reaper/fill in the blank is "better" thread, an Avid Sucks thread, or an I need help thread. But just in case it's an "I need help thread"..... www.petegates.com/pg-pt-prefs.htmlRun the free app, reboot, let PT rebuild it's pref's. Done. Been running hybrid systems on PT Mix, HD and HDX for way over a decade and have never had a hardware insert latency problem ever. Ever. It's not PT, it's in your system, non authorized hardware interface that's not talking with PT correctly or a corrupted preference. Good luck.
|
|
|
Post by ragan on Nov 19, 2016 14:27:18 GMT -6
I don't know if this is a : General PT hate thread, a Cubase/Reaper/fill in the blank is "better" thread, an Avid Sucks thread, or an I need help thread. But just in case it's an "I need help thread"..... www.petegates.com/pg-pt-prefs.htmlRun the free app, reboot, let PT rebuild it's pref's. Done. Been running hybrid systems on PT Mix, HD and HDX for way over a decade and have never had a hardware insert latency problem ever. Ever. It's not PT, it's in your system, non authorized hardware interface that's not talking with PT correctly or a corrupted preference. Good luck. Have you ever run a hybrid rig on PT native though? Not saying you're not correct, but many think PT Native's I/O is more problematic than HDX etc.
|
|
|
Post by indiehouse on Nov 19, 2016 14:48:55 GMT -6
I don't know if this is a : General PT hate thread, a Cubase/Reaper/fill in the blank is "better" thread, an Avid Sucks thread, or an I need help thread. But just in case it's an "I need help thread"..... www.petegates.com/pg-pt-prefs.htmlRun the free app, reboot, let PT rebuild it's pref's. Done. Been running hybrid systems on PT Mix, HD and HDX for way over a decade and have never had a hardware insert latency problem ever. Ever. It's not PT, it's in your system, non authorized hardware interface that's not talking with PT correctly or a corrupted preference. Good luck. It's definitely an "I need help thread". I'm not running PT HD software, nor have any intention to. I've got an BF Apollo 16, which I assume to be an authorized PT interface, even though it is third party. I don't have these issues often, but it's definitely a real thing. Thanks for the tip, Bill! I'll try it out. I have heard of pref's getting corrupted.
|
|
|
Post by tasteliketape on Nov 19, 2016 14:49:05 GMT -6
Shot in the dark but trash Pro Tools preferences
|
|
|
Post by indiehouse on Nov 19, 2016 14:49:44 GMT -6
Now, wouldn't you know it? Booted up my session and PT is working like a champ. How the hell am I supposed to troubleshoot an intermittent issue like this? It's maddening, I tell you.
|
|
|
Post by mulmany on Nov 19, 2016 15:07:38 GMT -6
Now, wouldn't you know it? Booted up my session and PT is working like a champ. How the hell am I supposed to troubleshoot an intermittent issue like this? It's maddening, I tell you. I upgraded to the newest pt12, and it fixed my odd issues I was having. The biggest one being the sudden pt cpu spikes that would crash pt while tracking. Vanilla here with a Motu 16a.
|
|
|
Post by wiz on Nov 19, 2016 15:47:11 GMT -6
Now, wouldn't you know it? Booted up my session and PT is working like a champ. How the hell am I supposed to troubleshoot an intermittent issue like this? It's maddening, I tell you. I don't have too many problems in Logic.. But , creation of a new session is not a bad way to go when something weird pops up. I logic, I save the project to a new location, which copies all the relevant files across to the new folder i create. Can you easily do a similar thing in Pro Tools? might help cheers Wiz
|
|
|
Post by indiehouse on Nov 19, 2016 16:15:46 GMT -6
Now, wouldn't you know it? Booted up my session and PT is working like a champ. How the hell am I supposed to troubleshoot an intermittent issue like this? It's maddening, I tell you. I don't have too many problems in Logic.. But , creation of a new session is not a bad way to go when something weird pops up. I logic, I save the project to a new location, which copies all the relevant files across to the new folder i create. Can you easily do a similar thing in Pro Tools? might help cheers Wiz Yeah, I can do that. Next time I have this issue, I'll try trashing the pref file then scrapping the session...then scrapping PT.
|
|
|
Post by Randge on Nov 19, 2016 19:01:54 GMT -6
Cough cough..Cubase...cough cough... Do you know if they sorted out the negative/0 latency bug for delay compensation in Cubase with RME interfaces? I have two RME 9632 cards here and have never encountered any problems. I don't know anything about the interfaces not working either. First Id heard of it.
|
|
|
Post by Bender on Nov 20, 2016 13:58:25 GMT -6
I have two RME 9632 cards here and have never encountered any problems. I don't know anything about the interfaces not working either. First Id heard of it. I don't think this was ever an issue with pci/pcie rme cards but more specifically a cubase -> RME interface problem a la ufx,& FF, series etc. From the cubase forums.. www.steinberg.net/forums/viewtopic.php?f=226&t=71278&sid=d3ce82fb47571dde693a8c6f19fe4bdb&start=25Anyway, I made the plunge a few months ago and upgraded to 8.5 artist but haven't pulled the trigger on pro yet as one huge feature I will be using is the FX insert routing for external hardware fx...but if it isn't fixed then I missed their summer sale otherwise I would've made it happen....oh well fingers crossed for another holiday sale
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 20, 2016 15:02:20 GMT -6
I don't know if this is a : General PT hate thread, a Cubase/Reaper/fill in the blank is "better" thread, an Avid Sucks thread, or an I need help thread. But just in case it's an "I need help thread"..... www.petegates.com/pg-pt-prefs.htmlRun the free app, reboot, let PT rebuild it's pref's. Done. Been running hybrid systems on PT Mix, HD and HDX for way over a decade and have never had a hardware insert latency problem ever. Ever. It's not PT, it's in your system, non authorized hardware interface that's not talking with PT correctly or a corrupted preference. Good luck. yay drbill - yellow card in rugby is ten minutes - musta been a red
|
|
|
Post by guitfiddler on Nov 21, 2016 4:56:24 GMT -6
Cough cough..Cubase...cough cough... Lol
|
|
|
Post by kilroyrock on Nov 21, 2016 6:59:58 GMT -6
Seeing as hardware delay is mostly travel delay vs plugin delay being processing delay (typically), I doubt the latency is outside the boundaries of ADC. If it was working fine and stopped working, then some sort of system limitation is being hit. The ADC is working fine, but there's some over punishing latency happening that throws off the timer. What happens when you increase your buffer?
|
|
|
Post by Ward on Nov 21, 2016 7:39:11 GMT -6
Now, wouldn't you know it? Booted up my session and PT is working like a champ. How the hell am I supposed to troubleshoot an intermittent issue like this? It's maddening, I tell you. I upgraded to the newest pt12, and it fixed my odd issues I was having. The biggest one being the sudden pt cpu spikes that would crash pt while tracking. Vanilla here with a Motu 16a. I have stuck with PT10HD and am still not experiencing any of these problems. Is it more problematic with PT11 and the move to HDX and Native, away from HD... since it uses up more horsepower? Maybe it did, but was also more rock solid in the process? Just wondering.
|
|
|
Post by indiehouse on Nov 21, 2016 8:30:54 GMT -6
Seeing as hardware delay is mostly travel delay vs plugin delay being processing delay (typically), I doubt the latency is outside the boundaries of ADC. If it was working fine and stopped working, then some sort of system limitation is being hit. The ADC is working fine, but there's some over punishing latency happening that throws off the timer. What happens when you increase your buffer? My buffer is maxed.
|
|
|
Post by indiehouse on Nov 21, 2016 8:33:26 GMT -6
Now, wouldn't you know it? Booted up my session and PT is working like a champ. How the hell am I supposed to troubleshoot an intermittent issue like this? It's maddening, I tell you. I upgraded to the newest pt12, and it fixed my odd issues I was having. The biggest one being the sudden pt cpu spikes that would crash pt while tracking. Vanilla here with a Motu 16a. I logged into my Avid account and saw that I had a free upgrade to PT12, so I updated last night. Hopefully that at least clears up the CPU spikes, which I'm getting on the same session. Can't make it through the entire track without PT crapping out. I'm only around 40% of system usage, so I'm not maxing out my CPU or anything.
|
|
|
Post by guitfiddler on Nov 22, 2016 18:25:35 GMT -6
I updated my Native Protools so I could pay more to fix the issues that the update brought me! Lol. I don't hate Avid.
|
|
|
Post by indiehouse on Jan 8, 2017 14:57:24 GMT -6
It's back. Damnit. I'm so frustrated. Just up and out of the blue. I'm going to delete the pref file as suggested above as soon as my backups finish. Then, I'm going to drop kick Pro Tools in the nuts. Or the Apollo. And that's part of the problem. I don't know what to blame.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 8, 2017 15:14:40 GMT -6
It's back. Damnit. I'm so frustrated. Just up and out of the blue. I'm going to delete the pref file as suggested above as soon as my backups finish. Then, I'm going to drop kick Pro Tools in the nuts. Or the Apollo. And that's part of the problem. I don't know what to blame. It'll be PT, I've constantly had issues with it since I can remember.. There's no automatic compensation for aux busses, the compensation delay with heavier plugins is mainly inaccurate and for it to work right I had to manually set it all up.. Moved to samplitude and not had one single issue. My workflow is to mix the track and then master it in the same session so I can tweak the mix if there's something I might have missed.. It's easier than bouncing it down and having to switch through sessions, the amount of latency difference when adding a master fader in PT kept wrecking the mix, so that workflow is a nooo goo.! You can get a free trial of Presonus One, Samplitude and probably Cubase. So just test it out, you've nothing to loose..
|
|
|
Post by indiehouse on Jan 8, 2017 15:16:15 GMT -6
Trashing pref did not help. I printed a kick that ran out through a Great River EQ-2NV into a Stam SA2A, and the track was way off from the original. Hardware delay compensation is NOT working for me. Grumble growl...
|
|
|
Post by indiehouse on Jan 8, 2017 15:18:37 GMT -6
I'm pretty much done with things that don't work for me, whether they are great or not. I no longer have the time I used to, and I've spent my afternoon troubleshooting instead of mixing. Same thing happened with my Motu 16a. Sounded great, but was a pain in the ass. I moved it. I'm gonna move on to Cubase after this project.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 8, 2017 15:21:01 GMT -6
wow, are you gonna be able to test cubase before committing - hate to think it was something else?
|
|