Pro Tools placing sound EARLY??

[Hotcrazyfruit]

Originally Posted by Zarabozo

I read the answer about 003 not being affected. So, yesterday I went out and got a 003 Plus Rack.

Sadly, the results are exactly the same as with my Digi 002 Rack: 5020 samples earlier.

So no, the 003 is not safe at all.

I think some people here are not doing the test right. If you bus the output of the click track to an audio track, there's no problem at all. It happens only when recording from an actual input in the interface.

Thats exactly what i did, and i got a 1200 sample .... un... delay

someone try the input only monitoring. see if it changes anything.

Nick

[TOM@METRO]

The number of seasoned professionals and serious beta testers that missed this is astounding to me. It really does help make the point for the need of ADC in these systems. I wonder how many sessions have gone to mixdown and beyond with unheard timing variations that can have subtle negative effects on a project. This shows that we are all capable of allowing latency (or in this case the reverse of it) to at times go undedicated. This is a serious issue. We need ADC. And we need this sissue fixed.

[Zarabozo]

Originally Posted by Hotcrazyfruit

Thats exactly what i did, and i got a 1200 sample .... un... delay

someone try the input only monitoring. see if it changes anything.

Nick

No, that didn't make a difference to me. Neither enabling/disabling Low Latency Monitoring.

[Zarabozo]

Originally Posted by Hotcrazyfruit

Thats exactly what i did, and i got a 1200 sample .... un... delay

someone try the input only monitoring. see if it changes anything.

Nick

What about "earliency" as opposed to "latency"? (as in early/late)

[MikeLip]

Originally Posted by TOM@METRO

The number of seasoned professionals and serious beta testers that missed this is astounding to me. (...) I wonder how many sessions have gone to mixdown and beyond with unheard timing variations that can have subtle negative effects on a project. (...) We need ADC.

Yeah the band were on my back.... "where's the new song!". 7 weeks of stress for me. I kept telling them "I'm not happy with it" - but i didnt know why. At least I told them this week it was Pro Tools' fault and not mine. Well, sort of (unpaid) compensation.

Edit: They were very understanding and knew something was wrong. They understand pro tools enough to know whats going on at wave form level when i showed them. So all good.

Mike.

[rqstudio]

Originally Posted by TOM@METRO

The number of seasoned professionals and serious beta testers that missed this is astounding to me. It really does help make the point for the need of ADC in these systems. I wonder how many sessions have gone to mixdown and beyond with unheard timing variations that can have subtle negative effects on a project. This shows that we are all capable of allowing latency (or in this case the reverse of it) to at times go undedicated. This is a serious issue. We need ADC.

I agree, for the "Standard of the Industry" to allow this is embarrassing! Everyone else has it, buck-up!

[mykhal c]

Originally Posted by TOM@METRO

The number of seasoned professionals and serious beta testers that missed this is astounding to me. It really does help make the point for the need of ADC in these systems. I wonder how many sessions have gone to mixdown and beyond with unheard timing variations that can have subtle negative effects on a project. This shows that we are all capable of allowing latency (or in this case the reverse of it) to at times go undedicated. This is a serious issue. We need ADC.

which is why i did what i did in the post below...

Originally Posted by mykhal c

ain't that the truth i mean i spent ALL day yesterday chasin' workarounds for this bug. i pulled out my bass to test the input placement (sorta like the click/mic/headphone test) too. what was weird is i could play and nail the note/transient right on the beat as i played longer into the test. when i played at the beginnin' of the test my notes landed early tho. so maybe my brain kicked in some ADC or somethin' without me realizin' it it needs to be fixed...YESTERDAY!!!!

DTS can we get a status on a cs timetable? i know...i know...i can probably answer that one myself

now granted this is just me playin' 1/4 note at a time to see where the input of my bass lands on the track. and as i posted the longer i recorded the more in-sync i was with the click and bein' close to sample accurate of nailin' the beat accordin' to PTLE edit window. and i did not watch the screen either while playin' 'cause i did not want that to influence me. so my point...just because it doesn't look right on the screen doesn't mean it didn't feel right. so to your point Tom, i agree we ALL are capable of allowin' latency. for me, i hope my 'ears' tell me what MikeLip's told him...that it didn't feel right!!! but let's be real, there are 'probably' hundreds of samples of latency between players when layin' down a track and it still can 'feel right'. none of my notes in my test felt outta time to 'me'. but not all were placed exactly on the beat. anyway...enough of my post...this DOES need to be fixed ASAP!!! DIGIAVID we'd like our CS now pls!!

[Benoni]

Originally Posted by spkguitar

Or at all. Benoni hadn't actually done the test at all when he claimed that it wasn't happening (so I think you can thank him for your waste of time/money ). After he did the test... he found that in fact it WAS happening.

Well to be fair, you are referring to a different thread, and the way I have been using the 003R and Eleven Rack, there was/is no problem. After you asked me to look over this thread and do a specific test, then I saw the problem with the 003R BUT NOT THE ELEVEN RACK.

[Benoni]

Originally Posted by rqstudio

I agree, for the "Standard of the Industry" to allow this is embarrassing! Everyone else has it, buck-up!

if this was HD it would of been fixed in a matter of hours insted of weeks

[mykhal c]

Originally Posted by Benoni

if this was HD it would of been fixed in a matter of hours insted of weeks

and the fact that it is NOT an OSX prob doesn't help our cause either

to add...there is 10-20 times the latency is W7 that there is in XP. and i wonder if this comin' into play also? there is a setting on GIGA mobos that if it is turned off will bring the latency back down to XP numbers..<10us. if anyone can remember the settin' and has a GIGA mobo to test this 'might' help shed some light also. i remember lookin' for it on my ASUS P5K and the settin' was not listed in my bios. man...i wish i could remember the name. damn, were's my gingko??

EDIT: i found it. it is HPET "High Precision Event Timer" in the BIOS. if someone with a GIGA mobo (Shawn i'm not lookin' at ya bro) could disable this to see if this has any bearin' with the timing issues it'd be great...probably doesn't but what the hell

EDIT: remembered that there is a software setting in system devices that allows one to disable HPET. i'll try it later to see if it matters.