headers
Tom Herbert | 1 Nov 02:52
Picon
Favicon

Newbie question on converting 4:3 to 16:9

Problem:  I want to burn a 320x240 wmv video to NTSC DVD, but I want 16:9 AR with the original image centered and
flanked by light gray bars (for my CRT HDTV).  I'm getting very good 4:3 output with the standard 4:3
presets, but have been unable to tweak options to get what I need.  In most cases the DVD player just won't
play it, and in come cases I get image stretching.  Here are a handful of the many video option combinations I
have tried without success.  Some are from memory and probably not exactly what I tried, but they're close. 
Most were basically shots in the dark:

... -s 720x480 -aspect 16:9 ... -padleft 66 -padright 68 -padcolor 8c8c8c
... -s 640x480 -aspect 16:9 ... -padleft 106 -padright 108 -padcolor 8c8c8c
... -s 640x480 -aspect 16:9 ... -padleft 40 -padright 40 -padcolor 8c8c8c
... -s 640x480 -aspect 4:3   ... -padleft 40 -padright 40 -padcolor 8c8c8c

This has to be a simple problem for the experts on this board.  Help?

 
 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com
Permalink | Reply | 0 comments |
headers
tripp | 1 Nov 04:30
Picon
Favicon

Re: Newbie question on converting 4:3 to 16:9


----- Original Message ----
From: Tom Herbert <ex_nessuno104 <at> yahoo.com>
To: ffmpeg-user <at> mplayerhq.hu
Sent: Thursday, November 1, 2007 3:52:30 AM
Subject: [Ffmpeg-user] Newbie question on converting 4:3 to 16:9

>Problem:  I want to burn a 320x240 wmv video to NTSC DVD, but I want
 16:9 AR with the original image centered and >flanked by light gray bars
 (for my CRT HDTV).  
>Most were basically
 shots in the dark:

they certainly were

>... -s 720x480 -aspect 16:9 ... -padleft 66 -padright 68 -padcolor
 8c8c8c

the easiest way is to pad and then resize

assuming it flag sequence actually works  (it doesn't for me)
-padleft 52 -padright 52 -padcolor
 8c8c8c -s 720x480 -aspect 16:9

otherwise:
-s 540x480 -aspect 16:9 -padleft 90 -padright 90 -padcolor
 8c8c8c 

 
gl
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Minelly | 1 Nov 06:21

Re: No sound when converting to flv

No, this would not help.

Actually, I have figured out, and I had to install libmp3lame _devel_ pack 
and everything started to work
great. No need to svn ffmpeg again.

Thanks for help to everyone.

Paul.

----- Original Message ----- 
From: "Rahul Shringarpure" <drawoh201 <at> gmail.com>
To: "FFmpeg user questions and RTFMs" <ffmpeg-user <at> mplayerhq.hu>
Sent: Thursday, November 01, 2007 1:40 AM
Subject: Re: [Ffmpeg-user] No sound when converting to flv

No, i mean new ffmpeg code from Subversion. I dunno why...It worked
for me, I had the same issues.

On 10/31/07, Paul Minelly <paulm <at> uusoftware.com> wrote:
> Do you mean I should pull a new  libmp3lame from SubVersion?
> How can I do it? They don't have subversion thing at their site.
>
> Or do you mean I should pull a new version of ffmpeg? But why?
> I even cannot build libmp3lame, so I cannot think of building ffmpeg as
> libmp3lame is not ready yet at my server. So why should I pull another
> version of ffmpeg
> as libmp3lame generates error while executing a make command?
>
> BTW, did you take a look at the error's output below? What does it mean?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hassan Adeel | 1 Nov 07:19
Favicon

difference between h263 and h264


Hi, whats the difference between h263 and h264, becoz i have a .3gp with
h264 codecs thats not going to be converted, but other 3gps with h.263 are
working, ffmpeg command line  converting both video but i can't do it with
my own written code.

I want to know whats codecs parameters should be used for h264 ( those are
different from h263), during decoding??

Note: during conversion of .3gp with h.264 i am unable to get "picture"
even for a single frame.
Permalink | Reply | 1 comment |
headers
Rich Felker | 1 Nov 08:08

Re: difference between h263 and h264

On Wed, Oct 31, 2007 at 11:19:08PM -0700, Hassan Adeel wrote:
> 
> Hi, whats the difference between h263 and h264,

h263 is essentially the same thing as mpeg4 asp, what ffmpeg calls
plain "mpeg4", the same format used by xvid, divx4+, and many other
popular implementations. officially they're not quite the same, and
each (h263 vs mpeg4 asp) has some minor features that the other lacks.

h264 is mpeg4 avc, a heap of relatively-high-cost micro-improvements
piled on top of mpeg4 which, taken all together, can give something
like a 30% improvement in overall compression (maybe more on
pathological content) at a computational cost of something like 300%.
the improvements include things like complex trees of bidirectionally
predicted frames, new macroblock encoding modes, cabac encoding for
the bitstream, bit-exact specifications for the dct and motion
algorithms, etc.

> becoz i have a .3gp with
> h264 codecs thats not going to be converted, but other 3gps with h.263 are
> working, ffmpeg command line  converting both video but i can't do it with
> my own written code.
> 
> I want to know whats codecs parameters should be used for h264 ( those are
> different from h263), during decoding??

for decoding, any modern version of ffmpeg supports both. there may be
some h264 features that aren't yet supported though.

> Note: during conversion of .3gp with h.264 i am unable to get "picture"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hassan Adeel | 1 Nov 08:17
Favicon

Re: difference between h263 and h264

Thanks for your iintrest!!

here is my code where i use avcodec_decode_video()...but i got "got_picture"
always false...why???

int write_output(AVStream *ist,AVFormatContext *oc,AVPacket* pkt)
	{
	    uint8_t *ptr;
	    int len, ret, got_picture, data_size, /*i,*/st_index;
	    static short *samples= NULL;
	    uint8_t *data_buf;
	    static unsigned int samples_size= 0;
	    int64_t ist_pts;
	    int are_we_at_eof = 0;
	    //printf("write_output: 1\n");
	    if(!pkt)
	    {
		  if(ist->codec->codec_type==CODEC_TYPE_VIDEO)
		  {
		     ivideo_pts= ivideo_next_pts; // needed for last packet if vsync=0
			 ist_pts = ivideo_pts;
		  }
		  else
		  if(ist->codec->codec_type==CODEC_TYPE_AUDIO )
		  {
			iaudio_pts= iaudio_next_pts;
			ist_pts =iaudio_pts;
		  }
	    }
	    else
(Continue reading)

Permalink | Reply | 0 comments |
headers
Houari | 1 Nov 08:14
Picon
Favicon

again on av_log

Hi all,

I am using ffmpeg to decode in MSVC (compiled it using msys/mingw) following the
guidance by Stephen Dranger. My question is, if I use av_log to debug the code
in libavcodec, how can I display it in the screen? Or can I dump it into a file?

Thank you,

Houari
Permalink | Reply | 1 comment |
headers
monkeyvu | 1 Nov 10:42
Picon
Favicon

convert from wmv to 3gp

Hi all,

I'm using ffmpeg in Windows, and my command line is as following

ffmpeg.rev10464>ffmpeg -i sample.wmv -f 3gp sample.3gp

But it shows an error :

Seems stream 1 codec frame rate differs from container frame rate: 1000.00 (1000
/1) -> 12.50 (25/2)
Input #0, asf, from 'sample.wmv':
  Duration: 00:00:31.1, start: 3.000000, bitrate: 110 kb/s
  Stream #0.0: Audio: wmav2, 22050 Hz, mono, 16 kb/s
  Stream #0.1: Video: wmv2, yuv420p, 320x240, 90 kb/s, 12.50 fps(r)
Output #0, 3gp, to 'sample.3gp':
  Stream #0.0: Video: h263, yuv420p, 320x240, q=2-31, 200 kb/s, 12.50 fps(c)
  Stream #0.1: Audio: libamr_nb, 22050 Hz, mono, 64 kb/s
Stream mapping:
  Stream #0.1 -> #0.0
  Stream #0.0 -> #0.1
[h263 @ 0098D2D0]The specified picture size of 320x240 is not valid for the H.26
3 codec.
Valid sizes are 128x96, 176x144, 352x288, 704x576, and 1408x1152. Try H.263+.
Error while opening codec for output stream #0.0 - maybe incorrect parameters su
ch as bit_rate, rate, width or height

Do you know this problem? Please help me, thanks very much :)
Permalink | Reply | 2 comments |
headers
Stefano Sabatini | 1 Nov 11:49
Picon
Favicon

Re: convert from wmv to 3gp

On date Thursday 2007-11-01 09:42:17 +0000, monkeyvu encoded:
> Hi all,
> 
> I'm using ffmpeg in Windows, and my command line is as following
> 
> ffmpeg.rev10464>ffmpeg -i sample.wmv -f 3gp sample.3gp
> 
> But it shows an error :
> 
> Seems stream 1 codec frame rate differs from container frame rate: 1000.00 (1000
> /1) -> 12.50 (25/2)
> Input #0, asf, from 'sample.wmv':
>   Duration: 00:00:31.1, start: 3.000000, bitrate: 110 kb/s
>   Stream #0.0: Audio: wmav2, 22050 Hz, mono, 16 kb/s
>   Stream #0.1: Video: wmv2, yuv420p, 320x240, 90 kb/s, 12.50 fps(r)
> Output #0, 3gp, to 'sample.3gp':
>   Stream #0.0: Video: h263, yuv420p, 320x240, q=2-31, 200 kb/s, 12.50 fps(c)
>   Stream #0.1: Audio: libamr_nb, 22050 Hz, mono, 64 kb/s
> Stream mapping:
>   Stream #0.1 -> #0.0
>   Stream #0.0 -> #0.1
> [h263 @ 0098D2D0]The specified picture size of 320x240 is not valid for the H.26
> 3 codec.
> Valid sizes are 128x96, 176x144, 352x288, 704x576, and 1408x1152. Try H.263+.
> Error while opening codec for output stream #0.0 - maybe incorrect parameters su
> ch as bit_rate, rate, width or height
> 
> 
> Do you know this problem? Please help me, thanks very much :)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Hassan Adeel | 1 Nov 13:22
Favicon

Re: [Ffmpeg-user] AVC: nal size 20453550

Hi,
  okz ..when i run myFFmpeg code then i  got following ouput..

[h264 @ 0x2574430]AVC: nal size 13147644
frame No: 1
[h264 @ 0x2574430]AVC: nal size 20453550
[h264 @ 0x2574430]AVC: nal size 19011758
[h264 @ 0x2574430]no frame!
Frames End while write_output
frame No: 2

i got i,2 frames from the output flv but i cant understand the error plus
how can i resolve it.

> On Wed, Oct 31, 2007 at 11:19:08PM -0700, Hassan Adeel wrote:
>>
>> Hi, whats the difference between h263 and h264,
>
> h263 is essentially the same thing as mpeg4 asp, what ffmpeg calls
> plain "mpeg4", the same format used by xvid, divx4+, and many other
> popular implementations. officially they're not quite the same, and
> each (h263 vs mpeg4 asp) has some minor features that the other lacks.
>
> h264 is mpeg4 avc, a heap of relatively-high-cost micro-improvements
> piled on top of mpeg4 which, taken all together, can give something
> like a 30% improvement in overall compression (maybe more on
> pathological content) at a computational cost of something like 300%.
> the improvements include things like complex trees of bidirectionally
> predicted frames, new macroblock encoding modes, cabac encoding for
> the bitstream, bit-exact specifications for the dct and motion
(Continue reading)

Permalink | Reply | 0 comments |

Gmane