What is the most precised DateTime I can use in NET 3.5?
What is actally precision of NET 3.5 DateTime variable ? It is 16 miliseconds? Do I have a option to replace it with some other type? Maybe with DateTimeOffset – is it has better precision?
My situation is that I have a WinForm C# 2008 Net 3.5 project which work with Start Date and then add between 100 and 500 time durations in miliseconds /video files duration/ . I understand that best is to keep the start date in DateTime varibale and to get current date with code
dtCurr = dtStart.AddMilliseconds(lI
This almost will solve the problem, as I’ll get inaccuracy with only 1 calculcation, not with all 100-500 calculations. Is that correct? Anyway, I’m interesting of the most precise DateTime I can use in NET 3.5
My situation is that I have a WinForm C# 2008 Net 3.5 project which work with Start Date and then add between 100 and 500 time durations in miliseconds /video files duration/ . I understand that best is to keep the start date in DateTime varibale and to get current date with code
dtCurr = dtStart.AddMilliseconds(lI
This almost will solve the problem, as I’ll get inaccuracy with only 1 calculcation, not with all 100-500 calculations. Is that correct? Anyway, I’m interesting of the most precise DateTime I can use in NET 3.5
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
David Johnson, CD
With video files why are you not counting the frames and dividing by the fps? You can't get any more precise with a video than an individual frame
ASKER
TO Dhaest
Well, I find this articles before you send me. Anyway, DateTimeOffset is more precise than DateTime , or it is the same?
To ve3ofa
Well, for my project - workign with a playlist with 24 hours duration few seconds in a day are acceptable solution. Anyway, more accurance is not possible for ordinary PC - most PC timer move between 1 and 5 seconds for a day .
And I already have other system which works with miliseconds, not with frame count.
Well, I find this articles before you send me. Anyway, DateTimeOffset is more precise than DateTime , or it is the same?
To ve3ofa
Well, for my project - workign with a playlist with 24 hours duration few seconds in a day are acceptable solution. Anyway, more accurance is not possible for ordinary PC - most PC timer move between 1 and 5 seconds for a day .
And I already have other system which works with miliseconds, not with frame count.
Video measurement is still more precise.. if the file is 2300 frames @ 23.97 fps the play length is 95.954 seconds depending upon the # of video's, involved plus the queuing speed a 24 hour playlist may be +/- a few minutes.
100 and 500 time durations in miliseconds /video files duration (this is what confused me)
100 and 500 time durations in miliseconds /video files duration (this is what confused me)
ASKER
To ve3ofa
100 and 500 time durations in miliseconds - i mean that I loop via all file's duration and show the current time every file start .
100 and 500 time durations in miliseconds - i mean that I loop via all file's duration and show the current time every file start .
ASKER
10x