Hello, I am really enjoying that digikam can now play video files but mine usually lags for 2-3 seconds in the beginning of each video. Every mp4 file starts in slow motion for me.
Can you download QtAV for windows and look if problem is the same. QtAV framework is used inside digiKam to play video. http://www.qtav.org/ Gilles Caulier
I see the same 2-3 second lag at the beginning of videos on Win7 but I do not see it on Win10. Both using digiKam 5.4.0 Also, in Win7, the video repeatedly plays the last 0.25 second of audio when it hits the end of the video. No way to stop the sound repeating. The same repeating sound happens if the video is paused in the middle. In Win10, the current time indicator at the bottom of the preview window keeps counting when the video reaches the end. This does not happen in Win7. I will try to install the QtAV framework and see if it has the same behavior.
I installed QtAV1.11.0-VS2013x86.exe on Win7 and do not see the initial lag problem using QtAV.Player. I also do not see the issue with audio repeating endlessly when the video is stopped in Win7. No testing done on Win10.
I think the big difference between digiKam fopr Window and QtAV player is the way to compile source code. digiKam use MXE crosss compiler, QtAV M$ Visual C++ (i think). So the optimizations can be very different, about DirectX for ex. Note : under MacOS and Linux, DK do not have this kind of latency problem. Gilles Caulier
I just installed QtAV on my Windows 10 but it did not change much. I am okay with the latency issue but the fact that QtAV does not see the rotation flag is annoying. I guess I will be pressing F4 instead of double clicking on mp4 files for now.
Note : about rotation, Video digiKam preview permit to rotate media with left mouse button over canvas. Gilles Caulier
I get a slideshow instead of a video preview on digiKam 5.4.0 on linux Mint 18.1 KDE. There is no sound either.
Looks like the output depends on the codec. Videos straight out of phone just lag in the beginning, videos compressed using ffmpeg are slideshows (very very slow)
(In reply to wildcowboy from comment #8) > Looks like the output depends on the codec. Videos straight out of phone > just lag in the beginning, videos compressed using ffmpeg are slideshows > (very very slow) Replying to my own comment. Now it looks like I have no lags with videos created by ffmpeg but there is a lag with videos created by phone/camera
I updated all DK 5.5.0 Bundle as pre-version release using last implementation from QtAV. Files are here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Can you test to see if problem still there ? Thanks in advance... Gilles Caulier
The lag can be also due to non OpenGL video widget used in digiKam. I used a simple widget, not based on OpenGL to not depend on it with video support. This is of course not optimum. The question is : the QtAV open GL widget will have low performnce if OpenGL is not available on client computer ? AppImage bundle do not know the target computer feature. OpenGL can be not available. If it's the case, the whish is to see QtAv video widget switching in decrease mode, typically in simple widget rendering. So QtAv openGL widget is adaptive with hardware ? Gilles Caulier
(In reply to caulier.gilles from comment #10) > I updated all DK 5.5.0 Bundle as pre-version release using last > implementation from QtAV. Files are here : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Can you test to see if problem still there ? Thanks in advance... > > Gilles Caulier Nothing changed on Linux Mint. Here is a screen cast: https://youtu.be/nqG9KZt8f9k This record actually looks worse than it is but that 1-2-3 latency in the beginning of the video looks realistic.
The lag seems to be gone on my Windows 7 system. There is a 1-2 second delay the first time I play a video, but then the video plays correctly from the beginning. I think that previously it was advancing through the movie during that time without correctly showing video. And it seems that after the first play, on subsequent plays the video shows with no initial delay at all, like something is being cached somewhere. This seems to be true even if I exit digiKam and restart it. More good news: the extremely annoying repeat of audio at the end of playing a movie also seems to be fixed. Bad news: In preview, switching from one video to another while the first video is playing causes the media player to report an error and no video is shown.
I posted an UPSTREAM report to QtAV team : https://github.com/wang-bin/QtAV/issues/835 Gilles Caulier
We need debug statements printed on the console when a video is played in digiKam. For Linux, just run digiKam from a terminal. For Windows, you need to install debugview program and run digiKam. debugview will capture all debug statements from digiKam. See this page for details : https://www.digikam.org/contrib Gilles Caulier
Created attachment 104518 [details] Screenshot of video switch failure Screenshot of DebugView log during video switch failure.
There is nothing about video player. Can you share the full debug trace from the beginning of digiKam ? Gilles Caulier
Created attachment 104519 [details] DebugView log of video switch failure 1: Launch digiKam 276: Open preview of first video 283: Switch to second video
I added a lengthy comment previously, but it seems to have disappeared. What I observe is that when a video is started in Preview, it plays normally. If I switch to a second video while the first is playing, I can hear the second video playing but there is no image. Only the message "An error has occurred with the media player...". If I wait until the audio stops and select another video, it plays properly. I don't think this was happening in the digiKam 5.5 version I downloaded on Feb 13.
Hum, There is nothing about usual printed information from QtAV player embedded in digiKam. Only debug trace from digiKam wrapped in debug log are visible. QtAV do not use it. What's happen if you run digikam.exe from the Windows terminal (cmd) ? There are more information printed. Typically under Linux all debug traces appears in the console. Gilles Caulier
When run from a console, it appears that control is immediately returned to the user, i.e. there is a console prompt. digiKam does not output any information at all. I looked in the Windows event viewer but did not find anything that seemed to be relevant to digiKam, QtAV or QT. Is the error message displayed by digiKam or by QtAV? Are you using a different version of QtAV now than what was used on Feb 13?
Git commit f28dc8392fc109bea86559caa84508fe5a04c64e by Maik Qualmann. Committed on 12/03/2017 at 18:37. Pushed by mqualmann into branch 'master'. add debug message for media player status M +1 -0 app/views/mediaplayerview.cpp https://commits.kde.org/digikam/f28dc8392fc109bea86559caa84508fe5a04c64e
I just reinstalled digiKam 5.5 (11 Feb 2017). It does not have a problem with switching videos while one is playing.
(In reply to caulier.gilles from comment #15) > We need debug statements printed on the console when a video is played in > digiKam. For Linux, just run digiKam from a terminal. > > For Windows, you need to install debugview program and run digiKam. > debugview will capture all debug statements from digiKam. See this page for > details : > > https://www.digikam.org/contrib > > Gilles Caulier -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options Starting digiKam into GDB... Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q' command to quit debugger session. GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam...done. Catchpoint 1 (throw) Starting program: /tmp/.mount_I0blN4/usr/bin/digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe78e2700 (LWP 4706)] digikam.widgets: Breeze icons ressource file found digikam.general: AlbumWatch use QFileSystemWatcher [New Thread 0x7fffe5ffd700 (LWP 4707)] [New Thread 0x7fffe57fc700 (LWP 4708)] digikam.general: Database Parameters: Type: "QSQLITE" DB Core Name: "/media/data/FamilyPictures/digikam4.db" DB Thumbs Name: "/media/data/FamilyPictures/thumbnails-digikam.db" DB Face Name: "/media/data/FamilyPictures/recognition.db" Connect Options: "" Host Name: "" Host port: -1 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "" Password: "" [New Thread 0x7fffe4ffb700 (LWP 4709)] [Thread 0x7fffe4ffb700 (LWP 4709) exited] digikam.dbengine: Loading SQL code from config file "/tmp/.mount_I0blN4/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 8 digikam.coredb: Core database: makeUpdates 8 to 8 digikam.database: Creating new Location "/FamilyPictures" uuid "volumeid:?uuid=e0deb5d0deb59eea" digikam.database: location for "/media/data/FamilyPictures" is available true KMemoryInfo: Platform identified : "LINUX" KMemoryInfo: TotalRam: 8244797440 digikam.general: Allowing a cache size of 200 MB digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0 digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0 digikam.thumbsdb: Thumbs database: have a structure version "3" digikam.general: Thumbnails database ready for use digikam.general: Switch to widget style: "Fusion" digikam.dimg: ("/usr/share/color/icc", "/home/andrey/.local/share/icc") [New Thread 0x7fffe4ffb700 (LWP 4715)] digikam.general: Camera XML data: "/home/andrey/.local/share/digikam/cameras.xml" [New Thread 0x7fffd5f9d700 (LWP 4716)] [New Thread 0x7fffd579c700 (LWP 4717)] [New Thread 0x7fffd4f9b700 (LWP 4718)] digikam.facedb: FaceDB SelectFaceSetting val ret = 0 digikam.facedb: FaceDB SelectFaceSetting val ret = 0 digikam.facedb: Face database: have a structure version "2" digikam.facesengine: Face database ready for use [New Thread 0x7fffc3fff700 (LWP 4719)] [New Thread 0x7fffc37fe700 (LWP 4720)] digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer [New Thread 0x7fffc2ffd700 (LWP 4721)] [New Thread 0x7fffc27fc700 (LWP 4722)] [New Thread 0x7fffc1ffb700 (LWP 4723)] [New Thread 0x7fffc17fa700 (LWP 4724)] [New Thread 0x7fffc0ff9700 (LWP 4725)] digikam.facesengine: Face database ready for use [New Thread 0x7fffa3fff700 (LWP 4726)] [New Thread 0x7fffa37fe700 (LWP 4727)] digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer [New Thread 0x7fffa2ffd700 (LWP 4728)] [New Thread 0x7fffa27fc700 (LWP 4729)] [New Thread 0x7fffa1ffb700 (LWP 4730)] [New Thread 0x7fffa17fa700 (LWP 4731)] digikam.geoiface: "setting backend marble" QtAV 1.11.0(Mar 9 2017, 11:27:18) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai University->S3 Graphics->Deepin, Shanghai, ChinaCopyright (C) 2012-2016 Wang Bin (aka. Lucas Wang) wbsecg1@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org capi::version: 0.6.0 [New Thread 0x7fffa0ff9700 (LWP 4732)] [Thread 0x7fffa0ff9700 (LWP 4732) exited] [New Thread 0x7fffa0ff9700 (LWP 4733)] [Thread 0x7fffa0ff9700 (LWP 4733) exited] [New Thread 0x7fffa0ff9700 (LWP 4734)] [New Thread 0x7fffd4551700 (LWP 4735)] digikam.general: AudioOutput backends: ("OpenAL", "null") digikam.general: Stacked View Mode : 0 [New Thread 0x7fff53ffd700 (LWP 4736)] [New Thread 0x7fff537fc700 (LWP 4737)] digikam.geoiface: "setting backend marble" [New Thread 0x7fff52ffb700 (LWP 4738)] digikam.general: "browse_album" digikam.general: "browse_tag" digikam.general: "browse_labels" digikam.general: "browse_date" digikam.general: "browse_timeline" digikam.general: "browse_search" digikam.general: "browse_fuzzysearch" digikam.general: "browse_gpssearch" digikam.general: "browse_people" [New Thread 0x7fff527fa700 (LWP 4739)] [New Thread 0x7fff51ff9700 (LWP 4740)] [New Thread 0x7fff517f8700 (LWP 4741)] [New Thread 0x7fff50ff7700 (LWP 4742)] [New Thread 0x7fff3fffe700 (LWP 4743)] digikam.widgets: Paths to color scheme : ("/tmp/.mount_I0blN4/usr/share/digikam/colorschemes") digikam.widgets: "Breeze" :: "" digikam.widgets: "LowKey" :: "/tmp/.mount_I0blN4/usr/share/digikam/colorschemes/lowkey.colors" QFSFileEngine::open: No file name specified digikam.dimg: Root lens database dir: "/tmp/.mount_I0blN4/usr/share/lensfun" digikam.dimg: Load lens database file: "6x6.xml" digikam.dimg: Load lens database file: "actioncams.xml" digikam.dimg: Load lens database file: "compact-canon.xml" digikam.dimg: Load lens database file: "compact-casio.xml" digikam.dimg: Load lens database file: "compact-fujifilm.xml" digikam.dimg: Load lens database file: "compact-kodak.xml" digikam.dimg: Load lens database file: "compact-konica-minolta.xml" digikam.dimg: Load lens database file: "compact-leica.xml" digikam.dimg: Load lens database file: "compact-nikon.xml" digikam.dimg: Load lens database file: "compact-olympus.xml" digikam.dimg: Load lens database file: "compact-panasonic.xml" digikam.dimg: Load lens database file: "compact-pentax.xml" digikam.dimg: Load lens database file: "compact-ricoh.xml" digikam.dimg: Load lens database file: "compact-samsung.xml" digikam.dimg: Load lens database file: "compact-sigma.xml" digikam.dimg: Load lens database file: "compact-sony.xml" digikam.dimg: Load lens database file: "contax.xml" digikam.dimg: Load lens database file: "generic.xml" digikam.dimg: Load lens database file: "mil-canon.xml" digikam.dimg: Load lens database file: "mil-fujifilm.xml" digikam.dimg: Load lens database file: "mil-nikon.xml" digikam.dimg: Load lens database file: "mil-olympus.xml" digikam.dimg: Load lens database file: "mil-panasonic.xml" digikam.dimg: Load lens database file: "mil-pentax.xml" digikam.dimg: Load lens database file: "mil-samsung.xml" digikam.dimg: Load lens database file: "mil-samyang.xml" digikam.dimg: Load lens database file: "mil-sigma.xml" digikam.dimg: Load lens database file: "mil-sony.xml" digikam.dimg: Load lens database file: "mil-tamron.xml" digikam.dimg: Load lens database file: "mil-zeiss.xml" digikam.dimg: Load lens database file: "misc.xml" digikam.dimg: Load lens database file: "rf-leica.xml" digikam.dimg: Load lens database file: "slr-canon.xml" digikam.dimg: Load lens database file: "slr-hasselblad.xml" digikam.dimg: Load lens database file: "slr-konica-minolta.xml" digikam.dimg: Load lens database file: "slr-leica.xml" digikam.dimg: Load lens database file: "slr-nikon.xml" digikam.dimg: Load lens database file: "slr-olympus.xml" digikam.dimg: Load lens database file: "slr-panasonic.xml" digikam.dimg: Load lens database file: "slr-pentax.xml" digikam.dimg: Load lens database file: "slr-ricoh.xml" digikam.dimg: Load lens database file: "slr-samsung.xml" digikam.dimg: Load lens database file: "slr-samyang.xml" digikam.dimg: Load lens database file: "slr-schneider.xml" digikam.dimg: Load lens database file: "slr-sigma.xml" digikam.dimg: Load lens database file: "slr-soligor.xml" digikam.dimg: Load lens database file: "slr-sony.xml" digikam.dimg: Load lens database file: "slr-tamron.xml" digikam.dimg: Load lens database file: "slr-tokina.xml" digikam.dimg: Load lens database file: "slr-ussr.xml" digikam.dimg: Load lens database file: "slr-vivitar.xml" digikam.dimg: Load lens database file: "slr-zeiss.xml" digikam.dimg: variant: QVariant(Digikam::LensFunIface::DevicePtr, ) digikam.dimg: dev: AEE :: AEE DV :: 6 digikam.dimg: Search for camera "" - "" ==> false digikam.dimg: Search for lens "" ==> false digikam.dimg: updating data [New Thread 0x7fff3eded700 (LWP 4744)] [New Thread 0x7fff3e5ec700 (LWP 4745)] [New Thread 0x7fff3ddeb700 (LWP 4746)] [New Thread 0x7fff3d5ea700 (LWP 4747)] [New Thread 0x7fff3cde9700 (LWP 4748)] [New Thread 0x7fff0ffff700 (LWP 4749)] [New Thread 0x7fff0f7fe700 (LWP 4750)] [New Thread 0x7fff0effd700 (LWP 4751)] [New Thread 0x7fff0e7fc700 (LWP 4752)] [New Thread 0x7fff0dffb700 (LWP 4753)] [New Thread 0x7fff0d7fa700 (LWP 4754)] [New Thread 0x7fff0cff9700 (LWP 4755)] [New Thread 0x7fff0c7f8700 (LWP 4756)] [New Thread 0x7fff0bff7700 (LWP 4757)] [New Thread 0x7fff0b7f6700 (LWP 4758)] [New Thread 0x7fff0aff5700 (LWP 4759)] [New Thread 0x7fff0a7f4700 (LWP 4760)] [New Thread 0x7fff09ff3700 (LWP 4761)] [New Thread 0x7fff097f2700 (LWP 4762)] [New Thread 0x7fff08ff1700 (LWP 4763)] [New Thread 0x7fff087f0700 (LWP 4764)] [New Thread 0x7fff07fef700 (LWP 4765)] [New Thread 0x7fff077ee700 (LWP 4766)] [New Thread 0x7fff06fed700 (LWP 4767)] [New Thread 0x7fff067ec700 (LWP 4768)] [New Thread 0x7fff05feb700 (LWP 4769)] [New Thread 0x7fff057ea700 (LWP 4770)] [New Thread 0x7fff04fe9700 (LWP 4771)] [New Thread 0x7fff047e8700 (LWP 4772)] digikam.dimg: updating data digikam.general: Using 4 CPU core to run threads digikam.general: new search text settings: "" : hasResult = false , validRows = 0 QFSFileEngine::open: No file name specified digikam.geoiface: ---- digikam.geoiface: ---- digikam.general: Added root album called: "FamilyPictures" digikam.general: Using 4 CPU core to run threads [New Thread 0x7fff03fe7700 (LWP 4774)] digikam.general: Action Thread run 1 new jobs digikam.geoiface: ---- digikam.geoiface: ---- digikam.general: Using 4 CPU core to run threads [New Thread 0x7fff037e6700 (LWP 4775)] digikam.general: Action Thread run 1 new jobs digikam.geoiface: ---- digikam.general: Cancel Main Thread digikam.geoiface: ---- digikam.general: Using 4 CPU core to run threads [Thread 0x7fff037e6700 (LWP 4775) exited] [New Thread 0x7fff037e6700 (LWP 4776)] digikam.general: Action Thread run 1 new jobs digikam.geoiface: "ROADMAP" digikam.geoiface: "setting backend googlemaps" digikam.geoiface: "ROADMAP" digikam.geoiface: "setting backend googlemaps" digikam.geoiface: "ROADMAP" digikam.geoiface: ---- digikam.general: Cancel Main Thread digikam.geoiface: ---- [Thread 0x7fff037e6700 (LWP 4776) exited] digikam.general: Using 4 CPU core to run threads [New Thread 0x7fff037e6700 (LWP 4777)] digikam.general: Action Thread run 1 new jobs digikam.geoiface: "ROADMAP" digikam.geoiface: ---- digikam.general: One job is done digikam.general: One job is done [Thread 0x7fff03fe7700 (LWP 4774) exited] digikam.general: One job is done digikam.general: Cancel Main Thread digikam.general: One job is done [Thread 0x7fff037e6700 (LWP 4777) exited] digikam.geoiface: ---- Recreating ksycoca file ("/home/andrey/.cache/ksycoca5_en-CA_kLyNrzGExf2ZjhzlV80KypOnyI8=", version 303) Menu "applications.menu" not found. "applications.menu" not found in ("/home/andrey/.config/menus", "/etc/xdg/menus") Saving kipi.plugins: Plugin_Flickr plugin loaded kipi.library: UI file : "/tmp/.mount_I0blN4/usr/share/kxmlgui5/kipi/kipiplugin_flickrui.rc" kipi.library: Loaded plugin "Flickr" kipi.plugins: Plugin_GoogleServices Plugin Loaded kipi.library: UI file : "/tmp/.mount_I0blN4/usr/share/kxmlgui5/kipi/kipiplugin_googleservicesui.rc" kipi.library: Loaded plugin "Google Services" kipi.plugins: Plugin_PrintImages plugin loaded kipi.library: UI file : "/tmp/.mount_I0blN4/usr/share/kxmlgui5/kipi/kipiplugin_printimagesui.rc" kipi.library: Loaded plugin "PrintImages" kipi.plugins: Plugin_SendImages plugin loaded kipi.library: UI file : "/tmp/.mount_I0blN4/usr/share/kxmlgui5/kipi/kipiplugin_sendimagesui.rc" kipi.library: Loaded plugin "SendImages" digikam.geoiface: ---- [New Thread 0x7fff037e6700 (LWP 4779)] QFSFileEngine::open: No file name specified digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" [New Thread 0x7fff03fe7700 (LWP 4780)] [New Thread 0x7fff02942700 (LWP 4781)] [New Thread 0x7fff02141700 (LWP 4782)] [New Thread 0x7fff01940700 (LWP 4783)] digikam.facesengine: Face database ready for use [New Thread 0x7fff0113f700 (LWP 4784)] [New Thread 0x7fff0093e700 (LWP 4785)] digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer [New Thread 0x7fff0013d700 (LWP 4786)] [New Thread 0x7ffeff93c700 (LWP 4787)] [New Thread 0x7ffeff13b700 (LWP 4788)] digikam.facesengine: Face database ready for use [New Thread 0x7ffefe93a700 (LWP 4789)] [New Thread 0x7ffefe139700 (LWP 4790)] digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer [New Thread 0x7ffefd938700 (LWP 4791)] QFSFileEngine::open: No file name specified digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.widgets: TURN ON fullscreen digikam.general: Stacked View Mode : 0 digikam.general: scan mode: ScanDeferredFiles digikam.general: total scan value : 28661 digikam.widgets: TURN OFF fullscreen digikam.general: Stacked View Mode : 0 digikam.widgets: TURN ON fullscreen digikam.general: Stacked View Mode : 0 digikam.database: items to tag () digikam.database: Complete scan took: 6696 msecs. digikam.general: Event is dispatched to desktop notifier through DBUS
Maik, Look the upstream response from QtAV team : https://github.com/wang-bin/QtAV/issues/835#issuecomment-286328343 Gilles
Git commit aa08f547c7c5ad421c26bcbe84889560d2c33799 by Maik Qualmann. Committed on 15/03/2017 at 20:25. Pushed by mqualmann into branch 'master'. check MediaStatus only on QtAV::InvalidMedia M +1 -5 app/views/mediaplayerview.cpp M +1 -4 utilities/presentation/audio/presentationaudiolist.cpp M +1 -4 utilities/presentation/audio/presentationaudiowidget.cpp https://commits.kde.org/digikam/aa08f547c7c5ad421c26bcbe84889560d2c33799
Git commit e21886dc5c22d4f6bbbb7fae77067fa7442d9821 by Maik Qualmann. Committed on 15/03/2017 at 21:30. Pushed by mqualmann into branch 'master'. check MediaStatus only on QtAV::InvalidMedia also in the slideshow M +0 -3 utilities/slideshow/slidevideo.cpp https://commits.kde.org/digikam/e21886dc5c22d4f6bbbb7fae77067fa7442d9821
This is still happening in appimage 5.6.0 on OpenSUSE. - Videos lag in the beginning. - Sometimes I see black screen when switch to next video using Previous/Next buttons or shortcuts. I hear the sound though.
This problem still reproducible with current 5.8.0 - pre-release Windows bundle available here : https://files.kde.org/digikam/ Gilles Caulier
(In reply to caulier.gilles from comment #29) > This problem still reproducible with current 5.8.0 - pre-release Windows > bundle > available here : > > https://files.kde.org/digikam/ > > Gilles Caulier I get no lag in Windows 10 but still get the problem reported by Bill. A video (MPEG4) stops playing but the counter keeps ticking away as if the end of the video is not recognised. Subsequently the pause symbol is continuously displayed and you cannot play the video from the start. Video attached.
Created attachment 109369 [details] Sample video.
The lag is one problem so fixed with 5.8.0. The H264 support is another one, depending of FFmpeg codecs installed in Windows bundle, through MXE package (3.4 version with specific compilation rules about codecs support). So the bundle packaging must be customized to support better H264 and H265 video. This is relevant of this bug : https://bugs.kde.org/show_bug.cgi?id=384807 Note : event is #384807 talk about Linux AppImage bundle, this also true to support better last ffmpeg codecs under MacOS and Windows. So i close this file now. Please continue this thread in #384807 Gilles Caulier
I still observe this issue on my setup with Digikam 5.9.0 on openSUSE Leap 15 (also on previous versions) I've posted more details here: https://github.com/wang-bin/QtAV/issues/835#issuecomment-395199524 If you think this is a different issue please let me know and I'll create a new report
See my comment on github file... Gilles Caulier
I do not think we implemented something wrong in digiKam. Here are a few videos that do not always start from the beginning, sometimes it takes several seconds to get the video image. However, I can reproduce the behavior just as synonymous under the QtAV player. Here also openSUSE. Maik
Sometimes I see black screen instead of the videos in my collection. Usually swtiching to previous/next file helps though. Just saying...
After one of the last updates of openSUSE Tumbleweed to Qt-5.11 and update of the QtAV packages, the problem no longer occurs. Maik