Bug 408363

Summary: Rescale rendering not working
Product: [Applications] kdenlive Reporter: Rafael Linux User <rafael.linux.user>
Component: Rendering & ExportAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED DUPLICATE    
Severity: normal CC: fritzibaby, rafael.linux.user
Priority: NOR    
Version First Reported In: Appimage - Refactoring   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Render settings

Description Rafael Linux User 2019-06-05 23:49:53 UTC
SUMMARY
Render rescale option not working, despite selected.

STEPS TO REPRODUCE
1. Create a FHD project
2. Click on "Render" and enable "More options"
3. Select under "Generic", "MP4"
4. Enable "Rescale", typing 640 x 360
5. Click "Render to file"

OBSERVED RESULT
Rendered file is in FHD

EXPECTED RESULT
Rendered file should be in HD

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.12.8
KDE Frameworks Version:  5.45.0
Qt Version: 5.9.4

ADDITIONAL INFORMATION
kdenlive-19.04.1c-x86_64.appimage
Comment 1 emohr 2019-06-06 16:14:31 UTC
Fixed with: https://invent.kde.org/kde/kdenlive/commit/6c6f31468519e4aabd407be9f0a6b81e811f51a1

*** This bug has been marked as a duplicate of bug 407678 ***
Comment 2 Rafael Linux User 2019-06-07 20:21:25 UTC
I'm sorry, but this bug is not a duplicate of bug 407678. I just check the issue again with version kdenlive-19.04.2c-x86_64.appimage and the bug is not gone!!
Comment 3 emohr 2019-06-08 08:39:34 UTC
Created attachment 120687 [details]
Render settings

I tried with 19.04.2 Windows and Linux with a 1080p50 clip rendered to 640x360 and on both systems I got a 640x360 mp4 file.
Comment 4 emohr 2019-06-08 10:02:57 UTC
Do you have movit enabled? If yes please try without movit.
Comment 5 Rafael Linux User 2019-06-08 19:35:00 UTC
My apologies. I replied to the wrong thread. The rendering rescaling problem is solved. Is the "Crop" effect rescaling issue what is not solved (bug 408235). So, I'm sorry but my fault. The export issue is solved with the patch of the bug you linked. 

THANK YOU