New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are video files supported? #31
Comments
Video support is currently a bit experimental. The Exiv2 metadata library can optionally be compiled with video support - I've tried this on a Linux machine and it crashed when opening video files. On Windows I just use the ready built version from https://sourceforge.net/projects/pygobjectwin32/. I've not tested this with video files, but will have a go later today. |
Running Photini from a Windows 7 command window (see http://photini.readthedocs.io/en/latest/other/installation.html#troubleshooting) I get this when I open a video file:
It appears this is a C++ exception that is not being caught in Python, where I could do something about it. I'll investigate further. |
I've found a workaround. Using the 'pgi' Python interface to GObject instead of the 'PyGObject' interface avoids the problematic library function. You can test this by opening a command window (as in the 'troubleshooting' documentation mentioned above) and installing pgi:
Do let me know if this works for you, and if you run into any other problems. Photini's support for video files will be minimal, as the installed version of the Exiv2 library doesn't handle them. I hope to improve this in future. |
I've managed to build and install GExiv2 on my main Linux box so it doesn't crash now. Exiv2 can't write to video files as far as I can tell, so all new/changed metadata has to be stored in sidecar files. The data fields are very different to still images, so there's some work in getting Photini to read them. There's also a lack of consistency between camera makers, e.g. time stamps relative to 1970 vs 1904. |
Thanks a lot for your detailed answers. When I open Photini from the Windows 10 command prompt as per the troubleshooting documentation, I get a different error:
The file I am opening is an If I install pgi from the command prompt, I am indeed able to open the video file in photini. It has no thumbnail. I successfully added a title to it and an XMP sidecar file was created. I didn't test further, in what sense is video support "minimal" ? |
I've written some documentation about video support in the current development version of Photini: http://photini.readthedocs.io/en/latest/manual/video.html |
I see. I think the windows version with pgi will be good enough for me, but I'm not sure whether you want to close the issue since you added a the "bug" label so I prefer to leave that up to you. Thanks again. |
I need to make sure I include pgi in the next Windows installer release. I'm currently having problems with the exiv2 library crashing if I do anything with an XMP namespace it doesn't know about. I may end up trying to compile my own copies of gexiv2 and exiv2 with video support. There's a bit of a learning curve before I get there though. |
Today I've succeeded in building exiv2 on Windows using MinGW. I have an executable exiv2.exe that can be run from a Windows command shell and reads video files. |
Release 2017.8.0 includes a Windows installer that has video support. As well as reading metadata from video files it can read image data to generate a thumbnail. (The extra libraries required have doubled the size of the installer though.) |
This is great news! I'm on a bad internet connection currently and unable to download the installer, but I will try the new version ASAP. |
Just tried and it is working as expected. Thanks a lot! |
Hello,
I see in the changelog "started adding support for video files", and that the Open Images dialog offers to select video files. But Photini crashes ("pythonw.exe has stopped working") as soon as I open a video file. I am using the latest version 2017.6.0 windows installer on Windows 10. I have tried with several AVI and MP4 videos.
So I wonder if perhaps video support is not complete yet? Or a specific issue with the Windows version? Or is it supposed to work and perhaps something wrong on my machine?
Thanks in advance.
The text was updated successfully, but these errors were encountered: