-
Notifications
You must be signed in to change notification settings - Fork 81
Windows Help #140
Comments
I am also getting the same issue on Windows 10 with a network drive. |
Also seeing the same issue with Windows 10 [h265ize]: [verbose] Encoding started at Wed, 8:13 PM |
Can you guys try running this with the |
I've been seeing the same, here is the output with --debug
|
|
Hi, I've a similar problem too, I don't know if is related. Under windows, I get error but under linux, the same file with same command run fine.
And if I try to manually run this:
Any idea? |
Opening an issue, per the ReadMe hoping for some help...
I'm on Windows 10. I've installed h265ize and just tested an encode using my Z: drive, which is a Mapped Network Drive. I get the error below no matter what video I throw at it:
Z:\test>h265ize -v -d Z:\test -q 22 -m slow
[h265ize]: [verbose] Handling keypresses...
[h265ize]: [verbose] Setting as-preset options...
[h265ize]: [verbose] Folder encoding started at Tuesday, October 29th 2019, 6:00:39 AM
[h265ize]: Processing foo.mp4...
[h265ize]: [verbose] Encoding started at Tue, 6:00 AM
[h265ize]: [verbose] Getting metadata...
[h265ize]: [verbose] Resolving video streams...
[h265ize]: [verbose] Upconverting...
[h265ize]: [verbose] Setting video bit depth...
[h265ize]: [verbose] Mapping streams...
[h265ize]: [alert] Audio does not have a title. Title set to "Unknown AAC LC (Stereo)".
[h265ize]: [verbose] Detecting auto crop...
[h265ize]: Crop Detection: 12/12
[h265ize]: [verbose] Mapping HE Audio streams...
[h265ize]: [verbose] Setting ffmpeg settings...
[h265ize]: [verbose] Encoding video...
[h265ize]: ffmpeg exited with code 1:
[h265ize]: [verbose] Finished encoding at Tue, 6:00 AM (a few seconds)
[h265ize]: Folder encoding finished at Tuesday, October 29th 2019, 6:00:40 AM
[h265ize]: [alert] The following videos (1) were not encoded:
- foo.mp4: ffmpeg exited with code 1:
[h265ize]: [verbose] Cleaning up temp files...
[h265ize]: Process exited.
The text was updated successfully, but these errors were encountered: