|
|
Post by Johnkenn on Oct 11, 2013 11:28:01 GMT -6
This shit is reeallly pissing me off. Recording out of time.
|
|
|
|
Post by popmann on Oct 11, 2013 12:08:54 GMT -6
In? ProTools? Have Logic? Flip over to it. Cubase doesn't use CoreAudio, so I don't know how well it plays with the Symphony as interface...wait...you're a UAD guy--are you using the Symphony as converters but the Apollo as interface?
I don't really know the details of how you're set up...but, can you use hardware inserts on the system? If you print one of those, do you see the same issue? Use a drum--soemthing with a nice clean transient.
|
|
|
|
Post by Johnkenn on Oct 11, 2013 14:13:37 GMT -6
PT Native using USB mode with I/O...It happened with a session that I was just opening to do vocals on...I had done some preliminary mixing, but nothing big, thank goodness. So - reopened the original tracks and boom...worked without the sample delay. Seems to be some corruption with that particular PTX file?? I used to be able to just switch buffer size and it would fix the issue, but it's not working for this particular session. It's TOTALLY unpredictable. I've had it happen on two different macs and two different I/O's...
|
|
|
|
Post by popmann on Oct 11, 2013 17:23:57 GMT -6
I've had it happen on PT10 on Windows. And yes--"jiggling the wires" ie restarting the app....or reopening....or pulling some insert and putting it back...I could always fix it. But, it's the reason I didn't choose PT. I wasn't going to pop for an HDX system and obviously their third party IO support (in the software version) isn't actually as rock solid as I'm used to working with. It's my biggest peeve. IMO-primary job of an DAW application is to keep everything time aligned.
It's the same way Cubendo was say a decade ago. They (at the time) blamed driver writers...and plug in coders...but, by at least v4, it was ROCK solid, knock on wood....with the same all of the above. I think they implemented some real time self checks--and just started ignoring what drivers and plug ins reported for latency. It's the only way to be solid with sol many hands in the code jar, IMO.
Did you strip all plug ins not made by Avid? At least deactivate them....but, I'd do a "save as" and rip them all out all together. You know-maybe next time it gets weird. It may be a latent plug on something that's causing it to shift and confusing it...
|
|
