https://bugs.kde.org/show_bug.cgi?id=374469

            Bug ID: 374469
           Summary: Kdenlive: Cannot reload file after creating proxy
                    video
           Product: kdenlive
           Version: 16.12.0
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: Video Display & Export
          Assignee: j...@kdenlive.org
          Reporter: marcdr...@protonmail.com
  Target Milestone: ---

Created attachment 103157
  --> https://bugs.kde.org/attachment.cgi?id=103157&action=edit
Sample error when reloading file,

I've got what might be a bit of an edge case here in that I'm having to work
over two drives (with most of the files on normal HD and some stuff on an SSD)
however, I don't think that's the reason.

I'm using PNG image sequences created by Natron because Kdenlive doesn't have
the facilities I need (not that it should!). 

This all works fine until I create a proxy for these clips (which are
bottlenecked by I/O from the HDD) - hence the reason for using a proxy. 

When I close and re-open Kdenlive, the link between the file and the proxy is
broken resulting in an error as shown.

This has created no end of heartache trying to figure out what was going on -
but I'm happy to have identified the bug (and bloody grateful to have Kdenlive,
TBH).

The workaround seems to be to reconnect the file manually in the diaglog
(recursive scanning isn't working for me - producing an abnormal termination).

This is what appears in the XML at the offending point I believe:

<property
name="kdenlive:originalurl">/run/media/marc/0016EB7B3AE5EBFA/Vocalise/Halo/%01d.png?begin:1</property>
  <property
name="kdenlive:proxy">/run/media/marc/fd43d48a-0e5b-44e1-b870-22b8a9c00185/PROXY/proxy/d7f5516f9998fa61fb1eae3e6c77a16d.mov</property>

I trust this is of assistance - I really don't want to have to go back to the
"Shark" if you know what I mean. :)

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

Reply via email to