Bug 388696

Summary:	Render to webm crash with AVStream error
Product:	[Applications] kdenlive	Reporter:	Ovidiu-Florin BOGDAN <kde.kfoar>
Component:	Rendering & Export	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	kde.kfoar
Priority:	HI
Version:	17.12.0
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Project file where this happens

Description Ovidiu-Florin BOGDAN 2018-01-08 20:46:48 UTC

Trying to render a video to webm fails with a Rendering crash with the error: 

Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.

Rendering to mp4 works fine.

Comment 1 Ovidiu-Florin BOGDAN 2018-01-08 20:48:28 UTC

Created attachment 109741 [details]
Project file where this happens

I've attached the project file where this happens.

Comment 2 Ovidiu-Florin BOGDAN 2018-01-09 07:23:15 UTC

This seems to be Manjaro specific, since I can't replicate this on Kubuntu 17.10 with the same version of Kdenlive.

Comment 3 Ovidiu-Florin BOGDAN 2018-01-10 20:52:04 UTC

The AppImage on the same Manjaro system does not present this issue.

On the installed version, I also have stuttering while playback from the Project Monitor.

Comment 4 Ovidiu-Florin BOGDAN 2018-01-10 21:01:37 UTC

I've reported this on Manjaro: https://bugs.manjaro.org/#ticket/zoom/17910

Comment 5 Jean-Baptiste Mardelle 2018-01-11 15:52:25 UTC

Can you please check if this is not a duplicate of issue #388503
https://bugs.kde.org/show_bug.cgi?id=388503

(replace vorbis with libvorbis for the audio codec)

Comment 6 Ovidiu-Florin BOGDAN 2018-01-13 20:33:21 UTC

(In reply to Jean-Baptiste Mardelle from comment #5)
> Can you please check if this is not a duplicate of issue #388503
> https://bugs.kde.org/show_bug.cgi?id=388503
> 
> (replace vorbis with libvorbis for the audio codec)

Yes, it is a duplicate of that bug after all for the rendering part. I haven't figured out the stuttering of the project monitor playback yet.

Thank you for your help.

*** This bug has been marked as a duplicate of bug 388503 ***