[kdenlive] [Bug 471094] Be able to select panels without firing up any action in the process...
https://bugs.kde.org/show_bug.cgi?id=471094 --- Comment #2 from Gabriel Gazzán --- (In reply to emohr from comment #1) > Monitor: clicking into monitor start/stop playback. Since 24.05: Can be > disabled in settings -> playback (commit: > https://invent.kde.org/multimedia/kdenlive/-/commit/ > 2d38282912cf2d6f4043e39c1cf9a1466f176b19) > > Timline: Yes that is on the to do list: > https://invent.kde.org/multimedia/kdenlive/-/work_items/1621 Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 485602] Jog/Shuttle settings dialog just shows disabled under Windows.
https://bugs.kde.org/show_bug.cgi?id=485602 --- Comment #3 from Gabriel Gazzán --- Thank you!! :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 485602] New: Jog/Shuttle settings dialog just shows disabled under Windows.
https://bugs.kde.org/show_bug.cgi?id=485602 Bug ID: 485602 Summary: Jog/Shuttle settings dialog just shows disabled under Windows. Classification: Applications Product: kdenlive Version: 24.02.2 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY Configure Kdenlive > Jog/Shuttle > section just shows "disabled" settings under Windows. Even though the device is working normally. It's more of a UX thing; it'd be nice to notice users that, under Windows, Kdenlive has no functional options for these kind of devices, but instead they are supposed to use the device driver's own options. Tested on Contour ShuttleXpress, Windows 11, all Kdenlive versions (including trunk). STEPS TO REPRODUCE 1. Configure Kdenlive > Jog / Shuttle OBSERVED RESULT All shown options are disabled, with no other guiding text. EXPECTED RESULT A. Show a warning text saying that, under Windows, device configuration should be done through the driver's interface. B. I don't know if it's possible, but any kind of device detection status flag would also be a nice touch. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478315] Keyframe interpolation modes, In and Out concepts wrong.
https://bugs.kde.org/show_bug.cgi?id=478315 --- Comment #4 from Gabriel Gazzán --- Created attachment 164052 --> https://bugs.kde.org/attachment.cgi?id=164052=edit OpenToonz ease in/out The OpenToonz Youtube video looks terrible, so here I've uploaded de same video. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478315] Keyframe interpolation modes, In and Out concepts wrong.
https://bugs.kde.org/show_bug.cgi?id=478315 --- Comment #3 from Gabriel Gazzán --- Another program that uses the In/Out concepts correctly is OpenToonz (Studio Ghibli's open source animation software) Here's a quick video I made showing it in action. https://youtube.com/shorts/FufHca0xjow -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478315] Keyframe interpolation modes, In and Out concepts wrong.
https://bugs.kde.org/show_bug.cgi?id=478315 --- Comment #2 from Gabriel Gazzán --- Also (and more relevant to potential Kdenlive potential users expectations) Premiere Pro uses this concept in the same way as After Effects. Here you can see someone explaining how to use it in Premiere Pro (and airing his previous own confusion about it) https://youtu.be/vupwCdFgWpE?t=200 (the video goes directly to the moment he talks about it) By the way, Blender is currently using this concept in the wrong (inverted) way. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478315] Keyframe interpolation modes, In and Out concepts wrong.
https://bugs.kde.org/show_bug.cgi?id=478315 --- Comment #1 from Gabriel Gazzán --- Created attachment 164048 --> https://bugs.kde.org/attachment.cgi?id=164048=edit Screenshot from Animator's Survival Kit, a well known and respected classic animation textbook. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478315] New: Keyframe interpolation modes, In and Out concepts wrong.
https://bugs.kde.org/show_bug.cgi?id=478315 Bug ID: 478315 Summary: Keyframe interpolation modes, In and Out concepts wrong. Classification: Applications Product: kdenlive Version: git-master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- Created attachment 164047 --> https://bugs.kde.org/attachment.cgi?id=164047=edit Adobe After Effects Manual SUMMARY *** When setting keyframe interpolation, the concept of what is considered "In" and what "Out" is wrong, in the current implementation. In: is when the time is "coming in" to the selected keyframe. Out: is when time is "going out" of the selected keyframe. *** ADDITIONAL INFORMATION There are a lot of references to this, but the main ones should probably be Adobe products (After Effects / Premiere Pro) and OpenToonz, all of the using the concept in the right way. A lot of classic animation related textbooks where the concept is explained clearly: Animator's Survival Kit, etc. Here you can see a demo of After Effects Easing In/Out into play: https://www.youtube.com/watch?v=UVox_2py9yU Below I will attach excerpts from the After Effects manual and from Animator's Survival Kit by Richard Williams, explaining the concept. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473755] New: Please, update 23.08 Beta's Spanish translation.
https://bugs.kde.org/show_bug.cgi?id=473755 Bug ID: 473755 Summary: Please, update 23.08 Beta's Spanish translation. Classification: Applications Product: kdenlive Version: 23.08.0 Platform: Other OS: Other Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY During the last month I've been doing a major revision of the Spanish UI translation, coinciding with the new Manual translation I started to work on in July (previously it was mostly untranslated). During this UI revision several terms and messages were changed/improved from previous versions, and together with those UI changes, the new manual pages were made to reflect them, to be in sync with what people see when using the program UI. Unfortunately, I've realized that the 23.08 Beta has taken a snapshot of the UI translation, older than the one containing the mentioned changes, so if released as it is now, the program UI in Spanish will have some (at times notorious) differences with the documentation about it, which it's not desirable. I know nobody will die for this, but if possible it'd be great to update the UI translation used in the 23.08 Beta to the current one in master. Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] Nightlies newer than "kdenlive-master-1575" can't load any media!
https://bugs.kde.org/show_bug.cgi?id=473366 Gabriel Gazzán changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Gabriel Gazzán --- problem solved in the latest nightlies (kdenlive-23.04.3-1197-windows-gcc-x86_64.7z and kdenlive-master-1591-windows-gcc-x86_64.7z) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] Nightlies newer than "kdenlive-master-1575" can't load any media!
https://bugs.kde.org/show_bug.cgi?id=473366 --- Comment #5 from Gabriel Gazzán --- Created attachment 160997 --> https://bugs.kde.org/attachment.cgi?id=160997=edit Warning message on first run. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] Nightlies newer than "kdenlive-master-1575" can't load any media!
https://bugs.kde.org/show_bug.cgi?id=473366 --- Comment #4 from Gabriel Gazzán --- I've just downloaded "kdenlive-master-1583-windows-gcc-x86_64.7z" and the problem still persists. I tried downloading the installable "kdenlive-master-1583-windows-gcc-x86_64.exe" and now the first time I run the program after installation a warning message displays. I'll attach the image here. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] Nightlies newer than "kdenlive-master-1575" can't load any media!
https://bugs.kde.org/show_bug.cgi?id=473366 --- Comment #3 from Gabriel Gazzán --- Created attachment 160968 --> https://bugs.kde.org/attachment.cgi?id=160968=edit Loading an existent project using the same sample AVI files This time the files seem to be loaded, but they only show and INVALID text in the Monitor (either project or clip monitor). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] Nightlies newer than "kdenlive-master-1575" can't load any media!
https://bugs.kde.org/show_bug.cgi?id=473366 --- Comment #2 from Gabriel Gazzán --- Created attachment 160967 --> https://bugs.kde.org/attachment.cgi?id=160967=edit Trying to import one of the sample avi files -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] Nightlies newer than "kdenlive-master-1575" can't load any media!
https://bugs.kde.org/show_bug.cgi?id=473366 Gabriel Gazzán changed: What|Removed |Added Summary|Since nightlies newer than |Nightlies newer than |"kdenlive-master-1575" |"kdenlive-master-1575" |program can't read any |can't load any media! |media! | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473366] New: Since nightlies newer than "kdenlive-master-1575" program can't read any media!
https://bugs.kde.org/show_bug.cgi?id=473366 Bug ID: 473366 Summary: Since nightlies newer than "kdenlive-master-1575" program can't read any media! Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY Since nightlies newer than "kdenlive-master-1575", the program can't read any imported media. I'm on Widows 11, perhaps this is a platform specific issue? STEPS TO REPRODUCE 1. Install any nightly version newer than 1575 2. Load any clip from disk. OBSERVED RESULT Error message on load. SOFTWARE/OS VERSIONS Windows: 11 Kdenlive version: Nightly #1581 KDE Frameworks Version: 5.108 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473087] Playback from the end of the Timeline doesn't work.
https://bugs.kde.org/show_bug.cgi?id=473087 --- Comment #2 from Gabriel Gazzán --- (In reply to Jean-Baptiste Mardelle from comment #1) > Git commit 8dcedfec03a5c8b4276c5c5d5ef772b700b8aa5e by Jean-Baptiste > Mardelle. > Committed on 08/08/2023 at 09:18. > Pushed by mardelle into branch 'release/23.08'. > > Fix play icon incorrectly active when playing from end, fix timeline not > playing from start > FIXED-IN: 23.08.0 > > M +11 -6src/monitor/glwidget.cpp > M +1-1src/monitor/glwidget.h > M +12 -7src/monitor/monitor.cpp > > https://invent.kde.org/multimedia/kdenlive/-/commit/ > 8dcedfec03a5c8b4276c5c5d5ef772b700b8aa5e Great. Than was fast! Thank you!! P.S. It seems nightlies are not being generated since 08/08/23, so I couldn't test it yet. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473086] List of Compositions/Effects names not translated in the UI.
https://bugs.kde.org/show_bug.cgi?id=473086 --- Comment #4 from Gabriel Gazzán --- (In reply to Bernd from comment #3) > (In reply to Gabriel Gazzán from comment #2) > > (In reply to Bernd from comment #1) > > > What language is missing? > > > > > > You seem to have good command of the English language so perhaps you could > > > help by providing the translation of said effects to whatever language you > > > want to see them translated to. > > > > > > The current state of the translation of the Kdenlive documentation is > > > listed > > > here > > > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs- > > > kdenlive-org/) where you can also find how to contribute to and help with > > > the translation. > > > > (In reply to Bernd from comment #1) > > > What language is missing? > > > > > > You seem to have good command of the English language so perhaps you could > > > help by providing the translation of said effects to whatever language you > > > want to see them translated to. > > > > > > The current state of the translation of the Kdenlive documentation is > > > listed > > > here > > > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs- > > > kdenlive-org/) where you can also find how to contribute to and help with > > > the translation. > > > > Hi Bernd, > > Thanks for answering so quickly. > > I am, in fact, the translator for Spanish, since 2011. :) > > Last month I've also taken the translation of the documentation in charge, > > and I'm doing it at a good pace. That has had the side effect of me really > > looking much deeper into every feature/option in the UI, so I started filing > > several issues here, in case they are of help. I have several others that I > > haven't managed to post yet, but they will come... > > > > Specifically, the problem I'm reporting here is that the vast majority of > > those compositions/effects names don't even appear in the PO file to be > > translated, so they should be in English in all locales, I guess. > > There's one honorable mention that I remember, that does appear in the PO > > (and is translated there), but still remains untranslated in the UI, and > > that is the "Wipe" transition. > > > > Cheers, > > g > > Very nice to meet you, Gabriel! > > I am currently working on the documentation updating old stuff, adding > missing stuff and bringing screenshots up to date. There are a few new > things Eugen and I are putting in to make it an even more useful > documentation. > > I don't know how i18n works and who or what creates the PO files you > mentioned. But in terms of translating effect names I am wondering whether > it would be better to focus on the effect descriptions than on the names. Same to me, Bernd! :) I see the work you're doing daily, when I update my SVN. It's much appreciated, there are various sections of the manual that are really out of date. Just for the record, I'm referring in this issue to the UI, not the documentation. Of course there are several effects with such strange names that I wouldn't dare to translate them (nor it'd make any sense), but at the same time, there are several other ones with much more common names, that users often see translated in other programs as well. So the idea would be to have as much effects with localized names as it makes sense. The same applies to compositions, which names are pretty standard in every comp app out there, and users are used to see them translated. Then, of course the effects' parameters (that's a whole other issue), and descriptions / "tooltips" are really useful to have localized too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473049] Slip Tool - Monitor background should be black while using it.
https://bugs.kde.org/show_bug.cgi?id=473049 --- Comment #3 from Gabriel Gazzán --- Created attachment 160802 --> https://bugs.kde.org/attachment.cgi?id=160802=edit The Out Point of the previous clip bigger than it should? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473049] Slip Tool - Monitor background should be black while using it.
https://bugs.kde.org/show_bug.cgi?id=473049 --- Comment #2 from Gabriel Gazzán --- (In reply to Bernd from comment #1) > (In reply to Gabriel Gazzán from comment #0) > > SUMMARY > > Project Monitor keeps displaying previously displayed frame (the one shown > > before starting to use the tool) as a background. > > > > > > STEPS TO REPRODUCE > > 1. Select Slip Tool > > 2. Start applying it and while doing so... > > 3. Observe the Project Monitor background. > > > > > > EXPECTED RESULT > > Black background. > > > > > > SOFTWARE/OS VERSIONS > > Windows: 11 > > KDE Frameworks Version: 5.108.0 > > Qt Version: 5.15.10 > > Which Kdenlive version are you using? Normally I use the most recent "daily build" when updating the translations, yesterday I also downloaded the Beta and installed it, to see if there were any changes, but the behavior was the same. If you need any other data or things for me to try, I'm here to help. P.S. 1: In fact, I just tested it again, and I realized that the frame shown as background seems to really be the Out Point of the previous clip in the Timeline (not the last shown frame before activating the tool, as I stated above). P.S. 2: I've also realized that there previous clip Out Point is not shown at the top-right corner, so perhaps, that's where the problem resides. Perhaps is that image, that is showing "full screen" on top of the black background. (I'll leave leave a screenshot showing it) Cheers, g -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473086] List of Compositions/Effects names not translated in the UI.
https://bugs.kde.org/show_bug.cgi?id=473086 --- Comment #2 from Gabriel Gazzán --- (In reply to Bernd from comment #1) > What language is missing? > > You seem to have good command of the English language so perhaps you could > help by providing the translation of said effects to whatever language you > want to see them translated to. > > The current state of the translation of the Kdenlive documentation is listed > here > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs- > kdenlive-org/) where you can also find how to contribute to and help with > the translation. (In reply to Bernd from comment #1) > What language is missing? > > You seem to have good command of the English language so perhaps you could > help by providing the translation of said effects to whatever language you > want to see them translated to. > > The current state of the translation of the Kdenlive documentation is listed > here > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs- > kdenlive-org/) where you can also find how to contribute to and help with > the translation. Hi Bernd, Thanks for answering so quickly. I am, in fact, the translator for Spanish, since 2011. :) Last month I've also taken the translation of the documentation in charge, and I'm doing it at a good pace. That has had the side effect of me really looking much deeper into every feature/option in the UI, so I started filing several issues here, in case they are of help. I have several others that I haven't managed to post yet, but they will come... Specifically, the problem I'm reporting here is that the vast majority of those compositions/effects names don't even appear in the PO file to be translated, so they should be in English in all locales, I guess. There's one honorable mention that I remember, that does appear in the PO (and is translated there), but still remains untranslated in the UI, and that is the "Wipe" transition. Cheers, g -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473087] New: Playback from the end of the Timeline doesn't work.
https://bugs.kde.org/show_bug.cgi?id=473087 Bug ID: 473087 Summary: Playback from the end of the Timeline doesn't work. Classification: Applications Product: kdenlive Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY While Timeline cursor is at the end of the timeline, starting playback won't work. Timeline cursor doesn't move, but still, the Play button in Project Monitor changes to "Pause", so there seems to be something going on in the background. OBSERVED RESULT Nothing happens. Last timeline frame shown in Project Monitor. EXPECTED RESULT Playback should start from the start of the Timeline. SOFTWARE/OS VERSIONS Kdenlive Version: 23.08.0 Beta Windows: 11 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 473086] New: List of Compositions/Effects names not translated in the UI.
https://bugs.kde.org/show_bug.cgi?id=473086 Bug ID: 473086 Summary: List of Compositions/Effects names not translated in the UI. Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY There are many compositions/effects names that are not currently translated in the UI. In case anyone may/wants to help with this issue, I've compiled all the names here. Thanks in advance!! The following Composition names don't show translated: · Addition · addition_alpha · Alpha ATOP · Alpha IN · Alpha OUT · Alpha OVER · Alpha XOR · Burn · Cairo Affine Blend · Cairo Blend · Circle Wipe · Color Only · Composite · Darken · Difference · Dissolve · Divide · Dodge · Grain Extract · Grain Merge · Hardlight · Horizontal Barn Door Wipe · Hue · Lighten · Luma · Mate · Multiply · Overlay · Push Down · Push Left · Push Right · Push Up · Rectangular Wipe · Saturation · Screen · Slide · Slide Down · Slide Left · Slide Right · Slide Up · Softlight · UV Map · Value · Vertical Barn Door Wipe · Wipe · Wipe Down · Wipe Left · Wipe Right · Wipe Up The following Effect names don't show translated: Alpha, Mask and Keying · Alpha gradient · Alpha operations · Alpha shapes · Alpha strobing · Bluescreen0r · Chroma Key: Advanced (Color Selection) · Despill · Key Spill Mop Up · Lumakey · Mask Apply · Obscure · Premultiply or Unpremultiply · Rectangular Alpha mask · Spillsupress · Transparency Audio · Adecorrelate · Adenorm · Adrc · Adynamicequalizer · Adynamicsmooth · Aexciter · Afreqshift · Alatency · Aphaseshift · Apsyclip · Arnndn · Aspectralstats · Asubboost · Asubcut · Asupercut · Asuperpass · Asuperstop · Atilt · Audio Levels · Auto Fade · Dialoguenhance · FFmpeg Audio Resampler · Speechnorm · Tiltshelf · Virtualbass Blur and Sharpen · Average Blur · Bilateral · Contrast Adaptive Sharpen · Dblur · Gaussian Blur · Planes Blur · Shape Adaptive Blur · Sharp/Unsharp · Smartblur · Square Blur Channels · Audio Pan · Balance · Pan Color and Image correction · 3 point balance · Apply LUT · Bézier Curves · Channel Extractor BLUE · Channel Extractor GREEN · Channel Extractor RED · Chroma Hold · CMYK adjust · Color balance · Color Channel Mixer · Color Contrast · Color Correct · Color Hold · Color levels · Color Overlay · Color Temperature · Colorize · Curves · Exposure · FTT-based FIR · Gamma (keyframeble) · Greyscale · Histogram Equalizer · Hue Shift · Levels · Limiter · Luminance · Monochrome · Negate · Normalize RGB video · RGB adjustment · Saturation · Sepia · SOP/Sat · Swapuv · Tint · Vibrance · Video Equalizer · White Balance · White Balance (LMS space) Deprecated · BurningTV · DCT Denoiser · DeLogo · Dither · Grain · K-Means · RGB Noise · Wave · Wavelet Denoiser EQ and filters · Allpass · Audio Equalizer (avfilter) · Band-pass · Band-Reject · Bass · High-pass · High-shelf · Low-pass · Low-shelf · Sox Band · Sox Bass Generate · Cairogradient · Draw Box · Draw Grid · Video grid · Vignette Grain and Noise · 3D FFT Denoiser · Chroma Noise Reduction · Denoiser · Gradfun · Median · Video Noise generator Image adjustment · Color Matrix · Deband · Dilation · EPX Scaler · Erosion · Hq*x Interpolator · Interlace field order · Interleave - Deinterleave · Kernel Deinterlacer · Kernel Deinterlacer · Phase · Set Range · Super2xsai · xBR Interpolator Misc · Alphaextract · Backgroundkey · Blockdetect · Blurdetect · Dnn_classify · Dnn_detect · Face blur · Face detect · FFmpeg Image Converter · FFmpeg Image Scaler · GPS Graphic · Grayworld · Hsvhold · Hsvkey · Huesaturation · Latency · Legacy FFmpeg Deinterlacer · Pixelize · Scdet · Scharr · Siti · Xine Deinterlacer Modulators · Flanger · Phaser · Pulsator · Sox Flanger · Sox Phaser · Treble · Vibrato Motion · Fade in · Fade out · Freeze · Nervous · Vertigo Pitch and Time · Sox Stretch Reverb, Echo and Delays · Compensation Delay · Sox Echo Stereo and Binaural Images ·
[kdenlive] [Bug 473049] New: Slip Tool - Monitor background should be black while using it.
https://bugs.kde.org/show_bug.cgi?id=473049 Bug ID: 473049 Summary: Slip Tool - Monitor background should be black while using it. Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY Project Monitor keeps displaying previously displayed frame (the one shown before starting to use the tool) as a background. STEPS TO REPRODUCE 1. Select Slip Tool 2. Start applying it and while doing so... 3. Observe the Project Monitor background. EXPECTED RESULT Black background. SOFTWARE/OS VERSIONS Windows: 11 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471850] New: "P" tag for proxy clips not translated in Timeline.
https://bugs.kde.org/show_bug.cgi?id=471850 Bug ID: 471850 Summary: "P" tag for proxy clips not translated in Timeline. Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- Created attachment 160037 --> https://bugs.kde.org/attachment.cgi?id=160037=edit "P" proxy clip tag in Timeline, not translated. SUMMARY The "P" letter that shows at clip headers when a clip is using its proxy doesn't show translated in the Timeline. It does so in the Project Bin though. Attached is a screen capture showing how it shows in the Spanish UI (where it should read "R", instead of "P"). Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464644] Regex for GoPro proxy clips (lrv) is worng
https://bugs.kde.org/show_bug.cgi?id=464644 Gabriel Gazzán changed: What|Removed |Added CC||gabcor...@gmail.com Platform|Appimage|unspecified OS|Linux |All Component|User Interface |Video Display & Export --- Comment #1 from Gabriel Gazzán --- Hi, I had to edit the GoPro LRV preset text file to be able to use it with my "Hero 7" camera generated files too. It's no big deal, but since the data is available online (see below), it'd be great if Kdenlive could incorporate it out of the box. In particular my camera files use a "GH" prefix. Here is a list of all file-naming patterns used in GoPro cameras: https://community.gopro.com/s/article/GoPro-Camera-File-Naming-Convention?language=en_US Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471175] Compact the UI as much as possible.
https://bugs.kde.org/show_bug.cgi?id=471175 --- Comment #1 from Gabriel Gazzán --- Created attachment 159755 --> https://bugs.kde.org/attachment.cgi?id=159755=edit Current UI, for comparison. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471175] New: Compact the UI as much as possible.
https://bugs.kde.org/show_bug.cgi?id=471175 Bug ID: 471175 Summary: Compact the UI as much as possible. Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- Created attachment 159754 --> https://bugs.kde.org/attachment.cgi?id=159754=edit compact UI mockup SUMMARY I think there's plenty of space that could be gained in favor of productive areas in the UI by trimming little empty spaces from around icons and texts almost everywhere. I've attached a mock-up to depict what could be achieved by doing so. Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471116] "Resize Item Start / End" functions - Suggestion for improvement.
https://bugs.kde.org/show_bug.cgi?id=471116 --- Comment #1 from Gabriel Gazzán --- At the very least, I think it could be useful to include in the Manual a Tip in the "Resizing a Clip" section, to suggest to temporarily activate the Slip Tool as a way to be able to see the actual span of the clip, before using the "Resize Item Start/End" functions. (It's a pity that when Slip Tool is active you can't move the timeline cursor though, because you have to deactivate it before moving the cursor, and then use the Resize Item function). The current Workflow is: 1. Activate Slip Tool 2. See what the total span of the selected clip is. 3. Deactivate it. 4. Move the time cursor to the intended place (a bit of a guesswork). 5. Use the Resize Item Start/End function. It could be way better if there was a way to move time cursor while Slip Tool is active, so workflow would be instead: 1. Activate Slip Tool 2. Move the time cursor to the intended place, while seeing the clip's max span. 3. Use the Resize Item Start/End function. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471116] New: "Resize Item Start / End" functions - Suggestion for improvement.
https://bugs.kde.org/show_bug.cgi?id=471116 Bug ID: 471116 Summary: "Resize Item Start / End" functions - Suggestion for improvement. Classification: Applications Product: kdenlive Version: git-master Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY It'd be useful to modify the behavior of these functions in one or both of the following ways, when the affected item is a clip: 1) When the timeline cursor is placed beyond the clip's original span, resize the clip's duration to the maximum possible one, even if it won't reach the timeline cursor position. 2) Having some way of showing an indicator of the original span of the selected clip in the timeline (I think of a colored line that spans the absolute extension of the original clip's content, or something along these lines). Perhaps a modifier key combination could be hold to temporarily show that line. In this way, the user would have an idea of where the maximum possible limits of the resized item could be effectively located. The idea is having something similar to what the Slip tool shows when a clip is selected, but as this function is not a tool it should be activated temporarily, before the function is used. This could alleviate not having 1) implemented, as at least the user would be able to see where to locate the cursor prior to using the function. Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471084] Improve Focus Timecode time input to make it faster.
https://bugs.kde.org/show_bug.cgi?id=471084 --- Comment #1 from Gabriel Gazzán --- Another variants possible I forgot to mention above: [digits typed --> resulting timecode] 1 --> 00:00:00:01 3: --> 00:00:03:00 2:: --> 00:02:00:00 1:15: --> 00:00:01:15:00 115: --> 00:00:01:15:00 etc... or in additive/subtractive form: [current time = 00:05:20:10] +15: --> 00:05:35:10 -15: --> 00:05:05:10 etc... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471094] New: Be able to select panels without firing up any action in the process...
https://bugs.kde.org/show_bug.cgi?id=471094 Bug ID: 471094 Summary: Be able to select panels without firing up any action in the process... Classification: Applications Product: kdenlive Version: git-master Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY One thing that often gets in the way of a smooth workflow in Kdenlive is the fact that whenever you make a click to select a panel to make it the active/current one, something always happens right away. This often results in a distraction (caused by the fact that you have to revert the change made, or stop the action being executed without intention and the resume what you went to do initially), so I think it should be avoided whenever technically possible. OBSERVED RESULT Depending on where you make click you get: - Project Bin: the Clip Monitor goes to front, even when you haven't selected any clip in there. - Monitors: start reproducing the shown video. - Timeline empty space [Selection Tool active]: change the time cursor position to where you made the click, clicking on an empty space in any track or even where there's no track at all. - Timeline Clip/Wipes/Track: Effects Stack panel goes to front. (OK, I know this can be switched on/off in Preferences, and it's not a bad thing per se, but just something to take into account when organizing panels in the UI, so not to end up having a messy workflow. EXPECTED RESULT Be able to make click on a panel to making it current, without any action starting to happen immediately. Perhaps there's a way to do it and I don't know it yet, if that's the case my apologies. Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471086] New: Timecode display more prominent
https://bugs.kde.org/show_bug.cgi?id=471086 Bug ID: 471086 Summary: Timecode display more prominent Classification: Applications Product: kdenlive Version: git-master Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY It would be handy to have timecode display in Monitors a little more "findable" at a glance, while editing. For this to happen I think of mainly two cosmetic changes: 1. Use a bigger font type with a stronger body (a bolder one). 2. Find a way to highlight the currently used timecode (that is, the clip or timeline one, depending on which panel is the current one). Perhaps by using a tinted background? I find this proposal more needed when editing in the timeline, because the eyes are posed over that lower part of the screen (the timeline), while the timecode counter is changing "silently" elsewhere (in the timeline monitor); so I think that having a somewhat more prominent "landmark" to quickly take your eyes to, would result in an improvement of the awareness of it. As a bonus, this proposal would also help in distinguishing the real "live" timecode, from that other timecodes present at the timeline toolbar, that my eyes were continually headed to when I started using the program, but where not was I was really looking for (the timecode in the monitor was it). Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471084] New: Improve Focus Timecode time input to make it faster.
https://bugs.kde.org/show_bug.cgi?id=471084 Bug ID: 471084 Summary: Improve Focus Timecode time input to make it faster. Classification: Applications Product: kdenlive Version: git-master Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY When inputting a specific timecode to jump to, it would be better to take the typed HH:MM:SS:FF digits in pairs from right to left. That's the way other programs do it, and it results in faster, more flexible interaction. Below is an example of what to expect from the proposed input method, assuming a 25 fps project: NOTE: when finished typing, user would need to press Enter key to end and process the desired input. [digits typed --> resulting timecode] 0 --> 00:00:00:00 24 --> 00:00:00:24 25 --> 00:00:01:00 5924 --> 00:00:59:24 5925 --> 00:01:00:00 595924 --> 00:59:59:24 595925 --> 01:00:00:00 etc... Also, it'd be just great to allow to enter relative numbers to advance/rewind a certain amount of time from the current time, like shown below: [current time = 00:05:20:10] +1510 --> 00:05:35:20 -1510 --> 00:05:05:00 +21510 --> 00:07:35:20 etc... Finally, I'm not inventing anything here, just describing how things work in Premiere Pro, in this respect. I'm not a big fan of copying features just for the sake of it, but this feature comes really handy while moving in the timeline on certain kinds of projects. Thanks for listening! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471082] New: I found "Guide" term to be confusing, while "Timeline Marker" would be more intuitive.
https://bugs.kde.org/show_bug.cgi?id=471082 Bug ID: 471082 Summary: I found "Guide" term to be confusing, while "Timeline Marker" would be more intuitive. Classification: Applications Product: kdenlive Version: git-master Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gabcor...@gmail.com Target Milestone: --- SUMMARY Hi, I find confusing the use of the term "Guide" to refer essentially to a marker (with all the same characteristics of markers). Even so, because usually on image related programs, a guide is almost always some kind of visual aid you expect to find overlaid on the image, to help you in aligning or distributing elements. Another place of confusion is that currently the panel where the user manages the markers is named "Guides". For all of this, I would find more intuitive (and standard) to refer to these guides as "Timeline Markers", as opposed to "Clip Markers" (like other video editing programs, as Premiere Pro, already do). As a bonus, options like "Add Marker/Guide quickly" would simplify to just "Add Marker quickly" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414939] Compositions names untranslatable.
https://bugs.kde.org/show_bug.cgi?id=414939 --- Comment #2 from Gabriel Gazzán --- Well, that's what I'm reporting: that they currently *can't* be translated. Whenever they do I will translate them for sure. ;) (Spanish translation is always at "100% translated" status since years ago, whatever you happen to see untranslated is most likely because either it is not available to be translated, or is a recently added feature that I still didn't see in the last PO file). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414939] New: Compositions names untranslatable.
https://bugs.kde.org/show_bug.cgi?id=414939 Bug ID: 414939 Summary: Compositions names untranslatable. Product: kdenlive Version: git-master Platform: Other OS: unspecified Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: vpi...@kde.org Reporter: gabcor...@gmail.com Target Milestone: --- Hi, I translate Kdenlive into Spanish since a looong time now, but it's the first time I come to report a bug (at least here, since Kdenlive lives inside the KDE project structure). SUMMARY I've seen that "Compositions" names still aren't available to be translated. I suppose it's something that's already under the radar, but after a search I couldn't find any report on this one, so I did this report. Thanks for all the efforts put into development, the program is looking great!! -- You are receiving this mail because: You are watching all bug changes.
