|
Post by ragan on Jan 27, 2019 14:30:00 GMT -6
Anyone here good at trouble shooting this?
I did a round trip latency test, did the the little calculation from samples to ms and entered the delay amount in the I/O menu for hardware inserts.
Was working beautifully (had my parallel drum aux going with hardware and was grinning from ear to ear) and then...it wasn't. Same delay figure, same hardware loop, but now it's phasey and muffled.
Any ideas anyone?
|
|
|
Post by kcatthedog on Jan 27, 2019 14:39:20 GMT -6
Happened in the same session or after reopening ?
|
|
|
Post by lcr on Jan 27, 2019 14:44:19 GMT -6
Im a quitter. The hardware insert plugin for Studio One 4 pings, sets the delay, allows you to ad or subtract any amount you want (not sure why?) input / output trim, you can send and return from any channels you want, you can insert a pic of the hardware and has a notes section. Do I need all these badass features that always work? No, but I couldnt get PT to consistently work, I would have mutes for no reason, it was a mess. But all the additional features in S1 are nice. Also, much more CPU efficient than PT, and cheaper to use. I didnt answer your question did I? Maybe someone can help you.
|
|
|
Post by ragan on Jan 27, 2019 15:11:56 GMT -6
Happened in the same session or after reopening ? It's happening in the 48k session I originally set up the delay comp in (which was working great) but not in another session which is at 88.2k (I adjust the comp for the different sample rate of course). It was working at both rates, in both sessions (with the appropriate delay figure entered) and now it's not working right in the 48k session. Muffled, phase thing going on.
|
|
|
Post by Steamy Williams on Jan 27, 2019 15:27:10 GMT -6
What type of audio interface are you using? Some USB and FireWire interfaces change their latency by a few samples from day-to-day.
|
|
|
Post by ragan on Jan 27, 2019 15:41:36 GMT -6
What type of audio interface are you using? Some USB and FireWire interfaces change their latency by a few samples from day-to-day. Symphony MKII Thunderbolt.
|
|
|
Post by indiehouse on Jan 27, 2019 15:46:28 GMT -6
Anyone here good at trouble shooting this? I did a round trip latency test, did the the little calculation from samples to ms and entered the delay amount in the I/O menu for hardware inserts. Was working beautifully (had my parallel drum aux going with hardware and was grinning from ear to ear) and then...it wasn't. Same delay figure, same hardware loop, but now it's phasey and muffled. Any ideas anyone? Happens to me all the time, randomly, for no reason. One day it works, the next it doesn’t. Maddening.
|
|
|
Post by ragan on Jan 27, 2019 15:56:52 GMT -6
Booooooooo
|
|
|
Post by ragan on Jan 27, 2019 16:08:46 GMT -6
I mean, this cannot be the product Avid intends to have out in the wild, right?
There's got to be a specific reason this is occurring.
|
|
|
Post by Blackdawg on Jan 27, 2019 16:22:34 GMT -6
Avid won't care because your using a third party interface. They will blame them. And suggest you use an avid one.
I haven't used normal pt in a while..so can't help much here.
That said.
What version of PT are you running and what OS version?
|
|
|
Post by kcatthedog on Jan 27, 2019 16:22:38 GMT -6
I didn’t have your specific problem but I never believed Avid got all the bugs out of pt. I had pt settings that would reset themselves when using my dbox, never made any sense: drove me bonkers so I bailed on PT.
|
|
|
Post by wiz on Jan 27, 2019 17:26:54 GMT -6
drbillhe does this flawlessly cheers Wiz
|
|
|
Post by lcr on Jan 27, 2019 17:43:55 GMT -6
Is the Dr. using vanilla or HD? The fact that the “whats new” at NAMM was very little to nothing except “even HD guys can pay us to increase track counts” is mind blowing to me. It really will become something we all laugh about someday (PT). “Remember when PT was the standard and the shanangins they would get away with?”
|
|
|
Post by lcr on Jan 27, 2019 17:47:02 GMT -6
I think PT was justified / ruled / made sense around the PT 5.5-6.5 days.. a mix plus back then made sense. Then it... well...
|
|
|
Post by ragan on Jan 27, 2019 17:51:02 GMT -6
drbill he does this flawlessly cheers Wiz I think he's also using Avid I/O. Which I get should be the most integrated, easy way to do it. But it's nonsensical that with some other interface, once you measure the round-trip latency and enter the correct figure, you'd still have randomness as to whether PT delay comp'd correctly. Working one day, not the next with the same settings? That can't be an acceptable thing for Avid, can it? Granted, I don't know what's causing it. Maybe it's not PT.
|
|
|
Post by popmann on Jan 27, 2019 18:23:25 GMT -6
Dr Bill uses an Avid ProTools hardware system. I've never had one of those fail to do much of anything I asked it to...and never had the "formerly nknown as LE" native version DO what I need it to with any consistency. When I see someone who buys protools software, you might as well tattoo "be nice to me, I don't know what I'm doing" on your forehead. And that's NOT a dig on Avid....who I'm going to point out AGAIN-I've never had a bad experience with any of their hardware systems. It's not contradictory to say that Yamaha (Steinberg) has the best NATIVE mixing systems...and Avid has the best digital mixing systems. Both may be subjectively or situationally wrong, I suppose...but, it's not contradictory.
|
|
|
Post by lcr on Jan 27, 2019 18:58:12 GMT -6
So what poopmann is saying is no blame to Avid for selling snake oil BS to dumb people, and means no offense to Avid in that statement.
|
|
|
Post by joey808 on Jan 27, 2019 19:13:16 GMT -6
HDX automatically delay compensates on hw inserts, vanilla does not, got to enter offsets manually. 2019 and no ping feature in protools, amazing!
|
|
|
Post by drbill on Jan 27, 2019 19:30:46 GMT -6
Current system - Maxed out cheese grater Mac, PT HDX2, 96 channels of AVID HD 16X16 and 192 I/O (which was not supposed to work with HDX, but which works perfectly), tons of hardware. More than enough to fill 96 channels. (Thinking about 128, but I swore I wouldn't go there. heh heh) I use delay compensation daily on hardware inserts all OVER the place. Channels, Busses, Mix Buss. (More hardware than plugins.) When I'm ready to start inserting hardware, I turn on Delay Compensation and...... Done. No pinging or jumping thru hoops needed. One second and everything is in perfect sync. I can probably count the number of delay compensation issues I've had over the last 10 years on one hand. And a quick restart solved them. It's an expensive system with expensive solutions. That work. Flawlessly. If you need that, upgrading is not that expensive (IMO) unless you compare price to some of the ultra cheap options and get all gripey about it. The system is high end, and it performs high end. In my world, time is money - so it's worth it. For others, maybe not. I know it's fashionable to hate on PT, but if you buy in, and really learn the software, it's amazing how the "inadequacies" of the system fade away. I'm not making light of those having issues. I know the pain - been there done that. I'm just saying that the continual blind comments that "PT Sucks!!" that I see all over the inter webs is unwarranted IMO. If your system is not working, either switch or move up to the system that DOES work for your application. (Probably HDX) I wish I could help ragan with his issues, but I've been running hardware DSP based systems since PT2 / 442 days. Dinosaur PT here..... LOL BEST OF LUCK dialing it in!!!
|
|
|
Post by ragan on Jan 27, 2019 19:35:19 GMT -6
So what poopmann is saying is no blame to Avid for selling snake oil BS to dumb people, and means no offense to Avid in that statement. “Dumb people” being, in this case, me. Well, I’m not tattooing that on my forehead and I don’t need him to be nice to me. Popmann has a lot of strong opinions and sometimes, when you pick your way through the hubris, there’s some good insight there. I like the sound of the Symphony a lot better than the Avid boxes and I like PT better than any other DAW I’ve used. There have been no issues for years and years using non-Avid interfaces with PT Native. Yesterday I discovered my first (this one). And we don’t even know what’s causing it so it’s meaningless to say Avid is to blame or to say they’re blameless. But there is an issue and I’m trying to get to the bottom of it.
|
|
|
Post by joey808 on Jan 27, 2019 19:48:08 GMT -6
|
|
|
Post by stratboy on Jan 27, 2019 20:16:07 GMT -6
Useful information, but I think Ragan's problem is getting PT to maintain the same delay compensation value over time, not setting the right value. I use MOTU 16A and 8A, not Avid. I occasionally have the same problem and have to go back and reset. I'm thinking about switching to Logic. Do any of you Logic users out there have experience with how Logic handles delay compensation?
|
|
|
Post by ragan on Jan 27, 2019 20:49:01 GMT -6
Useful information, but I think Ragan's problem is getting PT to maintain the same delay compensation value over time, not setting the right value. Yes, exactly. And it’s not that it’s not maintaining the value; it’s keeping what I entered. It’s just that yesterday that same value created perfect phase coherency and today it’s a mess.
|
|
|
Post by bradd on Jan 27, 2019 20:53:30 GMT -6
Spence, I’m a Logic user, but I mix on a console, so I don’t know exactly how Logic handles this. If you are thinking of switching to Logic, the best thing you can do is watch MusicTechHelpGuy’s video tutorials on YouTube. They are excellent and I see that he has a video on exactly this topic.
|
|
|
Post by drbill on Jan 27, 2019 22:37:47 GMT -6
Useful information, but I think Ragan's problem is getting PT to maintain the same delay compensation value over time, not setting the right value. Yes, exactly. And it’s not that it’s not maintaining the value; it’s keeping what I entered. It’s just that yesterday that same value created perfect phase coherency and today it’s a mess. I know you probably don't want to hear this, but if it worked yesterday, and today the same amount of compensation is in PT, it's almost certainly in your interface. My (uniformed) $0.02. When this kind of **** happens, it sometimes takes a complete hardware / computer shutdown and restart. If you haven't tried that, give it a go.
|
|