[Kdenlive-devel] Fwd: max_analyze_duration reached

[Pascal Fleury]

Hi Dan,

On Mon, Sep 22, 2014 at 3:30 AM, Dan Dennedy <dan at dennedy.org> wrote:

> On Sun, Sep 21, 2014 at 5:30 PM, Pascal Fleury <
> fleury at users.sourceforge.net> wrote:
>
>> Hello,
>>
>> I am completely stuck, any help welcome...
>>
>> I am about to finish a video project, where I use pretty long files
>> (several 1080p at 25 13 minute chunks, audio @ 96kHz stereo 32 bit float
>> for 1.5 hours) and it seemed to work nicely so far. I used proxy clips all
>> along, as working off the original video is just not possible.
>>
>
> I never use proxy clips, almost always source clips, and very occasionally
> transcode problematic clips.
>

On my machine, navigating through original clips is way too slow. Also I
have 4 video tracks, with mostly 2 tracks having a video at any given time.
Proxy clips are actually making the whole thing very usable, if not really
comfortable.


>
>
>> Now I try to render the project, and I face many issues: first, when
>> rendering the project with proxy clips set on the clips (the little 'P'),
>> it does not use the full resolution for the final render. I think this is a
>> known issue (ignores the little checkbox in the render dialog).
>>
>> My real issue is that if I remove the proxy clips, then it tries to
>> re-render the thumbnails on the time line, and gets them all wrong. The
>> files are correct, but it does not display the right images (takes some
>> others), and renders full black video.
>>
>> After saving and reloading, it's even worse, as I face the issue with
>> lots of lines like in the title (more, see below). And after this, _all_
>> clips on the timeline are zero length, completely ruining my project. I use
>> git for all text files, and did regular checkpoints, so I have not lost
>> much besides time, and rollbacks are easy.
>>
>>
> Sounds like "remove the proxy clips" is not a safe operation.
>

I think it tries to get the original clip length, and from the error
 message, seems to not get a useful answer. If it returns a length of zero
(or negative) in case it reaches the maximum analysis length, then it would
explain why my clips get all shrunk on the timeline.


>
>> So essentially, I am stuck with a project I cannot render after 60 hours
>> of editing time... Any help ? Anything I
>>
>
> I think you need a workaround for that problem with the checkbox being
> ignored, but I do not know anything about the proxy mode in Kdenlive. Maybe
> there is a way to modify the xml and render it with melt.
>

I will fiddle a bit more with that checkbox, as I think I had other issues
with sub-projects that I imported.


>
>
>> could do to get a final video from my project ? Or is this
>> max_analyze_duration from an underlying tool that I could downgrade/upgrade
>> ?
>>
>> I can definitely tell you that the message "max_analyze_duration
> reached" comes from libavformat. It appears very frequently in many tools
> (too verbose), is related to determining the duration of a clip, and is not
> likely related to your problem.
>

As I mentioned above, does libavformat then return a size of e.g. 0 if it
could not analyze it fully ?
Is there a cmdline tool that I could run on these WAV and video files to
see the failure mode ?


>
>
>> Also, I faced numerous issues with this project, mostly due to the size
>> of data and project I think, and I should probably do a write up. Where
>> would be a good avenue for this ? This list ?
>>
>> Thanks,
>> Pascal
>>
>> $ kdenlive
>> Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading
>> configurations from ~/.fonts.conf is deprecated.
>> [wav @ 0x7fe2f45da760] max_analyze_duration reached
>> [wav @ 0x7fe2f45e2620] max_analyze_duration reached
>> [wav @ 0x7fe2f48549c0] max_analyze_duration reached
>> [wav @ 0x7fe2f462a360] max_analyze_duration reached
>> [wav @ 0x7fe2f4608b20] max_analyze_duration reached
>> [wav @ 0x7fe2f4613220] max_analyze_duration reached
>> [mpegts @ 0x7fe2f4909a40] max_analyze_duration reached
>> [mpegts @ 0x7fe2f490cd80] max_analyze_duration reached
>> [mpegts @ 0x7fe2f4c35680] max_analyze_duration reached
>> [wav @ 0x7fe2f49175e0] max_analyze_duration reached
>> [wav @ 0x7fe2f49196a0] max_analyze_duration reached
>> [mpegts @ 0x7fe2f4c24220] max_analyze_duration reached
>> [mpegts @ 0x7fe2f4c29c00] max_analyze_duration reached
>> [mpegts @ 0x7fe2f49bfb20] max_analyze_duration reached
>> [...and hundreds more...]
>>
>>
>>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Kdenlive-devel mailing list
> Kdenlive-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdenlive/attachments/20140922/df841480/attachment.html>