Re: [Mjpeg-users] mencvcd script

2004-01-05 Thread Bernhard Praschinger
Hallo


 I'm not sure if this is the proper channel to ask about the mencvcd script, so
 let me know in whatever appropriate manner ;-)
For a proper solution of the problem the guys that wrote the script
would be the once to correct the problem.

 First, I could not simply do:
 
 mencvcd name -svcdout file.avi
 
 because I got this error:
 
 ++ WARN: [yuvscaler] Could not infer norm (PAL/SECAM or NTSC) from input data
 (frame size=576x432, frame rate=11988011:50 fps)!!**ERROR: [yuvscaler] No
 norm specified, cannot determine VCD output size. Please use the -n
 option!**ERROR: [mpeg2enc] Could not read YUV4MPEG2 header: system error (failed
 read/write)!
The problem ist the framerate specifed: 11988011:50, in combination
with you unusal framsize yuvscaler does not know what to do. The
framerate: 11988011:50 is closte to 24000:1001, so you should add
yuvfps before yuvscaler into the queue and ony change the framerate
header to 24000:1001, lookes like that: ... | yuvfps -c -r 24000:1001 |
...

You might have to set the framerate in mpeg2enc too. 

 So I did some playing around, and tried this:
 
 $mencvcd name -svcdout -vfr 4 -tvnorm n file.avi
 
 and it successfully encoded, but the sound was way *behind* the video, by about
 15- 20 seconds.
Than there is something else wrong. I guess the -tvnorm add some options
which are misinterpreded 3:1001 FPS instead of the 24000:1001

 Before I try playing around again (this takes a lng time), should I be going
 for a *higher* video framerate, or lower? I can't wrap this poor holiday-boozing
 noggin around it right now...
If you have encode some shorter streams first.

auf hoffentlich bald,

Berni the Chaos of Woodquarter

Email: [EMAIL PROTECTED]
www: http://www.lysator.liu.se/~gz/bernhard


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] mjpegtools 1.6.2 release candidate 3 online

2004-01-05 Thread Ronald Bultje
On Mon, 2004-01-05 at 05:30, Steven M. Schultz wrote:
   Now that mplex has been fixed the 1.6.1.93 or whatever the next
   RC-N is called (3 or 4 , something like that ;)) should be up in a
   couple days (right Ronald?).

*nod*. Unless any large bugs come around.

Ronald

-- 
Ronald Bultje [EMAIL PROTECTED]
Linux Video/Multimedia developer



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] mencvcd script

2004-01-05 Thread JoeHill
On Mon, 05 Jan 2004 07:58:16 +0100
Bernhard Praschinger [EMAIL PROTECTED] wrote:

 Hallo
 
 
  I'm not sure if this is the proper channel to ask about the mencvcd script,
  so
  let me know in whatever appropriate manner ;-)
 For a proper solution of the problem the guys that wrote the script
 would be the once to correct the problem.

Ok, that's really what I was thinking, but since it was available as part of
some of the mjpegtools packages on the download page, I was hoping someone
might at least give me a clue...and $DEITY knows I need a clue ;-)

  First, I could not simply do:
  
  mencvcd name -svcdout file.avi
  
  because I got this error:
  
  ++ WARN: [yuvscaler] Could not infer norm (PAL/SECAM or NTSC) from input
  data
  (frame size=576x432, frame rate=11988011:50 fps)!!**ERROR: [yuvscaler]
  No
  norm specified, cannot determine VCD output size. Please use the -n
  option!**ERROR: [mpeg2enc] Could not read YUV4MPEG2 header: system error
  (failed
  read/write)!
 The problem ist the framerate specifed: 11988011:50, in combination
 with you unusal framsize yuvscaler does not know what to do. The
 framerate: 11988011:50 is closte to 24000:1001, so you should add
 yuvfps before yuvscaler into the queue and ony change the framerate
 header to 24000:1001, lookes like that: ... | yuvfps -c -r 24000:1001 |
 ...
 
 You might have to set the framerate in mpeg2enc too. 

actually, the script does provide and option for setting the framerate to
24000:1001, and since no one had replied by the time I was going to bed, I
thought, what the heck, CD's are only about 50c each...

I forced my brain to do some logical thinking, and I figured if the sound is
*behind* the video, then I need a *lower* framerate. So I did the encoding
forcing a framerate of 24000:1001 and *BINGO*  it's dead on.

Thanks very much for your reply!

-- 
JoeHill ++ ICQ # 280779813
Registered Linux user #282046
Homepage: www.orderinchaos.org
+++
Things fall apart; the centre cannot hold...
-- William Butler Yeats


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] 1.6.2 on gcc 2.96?

2004-01-05 Thread Steven M. Schultz

On Mon, 5 Jan 2004, Dik Takken wrote:

 Will version 1.6.2 be compilable on gcc 2.96? I have posted problem
 reports about 1.6.1, which appears to be compilable only on gcc 3.x.

gcc 2.95.{3,4} was able to compile mjpegtools 1.6.1 without any
problems.   On some of my systems I use 2.95.3 to build the cvs
version of mjpegtools - works fine.

Which system is still using 2.96?   That was a troublesome version of
the compiler (I recall MPlayer being miscompiled by gcc 2.96).

Steven Schultz



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] problem with mplex and lpcm (Andrew Stevens please read!)

2004-01-05 Thread Gert Vervoort
Andrew,

Like Robert I noticed the problem with the xine software player. But, I 
also experienced problems while playing back the DVD on a Philips DVD 
recorder. In both cases adding the -W mplayer_hdr fixed the problem.

 Gert

Andrew Stevens wrote:

Gert, Robert,

Thanks very much for the LPCM feedback.   It is *extremely* interesting to get 
real feedback on some of these fiddly issues.  Just a quick question: are the 
noise problems Robert had with a hardware player or software?  If hardware, 
this would indicate there is a 'funny' alignment constraint in DVD for LPCM 
audio sectors a bit akin the really awful things done to MP2 audio in VCD.

cheers,

	Andrew



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
.

 





---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] 1.6.2 on gcc 2.96?

2004-01-05 Thread Richard Ellis
On Mon, Jan 05, 2004 at 08:35:31AM -0800, Steven M. Schultz wrote:
 
 On Mon, 5 Jan 2004, Dik Takken wrote:
 
  Will version 1.6.2 be compilable on gcc 2.96? I have posted problem
  reports about 1.6.1, which appears to be compilable only on gcc 3.x.
 
 gcc 2.95.{3,4} was able to compile mjpegtools 1.6.1 without any
 problems.  On some of my systems I use 2.95.3 to build the cvs
 version of mjpegtools - works fine.
 
 Which system is still using 2.96?   That was a troublesome version
 of the compiler (I recall MPlayer being miscompiled by gcc 2.96).

No one should be using 2.96.  That was never an official gcc release,
but instead was a redhat invention (which redhat release I do not
know) made by pulling a cvs copy of gcc and labeling it 2.96.  It
miscompiled lots of stuff, and it was/is object code incompatible
with everything but itself.  We should not expend any more than
minimal effort worrying about it, because the only true correct
answer to anyone still using it is properly upgrade.


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] 1.6.2 on gcc 2.96?

2004-01-05 Thread Dik Takken
On Mon, 5 Jan 2004, Richard Ellis wrote:

 On Mon, Jan 05, 2004 at 08:35:31AM -0800, Steven M. Schultz wrote:
 
  On Mon, 5 Jan 2004, Dik Takken wrote:
 
   Will version 1.6.2 be compilable on gcc 2.96? I have posted problem
   reports about 1.6.1, which appears to be compilable only on gcc 3.x.
 
  gcc 2.95.{3,4} was able to compile mjpegtools 1.6.1 without any
  problems.  On some of my systems I use 2.95.3 to build the cvs
  version of mjpegtools - works fine.
 
  Which system is still using 2.96?   That was a troublesome version
  of the compiler (I recall MPlayer being miscompiled by gcc 2.96).

 No one should be using 2.96.  That was never an official gcc release,
 but instead was a redhat invention (which redhat release I do not
 know) made by pulling a cvs copy of gcc and labeling it 2.96.  It
 miscompiled lots of stuff, and it was/is object code incompatible
 with everything but itself.  We should not expend any more than
 minimal effort worrying about it, because the only true correct
 answer to anyone still using it is properly upgrade.


Yes I know 2.96 is evil :) but I never had any problems with it. I have
used it to compile multiple generations of Linux kernels, XFree, KDE,
MPlayer. All of these have always been running rock-solid.

The real pain is that I have to do a complete re-install of my from
top-to-bottom customized installation if I want to get rid of that
stupid gcc 2.96

But if I am the only one with this compile problem, I understand your
decision to not do anything about it.

Dik


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] miro DC20 support ?

2004-01-05 Thread Lieven Desmet
On Wed, Dec 31, 2003 at 11:57:18AM +0100, Laurent Pinchart wrote:
Forgot to add that the output of lspci -v might help to identify the chip.

[EMAIL PROTECTED] lieven]$ lspci -v -s 00:0d.0
00:0d.0 Multimedia video controller: Miro Computer Products AG DC20 ASIC (rev 01)
Flags: medium devsel, IRQ 5
Memory at da00 (32-bit, non-prefetchable) [size=16M]

Yours truly,

Lieven Desmet
-- 
Lieven Desmet
DistriNet, Networking  Security

 K.U.Leuven, Dept. Computer ScienceTel: +32 (0) 16 32 76 68 
 Celestijnenlaan 200A  Fax: +32 (0) 16 32 79 96 
 B-3001 Heverlee, Belgium  Office: C200 A03.42  



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] mjpegtools 1.6.2 release candidate 3 online

2004-01-05 Thread Ronald Bultje
Hi Steven  all,

On Mon, 2004-01-05 at 18:06, Steven M. Schultz wrote:
   That's ok with me.  Having both is not necessary - either way is fine,
   but it does seem that pkg-config has become more popular and widely
   used.

Exactly, that's why I want to hop on that train too. I'll remove that in
the course of the next few days. Man, I'm slow. ;).

Ronald

-- 
Ronald Bultje [EMAIL PROTECTED]
Linux Video/Multimedia developer



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


Re: [Mjpeg-users] Compare yuvscaler and y4mscaler

2004-01-05 Thread Matto Marjanovic

Hiya,

 How does its speed compare to yuvscaler when encoding to
 similar quality (it that is possible anyway)? I have been
 using yuvscaler with the command line call:
 
   yuvscaler -v 0 -O SVCD -n n
 
 as a filter. What would be the scaling method whose resulting
 quality best aproximates to the yuvscaler call above?

I believe that for downscaling, yuvscaler defaults to its RESAMPLE mode,
 which is similar to y4mscaler's box kernel.  The other yuvscaler mode
 is BICUBIC, which should/would be similar to y4mscaler's cubic kernel.
 However, last time I checked, it still wasn't implemented quite correctly.
 (I need to re-check again, and record the version numbers when I do it.)

I haven't run any speed benchmarks lately.

So, to answer your second question:

 This is probably equivalent quality to the above yuvscaler command:
   y4mscaler -v 0 -I norm=ntsc -O preset=svcd -S option=box

 And this is definitely equivalent, if not much better, quality:
   y4mscaler -v 0 -I norm=ntsc -O preset=svcd -S option=cubic

 Do the presets set a good scaling method? Or should I worry
 about learning them to choose one?

No (and not really)... the current default is 'linear'; a better would be
 'cubic', and even better is something like 'sinc:8'.  I haven't had the
 time/attention yet to do more research into this question, so I haven't
 changed the default yet.

 I am trying it with the following commands:
 
 $ mkfifo -m 660 stream.yuv
 $ mplayer -noframedrop -vo yuv4mpeg -nosound -v -osdlevel 0 \
 the.two.towers.avi -sub the.two.towers.srt -subpos 78 \
 -vf expand=:504
 $ cat stream.yuv |
   y4mscaler -O preset=SVCD |
   mpeg2enc -v 0 -I 0 -s -f 5 -V 230 -S 800 -a 2 -F 1 -n n -4 2 -2 1 \
 -b 2800 -B 284 -q 6 -K FILE=matrix.txt -R 0 -E -11 \
 -o the.two.towers.m2v
 
 But y4mscaler gives the messages:
 
INFO: [y4mscaler] Input Stream Header:
INFO: [y4mscaler]frame size:  672x504 pixels (508032 bytes)
INFO: [y4mscaler]frame rate:  239759/1 fps (~23.975900)
INFO: [y4mscaler] interlace:  none/progressive
INFO: [y4mscaler]  sample aspect ratio:  ?:?
 **ERROR: [y4mscaler] Unknown norm; cannot determine SVCD format.
 
 Adding the option -I norm=NTSC to the y4mscaler command line does
 not help (the error message is the same from y4mscaler).

You need to add -I norm=NTSC *before* the -O preset=SVCD; options are
 evaluated in order.  (This is not clear in the manpage.  I'll fix that.
 In fact, it might make more sense to evaluate all -I options before any
 -O options...)

The 'norm' is inferred from the frame rate (not the frame size).  mplayer
 has provided a lame approximation to 24000/1001, and y4mscaler is looking
 for an exact match.  (Hmm... y4mscaler could be more lenient on the norm
 heuristic; that also goes on the TODO list.)


After that, y4mscaler will probably complain that it doesn't know the
 sample aspect ratio (SAR) of the input --- and, really, it can't do much
 without that.  mplayer should have provided that info; but maybe even
 mplayer doesn't know.  Or, maybe mplayer is rescaling everything, and
 pumping out plain old 1:1 pixels?  Or, mabye not, and the source still
 has a standard NTSC (10:11), or PAL (59:54) SAR.

If this is just some bootleg movie warez, it's probably in pretty sad shape
 as it is, and no one will notice anyway; just say -I sar=1:1.


Remember:  Digital video is like heroin.  If you want the best quality,
   you must Know your Source.  Otherwise you get what you get.
-matt m.


---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users


[Mjpeg-users] Re: [Mjpeg-developer] Re: [Dvdauthor-users] mpeg2desc -m is outputing 3 second delay

2004-01-05 Thread Florin Andrei
On Mon, 2004-01-05 at 05:56, Andrew Stevens wrote:

 I've now checked in a fix that should remove the internal overflow even for 
 really silly huge offsets...
 
   video_delay = static_castclockticks(job.video_offset)*CLOCKS/1000;
   audio_delay = static_castclockticks(job.audio_offset)*CLOCKS/1000;

Youpee! It works! :-) Thank you!

I patched mjpegtools-1.6.1.92-1.src.rpm with your modification, the
resulting src.rpm (that includes the patch) is here:

ftp://andrei.myip.org/media/mjpegtools/

Essentially, if you rebuild mjpegtools with your change, mplex -O works
without problems on RH9. Here are some examples:

# mplex -r 1 -f 8 -O 900 tahoe1-017.m2v tahoe1-017.mpa -o
test900.vob
# tcprobe -i test900.vob
[tcprobe] MPEG program stream (PS)
[tcprobe] summary for test900.vob, (*) = not default, 0 = not detected
import frame size: -g 720x480 [720x576] (*)
 aspect ratio: 4:3 (*)
   frame rate: -f 23.976 [25.000] frc=1 (*)
   PTS=1.0792, frame_time=41 ms, bitrate=8500 kbps
  audio track: -a 0 [0] -e 48000,16,2 [48000,16,2] -n 0x50 [0x2000]
(*)
   PTS=0.1792, bitrate=224 kbps
   -D 21 --av_fine_ms 24 (frames  ms) [0] [0]

# mplex -r 1 -f 8 -O -900 tahoe1-017.m2v tahoe1-017.mpa -o
test-900.vob
# tcprobe -i test-900.vob
[tcprobe] MPEG program stream (PS)
[tcprobe] summary for test-900.vob, (*) = not default, 0 = not detected
import frame size: -g 720x480 [720x576] (*)
 aspect ratio: 4:3 (*)
   frame rate: -f 23.976 [25.000] frc=1 (*)
   PTS=0.1792, frame_time=41 ms, bitrate=8500 kbps
  audio track: -a 0 [0] -e 48000,16,2 [48000,16,2] -n 0x50 [0x2000]
(*)
   PTS=1.0792, bitrate=224 kbps
   -D -21 --av_fine_ms -24 (frames  ms) [0] [0]

-- 
Florin Andrei

http://florin.myip.org/



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users