-
Notifications
You must be signed in to change notification settings - Fork 53
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
I can't use Skyfit2 on Ubuntu for MP4 videos #506
Comments
To change the backend to opencv, put/modify in the .config this variable: |
Hello, Thank you very much for your reply. Now, by changing the media_backend in the configuration I can open the file. The video information I get with ffprobe is: (resolution 3840x2160 and 24.24 fps) Metadata: But, when open the file with Skyfit2, I get this information: Mask resolution (1280, 720) does not match the image resolution (3840, 2160). Ignoring the mask. The value for FPS in SkyFit2 not match with the video information. It's correct? The values in .config file are: media_backend: cv2 uyvy_pixelformat: false width: 3840 Many thanks! |
I have found the reason in the hardcoded pipeline - matroskademux element causes it. |
Hello,
I have installed RMS and its utilities, including SkyFit2, several times, both on Ubuntu 22 and Ubuntu 20, following the procedure described, both with the supplied script (GRMSL_Install.sh) and with the conda packages, as documented in the project's Github page.
In both cases, always at the end of the process, when I try to open an mp4 video, I get the following error:
python3 -m Utils.SkyFit2 ./Estepa/M20240519_073311_Estepa.mp4 --config . --timebeg 20240518_224639.000000
0:00:04.023406629 49717 0x7f542c000b60 ERROR ebmlread ebml-read.c:139:gst_ebml_peek_id_length: Invalid EBML ID size tag (0x0) at position 0 (0x0)
This same command and video works for other colleagues with an older version of Skyfit2. It also works for me on Windows.
I have installed all the dependencies that you have been requesting. I have also seen that there is another issue in which this error is discussed and that says that it is solved by changing the media_backend, but I don't know how to do it.
Thank you very much for any help you can give me.
Ángel
The text was updated successfully, but these errors were encountered: