Anime4000 / IFME

Powerful x265 GUI Encoder
https://x265.github.io/
GNU General Public License v2.0
249 stars 54 forks source link

Error parsing slice header: byte_align not found at end of header ! #168

Closed redking974 closed 4 years ago

redking974 commented 6 years ago

Hi, I've recently update IFME to the 7.7 version. I was before on the 6.X because the 7.X was bugged on my system (Windows 10).

Now, it seems to work but after each conversion I got this yellow warnings. I post the end of my terminal :

Error parsing slice header: byte_align not found at end of header ! Error parsing slice header: byte_align not found at end of header ! Error parsing slice header: byte_align not found at end of header ! Error parsing slice header: byte_align not found at end of header ! Error parsing slice header: byte_align not found at end of header ! Error parsing slice header: byte_align not found at end of header ! HEVC Import results: 199560 samples (199564 NALUs) - Slices: 1900 I 36235 P 161425 B - 1 SEI - 1 IDR Stream uses forward prediction - stream CTS offset: 2 frames OpenGOP detected - adjusting file brand Saving video0000_eng.mp4: 0.500 secs Interleaving ifme [info]: Processing RAW MPEG video file OK! ifme [info]: Merging RAW files as single media file mkvmerge v22.0.0 ('At The End Of The World') 64-bit 'C:\Users\XXX\AppData\Local\Temp\IFME\video0000_eng.mp4': Using the demultiplexer for the format 'QuickTime/MP4'. 'C:\Users\XXX\AppData\Local\Temp\IFME\video0000_eng.mp4' track 0: Using the output module for the format 'HEVC/h.265'. The file 'G:\TEMP\REMUX.mkv' has been opened for writing. Progress: 100% The cue entries (the index) are being written... Multiplexing took 51 seconds. ifme [info]: Yay! All media done encoding...

I also remark that the remaining time/ENA is no more displayed into the console

I don't know if it's IFME or x265 or mkvtoolnix, because it was perfect when I was on the 6.X Here the plugins I change manually :

If it's not related to IFME, forgive me to open this issue.

Regards

Anime4000 commented 6 years ago

H.264 and H.265 raw bitstream will parse to mp4box...

why? because sometime mkvtoolnix can't read...

that yellow warning was normal, try play a video and see, see got any problem

mikelimtw commented 6 years ago

I'm getting this error on 7.7 currently. I am using standard installation for 7.7 except for AviSynth which I've substituted using AviSynth+.

EDIT1: I have checked my videos and they generally have stopped encoding. I mean the encoding generally finishes, but during playback, the encoded video will freeze at some point while the audio continues to play.

Anime4000 commented 6 years ago

try use other build of x265.exe and replace it, see if working fine

mikelimtw commented 6 years ago

@Anime4000 I'm not sure how to install newer plugin versions for IFME. Can you provide a link for me to read up on? I'm running on Windows 10.

Anime4000 commented 6 years ago

you can try this one: https://builds.x265.eu/

mikelimtw commented 6 years ago

I am using standard installation for IFME 7.7 ie I haven't changed or altered any of the plugins such as AviSynth etc.

I downloaded the nightly build for 2.7.351 vs 2017 AVX2 and extracted the files into the x265 plugin folder. I backed up the original files and renamed the 2.7.351 files the same names as included files. I'm still getting the error. I will try the link above and see if that helps. I'll let you know after I try them out.

Edit 1: I found something interesting. When using lower quality encoding such as fast/faster the encode usually goes to almost the end except for the final 30-40 seconds and then gets the errors. When setting it at the higher quality settings such as slow/slower it will usually fail somewhere in the middle of the encode. When set on the lower quality encodes I also get a total framecount; but when setting slow/slower the framecount is unknown.

MycroftHolmes1989 commented 6 years ago

Same here. Lots of files where the video and the current time freezes in the middle of the encoded output, but the audio works.

As an aside, any idea regarding how to find the defective output files?

Anime4000 commented 6 years ago

I encode a lot using MKV as container, no problem, I using older x265. for MP4, maybe MP4Box have issue?

MycroftHolmes1989 commented 6 years ago

Here's an example of defective file conversion: Input file: Here Output file: Here Console log: Here Screenshot: Here

Anime4000 commented 6 years ago

next version, I drop MP4Box, using FFmpeg as muxer