yeah, but, if that would be the case, then anything that is interlaced (not consistant 3:2 cadense pattern) would become 720p/60 or 1080p (by conversion to progressive and then reinterlaced by time expanding but still be progressive) something like that.
Try StreamFab Downloader and download from Netflix, Amazon, Youtube! Or Try DVDFab and copy Blu-rays! or rip iTunes movies!
+ Reply to Thread
Results 31 to 60 of 782
Thread
-
-
I hate VHS. I always did.
-
do not know if it is the right place to ask but are there a a friendly person that will help to make a cmd I can use for Riping my Fringe blu-ray so the quality remains but get the lower filesize it can get whit better compression sorry for the noob questions but there are so many different options it is of being dizzy of
-
@tola5: I don't think this encoder is quite ready yet. This thread, and other similar ones on it here, are dedicated to its development. Sure it's going to be great, but it needs a bit of time.
Use x264 for now. "Quality remains" will not happen compressing to a smaller size, with x264 or even with x265 here in the future, however today you can still get a good encode with x264 to a smaller size (use crf=18).I hate VHS. I always did. -
I say 1 year to be "ready" and to be "very good". Try 2-3 to be more "mature" (and "great").
I hate VHS. I always did. -
Why does x265 explicitly disable stuff that should be disabled implicitly?
a few example from common.cpp:
Code:else if (!strcmp(tune, "zero-latency")) { param->bFrameAdaptive = 0; param->bframes = 0; param->lookaheadDepth = 0; }
(all the other settings like bpyramid&co do not get mentioned)
Code:if (!strcmp(tune, "psnr")) { param->rc.aqMode = X265_AQ_NONE; param->rc.aqStrength = 0.0; param->rc.cuTree = 0; }
I understand that the defaults should mention these but all other method should explicitly change stuff which should be implicitly set.
----
Also the defaults mention 'param->bframes = 4;' as does
Code:else if (!strcmp(preset, "slow")) { param->lookaheadDepth = 25; param->bframes = 4; param->rdLevel = 4; param->subpelRefine = 3; param->maxNumMergeCand = 3; param->searchMethod = X265_STAR_SEARCH; }
Cu Selur -
ah, selur pointed out what i was missing.
Last edited by deadrats; 24th Dec 2013 at 09:45.
-
i'm probably overlooking something obvious but i find the way all this is written to be very odd.
Returns an integral value indicating the relationship between the strings:
A zero value indicates that both strings are equal.
A value greater than zero indicates that the first character that does not match has a greater value in str1 than in str2; And a value less than zero indicates the opposite. -
x265 first sets all parameters to default values. These default values are used for the "medium" performance preset.
So, I think the real question is - what should the default settings be? We want to provide high quality and good performance when someone runs x265 with default settings. At this point, these are the values we have determined to be the best choice. We welcome feedback on this topic (but of course, you and other experienced x265 users are always free to explicitly set any and all values to your preferred settings).
Tom -
Preset slow sets 'param->bframes = 4;' which is the same as the default presets -> there is not reason for that line to exist.
-> seems like you did not get my point -
Oh... I see what you are saying now. Yes, you're correct. I had cleaned that up when we did the last major change of performance presets, but it seems that there might be a few lines of redundant code in this section of common.cpp again.
Patches are always welcomed!
Thanks,
Tom -
Hello Guys!
The official webpage of x265 project (Member of Multicoreware INC) http://x265.org/about.html
I talked with the x265 developers (multicoreware) via facebook.
Here is their facebook page: https://www.facebook.com/multicoreware , where you can ask them about x265.
My first post:
"HI!
Are there any directshow version of x265 encoder? (For V.dub and Premiere) ?
Do you plan to make a vfw / directshow version of x265?
It would be very important!
Thank you!"
Their answer:
MulticoreWare Inc:
"Hi,
Thanks for your query. We got a response from the x265 team..
------------ We don't have one, it's not on the roadmap right now. It's very easy. Someone could do this in a few days; it's just a matter of resources and priority."
My second post:
"HI!
Is it allowed to create a vfw / directshow version of your x265 encoder?"
Their answer:
MulticoreWare Inc:
"Yes. x265 has a Open-source GPL license with the entire source code available for anyone to contribute back. Look at this link - https://bitbucket.org/multicoreware/x265/wiki/Home
multicoreware / x265 / wiki / Home — Bitbucket
bitbucket.orgTo compile x265 you must first install Mercurial (or TortoiseHg on Windows) and CMake 2.8.8 or later. To insure your build of x265 is capable of full performance, install YASM 1.2.0 or greater to compile assembly primitives. Then follow these easy steps "
So, are there any talented programmer who can do this "very easy" task?
DO NOT FORGET: IT WOULD BE A MILESTONE IN HEVC-HISTORY !
Thank you for your reply! -
Better yet, go to our x265 page here... https://www.facebook.com/x265project
My first post:
"HI!
Are there any directshow version of x265 encoder? (For V.dub and Premiere) ?
Do you plan to make a vfw / directshow version of x265?
It would be very important!
Thank you!"
Their answer:
MulticoreWare Inc:
"Hi,
Thanks for your query. We got a response from the x265 team..
------------ We don't have one, it's not on the roadmap right now. It's very easy. Someone could do this in a few days; it's just a matter of resources and priority."
My second post:
"HI! Is it allowed to create a vfw / directshow version of your x265 encoder?"
Their answer:
MulticoreWare Inc:
"Yes. x265 has a Open-source GPL license with the entire source code available for anyone to contribute back. Look at this link - https://bitbucket.org/multicoreware/x265/wiki/Home
So, are there any talented programmer who can do this "very easy" task?
DO NOT FORGET: IT WOULD BE A MILESTONE IN HEVC-HISTORY !
Thank you for your reply!
Best wishes for Happy Holidays!
Tom
MulticoreWare -
-
DirectShow okay, but heck vfw is:
a. avi centric so, b-frames (multiple reference frames) require 'patching'
b. simply old and hopefully dying
-> I don't think vfw should be a target and even DirectShow should not really be considered before 1.0 -
Yes, DirectShow is fine. But VFW is best left to the "rebels". I wouldn't prioritize it with x265.
I don't know if even AVI 2.0 worked with H.264 properly (seeing frames forward and backward, b-frames, multiple reference frames, etc.). I DOUBT it will be better with HEVC.
(Am I flame throwing? Nah. )I hate VHS. I always did. -
vfw requires the same hacks for H.264 that it required for MPEG-4 ASP regarding the b-frames&co, so it wouldn't require anything new for H.265 (aside from a new FOURCC) which then would again need some vfw decoder which associates that fourcc with a HEVC and can decoder HEVC. Still vfw really should die out,..
-
-
-
-
-
It's not about a debate, it's about facts. Test it yourself, encode the ParkJoy sample and check the resulting videos.
This sums it up pretty well:
http://forum.doom9.org/showthread.php?p=1658982#post1658982 -
Vast majority of doom9.org users are not professionals. (and they didn't use objective meters like PSNR)
Read this scientific comparison:
http://labs.divx.com/term/HEVC
Or this:
http://www.tomshardware.com/reviews/x265-hevc-encoder,3565-3.html -
-
That wasn't my point. I never implied that x264 does, or will, have better compression advantages over x265. I was suggesting x264 because it's fully ready now. And, I have no appetite to revisit a similar debate that was the early days of Xvid vs x264 of over 5-10 years ago. It got childish and became a waste of time when it should have been merely hypothetical and its only purpose to serve as a tracking of progress in the early days.
Of course we know x265 does/will have better compression advantages over x264. That's why we are even bothering with this in the first place and all of its growing pains.
Which is better today? I couldn't care less right now, and I don't think it's important at this point in time especially when things will change on a daily basis. I'm just waiting to see how much better x265 should be when it's much more ready in the future.I hate VHS. I always did. -
Originally Posted by StearsI hate VHS. I always did.
-
- the link to the x265 Evaluators Guide in the first post links to an old version.
- any plans for a new x265 Evaluators Guide since, the defaults&co changed? -
To whom this may interest...
Code:From: Tim Walker <tdskywalker@gmail.com> Reply-To: Development for x265 <x265-devel@videolan.org> To: x265-devel@videolan.org Subject: [x265] x265 integration and HandBrake Date: Wed 2014-01-15 02:21 AM Hi everyone, Someone named Zhang Zhiqiang has submitted a patch for review to integrate x265 encoding to HandBrake. The patch looks good overall, but some changes are still needed. While we do use ReviewBoard ( http://reviews.handbrake.fr ) for code review purposes, a lot of our development still happens on IRC, and I feel the patch would move forward quicker if we could get this developer to contact us on IRC. Does anyone here know Zhang Zhiqiang and could make this happen? He could join #handbrake-dev on freenode (voice will be given to him if he announces himself in #handbrake). If it's deemed preferable, the #x265 channel would do just fine. Thanks, Tim
Code:From: Tom Vaughan <tom.vaughan@multicorewareinc.com> Reply-To: Development for x265 <x265-devel@videolan.org> To: Development for x265 <x265-devel@videolan.org> Subject: Re: [x265] x265 integration and HandBrake Date: Wed 2014-01-15 03:12 AM Hi Tim, Yes, we know Zhang. He works for MulticoreWare (leaders of the x265 project). We'll have Zhang connect with you on IRC to move this forward. Thanks, Tom
Similar Threads
-
[HEVC] x265.EXE: mingw builds
By El Heggunte in forum Video ConversionReplies: 2221Last Post: 9th Feb 2021, 01:18 -
HEVC Encoder by Strongene Lentoid
By vhelp in forum Video ConversionReplies: 126Last Post: 19th May 2017, 12:58 -
theX.265 (a free HEVC) codec. Have you ever tried that HEVC encoder? (HELP)
By Stears555 in forum Video ConversionReplies: 41Last Post: 16th Sep 2013, 11:15 -
HEVC x265 Decoder
By enim in forum Newbie / General discussionsReplies: 5Last Post: 19th Aug 2013, 12:58 -
MulticoreWare Annouces x265/HEVC Mission Statement
By enim in forum Latest Video NewsReplies: 4Last Post: 9th Aug 2013, 22:09