pancakes

MicrostockGroup Sponsors


Author Topic: Many timelapses rejected though everything looks ok...  (Read 1006 times)

0 Members and 1 Guest are viewing this topic.

« on: July 05, 2019, 06:29 »
0
Hello,

It's interesting how Shutterstock rejecting timelapses though everything looks ok.
Every other agency approved the same clips. Here is the example of timelapse - https://www.dreamstime.com/timelapse-video-oak-tree-cumulus-clouds-moving-across-sky-timelapse-video-oak-tree-cumulus-clouds-moving-video151929369 [nofollow]
The message which I get from ST is that there is frame rate/shutter speed issues. But I really know that I used correct frame rate. Clips are high quality, without pixelation or artifacts. So what could be the problem?

Lukas


« Reply #1 on: July 06, 2019, 10:57 »
+1
Honestly the one from Dreamstime link looks a bit choppy as if there werent enough frames. Try using frame blending if you didnt.

« Reply #2 on: July 06, 2019, 12:33 »
+1
The time lapse is very good, reviewers for video at SS are notoriously total lunatics.
Simply resubmit and it will be accepted.
In a timelapse you can have choppiness only if the SS is too fast compared to the frequency of shots, but it is not really the case here (only a tiny bit of choppiness)

« Reply #3 on: July 07, 2019, 05:49 »
0
Honestly the one from Dreamstime link looks a bit choppy as if there werent enough frames. Try using frame blending if you didnt.

Thank you! It really could be the problem... I tried to use frame blending, but video looks kinda dizzy. Optical flow looks much better, so I will try it.  :)

« Reply #4 on: July 07, 2019, 05:50 »
0
The time lapse is very good, reviewers for video at SS are notoriously total lunatics.
Simply resubmit and it will be accepted.
In a timelapse you can have choppiness only if the SS is too fast compared to the frequency of shots, but it is not really the case here (only a tiny bit of choppiness)
Thanks, I will try to fix that choppiness in the editing! ;)

« Reply #5 on: July 07, 2019, 19:54 »
0
The time lapse you linked to on Dreamstime definitely has frame rate problems and if that's what you uploaded to Shutterstock, then they were correct in rejecting it...Dreamstime should have rejected it also.

I downloaded your Dreamstime timelapse and looked through it frame by frame and there's duplicate frames.

You need to look at your final footage in a video player app that lets you step through it frame by frame is see if there's any duplicate frames. I use a Mac and the default Quicktime Player works fine for that, just use the arrow keys to step through frame by frame. If you see any duplicate frame, they you're screwing something up. I'm not sure what an equivalent app would be on a PC.

You didn't say which app you're using to process your time lapse, but you need to make sure the frame rate of your source matched the frame of your comp or project and that matches the frame rate of your output.

If you're having to do any kind of frame blending or Optical flow, then you're definitely doing something wrong.


« Reply #6 on: July 07, 2019, 20:07 »
0
As a test, I randomly downloaded about 10 of your other videos (Drone, Time Lapse, Fire) off Dreamstime and about half of them had frame rate problems.

« Reply #7 on: July 08, 2019, 02:19 »
0
The time lapse you linked to on Dreamstime definitely has frame rate problems and if that's what you uploaded to Shutterstock, then they were correct in rejecting it...Dreamstime should have rejected it also.

I downloaded your Dreamstime timelapse and looked through it frame by frame and there's duplicate frames.

You need to look at your final footage in a video player app that lets you step through it frame by frame is see if there's any duplicate frames. I use a Mac and the default Quicktime Player works fine for that, just use the arrow keys to step through frame by frame. If you see any duplicate frame, they you're screwing something up. I'm not sure what an equivalent app would be on a PC.

You didn't say which app you're using to process your time lapse, but you need to make sure the frame rate of your source matched the frame of your comp or project and that matches the frame rate of your output.

If you're having to do any kind of frame blending or Optical flow, then you're definitely doing something wrong.

That is really wide analysis of my work. Thank You for that! I will definitely try to fix this problem. The problem probably is that I'm not matching my source videos with my composition. I'm using Premiere for that. For stitching timelapses I use LR timelapse, but main problem really could be in main composition in Pr... I will write when I will try to fix it...

« Reply #8 on: July 08, 2019, 07:44 »
+1
The time lapse you linked to on Dreamstime definitely has frame rate problems and if that's what you uploaded to Shutterstock, then they were correct in rejecting it...Dreamstime should have rejected it also.

I downloaded your Dreamstime timelapse and looked through it frame by frame and there's duplicate frames.

You need to look at your final footage in a video player app that lets you step through it frame by frame is see if there's any duplicate frames. I use a Mac and the default Quicktime Player works fine for that, just use the arrow keys to step through frame by frame. If you see any duplicate frame, they you're screwing something up. I'm not sure what an equivalent app would be on a PC.

You didn't say which app you're using to process your time lapse, but you need to make sure the frame rate of your source matched the frame of your comp or project and that matches the frame rate of your output.

If you're having to do any kind of frame blending or Optical flow, then you're definitely doing something wrong.

That is really wide analysis of my work. Thank You for that! I will definitely try to fix this problem. The problem probably is that I'm not matching my source videos with my composition. I'm using Premiere for that. For stitching timelapses I use LR timelapse, but main problem really could be in main composition in Pr... I will write when I will try to fix it...

Yes, like FB said, you have 1 duplicate frame every 5 frames. This means you have dropped a 24p (23.976p) video into a 30p (or 29.97p) timeline without changing the speed. If you want a 29.97p output you need to "Interpret" the file first so that it plays faster, and then drop it into a 29.97p timeline. Or just sell it as 23.976p. :)

Uncle Pete

  • Great Place by a Great Lake - My Home Port
« Reply #9 on: July 08, 2019, 10:16 »
0
The time lapse you linked to on Dreamstime definitely has frame rate problems and if that's what you uploaded to Shutterstock, then they were correct in rejecting it...Dreamstime should have rejected it also.

I downloaded your Dreamstime timelapse and looked through it frame by frame and there's duplicate frames.

You need to look at your final footage in a video player app that lets you step through it frame by frame is see if there's any duplicate frames. I use a Mac and the default Quicktime Player works fine for that, just use the arrow keys to step through frame by frame. If you see any duplicate frame, they you're screwing something up. I'm not sure what an equivalent app would be on a PC.

You didn't say which app you're using to process your time lapse, but you need to make sure the frame rate of your source matched the frame of your comp or project and that matches the frame rate of your output.

If you're having to do any kind of frame blending or Optical flow, then you're definitely doing something wrong.

That is really wide analysis of my work. Thank You for that! I will definitely try to fix this problem. The problem probably is that I'm not matching my source videos with my composition. I'm using Premiere for that. For stitching timelapses I use LR timelapse, but main problem really could be in main composition in Pr... I will write when I will try to fix it...

Yes, like FB said, you have 1 duplicate frame every 5 frames. This means you have dropped a 24p (23.976p) video into a 30p (or 29.97p) timeline without changing the speed. If you want a 29.97p output you need to "Interpret" the file first so that it plays faster, and then drop it into a 29.97p timeline. Or just sell it as 23.976p. :)

Good advice now I dopn't have to explain the same thing. In round numbers... Shooting at 24 and rendering at 30, isn't going to work.  :)


 

Related Topics

  Subject / Started by Replies Last post
56 Replies
12088 Views
Last post July 22, 2018, 09:21
by Brightontl
0 Replies
1408 Views
Last post January 15, 2018, 15:20
by Brightontl
0 Replies
1376 Views
Last post June 18, 2018, 07:05
by Brightontl
1 Replies
1939 Views
Last post July 19, 2018, 03:47
by Brightontl
2 Replies
2053 Views
Last post October 10, 2018, 05:22
by Brightontl

Sponsors

Microstock Poll Results