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. |
11th June 2010, 20:40 | #1602 | Link |
Registered User
Join Date: Dec 2002
Location: EUR
Posts: 159
|
Many thanks for this! Just did a short test with x264 and I'm getting a *very* healthy speedup compared to 32-bit + single-threaded avisynth.
32-bit run: x264 [info]: kb/s:2433.96 encoded 1000 frames, 7.80 fps, 2433.96 kb/s 64-bit run: x264 [info]: kb/s:2434.05 encoded 1000 frames, 9.90 fps, 2434.05 kb/s Output is slightly different (I'm not using vbv). This seems to come from resizing in avisynth MT as I did another run without resizing and the outputs were identical. Again, thank you! |
11th June 2010, 21:36 | #1604 | Link | ||||
.
Join Date: Jan 2006
Posts: 35
|
I got these warnings while using the 64bit version (looks like an avisynth bug), but encode turned out fine:
Quote:
encoded 3500 frames, 12.64 fps, 7140.72 kb/s 1st Pass - 32bit encoded 3500 frames, 12.15 fps, 7148.01 kb/s 2nd Pass - 64bit encoded 3500 frames, 1.92 fps, 7005.02 kb/s 2nd Pass - 32bit encoded 3500 frames, 1.92 fps, 7005.89 kb/s 64bit Quote:
Quote:
Quote:
Last edited by vinujan; 11th June 2010 at 21:41. |
||||
11th June 2010, 21:42 | #1605 | Link |
Registered User
Join Date: Dec 2002
Location: EUR
Posts: 159
|
You need SetMTMode at the beginning of your script (to avoid the pts-warnings). I don't have a ton of RAM so I use:
SetMemoryMax(1024) SetMTMode(1,1) If you've got a decent amount of memory, you can try: SetMTMode(2,0) er maybe SetMTMode(1,0) Last edited by nixo; 11th June 2010 at 21:47. |
11th June 2010, 22:45 | #1607 | Link |
Registered User
Join Date: Nov 2003
Posts: 1,281
|
Those error as caused by the resizers in avisynth64. There's dicussion about it on doom10. Nice to know that setmtmode will fix it though.
__________________
http://www.7-zip.org/ |
11th June 2010, 22:58 | #1608 | Link |
Compiling Encoder
Join Date: Jan 2007
Posts: 1,348
|
yes, it is known that JoshyD's resizer assembly code violates the win x86_64 calling convention which causes the non-monotonic warning in x264,
there could very well be other things that break/corrupt silently due to this violation outside of the visible warning. using SetMTMode masks the issue to not show that specific warning. |
12th June 2010, 04:42 | #1609 | Link |
Registered User
Join Date: Sep 2006
Posts: 82
|
Neuron2, many thanks for the autocrop which seems (so far) to make the same decisions as I would.
However I have an annoying (Windows) niggle: the window border in DGIndexNV has a dark inner line 1 pixel wide that makes it difficult to determine if you cropped enough. Here is a zoom on the right-hand border: . Could you by any chance add an inner white (or grey, or fluorescent pink...) border between the video image and the window border so that we can more easily spot if we have cropped sufficiently? |
12th June 2010, 11:20 | #1610 | Link |
Derek Prestegard IRL
Join Date: Nov 2003
Location: Los Angeles
Posts: 5,989
|
Fantastic news! I'll update all my binaries at work next week and see how things run! Now... to build up an IP KVM system so I can justify putting 2GB quadro cards in all my encoding servers and finally throw away Remote Desktop !!!
Derek
__________________
These are all my personal statements, not those of my employer :) |
12th June 2010, 13:54 | #1613 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Well, sorry then, I won't do anything to work around Windows sillinesses. The result would just be more silly. And people would complain that I am corrupting their video.
Not to mention how hard it would be to implement. Last edited by Guest; 12th June 2010 at 13:56. |
12th June 2010, 17:00 | #1614 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Encoding result with 64 bit tools for Baraka cropped to 1920*872 on my new rig :
x264 --tune film --keyint 25 --min-keyint 1 --bframes 3 --b-adapt 2 --ref 3 --bitrate 10000 --vbv-maxrate 10000 --vbv-bufsize 5000 --aud --fps 23.976 -o Baraka.264 Baraka.avs 29.28 fps encoding speed. It's better than real time! |
12th June 2010, 19:37 | #1617 | Link |
Registered User
Join Date: Sep 2006
Posts: 82
|
I'm getting this message on opening BBC HD since they went VBR and mixed TFF/MBAFF a week last Friday
Code:
--------------------------- Warning --------------------------- Trying to use an invalid (uninitialized) Picture Parameter Set with ID 0, expect the unexpected... Hit Yes to continue notifying this specific error type; hit No to disable it. Hit Cancel to suppress all further errors. --------------------------- Last edited by Clumpco; 12th June 2010 at 19:44. |
12th June 2010, 20:03 | #1619 | Link | |
Registered User
Join Date: Sep 2006
Posts: 82
|
Quote:
Since the 'error' occurred on a stream that had been edited first with VideoRedo I need to check first that the raw stream does it too. The problem may be coming from VideoRedo not dealing properly with the new BBC stream format, but I asked here just in case you had a quick simple answer. [UPDATE] The dgi/avs produced after this error hangs at 1 second from the end of the 1st pass of encoding with MeGui/x264. Additionally, the raw stream before editing with VideoRedo does not provoke the error message. I shall inform the VideoRedo people of the problem and post a sample here shortly just in case you can easily identify what they're doing wrong. PS - Re the border thing, I expressed myself badly. I meant to leave the video frame as it is and to increase your form size by 2 pixels all around. Cheers |
|
12th June 2010, 20:27 | #1620 | Link | ||
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
Quote:
|
||
|
|