[issue1784] ffmpeg -i udp:blablabla = hangs

2010-07-29 Thread Carl Eugen Hoyos

Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:

Fixed by Reimar in r24575.

--
status: open - closed
substatus: reproduced - fixed


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1784



[issue2040] strange interaction of avfilter with ffmpeg multiple output stream ad different widths

2010-07-29 Thread Stefano Sabatini

Stefano Sabatini stefano.sabatini-l...@poste.it added the comment:

ffmpeg currently doesn't properly supports filtering with more than one output.

Let's consider the command:
ffmpeg -i INPUT OUTPUT1 OUTPUT2

INPUT has size wxh, OUTPUT1 has size w1xh1, OUTPUT2 has size w2xh2.

A filterchain is automatically added for scaling from the input to the output,
in particular a scale filter is added to the end of the filter to rescale the
decoded frame to the size requested by the output.
The problem is that in this case the last scale filter will use the size w2xh2
for both OUTPUT1 and OUTPUT2.

A possible solution requires the use of a distinct filterchain for each input
and for each output.

This would allow for example to properly process a command of the kind:
ffmpeg -vf IN_VF -i INPUT -vf OUT_VF1 OUTPUT1 -vf OUT_VF2 OUTPUT2

while currently this command will only configure a single filterchain
corresponding to OUT_VF2.

--
topic: +ffmpeg


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2040



[issue2039] strange interaction of avfilter with ffmpeg multiple output stream ad different widths

2010-07-29 Thread Stefano Sabatini

Stefano Sabatini stefano.sabatini-l...@poste.it added the comment:

Duplicate of #2040.

--
status: new - closed
substatus: open - duplicate


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2039



[issue2039] strange interaction of avfilter with ffmpeg multiple output stream ad different widths

2010-07-29 Thread Carl Eugen Hoyos

Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:

Set issue 2040 as superseder.

--
superseder: +strange interaction of avfilter with ffmpeg multiple output stream 
ad different widths


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2039



[issue2040] strange interaction of avfilter with ffmpeg multiple output stream ad different widths

2010-07-29 Thread Carl Eugen Hoyos

Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:

Isn't this a duplicate of issue 2129 ?


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2040



[issue2136] Incorrect video duration when using -ss with -vcodec copy (for input videos encoded with libx264)

2010-07-29 Thread dabov

New submission from dabov kostadin.da...@gmail.com:

This bug is present in the current r24565 and also in ffmpeg 0.6. (It is
somewhat similar to Issue629.)

After using -ss with -vcodec copy as:

ffmpeg -ss 5 -i h264_encoded_with_libx264.mp4 -vcodec copy -an output.mp4

the duration of output.mp4 is 15.00 sec (instead of 10.04) and the duration of
the input video h264_encoded_with_libx264.mp4 is 15.04 sec.

Additional information: the input h264_encoded_with_libx264.mp4 was encoded
with -vcodec libx264 -vpre hq -b 300 -bt 300 -vsync 1 -r 30 
parameters.

Thank you for looking into this!

Regards,

Kostadin
File 'h264_encoded_with_libx264.mp4' not attached - you can download it from 
https://roundup.ffmpeg.org/file1006.

--
files: h264_encoded_with_libx264.mp4
messages: 11493
priority: normal
status: new
substatus: new
title: Incorrect video duration when using -ss with -vcodec copy (for input 
videos encoded with libx264)
type: bug


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2136



[issue2079] ffplay: segfault if coded video WxH dimension larger than desktop

2010-07-29 Thread scheutzo

scheutzo mike.scheut...@alcatel-lucent.com added the comment:

 Is there some reason why the scaling is not auto majically inserted when 
video is larger than screen size? It seems like u have to introduce some 
scaling if windows are resized.

Yes, you are right that a fit-to-window-rescaling is often necessary. The ffplay
code delegates this particular responsibility to the SDL library.

My guess is that the developer(s) assumed that SDL has the information to  make
the best choice between 'video card hardware scaling' and 'cpu software
scaling'. So, the ffplay code assumes that a video overlay can always be created
that is big enough to hold the entire unscaled image from the compressed stream.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2079



[issue2040] strange interaction of avfilter with ffmpeg multiple output stream ad different widths

2010-07-29 Thread Vitor

Vitor vitor1...@gmail.com added the comment:

On 07/29/2010 01:22 PM, Stefano Sabatini wrote:
 
 Stefano Sabatinistefano.sabatini-l...@poste.it  added the comment:
 
 ffmpeg currently doesn't properly supports filtering with more than one 
 output.
 
 Let's consider the command:
 ffmpeg -i INPUT OUTPUT1 OUTPUT2
 
 INPUT has size wxh, OUTPUT1 has size w1xh1, OUTPUT2 has size w2xh2.
 
 A filterchain is automatically added for scaling from the input to the output,
 in particular a scale filter is added to the end of the filter to rescale the
 decoded frame to the size requested by the output.
 The problem is that in this case the last scale filter will use the size w2xh2
 for both OUTPUT1 and OUTPUT2.
 
 A possible solution requires the use of a distinct filterchain for each input
 and for each output.
 
 This would allow for example to properly process a command of the kind:
 ffmpeg -vf IN_VF -i INPUT -vf OUT_VF1 OUTPUT1 -vf OUT_VF2 OUTPUT2

This seems less versatile than

ffmpeg -i INPUT -vf [in] split [out1][out2] OUTPUT1 OUTPUT2

that allows

ffmpeg -i INPUT -vf [in] split [A1][A2]; [A1] filter1 [out1]; [A2] filter2
[out2] OUTPUT1 OUTPUT2

But also allow several other funny tricks.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2040



[issue2136] Incorrect video duration when using -ss with -vcodec copy (for input videos encoded with libx264)

2010-07-29 Thread Carl Eugen Hoyos

Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:

Your video contains three I-frames at 0, 8.5 and 14.5 seconds.
With -vcodec copy, you can only cut at I-frames.

-ss 8.5 and -ss 14.5 work as expected.

--
status: new - closed
substatus: new - invalid


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2136



[issue1607] RTSP stream doesn't play

2010-07-29 Thread Ronald S. Bultje

Ronald S. Bultje rsbul...@gmail.com added the comment:

Attached patch screws up rtpdec_asf.c to play this stream. Things to 
note:
- this is actually RDT, not RTP ;-)
- each data packet comes with 8 bytes of ?? before the actual ASF data
- each ASF packet is 4 bytes short (according to the ASF muxer), and 
then has 4 padding bytes in the RTP packet. My hack to asfdec.c fixes 
that.
- the ASF header specifies only 1 stream, but the RDT specifies 2 (see 
ASMRuleBook). I can request both from the server; they appear mostly 
identical. Not sure how to expose that, since rdt.c automatically 
generates a second AVStream, but that currently isn't filled in
- the discard flag isn't set correctly, or rtsp.c screws up, so without 
my hack in rtsp.c, you hear duplicate packet music
- I should probably implement this in rdt_wmt.c or so, but was too lazy 
to properly separate it for now, hence my hacky patch. At least we know 
how it works now. ;-).


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1607


wmt.patch
Description: Binary data


[issue2123] dca sample does not play, channels wrongly detected (regression)

2010-07-29 Thread Anssi Hannula

Anssi Hannula anssi.hann...@iki.fi added the comment:

For the record, the reason I didn't reply to msg11351 in time was 
because I had expected to receive email messages for any comments made, 
while in fact I received only the initial new submission 
notification. Therefore I only noticed the activity on this issue now.

I'm sorry.


FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2123