|
General Discussion General discussion about SageTV and related companies, products, and technologies. |
|
Thread Tools | Search this Thread | Display Modes |
#21
|
||||
|
||||
@Neilm
I use 350/hr and that seems to be acceptable quality for me. But I get a wide variety of resolutions in my encodes, Is this because of the type of video it is, quality of channel or something else? I currently have everything at default except for using CBR 96 audio. Should I use a fixed width?
__________________
If this doesn't work right, Then: "I'm going to blow up the Earth!" |
#22
|
||||
|
||||
Quote:
The autogk compression test determines how 'compressable' the section of video is (depends on how much movement there is in the section, and channel noise can be confused as movement) then it chooses a resolution based on this compressability so that you gets the best resolution/bitrate combination for the chosen filesize... In (non-auto) GordianKnot, you get to do this part manually. Choosing a fixed width will mean that autogk can only alter the bitrate to fit the chosen filesize, which for a long/difficult to compress show may mean that the bitrate is too low, and you see the compression artifacts (blockyness/blurryness)
__________________
Check out my enhancements for Sage in the Sage Customisations and Sageplugins Wiki |
#23
|
|||
|
|||
Interesting. Thanks for the information. I will try limiting it to 350MB first, and see if this is acceptable. I guess I can queue up two jobs, one being the 350MB, and the second being 700MB, and see which one works better. If I start it tonight when I get home, I should have two files in the morning.
I'll leave it set to auto for the video size, and see what happens.
__________________
-Jason |
#24
|
|||
|
|||
Quote:
__________________
-Jason |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|