• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

rendered video problems (sticks/glitch in player)

Offline
#1 Anamorphic702
Hi I'm new and looked for similar problems on the forum but didn't see this exact problem. So I managed to complete a full lapse with de-flicker no problem on the trial version. Then I just upgraded to the license private version on my MAC.
I succesfully have rendered out the basic workflow on this version from LRT to LR.
But when using the deflicker workflow and/or HG workflow and rendering it out the final mp4 will not play correctly. It will open in all my players but it will STICK on the first couple of frames and maybe skip a couple other frames and thats it.
I've tried re-rendering a few times. I suspect something with the keyframes and/or a glitch with LR reading/writing the metadata??

I'm not sure how the log posting works but this is the only one I have to pull from my folder:




2014-05-14 22:56:39 +0000, DEBUG ------------------------------------------------
2014-05-14 22:56:39 +0000, DEBUG ---Launched LRTExport version 3.3.0
2014-05-14 23:03:45 +0000, TRACE Expecting LRTimelapse at: /Applications/LRTimelapse 3.app
2014-05-14 23:03:45 +0000, TRACE sourceName: raw import
2014-05-14 23:03:45 +0000, TRACE Outputfilename original: raw_import
2014-05-14 23:03:45 +0000, TRACE Outputfilename stripped: raw_import
2014-05-14 23:04:23 +0000, TRACE Expecting LRTimelapse at: /Applications/LRTimelapse 3.app
2014-05-14 23:04:23 +0000, TRACE sourceName: raw import
2014-05-14 23:04:23 +0000, TRACE Outputfilename original: raw_import
2014-05-14 23:04:23 +0000, TRACE Outputfilename stripped: raw_import
2014-05-14 23:04:38 +0000, TRACE Creating output Dir: /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/LR project folder/revised deflicker exports/LRT_raw_import
2014-05-14 23:04:38 +0000, TRACE Rendering: /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/raw import/_E8A5181.CR2
2014-05-14 23:04:44 +0000, TRACE Moving from /var/folders/z4/zd333_xd6cjcw8tg1q58d8kh0000gn/T/73BF6761-B7B5-4060-83FA-2377DC1B58F4/LRT_00001.jpg to /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/LR project folder/revised deflicker exports/LRT_raw_import/LRT_00001.jpg
2014-05-14 23:04:44 +0000, TRACE Rendering: /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/raw import/_E8A5182.CR2
2014-05-14 23:04:50 +0000, TRACE Moving from /var/folders/z4/zd333_xd6cjcw8tg1q58d8kh0000gn/T/73BF6761-B7B5-4060-83FA-2377DC1B58F4/LRT_00002.jpg to /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/LR project folder/revised deflicker exports/LRT_raw_import/LRT_00002.jpg
2014-05-14 23:04:51 +0000, TRACE Rendering: /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/raw import/_E8A5183.CR2
2014-05-14 23:04:56 +0000, TRACE Moving from /var/folders/z4/zd333_xd6cjcw8tg1q58d8kh0000gn/T/73BF6761-B7B5-4060-83FA-2377DC1B58F4/LRT_00003.jpg to /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/LR project folder/revised deflicker exports/LRT_raw_import/LRT_00003.jpg
2014-05-14 23:04:57 +0000, TRACE Rendering: /Volumes/My Book 1/Film Projects/Time Lapse/DP workflow TEST/raw import/_E8A5184.CR2
Offline
#2 gwegner
I don't think it has anything to do with the workflow you use - I think it's a problem with the player/hardware and the high bitrates LRTimelapse's encoder produces. Those high quality files are for further post processing, not directly playing.
If you want to play, export in Full HD, H.264, in Medium Quality. Then you can use the same intermediary sequences to output in higher qualities for further processing. I always generate two files. One for preview, one for postprocessing.
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#3 Anamorphic702
ok thanks G, I'll try that method.
Also one other quick Q, after I render out the high quality mp4, I want to edit in final cut pro 7, should I just convert to pro res with stream clip or maybe FCP media manager?

thanks again!
Offline
#4 gwegner
Best you would use LRTimelapse Pro to create the ProRes directly, otherwise you will definitely sacrifice quality going through the MP4...
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#5 Anamorphic702
So i upgraded to lrt pro and even after rendering to pro res 4k (UHQ and/or VHQ) files they will not play or work in final cut pro 7 or X. I can import or drag the file in there but again they just stick and cause the FCP to freeze up.
Final Cut X tells me there are dropped frames also.
Am I missing a workflow step?
Can either of the Final Cut Pros even handle ultra high quality 4K / pro res 444 files?

I'm confused??? gahhh!!
Offline
#6 gwegner
All Pros I know use the Prores 444 export, never heard of that problems. But I can't speak personally of FCP, since I don't use it.
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#7 Benobiwahn
Hi!

I`ve got a similar problem when importing time-lapse sequences that I´ve rendered with LRTimelapse into Final Cut Pro X. I think it just applies to sequences I have rendered after updating LRTimelapse to 4.7.3 the ones I rendered before can be read by FC pro X without any problem.

Are there any mentionable changes regarding the output file since the update? Please help! BTW, apart from that recent issue I love the software and have recommended it a thousand times already Big Grin
Offline
#8 gwegner
In 4.7.3 indeed I've changed the rendering to use the better and newer color profile BT.2020. I didn't experience any problems with any format in Premiere Pro.

Since I don't have Final Cut, could you please do me a favor and make a short test (just export and render 5 images) - first with LRT4.7.3, try prores and mp4 - then reinstall 4.7.1 (still on the download page) and rerender. Check if that makes a difference when importing into Final cut.

For me it would be important to know, which render settings you used, which worked and which not and if the differences happen with mp4 and/or prores.
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#9 Benobiwahn
Hi Gunter,

sorry for getting back so late. I can´t export proRes since i don't own the professional version. I´m always using mp4 to export my timelapses. I converted my time lapses (rendered with lrt 4.7.3) with another program from mp4 to mp4 and I could then import it into final cut. the problem just seems to happen with the original lrt 4.7.3 file.

regards
Offline
#10 gwegner
Ok, good to know that we are talking about MP4.
Which version of Mac OS are you using? And are you using the latest Final Cut?
Which settings do you use to render the MP4 files? Please try different qualities and resolutions. There are some combinations of very high resolution (4K) and Aspectratios (3:2) that produce MP4 files outside the specifications. You'll get a warning about this in the LRT render dialog. Make sure to avoid that combinations.
Please try Full HD, force 16:9, high quality. See if that imports.
Then you can try 3K and 4K UHD likewise.
Let me know.
Try playing the files with the builtin quicktime - does that work? Try playing in VLC player. Does that work?
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo

...also check out: