Quote:
|
Originally Posted by rds_correia
I can recall some weeks ago Karl also advised me that some folks can't play HCEnc's output on their SAPs.
|
It seems thats why 100% (at least proofed to be) mpeg2 compilant encoders do cost money
@ This subject In General
There are also two choices when choosing my encoder:
- Its meant to be played back by my OWN SAP device or ...
- Does it have to be "world" compatible.
I dont see that issue that hard emotionally cause:
IF we would insist on only 100% "world" playback compilant outputs, that would put the whole beginning of KVCD in question! Or even better the "KVCD SAP compatibility chart"
I remember clearly when we used to encode 1CD targets using non std. GOPs for instance. And there we didn't take care about people who couldn't playback such a "KVCD" specs based encoding.
The rule was simple "If you do a copy - then you do it for your own and therefore for your own SAP which can playback THAT kind of a copy".
Other intentions means sharing "world" compatible KVCD footages did mostly end up in Threads like "I got a KVCD, how can I reencode it so my SAP plays it back" ... Answer:"Do encode the ORIGINAL Source from scratch as it seems your SAP doesnt like KVCD".
If I do get a real "JOB" to encode Sources for DVD purposes etc. then there are for me NO experiments, means using encoders which have been proofed over years to be 100% world-non-problematic.
Also we should keep in mind that we didn't closed the Mencoder testing area cause libavcodec should be really fixed 100% by FFmpeg Team before. It was the fact that some people in here broke from the testing area out and released in regular sections Mencoder CLI guides for everyone which WAS tricky and could have put the name "KVCD" into a mess for users which just want to encode and which do trust in their encodes that they would work everywhere. And that was at "that" point not the fact.
I dont know WHAT they patched since 1/2 year and HOW that new ratecontrol implementation in Qenc does work as I dint testet it carefully by my own.
The main problem in here is (no matter whats the subject actually): We do behave like some peoples in other areas which do make their anti-propaganda on KVCD by just attacking everything which has something to do with it.
I do read soooo often ...
Q "I want to encode a KVCD"
A "What? Thats the biggest anti-standard shit in the world - WE DO keep the standard"
Q "But I heared that if the SAP supports it, it results in better blockless encodings"
A "As said we dont deal with that, use std. specs and go for 2-3 CDs, KVCD childish workouts are no subject in here, bye"
Let the people decide by themselfes what they choose IF it works on their SAP. We can give warnings oohhh yes as we got our experiencies.
If someone enters in Gleitz.de where Im also mod too and asks how to build a 1CD KVCD I shurely do give him a hand but for shure I do advice that he should check if his SAP accepts the larger GOP.
About the mplayer/ffmpeg Team.... hmmmm
It really seems that they are more interested in updating parts of recent technologies like aac, mpeg4, h264 or whatever.
The Loudness bug in ac3enc.c is almost known since the beginnning it was implementated ... no experienced coder gets into it why?
Hmmmm .... it seems it all depends on the "interests" of the code developers .
