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. |
13th April 2016, 19:06 | #24061 | Link | |
Registered User
Join Date: Nov 2013
Posts: 577
|
Quote:
some eventual problem with the settings of the x265 commandline I used. Anyway, I haven't made x264 reencoding on the same source to check if there would be any combing with that. Anyway, thank you for your answer. Last edited by mparade; 13th April 2016 at 19:08. |
|
13th April 2016, 19:13 | #24062 | Link | |
Registered User
Join Date: Nov 2013
Posts: 577
|
Quote:
|
|
13th April 2016, 23:19 | #24063 | Link | |
Registered User
Join Date: Aug 2005
Posts: 1,100
|
Quote:
FWIW, I did indeed buy the Season 1 set on DVD, used. I can't remember if it was from the UK or from here in the U.S. It was the Season 2 files that I was having trouble with, and I remember it took me quite a while to find a thread somewhere where someone HAPPENED to mention these Avisynth commands, and they happened to work IIRC (since it's been over a bloody YEAR since I dealt with this) I think what the deal was that the actual video looked interlaced, but it was encoded progressively. Even when I tried to play the native files on my OPPO, the deinterlacing apparently was not 'triggered' and you could see all the combing, etc... So, whatever this fellow was talking about reminded me of this uniquely odd situation that I had. Oh, and to tie it in to the overall discussion here (well, sort of... ) The thing that got me started with these files is that BDRB's built in deinterlacers didn't have any affect on the files - I'm GUESSING because they were encoded progressively and therefore didn't flag the fact that the video itself actually was (or looked) very interlaced. And I was puzzled thinking, wouldn't BDRB simply just re-encode the files and make them right? So, that is what got me started on the long quest to figure out what to do... Last edited by Lathe; 13th April 2016 at 23:26. |
|
14th April 2016, 00:39 | #24064 | Link | |
Registered User
Join Date: Apr 2003
Location: Within the main Source.
Posts: 895
|
Quote:
__________________
Life is not a journey to the grave; but rather to skid out broadside, thoroughly used, torn and warn and loudly proclaim; WOW; What a ride!!! Soon, I'm going to do it AGAiN in different skin!! |
|
14th April 2016, 10:07 | #24065 | Link | |
Registered User
Join Date: May 2006
Posts: 3,997
|
Quote:
script interlaced_.avs Code:
LoadPlugin("c:\.....\DGDecodeNV.dll") DGSource("c:\....\i_source.dgi",fieldop=0) Code:
"C:\.....\avs4x265.exe" --x265-binary "c:\....\x265.exe" --crf 27 --preset faster --interlace tff --output "c:\....\interlaced.265" "c:\....\interlaced_.avs" pause Last edited by Sharc; 14th April 2016 at 10:51. |
|
14th April 2016, 11:21 | #24066 | Link | |
Registered User
Join Date: Nov 2013
Posts: 577
|
Quote:
I think here the problem is that --interlace false is used by default by x265 (assuming progressive input). I am only making my assumptions. |
|
14th April 2016, 14:32 | #24069 | Link | |
Registered User
Join Date: May 2006
Posts: 3,997
|
Quote:
http://forum.doom9.org/showpost.php?...31&postcount=2 |
|
14th April 2016, 15:28 | #24070 | Link |
Registered User
Join Date: Nov 2013
Posts: 577
|
I will give you a feed back on this issue after checking the x265 encoded interlaced stream in mediainfo. Anyway, as far as I know, it is not enough to let x265 know that the source is interlaced by using a parameter such as --interlace tff in the command line but the avs file itself should have a SeparateFields() also at the end for the --interlace tff parameter to work properly.
Last edited by mparade; 14th April 2016 at 15:30. |
14th April 2016, 16:51 | #24071 | Link | |
Moderator
Join Date: Oct 2001
Posts: 20,975
|
Quote:
|
|
14th April 2016, 16:56 | #24072 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
x264 is a different software so that point is irrelevant. The x265 docs say:
Quote:
Do not assume because you can play it back in e.g. MPC-HC that it is encoded correctly. |
|
14th April 2016, 17:07 | #24073 | Link |
Moderator
Join Date: Oct 2001
Posts: 20,975
|
It is certainly based (from an interface standpoint) on X264, though. For the most part the command line parameters (that are supported) are the same. I'm guessing this was the reason I'd not used the --interlace parameter in the past (although I really can't remember).
Separating the fields and adjusting to fields-per-second is easy enough... but it would sure make a lot more sense for the encoder to separate them. Is it my imagination, or does it seem like people are getting more "snippety" on DOOM9 lately? Last edited by jdobbs; 14th April 2016 at 17:19. |
14th April 2016, 17:48 | #24074 | Link | |
Registered User
Join Date: May 2006
Posts: 3,997
|
Quote:
When I separated the fields x265 produces just encoded fields ("bobbing" half-height). Interlaced encoding with x265 seems still not to be stable, according to the warning of the encoder. |
|
14th April 2016, 18:10 | #24076 | Link |
Registered User
Join Date: Sep 2010
Posts: 120
|
No, it is not your imagination. Not just Doom, but every forum I follow. It is a sign of the impersonal times. The passive aggressive tone that would not be tolerated in a person to person interaction, has become the norm.
|
14th April 2016, 19:28 | #24078 | Link |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
That seems to be one of the combinations that doesn't play it correctly. I don't think it would be a good idea to create non-spec-compliant encodings to account for broken player. If the players get fixed eventually the encodes would break again. (and rightfully so)
|
Thread Tools | Search this Thread |
Display Modes | |
|
|