deleting or replacing hb does not remove the activity logs. they are found according to the instructions a couple posts up.
deleting or replacing hb does not remove the activity logs. they are found according to the instructions a couple posts up.
I think the "Nightly" needs an apology.I found my logs. As I expected, I was encoding using the H264 Levels:
mixed-refs=1:b-adapt=2:b-pyramid=none:trellis=0:weightp=0:vbv-maxrate=5500:vbv-bufsize=5500
And yes, I realize that this was probably used in the ATV2 preset. I will adjust accordingly.
I think the "Nightly" needs an apology.
I found my logs. As I expected, I was encoding using the H264 Levels:
mixed-refs=1:b-adapt=2:b-pyramid=none:trellis=0:weightp=0:vbv-maxrate=5500:vbv-bufsize=5500
And yes, I realize that this was probably used in the ATV2 preset. I will adjust accordingly.
vbv-maxrate=5500:vbv-bufsize=5500
No, and in fact that is as I said why you had 1. low file sizes / bitrate and 2. pixelation problems.Noted.
Other than the fact that this code probably led to my earlier pixelation problem, is it still a good code to use for ATV3 1080 encodes? All my other encodes look good to me, and I'm kind of used to the file sizes.
Basically this thread is a bust afaict. Sorry.
In the future if you want to go down this road ... please save us all a lot of time when you mess around and pastebin your logs. There is a reason for it. You frankly imo misrepresented what you were doing and were complaining about.
Much time was spent looking for a bug that ... never existed.
Btw, the presets use audio aac first track, ac3 second track. None of your logs showed that. Which is fine but claiming you are "using the atv 3 preset and something changed in hb" is at the very least, misleading. Frankly afaik you never even used it.
... Food for thought. Just sayin'.
I did use a preset, but failed to mention what I altered. I just didn't know how specific I had to be. I'm really no expert at this.
I am encoding Toy Story 3 from an MKV that was created from a Blu Ray source. I've done this twice. The first time, I chose the ATV3 preset and modified the H264 Profile from High to Main, and the H264 Level from 4.0 to 3.0. Link: http://pastebin.com/x0t47FAD
Why do you insist on changing things when you don't know why ? I am frankly befuddled by this.
Going from high to main and then level 4 to 3 of course will result in a larger file. But again, *why* are you messing with this ?
Because, a "lower" level and profiles uses less stringent encoding options (typically to allow playback compatibility for a given device, etc.). So, at the exact same rf value "lowering" those will typically create a larger file on the exact same source. Higher compression options are used in higher profiles and levels however often with a possible impact on device compatibiity.Why "of course"?
No, you are not annoying anyone however as others have stated you need to setup a systematic testing system if you want to change things willy nilly especially with x264 options. Also I spent a fair bit of time going by your descriptions of what was happening only to find out via activity logs etc that you handn't actually done what you said you had. Which is fine of course but again, less than accurate. People have tried to help you as much as possible on their own free time, which again is fine but Don't get mad because people don't want to explain every option HB / x264 has. It is not a one paragraph "quickie". Like vbv, it was set for a given rf, you change the rf but leave the vbv and voila, things change drastically as I explained up above.Actually, never mind. Clearly I'm annoying people when I'm simply just trying to understand things here.
Smaller size than what ? The earlier encode done with the same exact settings ? Your claim is that a different HB rev is creating different size output files with the exact same settings and source (as I understand it). I would need again to see the log from each encode which will provide much more detail as well as things like the svn number from each hb rev you are comparing. Otherwise, its like throwing darts in the dark.Oh, and I encoded that 54min mkv file from my earlier posts, also changing the profile to main and the level to 3.0, and it resulted in a smaller file size. Go fig.
I'm not going to lie. This ATV3 preset will take some getting used to. I encoded Toy Story.mkv from a BluRay source, changing only the Audio Kbps(Because I wanted to), and it spit out a file 3.2 gigs from a 19gig mkv. Then I did the same exact thing with Aliens, a 32.6 gig mkv, and the end file was 24.5 gigs.
In regards to Aspect ratio, what's the difference between Loose, Modulus 2 & Strict?
... and you are surpised ... why?
I'm no longer surprised by larger file sizes, but yes. A 24gig movie caught me off guard. How do you handle it? Do you accept it as is or do you pick other presets to bring the file size down?
well, I use personally the atv preset without vbv and rf 22. I am guessing you are still ramping the atv 3 preset up to a rf of 18 ? If so imo that is a crazy rf for a 1080p blu ray source.
Aliens is a notoriously huge bitrate hit. Very grainy and very complex scenes.
I would recommend you post your questions about detailed HB modification on the HB forum. Lot's of technical help there.No answer?
I would recommend you post your questions about detailed HB modification on the HB forum. Lot's of technical help there.
Wow.
vbv-maxsize=0:vbv-bufsize=0
Code:vbv-maxsize=0:vbv-bufsize=0
in the extra opts field should nullify it.