balintlaczko
commented
4 years ago Hmm that is strange. I can gladly step by and see, otherwise, you can maybe clone the repo and just run the patch (not the standalone app) and see the max console there. The fact that it gets the dim and the frame count means that there are probably no path issues, it manages to read the file. What you can try is:
- after the video is loaded, move the playhead and see if that causes the preview to update
- use Shift + left or Shift + Right to step through frames (or use the little arrows on the UI under the play button)
- in case the video file itself is not located on the same drive as the VideoAnalysis app, try to move the video there and see if it likes that more
I don't know of any external dependencies, everything should be packaged in /VideoAnalysis/resources/support and /VideoAnalysis/packages/VIDDLL/support. Could be that the system somehow refuses to use any dll files which are not in /windows/system32 but that used to be a problem on Windows XP (and maybe 7). Like I said, I can pay a visit and see it for myself too. :)
alexarje
I just tried running VideoAnalysis on a UiO server (VDI) with Windows 10 Enterprise. The program starts up as expected. When I load a video file the app detects the size and number of frames, but it does not show the preview image. It also chokes when trying to start the analysis. Tried with both avi and mp4 files, and these files run nicely on the system (in windows media player and VLC). Since the Max window is not present, I cannot see any error messages.
Any thoughts on how to proceed with figuring out the problem? Any dependencies that are required?