On Fri, 5 Aug 2005, Skip Intro wrote:
> What's the story on AC-3? Have you ever ran AC-3 audio-only DVD disk
> through a compatibility lab to see what the "coverage" is?
The last time (a while back I admit) I tried to use ffmpeg's AC3
audio and it didn't play the fellow (not a co
> AC3 would be the way to go for maximum compatibility (and take up
> a LOT less space than PCM). I use DVDSP's AC3 encoder because I
> was never able to get DVDSP (or my settop box) to accept ffmpeg's AC3
> output.
When testing disks we're producing at a commercial compatiblilty
company, the onl
On Sat, 6 Aug 2005, Gernot Ziegler wrote:
> since C routines always are the common denominator for porting to new
> platforms, I doubt that any of the developers will abandon these fallback
> routines altogether. That leads me to the statement that any
> compilation problems with the C only code
On Fri, 5 Aug 2005, Skip Intro wrote:
> I've never been able to get mplex to work with pcm audio!
Hmmm, it's been working OK for a while for other folks.
> trying this with 1.6.3, but previous versions are doing the same
> thing.
Ahhh, is that the "release candidate 1" kit that
Folks:
I've never been able to get mplex to work with pcm audio!
My source PCM sounds fine and my video looks fine pre-multiplex. When
I multiplex them together. If I load the audio into Adobe audition,
telling it it's 48000, 16 bits, Motorola byte order, it sounds fine.
Then if I multiplex it
Hej,
since C routines always are the common denominator for porting to new
platforms, I doubt that any of the developers will abandon these fallback
routines altogether. That leads me to the statement that any
compilation problems with the C only code must be a bug and was not
intended :-)
>
> N
Hello,
I get the main.c ( 1.42 ) and the makefile.am ( 1.24 ) of /yuvdenoise and
compile another time. Now everything is fine. Thanks for help
> De: "Odile Planquelle" <[EMAIL PROTECTED]>
> A: "Bernhard Praschinger" <[EMAIL PROTECTED]>
> Objet: Re: Re: [Mjpeg-users] yuvdenoise
> Date:
On Wed, 2005-08-03 at 03:39, David Stan wrote:
my 1st question is how do i know what modules or
drivers are loaded? which do i need?
/sbin/lsmod tells you what drivers are loaded, /sbin/lsmod | grep
zr36067 is what you're looking for. If it gives no output, don't worry,
just load the driver: /s
