On Sun, 10 Oct 2004, Florin Andrei wrote:
> > What about other hardware players?...
>
> It's not easy to test other players.
Depends where you live I guess. It's been trivial to take a couple
test DVDs to the local Circuit City (or Best Buy or whatever) and
ask to play a disk.
> I think i tested a cheap CyberHome CH-DVD 300 and i think that one
> played the disks fine. But i could be wrong.
And the Apex (which is another inexpensive/cheap brand) hasn't had
any problem either.
> In any case, the CH-DVD 300 has a wrong pedestal setting and the image
> is too dark....
There are times I would prefer that - better dark than washed out
(too light).
> You get what you pay for.
The Philips was not expensive (but it was not "cheap") and is the
best DVD/SVCD player I've had yet - will play wildly out of spec
VCDs/SVCDs and hasn't had any issues with the DVDs I've created.
> Well, it works even with mjpegtools, it's just the end result that
> doesn't play fine on the DVD player, and i'm not sure who's to blame.
I'm not sure it's an encoder issue. I've taken mpeg2enc generated
streams and had them play on the ultra cheap players (Apex), a somewhat
more expensive Audiovox portable player, a midrange Sony and then
my Philips. The only thing I can think of that I do differently is
use Apple's AC3 encoder and authoring programs (which perhaps the
muxing) rather than ffmpeg, mplex and dvdauthor. mpeg2enc generated
streams work fine (turns out the MPEG-1 problem I'm having is NOT
the encoder's fault at all).
I wonder if it's the audio stream or mplex'ing that is causing the
problems you're having.
Have you tried both MP2 and AC3 audio with the same results?
> I am positive it's 48kHz. Several different tools reported the same
> number. It's a typical value for stuff coming out of an amateur DV
> camcorder.
Unless the camcorder accidentally was set to the 32kHz mode ;)
The other possibility which I thought might have happened is that
'mp2enc' was used to encode the audio to MP2 and the "-r 48000" was
accidentally left out. The old behaviour of mp2enc was to default
to 44100 - thus mp2enc would silently resample from 48000 down to
44100 :(
If/when you find time it would be a valuable data point to know if
the 1.7.0 (CVS) version of mjpegtools behaves differently. If so, then
the problem's been fixed, if not then well, we're still on a hunt
for the cause of the problem.
Cheers,
Steven Schultz
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
