# This is the Video that never ends....

• So, exactly what does it mean when a video on CBS reports its length as NaN:NaN? And why are floats even being used there?

I have a .png to prove I saw it...

•  I have a .png to prove the earth is flat too.

• @medialint said:

medialint wrote the following post at Wed, Jun 4 2008 12:48 AM:

I have a .png to prove the earth is flat too.

Wouldn't it be great if there were some sort of, I don't know, *forum* where you could post stuff like that?

• @spamcourt said:

So, exactly what does it mean when a video on CBS reports its length as NaN:NaN?

The video was recorded in another universe where the set of branes doesn't have one for time?

I was about to say "imaginary time?", but then I remembered imaginary numbers are still numbers.

• @spamcourt said:

And why are floats even being used there?

Because it's easier to store a float in databases, and calculate lengths of video files in total seconds and then do the presentation stuff later, like convert it to minutes:seconds. So whatever they used to get the video length barfed somehow, and their float->output routine took the error value as a NaN. The real WTF would be not handling this more gracefully.

• [quote user="Renan "C#" Sousa"]

The video was recorded in another universe where the set of branes doesn't have one for time?

I was about to say "imaginary time?", but then I remembered imaginary numbers are still numbers.

[/quote]

Most libraries will return a NaN when asked to square root -1, so yeah it could be imaginary time (and if you plug imaginary time into the equations for relativity, it has all the properties of space ).

• @MarcB said:

@spamcourt said:

And why are floats even being used there?

Because it's easier to store a float in databases, and calculate lengths of video files in total seconds and then do the presentation stuff later, like convert it to minutes:seconds. So whatever they used to get the video length barfed somehow, and their float->output routine took the error value as a NaN. The real WTF would be not handling this more gracefully.

Huh, what's wrong with an INT field for that? You don't need floats for that, unless you want to record broken seconds, but then it would make more sense to store it as milliseconds plus that that kind of acquiricy is usually unrequired and unwanted in video players.

• @MarcB said:

Because it's easier to store a float in databases, and calculate lengths of video files in total seconds and then do the presentation stuff later, like convert it to minutes:seconds. So whatever they used to get the video length barfed somehow, and their float->output routine took the error value as a NaN. The real WTF would be not handling this more gracefully.
WRONG!  Dogbert got it right with the other dimension idea.  Try to keep up.

• @mentaldingo said:

[quote user="Renan "C#" Sousa"]

The video was recorded in another universe where the set of branes doesn't have one for time?

I was about to say "imaginary time?", but then I remembered imaginary numbers are still numbers.

Most libraries will return a NaN when asked to square root -1, so yeah it could be imaginary time (and if you plug imaginary time into the equations for relativity, it has all the properties of space ).

[/quote]

I remember reading that the Einsteinian distance metric is something like  d = (dx^2 + dy^2 + dz^2 - c.dt^2)^1/2, but shouldn't that imply that if you plug imaginary time into the equations of relativity, it has all the properties of negative space?

• @dtech said:

Huh, what's wrong with an INT field for that? You don't need floats for that, unless you want to record broken seconds,
'

They're could be storing the length as minutes, which would require floats, or fixed-point decimal at least, for storing seconds. Or maybe they're storing total frames and the FPS. Who knows. Just throwing out theories.

• Don't forget there are different video formats out there, some with a speed of 23.97 FPS. Now, if you want to display something, are you going to tell the number of frames and the framerate, or are you going to compute that number and display it neatly in minutes and seconds?

Sheez, some programmers think everything is an int!

• @TGV said:

Don't forget there are different video formats out there, some with a speed of 23.97 FPS. Now, if you want to display something, are you going to tell the number of frames and the framerate, or are you going to compute that number and display it neatly in minutes and seconds?
If it only was just 23,97. Unfortunately, it's 24/1,001, so the actual framerate is 23,976023.

• @TGV said:

Don't forget there are different video formats out there, some with a speed of 23.97 FPS. Now, if you want to display something, are you going to tell the number of frames and the framerate, or are you going to compute that number and display it neatly in minutes and seconds?

Sheez, some programmers think everything is an int!

2136721376890812038712376874

• @dtech said:

I agree, there's no reason to store anything other than seconds for video or audio metadata.

• @morbiuswilters said:

@dtech said:

I agree, there's no reason to store anything other than seconds for video or audio metadata.

But what if you need to show someone the alien artifacts at 21:23.6?

• @morbiuswilters said:

@dtech said:

I agree, there's no reason to store anything other than seconds for video or audio metadata.

Just store them in Control.txt, add a noodle and jam it!

• @bstorer said:

@morbiuswilters said:

@dtech said:

I agree, there's no reason to store anything other than seconds for video or audio metadata.

But what if you need to show someone the alien artifacts at 21:23.6?

Then your system has given SpecteSwamp further proof that the government tries to hide them.

@morbiuswilters said:

@dtech said:

I agree, there's no reason to store anything other than seconds for video or audio metadata.

Don't know if you're joking or not, further meta-data like aspect-ratio, resolution, FPS etc. are quite usefull, but in case that was a sneer at me: this is about a specific situation. In this situation (a video-player on a website) it's enough if the user knows how many minutes:seconds there are left and that he can start playing from a specific point with second accuracy. The player can get the information needed for reading (resolution, speed) from the container (.flv probably in this case) or video-data itself.

• @dtech said:

Don't know if you're joking or not, further meta-data like aspect-ratio, resolution, FPS etc. are quite usefull, but in case that was a sneer at me: this is about a specific situation. In this situation (a video-player on a website) it's enough if the user knows how many minutes:seconds there are left and that he can start playing from a specific point with second accuracy. The player can get the information needed for reading (resolution, speed) from the container (.flv probably in this case) or video-data itself.

I was serious -- nobody needs to know anything more than how many seconds in length the clip is and the actual number of frames is stored with the video.  You Dutch sure are a defensive lot!  Well, unless you see a couple of German guys on bikes riding towards your border, that is...

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.