[kdenlive] [Bug 470456] kdenlive crashes 24% into loading project clips with a segmentation fault

2023-05-30 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=470456

Darwin McGrath  changed:

   What|Removed |Added

Summary|kdenlive crashes 24% into   |kdenlive crashes 24% into
   |loading project clips   |loading project clips with
   ||a segmentation fault

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 457783] Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips.

2023-05-30 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=457783

Darwin McGrath  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 470456] New: kdenlive crashes 24% into loading project clips

2023-05-30 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=470456

Bug ID: 470456
   Summary: kdenlive crashes 24% into loading project clips
Classification: Applications
   Product: kdenlive
   Version: 23.04.1
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

Created attachment 159352
  --> https://bugs.kde.org/attachment.cgi?id=159352=edit
gdb output

SUMMARY
***
Opening .kdenlive file directly or via open or open recent menu items, in deb
or snap installations, normally or using gdb, causes kdenlive to crash after
project is 24% loaded.  I am able to open a smaller older project without
error.
***


STEPS TO REPRODUCE
1. Open kdenlive
2. Open project

OBSERVED RESULT
Project starts to open. Progress shows 24%. kdenlive hangs briefly then shuts
down ungracefully (disappears with no warning).
Smaller older project opens without error.

EXPECTED RESULT
Project should open

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04.02 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Attached gdb report showing messages until kdenlive hangs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-05-17 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #16 from Darwin McGrath  ---
It seems to be fixed!
Created a new project and opened and closed several times without errors.
Opened an older project. Made a small change and saved. A backup was created
due to the project format upgrade.

Odd behaviour: Opened up the resaved old project and had to search for one
video file recursively (?). The file hadn't been moved. Was not the first file
or the last. See attachment for image of error. There seems to be an incorrect
path duplication.

Once file is recursively found project seems to work fine on reloads.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-05-17 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #15 from Darwin McGrath  ---
Created attachment 159036
  --> https://bugs.kde.org/attachment.cgi?id=159036=edit
Missing File Issue after reloading upgraded project file

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-04-28 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #9 from Darwin McGrath  ---
(In reply to Jean-Baptiste Mardelle from comment #7)
> Sorry for this poor experience . Could you please attach a .kdenlive project
> file that doesn't open correctly to this bug report ? Thanks

Hi
I've attached the file and have also linked a video showing its creation.
Additionlly, in the video you can see the problem described in Bug 468998 where
kdenlive moves the goPro LRV files to the proxy save location.

Corrupting the file required closing and opening it twice, however there was a
proxy error on the first save.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-04-28 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #8 from Darwin McGrath  ---
Created attachment 158514
  --> https://bugs.kde.org/attachment.cgi?id=158514=edit
Corrupted File

Here is a link to a screencast video showing the creation of this corrupted
file

https://youtu.be/Qfjp2bolxgM

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-04-27 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #6 from Darwin McGrath  ---
(In reply to emohr from comment #5)
> This is the reason why we provide all Kdenlive versions ever published in
> the attic (https://docs.kdenlive.org/en/getting_started/installation.html).
> And you have always an AppImage or a Windows standalone version which you
> can save together with the project.

Apologies,
I meant the 22.04.03 appimage, not flatpak, from the attic crashed when saving
projects.
The idea of saving the appimage is good though, if it worked for me.
I tried flatpak installs instead of deb, and downgrading using synaptic package
manager (to 21.?.?). All had issues of some sort or another.
Essentially, I can't install an older version that works.
I'm more interested in switching back to 23.04.? when it's working in any case.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-04-27 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #4 from Darwin McGrath  ---
(In reply to emohr from comment #3)
> Never change the video editor version during a project (even not on other
> video editors). 
> 
> Version 23.04.0 has a new project file version which is not backwards
> compatible. 
> 
> I just realized we don’t have mentioned that.

Excellent advice.
I think it came through the Ubuntu update. I'm going to make sure I don't
confirm the update without checking the content from now on.

Actually, as the version went from 22 to 23 I had a thought there might be file
compatibility issues. But that wasn't the main problem. When I used the flatpak
to downgrade I couldn't save without crashing. I could open the corrupted file
in the older version even though it said corrupted in 23.04.0 but the timeline
was empty so it wasn't helpful.

Hopefully 23.04.1 fixes this. It's a really risky thing to try though.
Corrupted save files means you can't trust making a project on the software.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 469040] Constantly crashing and corrupting files

2023-04-27 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=469040

Darwin McGrath  changed:

   What|Removed |Added

 CC||dar...@mcgrathtoronto.com

--- Comment #3 from Darwin McGrath  ---
(In reply to emohr from comment #2)
> Thank you for reporting. We tested the new sequence feature before we
> released it. But there are lots of different setups possible we didn’t know.
> Some fixes are already pushed for 23.04.1. 
> 
> Seems to be similar to Bug 468962

Thanks emohr
I don't think it's similar to Bug 468962 as the user didn't seem to have
timeline or editing issues. Similar to my reported Bug 468999 though, as you
pointed out in that one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] Loading saved projects gives "Could not recover corrupted file" error

2023-04-27 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

--- Comment #2 from Darwin McGrath  ---
(In reply to emohr from comment #1)
> Thank you for reporting. Seems to be similar to Bug 469040
Thanks
Looks exactly the same.
Funny, I didn't come across other bug reports. I guess I don't know how to
filter properly.
Mine has a little bit more detail if that helps.

Same frustration level...I lost a project and have had to revert to another
open source editing software that shall go unnamed for the time being as
rolling back caused other problems.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468999] New: Loading saved projects gives "Could not recover corrupted file" error

2023-04-26 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468999

Bug ID: 468999
   Summary: Loading saved projects gives "Could not recover
corrupted file" error
Classification: Applications
   Product: kdenlive
   Version: 23.04.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
***
Loading saved projects results in "Could not recover corrupted file" error
***


STEPS TO REPRODUCE
1. Create and save a project
2. Close kdenlive
3.  Try to open project to continue work

OBSERVED RESULT
Project starts to open, loading clips in the project window then...
Error - kdenlive
Could not recover corrupted file

Continuing opens kdenlive with a blank project

EXPECTED RESULT
kdenlive should not corrupt the file
and/or
Project should open
or at the very least
Project should give more details on where the corruption occurs in the file as
it is not at the beginning of the loading process

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Ubuntu 22.04.2 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Project folder is Parent of Project file

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 468998] New: GoPro LRV Proxy moved to proxy folder then not found on project reload

2023-04-26 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=468998

Bug ID: 468998
   Summary: GoPro LRV Proxy moved to proxy folder then not found
on project reload
Classification: Applications
   Product: kdenlive
   Version: 23.04.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
***
Using GoPro LRV files to add clips to Project Bin. kdenlive MOVES LRV files to
proxy folder. Then on project reload can't find proxy files and rebuilds it's
own in the proxy folder.
***


STEPS TO REPRODUCE
1. Creat a new project
2. Add an LRV file to project bin (LRV and MP4 files are in the same source
directory)
3. Save the project (Project Folder is Parent of Project File)
4. Close and Open Project again

OBSERVED RESULT
If able to open project file without getting "Could not recover corrupted file"
Error (this is another big problem) then proxy is not found and kdenlive offers
to rebuild proxies (Can't be found because kdenlive moved the LRV file to proxy
folder)


EXPECTED RESULT
LRV file should NOT be moved to proxy folder

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04.2 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 464011] Title Clips appear as blank when created

2023-04-24 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=464011

Darwin McGrath  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Darwin McGrath  ---
Seems fixed in version 23.04.0

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 464011] New: Title Clips appear as blank when created

2023-01-08 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=464011

Bug ID: 464011
   Summary: Title Clips appear as blank when created
Classification: Applications
   Product: kdenlive
   Version: 22.12.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

Created attachment 155114
  --> https://bugs.kde.org/attachment.cgi?id=155114=edit
Image of the problem, Edit Warning and Correct result

SUMMARY
***
Adding a title clip results in a blank title clip in the Project Bin and no
text appearing in timeline preview when clip is used.
***


STEPS TO REPRODUCE
1. Create a title clip with content


OBSERVED RESULT
Title clip thumbnail in Project Bin is blank.
If title clip is dropped in timeline the thumbnail is blank and no title clip
content appears in timeline preview
Editiing title clip from Project Bin or Timeline, clicking Update Title in edit
window results in the following popup warning:
"Save Title - Kdenlive
You are editing an external title clip (/Path to Project Save directory/). Do
you want to save your changes to the title file or save the changes for this
project only?"
Options are: Save to title file, Save in project only
Clicking save to title file results in no change
Clicking save in project file results in the clip working correctly
Clicking the X in the top right corner of the popup window (cancelling the
window) results in the clip working correctly

EXPECTED RESULT
Title clip thumbnail in Project Bin and Timeline when used should show content.
Timeline preview should show content.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04.1 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This problem appeared after upgrading to 22.12.0 flatpak or .deb installs and
exists in 22.12.1 flatpak (deb not available currently to test)
I assumed it was a problem with my file structure but I have not made any
changes to that and can't find any new settings related to file locations in
kdenlive.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 462406] Changing lift gamma gain by clicking and holding creates multiple undo history entries. Requires many undo commands to reverse

2022-11-29 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=462406

Darwin McGrath  changed:

   What|Removed |Added

Summary|Changing lift gamma gain by |Changing lift gamma gain by
   |clicking and holding|clicking and holding
   |creates multiple undo   |creates multiple undo
   |history entries. requires   |history entries. Requires
   |many undo commands to   |many undo commands to
   |reverse |reverse

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 462406] New: Changing lift gamma gain by clicking and holding creates multiple undo history entries. requires many undo commands to reverse

2022-11-29 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=462406

Bug ID: 462406
   Summary: Changing lift gamma gain by clicking and holding
creates multiple undo history entries. requires many
undo commands to reverse
Classification: Applications
   Product: kdenlive
   Version: 22.08.3
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
***
Changing lift gamma or gain sliders or gamma or gain "dots" results in a long
chain of undo history elements when there should be a single entry upon release
of the mouse button. Undoing effect adjustment requires many undo commands.
***


STEPS TO REPRODUCE
1. Apply Lift gamma gain effect 
2. Move a slider or dot by clicking, dragging, and releasing with the mouse.


OBSERVED RESULT
Large string of undo entries in undo history


EXPECTED RESULT
Single entry, allowing a single undo command to reverse the change.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 22.04.1 LTS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 458784] Sorting the project bin by an order type does nothing if the order type is already selected

2022-09-08 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=458784

--- Comment #3 from Darwin McGrath  ---
(In reply to Jean-Baptiste Mardelle from comment #2)
> Thanks for your report. When I read it I wondered why you would like to
> select an already active sorting mode. then I realized date sorting was
> not working properly for newly inserted clips. I have now hopefully fixed
> it, so when a sorting ode is active it should correctly sort at insert time.
> If possible, please test  tomorrow's daily devel AppImage build to confirm
> the fix:
> https://binary-factory.kde.org/view/Windows%20MingW/job/
> Kdenlive_Nightly_mingw64/

Thanks!
Looks like it works in the nightly build.
I assumed I needed to go into the menu to sort because the clips came in
unsorted and that this bug was related to the menu selection process. Now I see
what you mean about date sorting not working at all. Ironically, now I'll just
be sorting by clicking the bar above the project clip list instead of going
into the menu. All good.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 458784] New: Sorting the project bin by an order type does nothing if the order type is already selected

2022-09-06 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=458784

Bug ID: 458784
   Summary: Sorting the project bin by an order type does nothing
if the order type is already selected
   Product: kdenlive
   Version: 22.08.0
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
***
Sorting the project bin by an order type (e.g. Date) does nothing if the order
type is already selected
***


STEPS TO REPRODUCE
1.  Import clips in project bin in something other than date order (e.g. by
name)
2.  Attempt to sort by Date.  Date is usually the selected option in the
dropdown on a first-time sort.


OBSERVED RESULT
No sorting takes place

EXPECTED RESULT
Clips should sort by Date ascending.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Ubuntu 22.04.1
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 457783] Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips.

2022-08-12 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=457783

--- Comment #1 from Darwin McGrath  ---
Issue with transition file not loading (luma01.pgm in the case of bar
horizontal) now occurs with composition wipe transitions as well.
In the list of project files luma01.pgm appears with no path. kdenlive unable
to find file on project reload. Requires either a manual search (file doesn't
exist so this fails) or deleting the clip as options. Deleting the clip results
in the transition in question reverting to a wipe with dissolve.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 457783] Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips.

2022-08-11 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=457783

Darwin McGrath  changed:

   What|Removed |Added

 CC||dar...@mcgrathtoronto.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 457783] New: Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips.

2022-08-11 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=457783

Bug ID: 457783
   Summary: Mix transitions don't work. Error message: Not enough
frames at clip [end/start] to apply the mix.
Transitions not saved if added to image clips.
   Product: kdenlive
   Version: 22.04.3
  Platform: Compiled Sources
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
Mix transitions not working
1. Mix transitions between video clips cannot be applied.
Error message is: "Not enough frames at clip [end/start] to apply the mix"
despite clips being 40+ seconds long
2. Mix transitions between image clips are not saved. Missing when project is
reloaded.


STEPS TO REPRODUCE
1. Create a new project and add video and image clips to the Project bin and
add them to the timeline
2. Double click between two video clips of suitable length to add mix. Will
receive error message, mix not created.
3. Double click between two image clips to add mix. Mix will be added. edit
transition as desired (e.g. slide)
4. Save file. Close kdenlive. open kdenlive, open saved project. transition is
gone or missing .pgm file message pops up.

OBSERVED RESULT
Error message when trying to create mix transition between video clips.
Mix Transitions between image clips gone or pgm file missing when reloading
project

EXPECTED RESULT
Should be able to add mix transitions between video clips.
Transitions should be saved.

SOFTWARE/OS VERSIONS
Windows: 11 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Attempted mix transition with slide from right to left and with luma bar
horizontal

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 456185] LRV proxy clips not used when fixing clip problems when opening a project.

2022-08-01 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=456185

--- Comment #3 from Darwin McGrath  ---
(In reply to Jean-Baptiste Mardelle from comment #2)
> Can you please test the daily development Appimage build to see if the
> problem is fixed for you ?
> https://binary-factory.kde.org/view/AppImage/job/Kdenlive_Nightly_appimage-
> centos7/

The problem seems fixed.

As I'm running Windows 11 I tested this using WSL to run the appimage file.
It ran and because the mount point is different for the Ubuntu instance opening
the test project required me to find the source files.
Searching recursively and manually and requiring proxies to be rebuilt resulted
in the expected behaviour:
Clips tagged as Proxies in the Project Bin. Rendering to file was done at high
resolution so high def original clips used instead of proxies.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 456185] New: LRV proxy clips not used when fixing clip problems when opening a project.

2022-06-30 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=456185

Bug ID: 456185
   Summary: LRV proxy clips not used when fixing clip problems
when opening a project.
   Product: kdenlive
   Version: 22.04.2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
Project uses LRV files for proxy files. If clip sources are moved (e.g.
directory name change or opening project on a different computer with a
different file structure) kdenlive popup asks user to search for clips
recursively or manually. Choosing recursive, LRV files are not set as proxies
and no clips in the project have proxies.
Choosing manual, selecting LRV sets the actual clip to the LRV file, not
setting the proxy as the LRV. Rendered output is low res.


STEPS TO REPRODUCE
1. Create a project that uses LRV files as proxies and add an LRV clip to the
Project Bin
2. add clip to timeline.
3. Save project
4. Move clips to a different location
5. Open Project
6. Search recursively for directory of clips, or manually for each clip.
7. When all clips found then select OK


OBSERVED RESULT
Project will have clips but no Proxy indicator and proxies are not used in
interface resulting in choppy preview.
If LRV was chosen as replacement clip manually then rendered output will be low
res.

EXPECTED RESULT
If LRV proxies are a selected option in Project settings then LRV files should
be searched for when finding clips recursively. If clips are found manually
then LRV should be set as proxy and mp4 as original regardless of whether LRV
or MP4 selected by user.


SOFTWARE/OS VERSIONS
Windows: 10/11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This could be a problem if using multiple machines while working on a single
project.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 454089] clips using Time Remap render using Proxy files

2022-05-27 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=454089

Darwin McGrath  changed:

   What|Removed |Added

Summary|clips using Time Remap  |clips using Time Remap
   |render in low quality   |render using Proxy files

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 454089] clips using Time Remap render in low quality

2022-05-24 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=454089

--- Comment #2 from Darwin McGrath  ---
(In reply to emohr from comment #1)
> I have tested according your settings with a clip 2720x1530 59.94fps and I
> don't get a low quality rendered file. But Kdenlive asked to "Transcode to
> edit friendly format" before I could apply time-remap. 
> 
> Can you test it again; right click on the problematic clip in the project
> bin -> "Transcode to edit friendly format" -> render again. Or put the
> transcoded clip into the timeline, make your speed setting and render just
> that clip.

Thanks for the quick response and apologies for my delay getting back to you.
I tried your suggestion first but it was not the issue.

I think I've figured out what is happening.
It looks like the Time Remapped clips use Proxy files to render instead of the
original files.

These are the steps I just took:
Test 1.:  Created a new file with the same clip and Time Remap settings to see
if it was some obscure option I'd changed.
Result 1: The new file rendered correctly at high quality.

Test 2: Created a proxy version of the Time Remapped clip in the new project so
that I can work without the preview stuttering.
Result 2: Even though the "Use Proxy Clips" is NOT selected in the Render
dialogue the clip with Time Remapping is rendered at low quality. Other clips
in the file without Time Remapping render at high quality.

Test 3: Created a proxy version of the other clip in the new project as well
Result 3: Same as Result 2. Low quality Time Remapped clip, high quality
regular clip.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 454089] New: clips using Time Remap render in low quality

2022-05-20 Thread Darwin McGrath
https://bugs.kde.org/show_bug.cgi?id=454089

Bug ID: 454089
   Summary: clips using Time Remap render in low quality
   Product: kdenlive
   Version: 22.04.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: dar...@mcgrathtoronto.com
  Target Milestone: ---

SUMMARY
Using Time Remap to speed up a portion of clips in a project results in the
entire clip using Time Remap rendering in low quality (appears blurry). Clips
in the project without Time Remap (including those sped up with Change Speed)
render in high quality (4K)


STEPS TO REPRODUCE
1. Add clips to project.
2. Enable Time Remap on a clip with a portion set to increase speed
3. Render project in high quality (4K) MP4-H265 or MP4-H264/AAC

OBSERVED RESULT
Entire Time Remapped clips within the rendered video are blurry. This includes
the portions of the clip sped up and portions left at speed=100%. Non Time
Remapped clips are rendered in 4K quality. 

EXPECTED RESULT
All rendered clips should be 4K

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
In Time Remap: Pitch Compensation on. Preserve Speed of next keyframes on.
Frame blending off. Changing these settings results in the same behaviour.
Rendering using 100% quality. Occurs with both Full Project and Selected Zone
render. Project set to 4K UHD 2160p 60fps. Clips are all 4K.

-- 
You are receiving this mail because:
You are watching all bug changes.