Question / Help How to fix "as behind target timestamp by xx"?

Z

ZeroWalker

Member
Have this on my Mic, and get it all the time no matter what settings i try.

Here is from a 5 hour recording:

Code: 
12:48:18:   New Scene
12:48:18: Using Monitor Capture
12:58:03: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 65
13:07:46: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 67
13:17:35: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 70
13:27:30: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 74
13:37:34: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 69
13:47:45: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 75
13:58:06: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 72
14:08:34: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 70
14:19:09: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 79
14:29:53: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 79
14:40:45: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 80
14:51:41: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 82
15:02:46: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 75
15:13:58: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 79
15:25:17: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 84
15:36:46: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 80
15:48:26: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 87
16:00:14: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 85
16:12:09: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 84
16:24:12: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 84
16:36:24: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 85
16:48:44: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 87
17:01:13: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 90
17:13:50: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 94
17:25:37: Total frames encoded: 499184, total frames duplicated: 76 (0.02%)
17:25:37: Number of frames skipped due to encoder lag: 29 (0.01%)
17:25:37: Total frames rendered: 499153, number of late frames: 3 (0.00%) (it's okay for some frames to be late)


I am currently using "Use Mic QPC Timestamps" as i think it improves it, or perhaps it didn't do anything, can't really remember. Never the less, no setting solved it, it's Always there.

I have no idea if it goes up and up all the time, as i think i never seen it above 100, but i am not to sure about that.

Also, i think the Mic is off sync by about 100ms, so i make a +100 delay to solve that.
However asfter a while (as you can see), it goes the other way around, making it in sync normally, and making my setting off sync instead. (At least that's what i make out of it, Positive and Negative Delay).

Meaning, normally it's 100 Positive, but after awhile it will go to 100 negative, making it 0, and perhaps continuing.

Well in other words, it simple messes thing up no matter what;P

So, is there anything that can be done?

As it at least detects that something is off, that's a sign that it knows what's going on, and therefore a solution should be possible.
 
R

R1CH

Forum Admin
Developer
It gives more time for the audio to be caught and mixed with the appropriate video.
 
Z

ZeroWalker

Member
Tried at 1000, same results:

Code: 
15:32:59:   New Scene
15:32:59: Using Monitor Capture
15:42:47: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 64
15:52:40: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 66
16:02:37: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 69
16:12:44: Audio timestamp for device 'Microphone (Samson C03U              )' was behind target timestamp by 73
16:20:37: Total frames encoded: 85784, total frames duplicated: 12 (0.01%)
16:20:37: Total frames rendered: 85785, number of late frames: 0 (0.00%) (it's okay for some frames to be late)

EDIT:

Also tried at 2000, same thing, as well as 0 (which seem to have been defaulted to 60 which is the lowest).

So Scene Buffering seem to do nothing at all sadly enough.
 
Last edited:
L

Lain

Forum Admin
Lain
Forum Moderator
Developer
That overclock may be partly to blame. However, before you go reverting the overclock, I want you to try something:

1.) Open a command prompt as administrator, then execute this command: bcdedit /set useplatformclock true
2.) Restart your computer, go in to bios and check for an "HPET" or "High Precision Event Timer" option, and enable it. If it's not there, that's fine.
3.) Try OBS again.

If this doesn't help, then you may have to look at your overclock, because I'm almost totally positive that it's affecting the system timing, and thus OBS' internal timing.
 
Z

ZeroWalker

Member
Ah, have done stuff like that before to try to think desyncing problems.
Sadly none of it has ever helped.

But will try it out just in case, better safe than sorry!

(HPET is always enabled for me as far as i know)
 
Z

ZeroWalker

Member
Tried with useplatformclock, and also checked that it was truly on with the QueryPerformanceFrequency (14.xx).
Same Results.

Will now try without overclock.

Update:

Same results with stock:(

Older file = bcedit setting
Newer file = non-overclock
 

Attachments

  • 2014-06-18-0810-02.log
    9.3 KB · Views: 13
  • 2014-06-18-0612-58.log
    10.3 KB · Views: 13
Last edited:
Z

ZeroWalker

Member
Is it really just me who has this problem?
I mean, the Mic is quite famous, i can't see how other's don't have it, at least some should.
I would like to know if it perhaps is the Mic itself that's failing to cooperate with the system, or if it's the other way around.
 
Z

ZeroWalker

Member
Okay i did test without QPC which i have done before, but there is actually a difference.

Normally, it would be 60ms behind after 10min, then increase about 1-5ms per 10min.

Without QPC this is the result.

Code: 
08:18:13: ------------------------------------------
08:26:54: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 70
08:37:34: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 90
08:48:12: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 100
09:00:58: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 110
09:23:18: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 120
09:37:14: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 130
09:53:03: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 140
10:17:28: Audio timestamp for device 'Microphone (Samson C03U )' was behind target timestamp by 150
10:32:07: Total frames encoded: 241011, total frames duplicated: 6 (0.00%)
10:32:07: Total frames rendered: 241025, number of late frames: 1 (0.00%) (it's okay for some frames to be late)

As you can see, the difference is extremely different, it goes way higher in a much faster rate.

so QPC does indeed improve it, but it does decrease the "Latency?" on the input by 100ms, so i have to increase it, which i don't need normally (This however is actually good for me, as it syncs with the Webcam Delay, making all sound in sync realtime).


But the issue still exist that it does increase over time.



Here is an other post i accidentally posted on the wrong topic.


Is there a way to skew timing?
For example, if they are always increasing/decreasing at a constant rate, it it possible to tune it to stay in sync manually?

I usually have to do this with recordings afterwards if the Recording Software doesn't do it for me, and i use this application to make a formula for it: http://forum.exkode.com/index.php?topic=324.0

This is not bound to Dxtory, it's just a way to see the timings and how they are synced to the "PC Timing", by that you can make a calculation on how faster/slower the length of the audio should be to stay in sync with the PC (in this case, Video).

Thanks
 
You must log in or register to reply here.
Top