News for hackers. Stuff that matters.
Re:First-Person Hyper-lapse Videos by skizm on Sunday August 10, 2014 @06:10PM (#8160928)
You think a week of post end processing? I didn't read the paper or anything so I could be way off base, but I would assume the algo simply has to choose which frames to keep and which to toss. I doubt this would take an enormous amount of time even with HD videos. The algo is most likely just really clever in how it chooses a good frame vs a bad one.

On the other hand, if it is actually generating a lot of "best guess" images to put between gaps that are too large to bridge (too many bad frames in a row) with the current frames I could see that taking a bit longer, but not a week.

Re:First-Person Hyper-lapse Videos by Game_Ender on Sunday August 10, 2014 @06:13PM (#8160936)
It does 3D scene and camera path reconstructions then re-renders the scene from different perspectives. It's not just "picking the best frames". The technical explanation video goes into the details: https://www.youtube.com/watch?v=sA4Za3Hv6ng
Re:First-Person Hyper-lapse Videos by sjtrny on Sunday August 10, 2014 @06:27PM (#8160969)
Maybe you should watch the technical video or read the paper before commenting.
Re:First-Person Hyper-lapse Videos by ascorbic on Monday August 11, 2014 @02:53AM (#8162250)
The paper says it took 23,700 minutes to do just the frame selection for the 13 minute bike input video. That's over two weeks.
Re:First-Person Hyper-lapse Videos by phorese on Monday August 11, 2014 @10:15AM (#8163310)
Actually it says that it took 13 minutes to process 23,700 frames! :)
Re:First-Person Hyper-lapse Videos by ascorbic on Thursday August 14, 2014 @06:06AM (#8176751)
No, see table 1: "input duration (minutes and seconds), input frame count". It says the source file is 13 minutes 11 seconds and that it has 27,000 frames. In table 2 it says that source selection took 1 minute per frame. That's where I got 27,000 minutes from.
Re:First-Person Hyper-lapse Videos by phorese on Thursday August 14, 2014 @08:43AM (#8177141)
Ah, good call, thanks!

I now think we both got it wrong (but me more so than you): Table 2 specifies "1 min/frame", but the source frame selection happens for output frames, not input frames. Table 1 lists a total of 2189 output frames for the 23700 input frames of the "BIKE 3" sequence, so I guess we're looking at 2189 minutes?

Correct me if I misread anything. Again.