-
Notifications
You must be signed in to change notification settings - Fork 63
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
Video downloader #303
Video downloader #303
Conversation
makes no difference anyway; issue with subprocesses/ffmpeg not unzipping process.
DOES NOT WORK DUE TO CURRENT ffmpeg/subprocess issue
Even more confusion. I made a simple bash script wrapper.
I can run that with expected variables and get a good result. But not when 4CAT runs it. I can hardcode the unzipped videos and have 4CAT use them as parameters and still get the same NAL unit errors resulting in return code 69.
While I can literally open up python3
Return code 0 and good results. Clearly I've lost my mind. |
I've no idea. The video_frames processor refuses to work even if I extract videos myself and just feed it that directory. I made a simple |
Thinking specifically about the |
there??), update description
Currently the videohash library will not work with 4CAT due to the |
OK, I've tested this and I think it's mostly ready for merging (aside from the hash processor). The migrate script can install ffmpeg in existing Docker containers, I haven't tested other options very extensively. Let's take a last look after the winter break. |
Ok. I haven’t looked through all your commits and must have missed commenting earlier, but I had added my working videohash library to setup.py already so there shouldn’t be any issue there with that processor either manual install or Docker. Also Docker setup was already updated to install ffmpeg, the only issue was needing an additional step with a manual install which could have been solved with first run. Adding it to the newest migrate makes sense for upgrades. |
noticed some processors (that used iterate_archive_contents were not removing staging areas if one was provided
This is a proxy check since we are using the .env file copied into the Docker container. It will always be the version used to create the Docker container, but if a user already updated the .env file and for some reason has not yet used that .env file to create the 4CAT container, this message would still appear.
I see that the |
had a set where the last timeline was the widest and the canvas was being cut short. Still seems that if the last is the widest, the thumbnails layer on top of "made with 4CAT".
last commit fixes issue with timelines, but the "made with 4CAT" is overwritten if the last timeline is the full width of the canvas. |
The only part that currently works without issue is the video downloader.
Right now, I am stuck on an issue with
ffmpeg
which is annoyingly the basis of a very different processors. It seems that when runningffmpeg
as a python subprocess, it produces errors such as the following:Eventually ending as such:
As far as I can tell, running the same command as being used in subprocess does not produce these errors if run directly. This seems to be true on Linux at least. The command creates the desired number of frames (depending on provided framerate) while as a python subprocess only a few (3-5) frames are created before failure. I was able to determine that it has nothing to do with the unzipping process by hardcoding an unzipped folder and testing that as the source.
The processors/visualisation/video_frames.py is a bare bones wrapper for subprocess running
ffmpeg
.