[kdenlive] [Bug 371279] New: option to 'Remove Space' without 'Track Select' dialogue

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 371279
   Summary: option to 'Remove Space' without 'Track Select'
dialogue
   Product: kdenlive
   Version: 16.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

Currently when removing a space on the timeline, the user hits a keyboard
shortcut (G for me, I forget what the default is) and then is presented with a
dialog asking them to select which track to apply the action to. 
This makes for tedious and repetitive action when removing a lot of spaces on a
particular track - I'm always looking for ways to replace any actions I perform
with the mouse to actions performed with keyboard shortcuts, as it always
results in a increase in speed.

What I would suggest as a fix to this issue would be to keep the defaults as
they are (the dialogue helps new users understand what they are about to do and
doesn't confuse them) but include a checkbox in the preferences called 'use
selected track when Removing Space'. 

This way, whichever track is currently highlighted will always be the one which
has space removed, and people who use 'remove space' a lot can do so much
faster without having to constantly reach for the mouse and select the same
answer in a dropdown menu. 

(you might also include a note in the track selection dialog saying 'track
selection preferences can be set in Kdenlive's preferences' or something
similar, so that people who also find this frustrating will discover that there
is a fix available.)

Reproducible: Always

Steps to Reproduce:
1. place cursor in a gap on the timeline
2. hit shortcut for 'remove space'
3. dialog window pops up
4. reach for the mouse
5. select correct track
6. hit ok.
7. space is removed
8. repeat for as many spaces as you need to remove.


Expected Results:  
1. use the up/down arrows to select the track in which you will be working.
2. place cursor in a gap on the timeline
3. hit shortcut for 'remove space'
4. space is removed.
5. repeat for as many spaces as you need to remove.

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

[kdenlive] [Bug 358504] Possibility to show duration of selected zone

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #4 from Sam Muirhead  ---
(In reply to Jean-Baptiste Mardelle from comment #3)
>  Is it what you need?

yes, that works, thank you! 

Personally I would find it more logical/discoverable if I could hover the mouse
_anywhere_ in the timeline zone (i.e. the area marked blue on the botom half of
the timeline scale, not the numbered section above it). When hovering over the
numbers (the top half of the this timeline scale) or any area _outside_ of the
selected zone, the tooltip would have its current behaviour (show position, not
length of zone). 

But I understand if others feel differently, and the current solution will
certainly work fine for me.

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

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

[Baloo] [Bug 362222] New: Baloo crashes every session; file search doesn't work

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 36
   Summary: Baloo crashes every session; file search doesn't work
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: s...@cameralibre.cc
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
This error message occurs during every session, and I assume that the lack of
functioning 'search' facility in Dolphin is also related to it. It happens
seemingly randomly, regardless of which program I am using or if I'm
creating/deleting files, doing CPU-intensive work, or anything else.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fda8ee008c0 (LWP 1398))]

Thread 2 (Thread 0x7fd943b2f700 (LWP 2703)):
[KCrash Handler]
#6  0x7fda8ce4b418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fda8ce4d01a in __GI_abort () at abort.c:89
#8  0x7fda8b650002 in mdb_assert_fail (env=0x1a4ebe0,
expr_txt=expr_txt@entry=0x7fda8b651a5f "rc == 0",
func=func@entry=0x7fda8b652398 <__func__.7098> "mdb_page_dirty",
line=line@entry=2065, file=0x7fda8b651a40 "mdb.c") at mdb.c:1481
#9  0x7fda8b6456a5 in mdb_page_dirty (txn=0x1b27b20, mp=) at
mdb.c:2065
#10 0x7fda8b646863 in mdb_page_alloc (num=num@entry=1,
mp=mp@entry=0x7fd943b2ddf8, mc=0x7fd943b2e330) at mdb.c:2246
#11 0x7fda8b646ac9 in mdb_page_touch (mc=mc@entry=0x7fd943b2e330) at
mdb.c:2364
#12 0x7fda8b6486df in mdb_cursor_touch (mc=mc@entry=0x7fd943b2e330) at
mdb.c:6267
#13 0x7fda8b64b805 in mdb_cursor_put (mc=0x7fd943b2e330,
key=0x7fd943b2e710, data=0x7fd943b2e720, flags=) at mdb.c:6401
#14 0x7fda8b64e260 in mdb_put (txn=0x1b27b20, dbi=8,
key=key@entry=0x7fd943b2e710, data=data@entry=0x7fd943b2e720,
flags=flags@entry=0) at mdb.c:8759
#15 0x7fda8dfe0629 in Baloo::IdFilenameDB::put
(this=this@entry=0x7fd943b2e790, docId=docId@entry=25509614657272833, path=...)
at ../../../src/engine/idfilenamedb.cpp:75
#16 0x7fda8dfdc58a in Baloo::DocumentUrlDB::add
(this=this@entry=0x7fd943b2ea50, id=id@entry=25509614657272833,
parentId=parentId@entry=25332872458075137, name=...) at
../../../src/engine/documenturldb.cpp:135
#17 0x7fda8dfdc916 in Baloo::DocumentUrlDB::put
(this=this@entry=0x7fd943b2ea50, docId=docId@entry=25509614657272833, url=...)
at ../../../src/engine/documenturldb.cpp:69
#18 0x7fda8dff40ea in Baloo::WriteTransaction::addDocument
(this=0x7fd93c003460, doc=...) at ../../../src/engine/writetransaction.cpp:56
#19 0x7fda8dfedfe9 in Baloo::Transaction::addDocument
(this=this@entry=0x7fd943b2eb30, doc=...) at
../../../src/engine/transaction.cpp:226
#20 0x0041ec74 in Baloo::ModifiedFileIndexer::run (this=0x1ff3190) at
../../../src/file/modifiedfileindexer.cpp:99
#21 0x7fda8d90c343 in QThreadPoolThread::run (this=0x1f96020) at
thread/qthreadpool.cpp:93
#22 0x7fda8d90f84e in QThreadPrivate::start (arg=0x1f96020) at
thread/qthread_unix.cpp:331
#23 0x7fda8c5736fa in start_thread (arg=0x7fd943b2f700) at
pthread_create.c:333
#24 0x7fda8cf1cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fda8ee008c0 (LWP 1398)):
#0  0x7fda8cf0c9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fda8a1246c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fda8a0e0e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fda8a0e12c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fda8a0e142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fda8db46a7f in QEventDispatcherGlib::processEvents (this=0x1a49380,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#6  0x7fda8daeddea in QEventLoop::exec (this=this@entry=0x7ffe0cfd3b60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7fda8daf5e8c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#8  0x0041698c in main (argc=1, argv=) at
../../../src/file/main.cpp:88

Reported using DrKonqi

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #7 from Sam Muirhead  ---
You're fast! thanks!

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #5 from Sam Muirhead  ---
ah - when you choose 'use placeholder for missing clips' then it seems to work
as normal. So it functions ok, it's just that the warning dialog should not be
appearing.

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #4 from Sam Muirhead  ---
This bug has reappeared, at least in 16.07.70, I don't know if it existed
earlier as well.
The problem occurs not only when there is a period in the name, but it occurs
also when I rename the images to replace the period with an underscore.

To test the problem, you can download a project file and image sequence here:
http://www.cameralibre.cc/owncloud/public.php?service=files=978f0b221ff5849decd66bf7d19c9773

To replicate the bug:
1. create new kdenlive project.
2. click on 'add clip'
3. navigate to 'electronics' folder and select breadboard.0001.png
4. choose 'import image sequence' option
5. click OK.
6. save & close Kdenlive
7. re-open the project, and you'll get a 'missing clips' dialog, and relinking
the files with 'searh recursively' doesn't work.

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

[kdenlive] [Bug 361838] New: Colour picker for Colour Clip can't work due to darkened background

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 361838
   Summary: Colour picker for Colour Clip can't work due to
darkened background
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

Trying to create a colour clip with the same colour as a background in another
clip is currently impossible with the colour picker tool, due to background
darkening.

Reproducible: Always

Steps to Reproduce:
When choosing 'Add Colour Clip' in the Project Bin, I often want to replicate
an existing background colour of another element in my edit. 
So from the colour dropdown, I choose "custom..."
In the dialogue box that appears, I choose 'pick screen colour'
I can then pick a colour from the clip in the project monitor - but everything
else has been darkened slightly to highlight the colour dialogue box.

Actual Results:  
The resulting colour clip is much darker than the colour I was trying to
sample.

Expected Results:  
Darkening the background in order to highlight the dialogue box is useful in
all other situations, so maybe the solution should be that the background stays
darkened until the 'pick screen colour" button is pressed - from this moment
until a colour is selected, everything would be shown at normal brightness
levels, and then once selected, the background would be darkened again.


Kdenlive version 16.07.70 - I'm using the kdenlive-testing ppa on kubuntu
15.10.

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #14 from Sam Muirhead  ---
no objections from my side!

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

[kdenlive] [Bug 358503] some timecode is not displayed in monospace font

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #2 from Sam Muirhead  ---
ok, thanks!

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

[kdenlive] [Bug 358648] New: Allow configurable columns in Project Bin

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 358648
   Summary: Allow configurable columns in Project Bin
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

I brought up this topic in the forum and TheDiveO helped refine it to this
idea: 

Basically the specific goal is to be able to show a 'Markers' column in the
Project Bin alongside (sub)clips, so that the user can very quickly scan the
Bin and find clips containing relevant quotes or material that they have noted
down in the form of markers.
(see the forum topic to understand how this fits into a workflow for a fast
initial rough cut: https://forum.kde.org/viewtopic.php?f=265=130736)
in this image you see the use of markers in the Timeline, however there's no
similar marker info in the bin:
http://www.cameralibre.cc/wp-content/uploads/kdenlive.png

To achieve that goal, and to allow people to adapt the Bin to their own needs,
we thought the best method would be to allow the columns in the Project Bin to
be configurable, like in Dolphin/Nautilus etc - you could choose to show or
hide Thumbnails/Clip Name/Description/Creation Time/Duration/Markers etc.

Reproducible: Always

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

[kdenlive] [Bug 351722] SUGGESTION - 15.08 Add "remove in & out zone" button to the Clip Monitor

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #4 from Sam Muirhead  ---
To me it seems strange that you would ever need to clear the in and out
points..? I just navigate with JKL and set new points using the I and O
shortcuts, with no need to ever clear them - they just update with new points. 
But then, as you say, some people prefer to use the mouse... I had no idea that
there were 'handles' until you mentioned it - I just tried it out, but I still
don't really understand the workflow for using the mouse for this, so I think I
will just butt out. 
Nevermind then, as you were :)

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

[kdenlive] [Bug 351722] SUGGESTION - 15.08 Add "remove in & out zone" button to the Clip Monitor

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

 CC||s...@cameralibre.cc

--- Comment #2 from Sam Muirhead  ---
Hi Jesse, do you mean 'delete the In & Out points' or 'remove the footage
between the In & Out points'?

If you mean 'delete the In & Out points' - what is the use case for this
feature?

If you mean 'remove the footage between the In & Out points' then the 'Ripple
Delete' shortcut achieves this in the timeline:
https://userbase.kde.org/Kdenlive/Manual/Timeline/Editing#Cutting_Footage_from_multiple_aligned_tracks_-_Ripple_Delete
 
(I have it mapped to a single key (U), rather than Ctrl+X so that it's faster
and in the same area as J, K, L, I & O)

In the clip monitor, I don't know of a feature that does anything like this.
Again, a use case would be helpful to understand the situation.

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

 CC||s...@cameralibre.cc

--- Comment #3 from Sam Muirhead  ---
Although using a strikeout to maintain consistency with the other icons makes
sense in one way, unfortunately in the case of the 'lock track' icon it feels
counter-intuitive to me:

First of all because the proposed icon is a crossed-out OPEN padlock, so the
icon effectively says 'Not unlocked'. 
Secondly, because the default in this case is for tracks to be unlocked, so the
default view of a track header would be two normal icons (Audio+Video) and one
strikethrough icon (lock). To me at least, seeing something crossed out
indicates that I have chosen to cross it out - it is not in its default state,
I have turned something off. 

A solution that I would find more logical would be to keep the current icons,
but have the padlock body filled in when it is locked (see attachments).
This has three advantages:
1. It clearly differentiates 'locked' from 'unlocked'
2. The icon is much more noticeable when filled in - if you have accidentally
locked a track, or you've forgotten that you locked a track, and you're
wondering why you can't move something, it is useful to have a visible sign of
any unusual settings that may be causing the problem.
3. The solidity of the locked icon in comparison with the light outline of the
unlocked icon emphasizes this 'active effect' versus 'inactive default'
relationship.

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #6 from Sam Muirhead  ---
Created attachment 96825
  --> https://bugs.kde.org/attachment.cgi?id=96825=edit
existing Lock icon (breeze-light)

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #7 from Sam Muirhead  ---
Created attachment 96826
  --> https://bugs.kde.org/attachment.cgi?id=96826=edit
existing Unlock icon (breeze-dark)

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #4 from Sam Muirhead  ---
Created attachment 96823
  --> https://bugs.kde.org/attachment.cgi?id=96823=edit
filled-in Lock icon (breeze-light)

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #5 from Sam Muirhead  ---
Created attachment 96824
  --> https://bugs.kde.org/attachment.cgi?id=96824=edit
filled-in Lock icon (breeze-dark)

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

[kdenlive] [Bug 358439] 15.13 git master: proposal for better "unlocked track" icon

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

  Attachment #96825|existing Lock icon  |existing Unlock icon
description|(breeze-light)  |(breeze-light)

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

[kdenlive] [Bug 358387] Kdenlive-git - Consider option in context menu to "Show clip in timeline" which highlights all clip instances in timeline

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

 CC||s...@cameralibre.cc

--- Comment #1 from Sam Muirhead  ---
I agree! this would be very useful, particularly on longer projects.

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

[kdenlive] [Bug 358504] New: Possibility to show duration of selected zone

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 358504
   Summary: Possibility to show duration of selected zone
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

It would be very useful if there was a timecode box somewhere in the GUI (or an
option to reveal one) which showed the duration of the selected zone between In
and Out points. 

I have to calculate this duration manually whenever I'm trying to keep track of
certain sections of an edit - eg. to compare the lengths of particular scenes,
to see how much time I am giving to particular subjects. 
This is particularly frustrating when working with a Producer, when they ask me
how long a particular section of the timeline is - in Final Cut or Avid I could
have a quick answer, but with Kdenlive I suddenly show everybody in the room
how bad at mathematics I am:
"um... hang on, I will tell you soon... just working it out... ok, um, 14
minutes 21 seconds 7 frames minus, ah, 9 minutes, 32 seconds, and 17 frames...
errr..?"

Reproducible: Always

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

[kdenlive] [Bug 358503] New: some timecode is not displayed in monospace font

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 358503
   Summary: some timecode is not displayed in monospace font
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

(at least in my install) the timecode displayed under the Clip Monitor and
Project Monitor is in a proportional width font, meaning playback causes a
slight jitter like that seen with https://bugs.kde.org/show_bug.cgi?id=356661

could this be changed to a monospace font, like the status bar?

Reproducible: Always

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

[kdenlive] [Bug 357855] Upgraded 0.9x project retains previous Project End point, even when clips are deleted.

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #4 from Sam Muirhead  ---
Thanks- I will experiment with a fresh project and see if I can reproduce it!

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

[kdenlive] [Bug 357855] Upgraded 0.9x project retains previous Project End point, even when clips are deleted.

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #1 from Sam Muirhead  ---
Created attachment 96593
  --> https://bugs.kde.org/attachment.cgi?id=96593=edit
screenshot showing problem

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

[kdenlive] [Bug 357855] Upgraded 0.9x project retains previous Project End point, even when clips are deleted.

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #2 from Sam Muirhead  ---
project is in /kdenlive folder on this git repository:
https://gitlab.com/cameralibre/FragDenStaat-Animation/tree/master

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

[kdenlive] [Bug 357572] Project with many missing clips fails to open

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #2 from Sam Muirhead  ---
I followed your instructions but I didn't see a kcrash dialog when it crashed.
There's nothing that looks relevant in /tmp. Any ideas?
Behaviour and output from the terminal is the same as opening the project with
the other installs.

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

[kdenlive] [Bug 357572] Project with many missing clips fails to open

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #4 from Sam Muirhead  ---
thanks, done it: http://pastebin.com/eJJW0VEd

this time the behaviour is slightly different - the kdenlive GUI freezes on
'loading playlist' while the terminal reports a segfault.

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

[kdenlive] [Bug 357572] Project with many missing clips fails to open

[Sam Muirhead via KDE Bugzilla]

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

--- Comment #7 from Sam Muirhead  ---
ah, ok. Thank you, and good luck!

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

Sam Muirhead  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Sam Muirhead  ---
(In reply to Jean-Baptiste Mardelle from comment #2)
> Thanks for the report. Indeed, I found several major bugs in slideshows that
> I just fixed in git master and 15.12 branch. Please test again and let me
> know...

Tested - it works! great job, thanks a lot.

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

[kdenlive] [Bug 357397] New: Image Sequence (with period in filename) missing upon re-opening project

[Sam Muirhead via KDE Bugzilla]

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

Bug ID: 357397
   Summary: Image Sequence (with period in filename) missing upon
re-opening project
   Product: kdenlive
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: s...@cameralibre.cc

When opening a saved project, if it contains any image sequences with a period
in their filename, I get a Warning:Missing Clips dialog box and then I am
unable to relink the files using Search Recursively.

The workaround is easy - either import the image sequence using the 'Import
Slideshow Clip' option, or batch rename the files to remove the period before
importing into Kdenlive as an image sequence. Both of these options work with
no problems.

This bug is likely to affect anyone editing Synfig animations in Kdenlive
because by default, Synfig exports PNG sequences with the pattern:
SceneName.0001.png
SceneName.0002.png
SceneName.0003.png
Of course you can change this in Synfig to remove the period and avoid the
problem that way, but it would be a nasty surprise if you had done a lot of
work on your Synfig animation in Kdenlive and weren't able to retrieve it!

Reproducible: Always

Steps to Reproduce:
1.Click on Import Clip, navigate to folder containing image sequence
SceneName.0001.png
SceneName.0002.png
SceneName.0003.png
...
2. Click on SceneName.0001.png, check 'import as image sequence' option.
Import.
3. Edit the image sequence in kdenlive. 
4. Save SceneName.kdenlive & quit.
5. Open SceneName.kdenlive 


Actual Results:  
Warning: Missing Clips dialog appears, showing 'SceneName.%4d.png | File not
found'
Use Search recursively to navigate to the right folder - no change, File not
found.


Kdenlive 15.13.0
Qt 5.4.2
Kubuntu 15.10

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