x264 w/ 3:2 pulldown and hrd - Page 3

SealTooGreat · 22nd June 2007, 22:38

Trahald, if you have the will to that, it would very appreciated. Thanks

Trahald · 23rd June 2007, 17:39

The diff link on that thread gives an error message. couldnt get get the patch file

Also.. I just use diff/patch from zlib . this works, although it produces slightly different looking patch files (although they work). what svn app are you using?

uteotw · 27th June 2007, 12:28

Quote:

Originally Posted by Trahald

... what svn app are you using?

Errr... if you were asking me, I use Tortoise.
the whole thing is new to me. It's easy to select to diff and patch files but applying is confusing because source files have changed since the patch were created. So at that point I'm not too sure what to do.

Trahald · 30th June 2007, 22:03

i should have out a threaded version with aq/hrd/pulldown for 663 by tomorrow. svn command line seems to work the best for me thanks

Trahald · 1st July 2007, 19:07

ok.. check the sourceforge page. 663 checkout with aq hrd pulldown and pthread-w32 .
will put up a combined hrdpulldown patch in a day or so

quantum · 1st July 2007, 19:46

When using --threads 2 I see:
x264 [warning]: not compiled with pthread support!

And it's not using both cores.

uteotw · 1st July 2007, 22:19

Quote:

Originally Posted by Trahald

ok.. check the sourceforge page. 663 checkout with aq hrd pulldown and pthread-w32 .
will put up a combined hrdpulldown patch in a day or so

You da man!

Will give it a try this week and report back
Thanks a million

Trahald · 2nd July 2007, 01:29

!

663b up! I compiled and tested it properly in debug mode.. then when i switched to release i missed a step. sorry. This one works.

SealTooGreat · 2nd July 2007, 04:28

Trahald, your 663b doesn't support mp4 output. It's 632kb in size, while official r663 is 935kb.

Sagittaire · 2nd July 2007, 05:14

Quote:

Originally Posted by SealTooGreat

Trahald, your 663b doesn't support mp4 output. It's 632kb in size, while official r663 is 935kb.

mp4 and mkv output is completely useless here. This build produce HDDVD/BD compliant stream and these stream must be ES.

SealTooGreat · 2nd July 2007, 05:50

^Yes, I know that, but you don't always make HDDVD/BD complaint,

there are common x264 encodes as well. Little versatility would be appreciated.

Trahald · 2nd July 2007, 07:16

i'll think about it.. since pulldown isnt needed in those containers i didnt make it a priority.

woah! · 2nd July 2007, 08:22

how do you tell it to do a 59.94 pulldown, --pulldown 32 i assume does 23.976 to 29.97 yes? can 59.94 be done from 23.976 ?

woah! · 2nd July 2007, 11:28

if your interested i have another head scratcher for you:

i am finding the timecodes of the hrd build 663 arent adding up to what i see as the correct timecode output from cinevision.

to test that theory i put the resulting .264 through your h264info app and applied 29.97fps to it. now that shouldnt have really changed anything right as it should have been pulldown 29.97 to begin with.

but after processing it into cinevision it gave the exact same timecode as the cinevision result which i believe is correct.

heres a screenie of what i mean below, the properties you see shows the .264 file is 29.97 but the time is out by about 11 frames.

quantum · 3rd July 2007, 00:17

Quote:

Originally Posted by Trahald

663b up! I compiled and tested it properly in debug mode.. then when i switched to release i missed a step. sorry. This one works.

Thanks. Threads are working. Now for some testing.

Trahald · 6th July 2007, 20:51

663d is available. fixes the duration issue. should match h264info exactly.

quantum · 7th July 2007, 04:13

It appears you left several dependencies for this build. It works on my machine with Visual Studio installed, but it fails on another. The other machine runs all previous versions.

quantum · 7th July 2007, 16:50

There's something else going on since the thread support was added. There is an audio sync issue with builds after 616c. The audio falls out of sync half way through the movie. It's in sync for the first half, then out of sync by about a second for the entire second half.

Using the same command line with 616c the audio is fine. I'm starting another encode with 663c without threads to see if it's the threads or something else with the new builds.

I see the timing is different for both streams using Streameye. At frame 100,000, the old version is 1:09:30 while the new (out of sync) version is 1:09:49.

I haven't tested 663d yet because it won't run on the PC I use for encodes.

Trahald · 7th July 2007, 20:50

i built 663e now w/out gpac so give that a whirl. (i tested it on a virtual pc window that wouldnt run 663d but does run 663e)

quantum · 7th July 2007, 20:56

Using 663b without --threads 2 results in OK audio, so it appears to be a threads problem. With threads, the problem starts approximately halfway through my 206,000 frame test movie.

Nice work so far. This is already one of the few ways to reliably get video into scenarist. If we can have threads, I'd prefer it over Cinevision.

23rd June 2007, 17:39	#42 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	The diff link on that thread gives an error message. couldnt get get the patch file Also.. I just use diff/patch from zlib . this works, although it produces slightly different looking patch files (although they work). what svn app are you using? __________________ ...yeah...but...why on earth would I compare apples with apples?

30th June 2007, 22:03	#44 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	i should have out a threaded version with aq/hrd/pulldown for 663 by tomorrow. svn command line seems to work the best for me thanks __________________ ...yeah...but...why on earth would I compare apples with apples?

1st July 2007, 19:07	#45 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	ok.. check the sourceforge page. 663 checkout with aq hrd pulldown and pthread-w32 . will put up a combined hrdpulldown patch in a day or so __________________ ...yeah...but...why on earth would I compare apples with apples?

2nd July 2007, 01:29	#48 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	! 663b up! I compiled and tested it properly in debug mode.. then when i switched to release i missed a step. sorry. This one works. __________________ ...yeah...but...why on earth would I compare apples with apples?

2nd July 2007, 07:16	#52 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	i'll think about it.. since pulldown isnt needed in those containers i didnt make it a priority. __________________ ...yeah...but...why on earth would I compare apples with apples?

22nd June 2007, 22:38	#41 \| Link
SealTooGreat Registered User Join Date: Dec 2006 Posts: 302	Trahald, if you have the will to that, it would very appreciated. Thanks

1st July 2007, 19:46	#46 \| Link
quantum Registered User Join Date: Nov 2002 Location: USA Posts: 528	When using --threads 2 I see: x264 [warning]: not compiled with pthread support! And it's not using both cores.

2nd July 2007, 04:28	#49 \| Link
SealTooGreat Registered User Join Date: Dec 2006 Posts: 302	Trahald, your 663b doesn't support mp4 output. It's 632kb in size, while official r663 is 935kb.

2nd July 2007, 05:50	#51 \| Link
SealTooGreat Registered User Join Date: Dec 2006 Posts: 302	^Yes, I know that, but you don't always make HDDVD/BD complaint, there are common x264 encodes as well. Little versatility would be appreciated.

2nd July 2007, 08:22	#53 \| Link
woah! Registered User Join Date: Oct 2003 Posts: 435	how do you tell it to do a 59.94 pulldown, --pulldown 32 i assume does 23.976 to 29.97 yes? can 59.94 be done from 23.976 ?

2nd July 2007, 11:28	#54 \| Link
woah! Registered User Join Date: Oct 2003 Posts: 435	if your interested i have another head scratcher for you: i am finding the timecodes of the hrd build 663 arent adding up to what i see as the correct timecode output from cinevision. to test that theory i put the resulting .264 through your h264info app and applied 29.97fps to it. now that shouldnt have really changed anything right as it should have been pulldown 29.97 to begin with. but after processing it into cinevision it gave the exact same timecode as the cinevision result which i believe is correct. heres a screenie of what i mean below, the properties you see shows the .264 file is 29.97 but the time is out by about 11 frames.

6th July 2007, 20:51	#56 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	663d is available. fixes the duration issue. should match h264info exactly. __________________ ...yeah...but...why on earth would I compare apples with apples?

7th July 2007, 04:13	#57 \| Link
quantum Registered User Join Date: Nov 2002 Location: USA Posts: 528	It appears you left several dependencies for this build. It works on my machine with Visual Studio installed, but it fails on another. The other machine runs all previous versions.

7th July 2007, 16:50	#58 \| Link
quantum Registered User Join Date: Nov 2002 Location: USA Posts: 528	There's something else going on since the thread support was added. There is an audio sync issue with builds after 616c. The audio falls out of sync half way through the movie. It's in sync for the first half, then out of sync by about a second for the entire second half. Using the same command line with 616c the audio is fine. I'm starting another encode with 663c without threads to see if it's the threads or something else with the new builds. I see the timing is different for both streams using Streameye. At frame 100,000, the old version is 1:09:30 while the new (out of sync) version is 1:09:49. I haven't tested 663d yet because it won't run on the PC I use for encodes.

7th July 2007, 20:50	#59 \| Link
Trahald Wewkiee Join Date: Feb 2002 Location: kashyyyk Posts: 2,269	i built 663e now w/out gpac so give that a whirl. (i tested it on a virtual pc window that wouldnt run 663d but does run 663e) __________________ ...yeah...but...why on earth would I compare apples with apples?

7th July 2007, 20:56	#60 \| Link
quantum Registered User Join Date: Nov 2002 Location: USA Posts: 528	Using 663b without --threads 2 results in OK audio, so it appears to be a threads problem. With threads, the problem starts approximately halfway through my 206,000 frame test movie. Nice work so far. This is already one of the few ways to reliably get video into scenarist. If we can have threads, I'd prefer it over Cinevision.