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. |
2nd April 2010, 11:23 | #441 | Link | ||
Programmer (or just 教务长)
Join Date: Oct 2008
Location: Valencia, Spain
Posts: 4,251
|
r1309M:
Quote:
r1510: Quote:
I think the difference is not with the switches but with the patch [x264_hrd_pd_interlace.16_r1301.diff] which is working. I'll have to find the latest x264 revision which works with this hddvdmux and report back. Last edited by deank; 2nd April 2010 at 11:30. |
||
2nd April 2010, 19:04 | #442 | Link | |
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,843
|
Quote:
I'm getting very good results with x264 now- I wish someone made a GUI to make x264 more like finish product. DS, how can I force I frames (for chapters)? Can I segment re-encode? Thx |
|
2nd April 2010, 23:43 | #444 | Link |
Registered User
Join Date: Feb 2009
Location: USA
Posts: 676
|
Sorry if this has been asked a million times by now..
But is the pulldown option in current spec supporting hardware devices? i.e would my WDTV Live recognize a pulldown flag in an H264 encode? And is this intended to be used for VFR sources? I.e Anime? I've never encoded anything other than VFR MKV's so I know little about how pulldown works, etc.. What would be the process of encoding a file with pulldown? How do you specify where to flag pulldown scenes, etc? If there is some kind of documentation someone could link to.. I might like to read that to see if its of any potential use for me. Thanks. |
2nd April 2010, 23:49 | #445 | Link | |
Registered User
Join Date: Nov 2004
Location: Poland
Posts: 2,843
|
Quote:
|
|
3rd April 2010, 01:25 | #447 | Link | ||||
Guest
Join Date: Jan 2002
Posts: 21,901
|
"Sorry if...": one of those weak conditional apologies.
Quote:
Quote:
Quote:
Quote:
Last edited by Guest; 3rd April 2010 at 04:14. |
||||
3rd April 2010, 09:08 | #449 | Link |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
Code:
--nal-hrd <string> Signal HRD information (requires vbv-bufsize) - none, vbr, cbr (cbr not allowed in .mp4)
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists |
3rd April 2010, 10:02 | #451 | Link |
Registered User
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
|
Just a wrong assumption, some switches lack <string>, --profile, --preset etc.
The default value for --nal-hrd is none, right?
__________________
https://github.com/stax76/software-list https://www.youtube.com/@stax76/playlists |
3rd April 2010, 12:52 | #452 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Code:
void x264_param_default( x264_param_t *param ) { [...] param->i_nal_hrd = X264_NAL_HRD_NONE; [...] }
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
3rd April 2010, 22:14 | #453 | Link |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
x264 build with (hopefully) HRD fixed.
Test this build and see if it passes muxing--if it does, we'll push it and x264 will be Blu-ray compliant. Really, this time! |
4th April 2010, 08:42 | #454 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,316
|
Ok, i've got it. Result from me not before tomorrow, time to encode...
Encoding will be with : @echo off SET E_SRC=%6%1.avs SET E_DST=%3%1.264 SET STAT_FILE=%1.stats SET TUNING=%4 SET LOG_FILE_1=%1_log_1.txt REM Set of max bitrate (ici le bitrate max) set MAX_BR=39000 REM Set of Buffer (ici le buffer) set BUF_BR=30000 x264_x86.exe --profile "high" --preset "placebo" --tune %TUNING% --bitrate %2 --stats %STAT_FILE% --level "4.1" --qpmin 0 --qpstep 2 --vbv-maxrate %MAX_BR% --vbv-bufsize %BUF_BR% --keyint 24 --min-keyint 2 --mvrange 511 --ref 4 --bframe 3 --slices 4 --b-pyramid "strict" --aq-mode 2 --aud --nal-hrd "vbr" --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --qpfile %5 --threads 0 --thread-input --output %E_DST% %E_SRC% 2> %LOG_FILE_1% tuning : animation bitrate : 39000 Last edited by jpsdr; 4th April 2010 at 08:45. |
4th April 2010, 12:46 | #455 | Link | |
Programmer (or just 教务长)
Join Date: Oct 2008
Location: Valencia, Spain
Posts: 4,251
|
Quote:
|
|
4th April 2010, 13:17 | #456 | Link | |
x264 developer
Join Date: Sep 2005
Posts: 8,666
|
Quote:
|
|
4th April 2010, 16:42 | #457 | Link |
Programmer (or just 教务长)
Join Date: Oct 2008
Location: Valencia, Spain
Posts: 4,251
|
Well... I never said it is x264's fault...
I'm not much into c++ programming, but I took the liberty to edit the source of this tool which seems to use code fragments from h264_info. For some reason it can't properly detect/find the required data to start decoding the frames... I added some log lines and here is what I get: The working: Code:
(9)Access unit delimeter (7)Sequence parameter set (8)Picture parameter set (6)SEI (6)SEI (5)Coded slice of an IDR picture (9)Access unit delimeter (6)SEI (1)Coded slice of non-IDR picture (9)Access unit delimeter (6)SEI (1)Coded slice of non-IDR picture (9)Access unit delimeter (6)SEI (1)Coded slice of non-IDR picture Code:
(9)Access unit delimeter (7)Sequence parameter set (8)Picture parameter set (9)Access unit delimeter <<-- I guess here it gets confused because it misses 3 important packets (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (?)unknown value (7)Sequence parameter set (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (7)Sequence parameter set (8)Picture parameter set (2)Coded slice of data partition A (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (9)Access unit delimeter (3)Coded slice of data partition B (9)Access unit delimeter (7)Sequence parameter set (8)Picture parameter set (?)unknown value the working stream has 00 00 00 01 06, while the non working has 00 00 01 06 --- and that's exactly what confuses the tool (the red-bold text above). Probably it doesn't recognize the bitstream. I also tried with 0 and 4 slices with the same result. The resolution in 2 packets back is proper: (04 16) (07 8C) while in the other is (48 28) (07 8C)... I'm probably completely wrong to compare these things, but I just wanted to report my limited findings. I hope it is not a complete waste of your time to check it. Dean Last edited by deank; 4th April 2010 at 17:02. |
4th April 2010, 19:27 | #460 | Link |
Pig on the wing
Join Date: Mar 2002
Location: Finland
Posts: 5,731
|
Does anybody have any figures how much more efficient the interlaced encoding should now be compared to the previous version without this patch? I did a test on an interlaced clip (5000 frames) and the bitrates were almost the same with r1471 and r1510. I did apply the TFF option in r1510 and "interlaced" in r1471. Other settings stayed the same.
__________________
And if the band you're in starts playing different tunes I'll see you on the dark side of the Moon... |
Thread Tools | Search this Thread |
Display Modes | |
|
|