[digikam] [Bug 484858] New: Multiple instances of Gimp opened

2024-04-01 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484858

Bug ID: 484858
   Summary: Multiple instances of Gimp opened
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: myaccount...@protonmail.com
  Target Milestone: ---

There was earlier bug fixed which opened multiple instances of Gimp (and
possibly other programs) when "Open with default program" buttom is pressed.
This bug seems to have reappeared in 8.3.0. appimage.

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

[digikam] [Bug 484373] Wrong time/timezone data

2024-03-26 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484373

--- Comment #5 from Such A Shame  ---
Ok, I may have misinterpreted origin of the bug in the end here. My original
notice was that there seems to be "Z" timezone sent to iNaturalist now after
upgrade. And this may be the cause for +2 h time which constantly gets
submitted. This problem started to occur after upgrade to 8.3.0 and there
wasn't any issues before. 

Just confirmed that 8.2.0 sent same image resulting time "08:49 EET" shown at
iNaturalist while 8.3.0 resulted to "10:49 EET". When trying to edit them via
web interface after submitting, editing shows "08:49:16" and "08:49:16Z"
respectively.

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

[digikam] [Bug 484373] Wrong time/timezone data

2024-03-25 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484373

--- Comment #3 from Such A Shame  ---
It's actually image file creation date which gets +2 h time (shown at "File
Properties", while "digiKam properties" shows correct time). At least iNat
plugin seems to send this wrong time to iNaturalist as it strips all metadata
from pictures itself.

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

[digikam] [Bug 484373] Wrong time/timezone data

2024-03-24 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484373

--- Comment #1 from Such A Shame  ---
Appeared after upgrading 8.2.0 -> 8.3.0 appimage, but didn't verify by
reverting back.

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

[digikam] [Bug 484373] New: Wrong time/timezone data

2024-03-24 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484373

Bug ID: 484373
   Summary: Wrong time/timezone data
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Date
  Assignee: digikam-bugs-n...@kde.org
  Reporter: myaccount...@protonmail.com
  Target Milestone: ---

Checking image properties at digikam, pictures have +2 h wrong time visible.
This wrong time is also exported out via plugins.

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

[digikam] [Bug 484234] MP3 slider stopped working

2024-03-22 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484234

--- Comment #1 from Such A Shame  ---
For example mp4 videos no problems with this.

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

[digikam] [Bug 484234] New: MP3 slider stopped working

2024-03-22 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=484234

Bug ID: 484234
   Summary: MP3 slider stopped working
Classification: Applications
   Product: digikam
   Version: 8.3.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: myaccount...@protonmail.com
  Target Milestone: ---

While playing mp3 files at preview window slider for changing positions at
bottom screen and time details stopped working after switching 8.2.0->8.3.0
apimage. Length shows correctly at properties tag, and play correctly.

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

[digikam] [Bug 478991] BQM removes tags and ratings

2023-12-27 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=478991

--- Comment #7 from Such A Shame  ---
Thx for explanation. Will try to simplify my scripts. (Still hoping for feature
to run these scripts directly by left clicking images. You have abundance of
technical features included which is great, but at some places usability
improvements would be very helpful. Thank you for your work.)

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

[digikam] [Bug 478991] BQM removes tags and ratings

2023-12-26 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=478991

--- Comment #4 from Such A Shame  ---
Ok, I have workflow where I first run custom shell script then use built in
"Assign Labels" feature to mark it with colour label, which creates the
problem. Running custom script only works fine. So the problem is actually in
this built in feature.

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

[digikam] [Bug 478991] BQM removes tags and ratings

2023-12-26 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=478991

--- Comment #3 from Such A Shame  ---
Sry, I sent wrong script. I'll check one thing from the correct one before
sending it.

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

[digikam] [Bug 478991] BQM removes tags and ratings

2023-12-26 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=478991

--- Comment #2 from Such A Shame  ---
Example script which worked perfectly before is as simple as:

cp $INPUT $OUTPUT
convert -geometry 2048x2048 -sharpen 2 -quality 85 -strip $INPUT $OUTPUT

I can't grasp the nuances you suggest from documentation given (first copying
input to target).

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

[digikam] [Bug 478991] New: BQM removes tags and ratings

2023-12-25 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=478991

Bug ID: 478991
   Summary: BQM removes tags and ratings
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: BatchQueueManager-Core
  Assignee: digikam-bugs-n...@kde.org
  Reporter: myaccount...@protonmail.com
  Target Milestone: ---

SUMMARY
BQM removes all tags and star ratings.

STEPS TO REPRODUCE
1. Select file with tags and stars
2. Run BQM script with setting to overwrite file

OBSERVED RESULT
3. File is converted but tags and stars are removed

EXPECTED RESULT
3. File is converted and tags and stars are retained

Appeared in appImage 8.2.0

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-09-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #20 from Such A Shame  ---
Problems started again immediately today with 8.1.0, no USB drive attached.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-09-07 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #19 from Such A Shame  ---
I'm inclined to say this appears to affect 8.1.0 but not 8.0.0. 

There was long while without any problems (using 8.1.0 only) but now I got
8.1.0 doing this very quickly and constantly (three times) after restarts, but
using 8.0.0 every time in between not (three times slightly longer sessions).
What I was doing was transferring files from internal hard disk to USB
connected drive and rather soon after this error appeared - I'm unsure if this
particular action is relevant to this display bug. However I also got one
immediate crash after start with 8.0.0 too (program closed) but I haven't
single time been able to get this particular bug appear with that version.

So it looks like thumbnail view partially becomes visible but some sort of
preview layer stays hanging around but positioned to up at centre frame. All
processes will continue normally (like searching new files) if they were
running but the window/UI is unresponsive.

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

[digikam] [Bug 393382] Add documentation section about the BQM custom shell scripts tool.

2023-08-17 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=393382

--- Comment #20 from Such A Shame  ---
Can't make scripts work without constantly getting "Failed to process item..."
& "Failed to create file..." however occasionally file is there after
refreshing. Applies for both images and sound.

BQM seems to have base tool for cropping but why it's not possible to do
cropping to center as it would possibly be the most likely use case?

There's plenty of very nice tools in this software but these could be made more
intuitive and effective to use.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-09 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #18 from Such A Shame  ---
So far 8.0.0 has been running fine, will continue testing.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #16 from Such A Shame  ---
No, I switched to xfce because of earlier bug and stayed with it.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #14 from Such A Shame  ---
Can't find 8.0.0 here https://download.kde.org/Attic/digikam/

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

[digikam] [Bug 468593] Thumbbar scrolls to 100th image when >100th image is tagged

2023-08-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=468593

--- Comment #8 from Such A Shame  ---
See if this is related https://bugs.kde.org/show_bug.cgi?id=472918 and bug is
not properly fixed or it was deeper than this.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #13 from Such A Shame  ---
Well... now I had it while just browsing pictures at external drive. Didn't yet
open the plugin. It may be that it started with 8.1.0 but it does have some
relation to external drive to make occurences regular.

Actually: this must have been caused by the bug fix
https://bugs.kde.org/show_bug.cgi?id=468593 or what caused that bug in the
first place. There's no other explanation! This dealt with same area already.

I try reverting back to 8.0.0 if I find it if it fixes the problem, unless it
was there already and the problem wasn't just that what was fixed but only part
of it and this larger issue came with 8.0.0 already.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #12 from Such A Shame  ---
I can do just one upload at time and then restart digikam...

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-08 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #11 from Such A Shame  ---
What you said earlier is based in wrong assumption as I've hidden data from
these logs. These lines appear (correctly) multiple times because they're
different locations. They look repeating because I've removed drive names from
the logs and look normal in original log. 

It's evident that these problems occur more (nearly constantly) when I work
with external drive, but that may be eg. because I have so much data there
etc., and as I said earlier I had such occurring also without it connected but
after very long time of use. However this started recently and I don't recall
this occurring other times than while keeping iNaturalist plugin window open.
(Unless it started with 8.1.0 which I updated roughly same time, but I somehow
doubt it. This plugin would be more likely cause?)

Here's end of latest error, just the end of log included:

unknown: Start of Image  ( 1 )
unknown: Miscellaneous marker 0xe1, length 13820  ( 1 )
unknown: Miscellaneous marker 0xe1, length 2556  ( 1 )
unknown: Define Quantization Table 0  precision 0  ( 1 )
unknown: Define Quantization Table 1  precision 0  ( 1 )
unknown: Start Of Frame 0xc0: width=3000, height=4000, components=3  ( 1 )
unknown: Component 1: 1hx2v q=0  ( 1 )
unknown: Component 2: 1hx1v q=1  ( 1 )
unknown: Component 3: 1hx1v q=1  ( 1 )
unknown: Define Huffman Table 0x00  ( 1 )
unknown:   0   1   4   3   1   1   1   1  ( 2 )
unknown:   0   0   0   0   0   0   0   0  ( 2 )
unknown: Define Huffman Table 0x10  ( 1 )
unknown:   0   1   3   3   2   4   5   2  ( 2 )
unknown:   4   4   4   6   1   0   2  19  ( 2 )
unknown: Define Huffman Table 0x01  ( 1 )
unknown:   0   3   1   1   1   1   1   0  ( 2 )
unknown:   0   0   0   0   0   0   0   0  ( 2 )
unknown: Define Huffman Table 0x11  ( 1 )
unknown:   0   2   2   2   2   2   2   1  ( 2 )
unknown:   3   4   2   2   1   1   2  15  ( 2 )
unknown: Start Of Scan: 3 components  ( 1 )
unknown: Component 1: dc=0 ac=0  ( 1 )
unknown: Component 2: dc=1 ac=1  ( 1 )
unknown: Component 3: dc=1 ac=1  ( 1 )
unknown:   Ss=0, Se=63, Ah=0, Al=0  ( 1 )
Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default
sRGB ICC profile.
unknown: End Of Image  ( 1 )
Digikam::TileGrouper::updateClusters: iterating over  142  took  0.00194066 
seconds
Digikam::TileGrouper::updateClusters: "created cluster 0: 4 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 1: 8 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 2: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 3: 4 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 4: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 5: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 6: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 7: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 8: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 9: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 10: 8 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 11: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 12: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 13: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 14: 3 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 15: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 16: 5 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 17: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 18: 4 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 19: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 20: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 21: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 22: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 23: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 24: 1 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 25: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 26: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 27: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 28: 3 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 29: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 30: 2 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 31: 3 tiles"
Digikam::TileGrouper::updateClusters: "created cluster 32: 1 tiles"

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-04 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #10 from Such A Shame  ---
No, it just happened without external drive connected. I have no log for this
occurrence.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-04 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #9 from Such A Shame  ---
Yes, in fact it may be that these problems have occurred only when I have had
external drive connected. However these problems seem to occur only in digikam
and they have started recently, and I still believe they may be related to
inaturalist plugin.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-04 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #7 from Such A Shame  ---
Created attachment 160730
  --> https://bugs.kde.org/attachment.cgi?id=160730=edit
crash

And one complete crash...

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-04 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #6 from Such A Shame  ---
+ please remove the log files / outputs after you have analyzed them

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-04 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #5 from Such A Shame  ---
Created attachment 160728
  --> https://bugs.kde.org/attachment.cgi?id=160728=edit
full log #2

One shorter complete log attached. Digikam was already once crashed already and
after restart did it very soon again. Only the middle frame of the main window
appears to be affected and its possible to add images to iNaturalist plugin
window from elsewhere. After crashing the log did scroll adding more events for
some time before finishing.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-03 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #4 from Such A Shame  ---
Here's end of the log file. There's two mentions of errors and - if related -
there was earlier four times lines

Digikam::PreviewLoadingTask::execute: Preview quality:  2

above, which were now changed to

Digikam::PreviewLoadingTask::execute: Preview quality:  0

below.



unknown: Start of Image  ( 1 )
unknown: Miscellaneous marker 0xe1, length 20988  ( 1 )
unknown: Miscellaneous marker 0xe1, length 3994  ( 1 )
unknown: Miscellaneous marker 0xe2, length 94  ( 1 )
unknown: Define Quantization Table 0  precision 0  ( 1 )
unknown: Define Quantization Table 1  precision 0  ( 1 )
unknown: Start Of Frame 0xc0: width=4608, height=3456, components=3  ( 1 )
unknown: Component 1: 2hx1v q=0  ( 1 )
unknown: Component 2: 1hx1v q=1  ( 1 )
unknown: Component 3: 1hx1v q=1  ( 1 )
unknown: Define Huffman Table 0x00  ( 1 )
unknown:   0   1   5   1   1   1   1   1  ( 2 )
unknown:   1   0   0   0   0   0   0   0  ( 2 )
unknown: Define Huffman Table 0x01  ( 1 )
unknown:   0   3   1   1   1   1   1   1  ( 2 )
unknown:   1   1   1   0   0   0   0   0  ( 2 )
unknown: Define Huffman Table 0x10  ( 1 )
unknown:   0   2   1   3   3   2   4   3  ( 2 )
unknown:   5   5   4   4   0   0   1 125  ( 2 )
unknown: Define Huffman Table 0x11  ( 1 )
unknown:   0   2   1   2   4   4   3   4  ( 2 )
unknown:   7   5   4   4   0   1   2 119  ( 2 )
unknown: Start Of Scan: 3 components  ( 1 )
unknown: Component 1: dc=0 ac=0  ( 1 )
unknown: Component 2: dc=1 ac=1  ( 1 )
unknown: Component 3: dc=1 ac=1  ( 1 )
unknown:   Ss=0, Se=63, Ah=0, Al=0  ( 1 )
Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default
sRGB ICC profile.
unknown: End Of Image  ( 1 )
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  2  CPU core to run
threads
Digikam::ActionThreadBase::run: Action Thread run  2  new jobs
Digikam::DFileOperations::sidecarFiles: Detected a sidecar
"/PATH2/PATHa/PATHj/PATH_1021T160449.JPG.xmp"
Digikam::DFileOperations::sidecarFiles: Detected a sidecar
"/PATH2/PATHa/PATHj/PATH_1021T160457.JPG.xmp"
Digikam::DFileOperations::sidecarFiles: Detected a sidecar
"/PATH2/PATHa/PATHj/PATH_1021T160504.JPG.xmp"
unknown: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14015, resource
id: 23727813, major code: 40 (TranslateCoords), minor code: 0
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::IOJobsThread::slotOneJobFinished: Thread Finished
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Finish Main Thread
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  2  CPU core to run
threads
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
Digikam::ItemQueryBuilder::buildQueryFromXml: " ( ( 
ImagePositions.LongitudeNumber > ? AND ImagePositions.LatitudeNumber < ?  AND
ImagePositions.LongitudeNumber < ? AND ImagePositions.LatitudeNumber > ?  ) ) "
Digikam::ItemLister::listSearch: Search query:
 "SELECT DISTINCT Images.id, Images.name, Images.album,   
Albums.albumRoot,ImageInformation.rating, Images.category,   
ImageInformation.format, ImageInformation.creationDate,   
Images.modificationDate, Images.fileSize,ImageInformation.width,
ImageInformation.height,ImagePositions.latitudeNumber,
ImagePositions.longitudeNumber  FROM ImagesLEFT JOIN ImageInformation
ON Images.id=ImageInformation.imageidLEFT JOIN ImageMetadataON
Images.id=ImageMetadata.imageidLEFT JOIN VideoMetadataON
Images.id=VideoMetadata.imageidLEFT JOIN ImagePositions   ON
Images.id=ImagePositions.imageidLEFT JOIN ImageProperties  ON
Images.id=ImageProperties.imageidINNER JOIN Albums  ON
Albums.id=Images.album WHERE Images.status=1 AND (  ( ( 
ImagePositions.LongitudeNumber > ? AND ImagePositions.LatitudeNumber < ?  AND
ImagePositions.LongitudeNumber < ? AND ImagePositions.LatitudeNumber > ?  ) ) 
);" 
 (QVariant(double, PATH1), QVariant(double, PATH2), QVariant(double, PATH3),
QVariant(double, PATH4))
Digikam::ItemLister::listSearch: Search result: 1320
Digikam::ActionThreadBase::cancel: Cancel Main Thread
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Finish Main Thread
Digikam::DMetadata::loadUsingFFmpeg: Parse metadada with FFMpeg:
"/PATH2/PATHa/PATHh/PATH_0728T191353.MP3"
QtAV::qtav_ffmpeg_log_callback: [FFmpeg:mp3] Estimating duration from bitrate,
this may be inaccurate
Digikam::DMetadata::loadUsingFFmpeg: -- FFMpeg audio stream metadata entries :
Digikam::DMetadata::loadUsingFFmpeg: QMap()
Digikam::DMetadata::loadUsingFFmpeg: -
Digikam::DMetadata::loadUsingFFmpeg: -- FFMpeg root container metadata entri

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-02 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

--- Comment #2 from Such A Shame  ---
Occurs also in Thumbnails mode trying to double click image to preview.
Thumbnails become locked, scrollbar moves but doesn't scroll images and there's
line at bottom half to show border of expected preview window (however it
should be there but top half). iNat plugin open at background.

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

[digikam] [Bug 472918] Preview mode becomes unresponsive

2023-08-02 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

Such A Shame  changed:

   What|Removed |Added

Version|8.2.0   |8.1.0

--- Comment #1 from Such A Shame  ---
sry 8.0.0 -> 8.1.0

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

[digikam] [Bug 472918] New: Preview mode becomes unresponsive

2023-08-02 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=472918

Bug ID: 472918
   Summary: Preview mode becomes unresponsive
Classification: Applications
   Product: digikam
   Version: 8.2.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: myaccount...@protonmail.com
  Target Milestone: ---

Preview mode shifts preview and thumnail locations abruptly (from up to down
and vice versa) and becomes unresponsive (*possibly* at time when hitting ESC
to return to thumbnails). Program has to be restarted to get rid of it but now
it keeps coming back very soon after restarting.

This has appeared frequently after switching from appimage 8.1.0 to 8.2.0. OR
after starting to use iNaturalist export plugin (which view has different and
not fatal UI unresponsiveness too).

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

[digikam] [Bug 471492] Scripts in context menu

2023-07-30 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=471492

--- Comment #13 from Such A Shame  ---
Converted file was actually found from directory as

BatchTool-smFwpk-f6181d32.digikamtempfile.MTS.m4a

but for some reason doesn't appear at digikam. If I manually rename it, it will
show after refreshing.

If I change code to

ffmpeg -i $INPUT -vn -c:a copy $INPUT.m4a

file has correct name but same error messages appear and view has to manually
refreshed to make the file show. Also database is not updated (tags and
locations are not given to new files).

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

[digikam] [Bug 471492] Scripts in context menu

2023-07-29 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=471492

Such A Shame  changed:

   What|Removed |Added

Version|8.0.0   |8.2.0

--- Comment #12 from Such A Shame  ---
Is it possible to run BQM only for image files? I've tried to run it for sound
and video, but for example separating audio from video with:

ffmpeg -i $INPUT -vn -c:a copy $OUTPUT.m4a

gives

ORIGINALFILENAME ...Failed to process item...
ORIGINALFILENAME ...Failed to save item...

There actually seems to be many places where to adjust filenames: i) Queue
settings -> Behavior, ii) Tool settings -> Output file type,iii) and possibly
within code too??

#2) I tried to install digikam source code via kdesrc-build but some dependency
couldn't be installed (and installer for some reason tries to use home
directory where I don't have enough space). Completely different guide at
https://www.digikam.org/api/ appears to have some presuppositions I don't
understand. There's also another plugin I would like to see if it could be
improved.

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

[digikam] [Bug 471492] Scripts in context menu

2023-07-23 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=471492

--- Comment #11 from Such A Shame  ---
I was able to find source code locations

digikam / core / app / items / utils / contextmenuhelper.h/cpp
digikam / core / dplugins / bqm

First supposedly has enough examples to create proper context menu item. 

Latter possibly has needed functionality i) to list all workflows* in context
menu and then ii) method to call to execute for selected items? 

*However I think some of these commands could be even built in (not user
scripts) so I think possibly all precoded functionality ("plugins") could be
made (safe way) directly available via context menu.

I could possibly try to figure out how to get either of this (user sripts
and/or plugins added directly to context menu) done in C++.

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

[digikam] [Bug 471492] Scripts in context menu

2023-07-15 Thread Such A Shame
https://bugs.kde.org/show_bug.cgi?id=471492

--- Comment #10 from Such A Shame  ---
For repeated tasks there's just too much unnecessary clicking when you have to
use separate window, including selecting background window, switching control
panel tabs and emptying the queue. (You can't even click-by-click remove single
items from queue in cases that would be faster, but you have to select next
file after deleting previous...) To some extent would be helpful even if the
queue could be set to automatically emptied after running.

However context menu integration would be the easiest way to handle this kind
of extra automation which wouldn't need to be included to actual tool/manager
itself. I'm quite sure this feature could be implemented with rather small
amount of code calling existing methods the way that they're run together
without further interaction during the whole process after selecting items and
executing command from context menu.

i) transmit list of selected items to this pipe
ii) apply desired command to them
iii) reset feature (remove queue and possibly command it it's left preset)
iv) end

It's already possible to close the bqm window during process and see the
progress bar at main window status bar, so no window need to be opened at all.
So part of the problem is that whatever was done is left to bqm if reopened and
causes hazzle to run even same commands to different files, and running them
could have easier method/alternative in the first place.

Tool itself is very nice, including how database is maintained both in
replacing and creating new files. I've yet to experiment running multiple
commands at once.

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