-
Notifications
You must be signed in to change notification settings - Fork 77
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
Internal engine sometimes produces bad mkv files #51
Comments
No issue in the original USM file, and if the decryption fails it won't look like this. I would've said it looks more like a playback issue, like if your device/player doesn't support the video codec (VP9 in our case). You might want to check the playback statistics in the player, to see if frames are correctly decoded and aren't corrupted. |
try to use another engine like FFmpeg. In some cases, the internal engine works wrong |
Thanks for the resposne. After checking the unmerged files, I realised that the unmerged videos don't have the issues I mentioned, so I tried converting it with ffmpeg using |
Yeah. The internal engine will break 1-2s randomly |
By the way is it just me or is GICutscenes no longer outputs the help text with the -h command? Wanted to check help to see if there was a verbose/debug mode or something but was unable to.
|
May I have a look at the merged file with the internal engine ? (with some file transfer platform). |
Sure thing. I've uploaded the videos here and included a log of my console output. There was also a 3.0 cutscene that I noticed had a glitch so I included that too. Please let me know when you've downloaded it so I can remove them. edit: added some cutscenes from 2.8 event too. |
This error is really suspect, but it might be related to the CommandLine library. |
That error happened a long time ago This video crashed in 1:37 Cs_Inazuma_LQ1203105_YaeMiko_Girl |
Alright thank you guys, I downloaded all the videos. I'll try to look into the mkv structure. |
Okay, so analyzing some of these files with
|
Okay, with more analysis, I found that blocks with a size of 0xFF were considered invalid, as apparently the matroska format considers that it indicates an unknown size. Since block size is calculated as varint, I have to tweak this function a bit I think. |
Closing the issue, as it should be resolved in the release 0.4.1. |
Hi, I used the latest versions.json to convert all the new cutscenes, but I've been having an issue with the resultant videos. For some reason, these cutscenes always convert with problems in the video, always at the same positions. These are skips and pixelation(?) so it seems like parts of the video just aren't converting correctly? I ran a repair from the launcher in case it was my local files being the issue, but it didn't modify any of the video files. Has anyone else experienced this issue? Are these possibly issues in the original USM files or something?
The text was updated successfully, but these errors were encountered: