Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
4th June 2014, 03:51 | #21 | Link |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,664
|
Hi Kurtnoise,
Thanks for this tool, with x265 picking up pace this tool should become very handy. Any possibility of adding some of the enhancements of avs4x264mod? |
4th June 2014, 13:38 | #23 | Link | |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,664
|
Quote:
-- When x264′s parameter “input-depth” is set and is not equal to 8, divide “width” by 2....
-- Make x264_64.exe path changeable. The path of x264 binary can be set by --x264-binary "x264_path"...
-- Directly output i422/i444 with AviSynth 2.6 csp YV16/YV24.
-- Do not add --input-res/--fps/--frames/--input-csp if already defined. -- Correct number of frames to be handled when --frames is defined.
-- Add "--seek-mode" to decide use "fast" seek mode or "safe" seek mode when has "--seek"....
-- Correct framerate to proper NTSC fraction if applicable.
I hope I'm not asking for too much. |
|
5th June 2014, 08:12 | #24 | Link |
Swallowed in the Sea
Join Date: Oct 2002
Location: Aix-en-Provence, France
Posts: 5,191
|
Let's try with the 0.4 release and tell me if all is fine...
|
5th June 2014, 09:27 | #26 | Link | |
Swallowed in the Sea
Join Date: Oct 2002
Location: Aix-en-Provence, France
Posts: 5,191
|
It's smaller because I didn't include the compressor anymore...
About the changelog : Quote:
Last edited by Kurtnoise; 5th June 2014 at 13:40. Reason: fixed typos |
|
6th June 2014, 03:28 | #28 | Link | |
Registered User
Join Date: Mar 2012
Location: Texas
Posts: 1,664
|
Quote:
Quickly encoded a small sample with 16-bit YV12 input to 10-bit x265, it seems to be working properly. I did not test --seek-mode or 8-bit x265 (will test more thoroughly this weekend). I hate to bother again but if it's not too much trouble can you please add this: -- Print full command-line piped to x264_64.exe to screen, prefixed by “avs4x264 [info]:”. |
|
6th June 2014, 07:57 | #29 | Link |
Swallowed in the Sea
Join Date: Oct 2002
Location: Aix-en-Provence, France
Posts: 5,191
|
Done in the 0.5 release...
|
6th August 2014, 20:17 | #30 | Link |
Registered User
Join Date: Nov 2009
Posts: 2,405
|
Thanks for the tool, Kurtnoise.
Sadly since 0.4 I get an error which does not appear when using 0.3. My command line: "D:\MeGUI\tools\x265\avs4x265.exe" --x265-binary ".\x64\x265.exe" --crf 23 --output "D:\MeGUI\_SAMPLE_VIDEOS\1.mkv.hevc" "D:\MeGUI\_SAMPLE_VIDEOS\1.avs" avs4x265 output: Code:
avs [info]: AviSynth 2.58, build:Dec 22 2008 [08:46:51] avs [info]: Video colorspace: YV12 avs [info]: Video resolution: 1920x1080 avs [info]: Video framerate: 24000/1001 avs [info]: Video framecount: 3388 Error: Failed to create process <2>! "D:\MeGUI\tools\x265\avs4x265.exe" --x265-binary "D:\MeGUI\tools\x265\x64\x265.exe" --crf 23 --output "D:\MeGUI\_SAMPLE_VIDEOS\1.mkv.hevc" "D:\MeGUI\_SAMPLE_VIDEOS\1.avs" So this is not an important problem. But perhaps you can add in the next version an error message when the exe cannot be located (and maybe revert to the old functionality that relative paths are ok). Thanks for your time! |
6th March 2015, 12:33 | #35 | Link |
Registered User
Join Date: Jul 2013
Posts: 60
|
@LigH - thanks for the suggestion! that would work I guess, but I found an alternative that I like much more:
https://github.com/rdp/ffmpeg-windows-build-helpers/ contains a completely automated build script for ffmpeg with x265 (and a lot of other libraries) that has the parameter --high-bitdepth=y which makes it add the -DHIGH_BIT_DEPTH=ON cmake parameter for x265. with that I can simplify my encoding a bit by doing encoding and packing into an mp4 container in a single step |
9th March 2015, 21:17 | #38 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Well, as already documented many times: ffmpeg works like a "filter". It writes an output file preferably only once, so that it could also write to a pipe where "rewind and overwrite the header" is technically not supported. But there are containers which would need values in the header = the beginning of a file which are only known at the end of the conversion. A program which writes a complete container would have to know the whole content before it starts to write the file. ffmpeg may not do that well in all cases. MP4Box does that.
That is my current level of knowledge for years already. If I am wrong now, because ffmpeg improved in this case, please correct me. |
10th March 2015, 01:34 | #39 | Link | |
Registered Loser
Join Date: Mar 2009
Posts: 3
|
Quote:
|
|
30th March 2015, 08:26 | #40 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
@ Kurtnoise:
The direct link to the v0.5 release returns a valid ZIP download; but the "here" URL in your starting post returns an error page. Looks like you don't have a "website" there anymore. |
Thread Tools | Search this Thread |
Display Modes | |
|
|