-
Notifications
You must be signed in to change notification settings - Fork 88
illegal character N error #19
Comments
seems to be something to do with subtitles. Ironic these videos are also already h265 Any recommendations to try would be great. |
Hmmm. From the looks of it, h265ize tried to encode a subtitle file (the .sub). This would explain why handbrake says no titles detected. I don't know exactly what those input errors are from but I expect they are caused by trying to get data about the encoded file since handbrake didn't give an error code. Anyway, they are safe to ignore if they don't really bother you.Sent from myMail app for Android Thursday, 18 February 2016, 07:40PM -08:00 from jsdouglas22 < notifications@github.com> :
|
Well the problem is its crapping out by giving ffmpeg error stream map 0:2
|
Hmmm. I see your issue. Firstly, can you give me a copy of a file that isn't working so I can test it myself? I'm guessing the issue is stemming from ffprobe identifying a stream 0:2 but when ffmpeg goes to encode it it doesn't see stream 0:2. The relevant debug data from ffprobe:
|
Also, if you want to encode videos already in h265 you can use the |
Only looking to do non h265 I will send the file later on I am currently
|
I'll be gone all day today too, so that works out perfect. |
Found it. Handbrake recently removed the FDK AAC encoder because of licencing problems. So handbrake wasn't encoding one of the streams and that why you were getting the missing stream error. I just uploaded a new version, that should fix your problem. |
Working good now, thanks! |
It seems to crap out because of this, before I was getting a bunch of unary operator expected; according to manuals i read i could correct this by added an additional [ around if /&& statements, which i've done (see attachment) however I am getting illegal character N
h265ize.log-h265ize-bash.zip
The text was updated successfully, but these errors were encountered: