[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-07-07 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=407778

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #25 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-06-22 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #24 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-06-08 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

Robert  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |NEEDSINFO

--- Comment #23 from Robert  ---
I would personally consider this bug thread resolved and I think the remaining
issue I had is very different than the one described by this thread.  I have
filed a different bug at :

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

If you want me to update it to 'resolved', when I'm satisfied, let me know.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-06-04 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #22 from Robert  ---
Hi, just curious if the bug I mentioned in my last comment is still on your
radar: "If I render videos that have the ':' character in them, the output
rendered video just shows blank white frames.  I was able to work around this
by renaming all videos in my project to not include the ':' character.".

It's a bit different than the bug I reported, but I can file a separate bug for
it if you want.  If you need repo steps, let me know.

For now I'll just keep re-naming all my files to ones that kdenlive can work
with, but it would be cool if it worked out of the box.  It makes doing backups
easier without all the renaming.

Also, is there anywhere I can do 'donations' to the kdenlive project (not kde
overall) to help keep the bug fixers well fed?  You guys should consider
setting up a patreon.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-25 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #21 from Robert  ---
Hi, a brief update:

-  I've tried out the new kdenlive-19.04.1c-x86_64.appimage and the time
drifting after saves issue appears to be fixed for me.
-  I've edited a fairly large project based on the same files, and I haven't
gotten the 'Invalid clip' error again so that appears to be fixed.  I have also
been testing through opening with a desktop app shortcut which seemed to
trigger the issue before.
-  I do still think there is still one bug which happens on rendering.  I
haven't dug into the source, but I have a hunch that there is another instance
of the same colon related bug.  If I render videos that have the ':' character
in them, the output rendered video just shows blank white frames.  I was able
to work around this by renaming all videos in my project to not include the ':'
character.  Also, for whatever reason, I don't get this error if I run the
kdenlive app image directly from the command-line.  Not sure why, most of the
environment variables are the same.

If you need a set of repo steps for rendering bug, let me know.  I anticipate
that the previous repo steps should be easily adapted.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-24 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #20 from Robert  ---
Fantastic, I need to do some video editing this weekend, so this comes at just
the right time.  Thank you for the quick turn-around.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-24 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #19 from Jean-Baptiste Mardelle  ---
Ok, so I think the issue should now be solved in the latest AppImage:
https://files.kde.org/kdenlive/release/kdenlive-19.04.1c-x86_64.appimage.mirrorlist

Please test if possible and let us know.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-24 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #18 from Jean-Baptiste Mardelle  ---
Git commit efbf6bd1002174b893befd1f216f594ba0db1839 by Jean-Baptiste Mardelle.
Committed on 24/05/2019 at 09:14.
Pushed by mardelle into branch 'Applications/19.04'.

Fix invalid clip on project opening

M  +5-24   src/bin/projectitemmodel.cpp
M  +10   -6src/mltcontroller/clipcontroller.cpp

https://invent.kde.org/kde/kdenlive/commit/efbf6bd1002174b893befd1f216f594ba0db1839

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-23 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #17 from Robert  ---
Awesome, glad to hear.  I look forward to trying out the next release :)

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-23 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #16 from Jean-Baptiste Mardelle  ---
Ok, we seem to have a regression that prevents clips with a colon ':' to load
correctly. This is the reason for the invalid clip error message. working on it

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-23 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #15 from Jean-Baptiste Mardelle  ---
Git commit bc32c54a408d283de1a0568301dcd3c626967632 by Jean-Baptiste Mardelle.
Committed on 23/05/2019 at 06:25.
Pushed by mardelle into branch 'Applications/19.04'.

Do not use MLT producer's get_length_time methd as it changes the way the
length property is stored, causing inconsistencies (clock vs smpte_df)

M  +1-1src/mltcontroller/clipcontroller.cpp

https://invent.kde.org/kde/kdenlive/commit/bc32c54a408d283de1a0568301dcd3c626967632

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-22 Thread Jean-Baptiste Mardelle
https://bugs.kde.org/show_bug.cgi?id=407778

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #14 from Jean-Baptiste Mardelle  ---
Thanks for your investigation. I can confirm the behavior described in your
last comment. It only happend on project profiles with non integer fps, and the
clip duration seems to vary slightly between saves. I still have to investigate
if the problem is in MLT or Kdenlive, and if this has real consequences, will
get back to you soon on that. Not sure this is the cause of your "invalid clip"
errors though.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-21 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #13 from Robert  ---
Here are exact repo steps:

mkdir /tmp/test
cd /tmp/test
wget https://files.kde.org/kdenlive/release/kdenlive-19.04.1b-x86_64.appimage
$  md5sum kdenlive-19.04.1b-x86_64.appimage
# f0ab2ecf3f606e1f1fc36e2a3929f9f7  kdenlive-19.04.1b-x86_64.appimage
chmod u+x kdenlive-19.04.1b-x86_64.appimage
wget "http://www.robertelder.ca/Screencast 2019-05-21 14:55:40.mp4"
./kdenlive-19.04.1b-x86_64.appimage
#  Add clip 'Screencast 2019-05-21 14:55:40.mp4'.  Don't add to timeline.  If
prompted to create profile for clip, click 'Cancel'.
#  After clip has been added, do save as 1.kdenlive in current directory.
./kdenlive-19.04.1b-x86_64.appimage 1.kdenlive  #  Then change *nothing* and
'save as' 2.kdenlive
./kdenlive-19.04.1b-x86_64.appimage 2.kdenlive  #  Then change *nothing* and
'save as' 3.kdenlive
./kdenlive-19.04.1b-x86_64.appimage 3.kdenlive  #  Then change *nothing* and
'save as' 4.kdenlive
./kdenlive-19.04.1b-x86_64.appimage 4.kdenlive  #  Then change *nothing* and
'save as' 5.kdenlive
./kdenlive-19.04.1b-x86_64.appimage 5.kdenlive  #  Then change *nothing* and
'save as' 6.kdenlive

#  Then observe that the project files include different times:
robert@robert-msi-ge62:/tmp/test$ grep -Hn 'id="producer0"' *.kdenlive
1.kdenlive:4: 
2.kdenlive:4: 
3.kdenlive:4: 
4.kdenlive:4: 
5.kdenlive:4: 
6.kdenlive:4: 

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-21 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #12 from Robert  ---
Created attachment 120236
  --> https://bugs.kde.org/attachment.cgi?id=120236=edit
screenshot for fps.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-21 Thread alcinos
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #11 from alcinos  ---
Thank you very much with the in-depth exploration!

When you don't accept to create the profile, or switch to an existing profile,
it means that potentially the fps of the project and the fps of your video
samples don't match.
My theory, based on what you show, is that the fps conversion math (used for
example to compute the length of the clips in frames), will create small but
real rounding errors, and when you repeat that over and over the errors will
compound.

I'm a bit short on time right now but will definitely take a look soon, if
confirmed it would be a serious bug.

To be sure I reproduce exactly what you did, would you mind giving me the
default fps of your projects in kdenlive? It should be displayed in the title
of the app when you open a fresh kdenlive.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-21 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #10 from Robert  ---
Hi, 

Thanks for the response.  For the ordering of the group encodings, I would like
to cast a vote that the ordering be canonicalized somehow, or at least made
predictable so that doing 'save as' with a project with no changes produces a
new .kdenlive project with idential hash checksums (just for debugability).

I'm fairly sure it's not a bad disk problem, I've experienced this in testing
from my SSD and larger spinning disk.  Here's the one I'm using now:

After doing sudo smartctl -a /dev/sdb
SMART overall-health self-assessment test result: PASSED
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED 
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000b   100   100   062Pre-fail  Always  
-   0
  2 Throughput_Performance  0x0005   100   100   040Pre-fail  Offline 
-   0
  3 Spin_Up_Time0x0007   122   122   033Pre-fail  Always  
-   2
  4 Start_Stop_Count0x0012   098   098   000Old_age   Always  
-   3200
  5 Reallocated_Sector_Ct   0x0033   100   100   005Pre-fail  Always  
-   0
  7 Seek_Error_Rate 0x000b   100   100   067Pre-fail  Always  
-   0
  8 Seek_Time_Performance   0x0005   100   100   040Pre-fail  Offline 
-   0
  9 Power_On_Hours  0x0012   068   068   000Old_age   Always  
-   14199
 10 Spin_Retry_Count0x0013   100   100   060Pre-fail  Always  
-   0
 12 Power_Cycle_Count   0x0032   099   099   000Old_age   Always  
-   1990
191 G-Sense_Error_Rate  0x000a   100   100   000Old_age   Always  
-   0
192 Power-Off_Retract_Count 0x0032   100   100   000Old_age   Always  
-   28
193 Load_Cycle_Count0x0012   097   097   000Old_age   Always  
-   32587
194 Temperature_Celsius 0x0002   115   115   000Old_age   Always  
-   52 (Min/Max 12/64)
196 Reallocated_Event_Count 0x0032   100   100   000Old_age   Always  
-   0
197 Current_Pending_Sector  0x0022   100   100   000Old_age   Always  
-   0
198 Offline_Uncorrectable   0x0008   100   100   000Old_age   Offline 
-   0
199 UDMA_CRC_Error_Count0x000a   200   200   000Old_age   Always  
-   0
223 Load_Retry_Count0x000a   100   100   000Old_age   Always  
-   0

SMART Error Log Version: 1
No Errors Logged

So, I spent the entire day messing around with this to try and figure out why
it was getting corrupted, and I'm pretty sure I've found *a* bug.  Not sure if
it's the one we're looking for.

Long story short is that you should be looking for reproducibility in the
ability to open a project, make *absolutely no changes*, then save the file. 
What I see happening is I can create a new project, add a single clip.  Don't
add it to timeline, add to project.  Save project as.  Re-open new project,
change nothing, save as.  Repeat this like 6 times, then diff the project files
and you'll see a trend like this:

a.kdenlive: 
b.kdenlive: 
c.kdenlive: 
d.kdenlive: 
e.kdenlive: 
f.kdenlive: 
g.kdenlive: 

Note that the time length keeps going down.  If you add the clip to the
timeline, you can see it move around and if you add multiple clips, empty spots
slowly creep in.  I did some tests to see if the change is deterministic, and
doing 6 tries of save as from a single point seem to deterministicly change the
track length.  

I also noticed that sometimes when I add a clip there is a message about
creating a 'profile' for the clip.  Sometimes it is a popup dalog you have
answer, and sometimes it's a small sub-window in the clips area (why the
difference?).  I found that if you click cancel or ignore the message you get
this time 'drifting' effect after save, but it never asks for a profile again. 
If I click 'create' the profile, it seems to stop drifting on multiple saves,
so perhaps I really *have* to create a profile?  If so, that message should be
much more forceful rather than allowing subtle drifting and blank parts in the
track.

Another important point:  Sometimes, I don't get that 'create profile' message
at all.  For example, if I add the Screencast 2019-05-21 14:55:40.mp4 video,
then save exit.  Re-open project, then add VID_20190520_093206251.mp4, I get
*absolultely no* message about creating profiles.  Whereas, if I add
VID_20190520_093206251.mp4 first I get a mandatory prompt for it.

Here are the source videos to test with:

wget "http://www.robertelder.ca/Screencast 2019-05-21 14:55:40.mp4"
wget "http://www.robertelder.ca/VID_20190520_093206251.mp4;

No project file is necessary, create a new project from scratch.


Now, that's one definite issue, but unfortunately, I was not able to reproduce
the corruption issue all day today when launching kdenlive appimage from the
command-line.  I can often re-produce it when launching kdenlive by

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-21 Thread alcinos
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #9 from alcinos  ---
The difference you see is in the encoding of the groups, it doesn't matter for
the issue at hand.


Where is the media located? Is it on an external hard-drive for example? Is it
possible that you have a faulty disk that causes the file to be read with
errors?

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread emohr
https://bugs.kde.org/show_bug.cgi?id=407778

emohr  changed:

   What|Removed |Added

 CC||fritzib...@gmx.net
  Flags||Brainstorm+

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #8 from Robert  ---
Hi, I just did a test to delete one of the solid colour clips with one of the
clips that I have trouble with.  I then saved it, closed kdenlive, then
re-opened the file with no problems.  Then, I made 0 modifications and 'saved
as' the file again with another name.  I then did a diff of the two 'idential'
project files and found some of the xml tags moved around, but the content was
the same.

Then, I re-opened the latest project file and cut the offending clip into 3
major sections, deleted off a couple slices, and re-arranged the last clip so
it was in the middle two on the end.  Then I saved this file as '6.kdenlive'.

Then, I found something interesting:  If I open 6.kdenlive, then make no
modifications, save as to 7.kdenlive, I can see what I think are functional
differences in the 'children' section.  See attached two files as an example
(do a vim -d on them).  Note that I can still load the project and it looks
fine at this point as I can still edit/watch everything, but it seems fishy
that these number are changing.  I just did a re-open of 6.kdenlive and saved
it as '7-again.kdenlive' which is idential to 7.kdenlive so at least it might
be a deterministic change?

Actually, after staring at the diff for a bit, I can see that the change affect
the 'kdenlive:docproperties.groups' JSON array by re-arranging the order of the
objects.  I don't know enough about kdenlive internals to know if that is
really a functional difference or not, but it certainly doesn't make
reproducibility easier.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #7 from Robert  ---
Created attachment 120208
  --> https://bugs.kde.org/attachment.cgi?id=120208=edit
7.kdenlive

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #6 from Robert  ---
Created attachment 120207
  --> https://bugs.kde.org/attachment.cgi?id=120207=edit
6.kdenlive

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread alcinos
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #5 from alcinos  ---
The appimage should contain everything you need, I wound not worry about that
at this point.

So, if this simple test with a color producer works, we need to look further.

Can you try to reproduce the same test, replacing the color producer with one
video clip that you know for a fact it was getting flagged as "invalid clip" by
kdenlive?

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #4 from Robert  ---
Thanks.  I have followed these instructions and created a project with 2
separate saved points.  I can load both of them without issue.  I can also
render an output file that looks ok and renders properly on my computer.

See all artifacts at:

wget http://www.robertelder.ca/colortest1.tar

Also, you noted that my desktop QT version is old.  As I understand the
.appimage file gets around the outdated dependency problem by bundling all
dependences.  My question is, what important dependencies does it *not* bundle?
 I extracted it and I can see that it contains a copy of melt, but if this
problem is specific to me, then it must be in a very low-level dependency.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread alcinos
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #3 from alcinos  ---
Ok, let's try to get to the bottom of this.

First note: your Qt version (Qt: 5.9.5) is old, and it has known bug. This
means that you have to stick to the AppImage.

Now, using this appimage try this:
1. Create a new project
2. Go to Project -> add color clip, chose whatever color you want
3. It will add a color clip to the bin. Check whether you can visualize it
4. Add it on the timeline, resize it and move it a bit, and check if you can
preview the timeline
5. Save, close the program, then open again the project and see if you can
continue editing.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread Robert
https://bugs.kde.org/show_bug.cgi?id=407778

--- Comment #2 from Robert  ---
(In reply to alcinos from comment #1)
> Disclaimer: I haven't looked deep into that yet. 
> I just want to point out that if showing a red producer with melt doesn't
> work for you, there is a stream of things that may break, since your melt
> installation seems broken. We need to make sure the simple things work
> before attempting more complex ones.
> 
> Maybe you can try to build melt from source, and install it with sudo make
> install (make sure to uninstall any previously installed version / package),
> and report what happens when you try to output the red consumer.

Hi alcinos, thanks for your response.  I did (on at least one occasion), build
melt from source and actually sudo make install it.  I think I did that with
v6.16?  Same result when playing video/color:red.  Having said, that, there are
a lot of dependencies that the 'melt' executable relies on and I'm not 100%
sure I uninstalled all its dependencies.

Therefore, I did what I figured would be a stronger test which is build melt in
a directory in /tmp/, and then do '. setenv' to let the mlt package do whatever
it does to set paths, and then test the local melt executable that way without
install.  Same result.

Here is the bug I filed for melt:

https://github.com/mltframework/mlt/issues/445

Dan Dennedy suggested that perhaps there is an issue with my SDL2 (a dependency
of mlt?).  Even if that's the case, I would argue that kdenlive should be smart
enough to detect this subtle corruption condition and at least issue warnings
to the user for this situation where, clearly, an unmodified project file will
have its track lengths changed without any modifications to the project.  In
such a case, regular warnings that say something like 'Warning:  track length
changed' might arouse suspicion and make it a bit faster to track down bugs.

As of this time, I am not aware of any action item I can take to further assist
in fixing this issue.  The mlt bug I filed has been closed, and I don't know
enough about SDL2 or how it interacts with mlt to know what to investigate
there.  Please suggest further courses of action.

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

[kdenlive] [Bug 407778] Saved Project File Track Times Change Randomly Causing 'Invalid clip producer4 on track playlist at ...'

2019-05-20 Thread alcinos
https://bugs.kde.org/show_bug.cgi?id=407778

alcinos  changed:

   What|Removed |Added

 CC||french.ebook.lo...@gmail.co
   ||m

--- Comment #1 from alcinos  ---
Disclaimer: I haven't looked deep into that yet. 
I just want to point out that if showing a red producer with melt doesn't work
for you, there is a stream of things that may break, since your melt
installation seems broken. We need to make sure the simple things work before
attempting more complex ones.

Maybe you can try to build melt from source, and install it with sudo make
install (make sure to uninstall any previously installed version / package),
and report what happens when you try to output the red consumer.

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