Quote:
Originally Posted by jdobbs
I've imported multiple 2160p sources and haven't experienced what you describe. Are you sure you are letting it complete? When TSMUXER creates the structure it marks it as 1080p (because it doesn't support 2160p directly) -- but BD-RB corrects that after the TSMUXER session is completed.
|
yep, after encode this keep with 1080p info, when open the encoded disc in bdrebuilder.
Another stranger things that happened, but with a legit 1080p, the CPU use is around 20%, this is a bug ?
I already see this low cpu use in the past, but i don't know how I fix this
