Luca Abeni lucab...@email.it added the comment:
Speex in RTP is currently not supported (as the error message suggests
:), because noone wrote the code for packetising speex frames in RTP
packets.
Old ffmpeg versions used to send out random (non standard, and probably
unplayable) streams
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Fix type.
--
priority: normal - wish
type: bug - feature_request
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2151
New submission from gnif ge...@spacevs.com:
This program makes multiple uses of open-source libraries including
ffmpeg without source, or any references to the GPL.
http://www.tipard.com/dvd-ripper.html
Files in this program:
avcodec-52.dll
avdevice-52.dll
avfilter-0.dll
gnif ge...@spacevs.com added the comment:
Depends on if the avi header is inconsistent with the encoding information
in the DTS stream, I dont know enough about avi to comment on which is the
problem, but I would expect that ffmpeg should prefer the channel count
provided by the actual codec
blindbunny ffmpegbugs.10.noonee...@spamgourmet.com added the comment:
Ah, cehoyos, could you elaborate? Are you saying that the command line I posted
does the right thing in not producing the result I want? If so, what do I need
to change in the command so that both videos are scaled in the
New submission from jslav js...@mail.ru:
Decoding the MPEG4 stream I encountered the issue of memory violation.
FFMPEG build without MMX/SSE support doesn't raise this exception.
Looked carefully difference in _c vs _ssse4 implementation, I found, that in
routine put_h264_chroma_mc4_c(...) has
jslav js...@mail.ru added the comment:
put_h264_chroma_mc4_c works fine.
-lowres 2 option works fine as well
-lowres 3 option raises same exception in procedure put_pixels8_mmx()
FFmpeg issue tracker iss...@roundup.ffmpeg.org
New submission from blindbunny ffmpegbugs.10.noonee...@spamgourmet.com:
I am trying to convert a Bluray title with ffmpeg. On this particular file,
ffmpeg automatically adds a scaling filter, which I cannot get rid of, to scale
the 1080p video stream down to 720x480. Interestingly, the file
Reimar Döffinger b...@reimardoeffinger.de added the comment:
On Mon, Aug 09, 2010 at 01:04:34PM +, blindbunny wrote:
Ah, cehoyos, could you elaborate? Are you saying that the command line I
posted
does the right thing in not producing the result I want? If so, what do I need
to change
570ff nicolas.cance...@laposte.net added the comment:
Thank you, lucabe72, for this clear answer.
Could you, by any chance, offer me an easy way to be notified when Speex would
be supported over RTP? Otherwise, I'll just check FFmpeg's page regularly.
Hats off to your efficiency.
Nicolas
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
You could add yourself to the Nosy List?
--
substatus: analyzed - open
topic: +avformat
FFmpeg issue tracker iss...@roundup.ffmpeg.org
Ronald S. Bultje rsbul...@gmail.com added the comment:
av_picture_copy(pict, pict_src,
-vp-pix_fmt, vp-width, vp-height);
+vp-pix_fmt, dst_width, dst_height);
#else
sws_flags = av_get_int(sws_opts, sws_flags, NULL);
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Is an external library (x264) required to reproduce the problem? If not, please
do not use it.
Afaict, this is not a regression (at least not avfilter-related).
--
status: new - open
substatus: new -
blindbunny ffmpegbugs.10.noonee...@spamgourmet.com added the comment:
The issue is also present with an internal codec (see below). What do you mean
by 'not a regression'? Does that statement have any consequence for me as a bug
reporter?
# ffmpeg -i /tmp/misscaling-video.m2ts -vf
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
I fear there is no issue as long as you don't use -map 0.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2156
blindbunny ffmpegbugs.10.noonee...@spamgourmet.com added the comment:
Uhm, that statement is a bit surprising to me :-) Doesn't my test case clearly
demonstrate that there is an issue? After all, it is impossible to re-code video
stream 0:0/0x1011 at its native frame size. This issue is present,
scheutzo mike.scheut...@alcatel-lucent.com added the comment:
Doesn't the top half of the #if/#else truncate the picture unscaled?
The values stored in vp-width and vp-height are larger than the actual buffer
size allocated by libSDL. Which is why a buffer overrun occurs.
If the
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Do you know where this behaviour is documented?
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2079
scheutzo mike.scheut...@alcatel-lucent.com added the comment:
Doesn't the top half of the #if/#else truncate the picture unscaled?
I just noticed you were asking about the partial-fix-1.patch.
This first attempt wasn't successful libSDL doesn't reduce bmp-w and bmp-h if
it decides to return
scheutzo mike.scheut...@alcatel-lucent.com added the comment:
Do you know where this behaviour is documented?
The libSDL API does not discuss the exception behavior of SDL_CreateYUVOverlay
at all. And a google search of their discussion forum turns up nothing related
to this topic. So that
New submission from Pete Eberlein p...@sensoray.com:
Please add a mapping for the V4L2_PIX_FMT_NV12 format to PIX_FMT_NV12 for
video4linux2 devices using the rawvideo codec.
small patch:
Index: libavdevice/v4l2.c
===
---
New submission from loopy123 bob.hav...@gmail.com:
in libavfilter/vf_scale.c
at line 117 (of 217)
I added the MOD 2 to the h and w variables to ensure that the
resulting calculated height and width is always divisible by two:
if (w == -1)
w = av_rescale(h, inlink-w, inlink-h) + (
New submission from Thierry tfo...@gmail.com:
../svn/configure --disable-everything --cc=gcc --enable-muxer=rtp
/usr/local/ffmpeg/svn/libavformat/sdp.c:243: undefined reference to
`ff_split_xiph_headers'
--
messages: 11627
priority: normal
status: new
substatus: new
title: SVN 24744:
New submission from Eric Pardee ffmpeg-u...@ericpardee.com:
Source file is Avid MXF DNxHD 145, which has been stripped to it's essence using
aafextract from AAF (1.1.3).
During decode, I see:
[dnxhd @ 0x1b7b7a0]error in header
Error while decoding stream #0.0
... (continues)
Complete, uncut
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Complete, uncut output of ffmpeg and sample missing.
Should you decide to upload a sample, please create a new directory issue2160.
--
status: new - open
substatus: new - needs_more_info
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Please use svn di to create patches (and don't forget to mention what your patch
does).
--
status: new - open
substatus: new - needs_changes
FFmpeg issue tracker
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Could you mention which camera or device you tested?
--
status: new - open
substatus: new - open
type: feature_request - patch
FFmpeg issue tracker
Eric Pardee ffmpeg-u...@ericpardee.com added the comment:
/usr/local/bin/ffmpeg -f dnxhd -r 29.97 -s 1920x1080 -i
dnxhd_145_decode_error.mxf -vcodec mjpeg -y ~/out.mov
FFmpeg version SVN-r24613, Copyright (c) 2000-2010 the FFmpeg developers
built on Jul 30 2010 18:22:59 with gcc 4.4.3
Pete Eberlein p...@sensoray.com added the comment:
The device is a frame grabber/MPEG encoder Sensoray Model 2253.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2157
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Assign to v4l2 maintainer.
--
assignedto: - lucabe72
nosy: +lucabe72
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2157
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Assign to v4l2 maintainer.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2157
Thierry tfo...@gmail.com added the comment:
Not sure if this is the same problem or not, but when use the latest ffmpeg SVN
and either lame
0.97, 0.98, 0.98.2, 0.98.4 and head, I'm getting the error: output buffer too
small.
But when I logged some outputs, the problem happened even before we
itskhan veritonjav...@gmail.com added the comment:
if their is any white spaces like new folder then file wont be stored .in that
folder.
--
priority: normal - important
title: Nellymoser Bug with silences transcoding - Spces are problem if file
need to be stored
33 matches
Mail list logo
