[issue1233] vc1_decode_init may cause heap corruption
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment: Are you sure you have read http://ffmpeg.org/bugreports.html (esp. the last, bold, pragraph)? I also fear a patch that fixes your problem will be necessary. -- status: new - open substatus: new - needs_more_info _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1233 _
[issue1190] Fix build failure on NetBSD in bktr driver
Adam Hoka ah...@netbsd.org added the comment: Sorry, the bug is still present in ffmpeg. Please fix, thanks. -- status: closed - open substatus: invalid - reproduced _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1190 _
[issue520] Segmentation Fault and Valgrind reports invalid read of size 4 at indeo3_decode_frame() (indeo3.c:219)
compn te...@twmi.rr.com added the comment: moved. incoming/issue520$ ls 1-dog.avi 1-dog.txt FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue520
[issue1233] vc1_decode_init may cause heap corruption
Karl Blomster thefl...@uppcon.com added the comment:
Actually, ok. Removing .7z and adding files separately.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1233
_#include libavformat/avformat.h
#include libavcodec/avcodec.h
#include libavutil/log.h
#include stdio.h
#include stdint.h
int main (void) {
AVCodec *codec;
AVCodecContext *cc;
uint8_t *buf;
FILE *data;
long fsz;
int ret;
av_register_all();
av_log_set_level(AV_LOG_ERROR);
cc = avcodec_alloc_context2(CODEC_TYPE_VIDEO);
codec = avcodec_find_decoder(CODEC_ID_VC1);
data = fopen(extradata.bin, rb);
fseek(data, 0, SEEK_END);
fsz = ftell(data);
rewind(data);
buf = malloc(fsz);
fread(buf, 1, fsz, data);
cc-extradata = buf;
cc-extradata_size = fsz;
fclose(data);
ret = avcodec_open(cc, codec);
printf(avcodec_open returned: %d\n, ret);
avcodec_close(cc);
ret = avcodec_open(cc, codec);
printf(avcodec_open returned: %d\n, ret);
avcodec_close(cc);
return 0;
}
[issue1233] vc1_decode_init may cause heap corruption
Karl Blomster thefl...@uppcon.com added the comment: Codec extradata _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1233 _ extradata.bin Description: Binary data
[issue1190] Fix build failure on NetBSD in bktr driver
Luca Barbato lu_z...@gentoo.org added the comment: Please do not force us to remove your account. I mark it as wont_implement. You may feed the configure with additional -D_NETBSD_SOURCE=1 and that should make it build I think. -- status: open - closed substatus: reproduced - wont_implement _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1190 _
[issue783] MinGW GCC-4.4.0 builds broken shared version of ffmpeg on Windows
compn te...@twmi.rr.com added the comment: gcc 4.4 has been giving ffmpeg and mplayer troubles for the past few months... on all operating systems just fyi. FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue783
[issue1225] h264 decoding corruption: Open Remote Play: PlayStation FW 2.80
Darryl Sokoloski d...@rryl.ca added the comment: I found out what the problem is, and there is no fix for this. If the source MAC address does not match that of a registered PSP, the PS3 injects or rather changes, a random byte here and there in the video stream (after encryption). Thus, when decrypted, that bad byte turns in to a an entire bad block (128-bit, 16 bytes in this case) of data. Pumping that in to libavcodec causes bad things to happen as would be expected. Thanks again for taking a look, even if it was a red herring. -- status: open - closed _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1225 _
[issue1210] mpeg4es convert to cfr - fast playback
Bachman Kharazmi bac...@gmail.com added the comment: ok, before I start looking for between what svn revisions it got broken I need help to findout from what svn revision the 0.4.9 release tagged with so I have a starting point. _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1210 _
[issue1153] ac3dec 5.1 material is 3x softer than 2.0 material
Mark Spieth mspi...@digivation.com.au added the comment: sorry for the delay dialnorm is the difference. 5.1 sits at 28 2.0 sits at 22 so this is a 6dB difference (x2 voltage) compression also varies differently 5.1 varies from -6 to +5 2.0 varies from -5 to +22 doesnt explain the x3 experimental value though but comes closer. _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1153 _
[issue1153] ac3dec 5.1 material is 3x softer than 2.0 material
Reimar Döffinger b...@reimardoeffinger.de added the comment: On Sat, Jun 27, 2009 at 03:34:33PM +, Mark Spieth wrote: Mark Spieth mspi...@digivation.com.au added the comment: sorry for the delay dialnorm is the difference. 5.1 sits at 28 2.0 sits at 22 so this is a 6dB difference (x2 voltage) compression also varies differently 5.1 varies from -6 to +5 2.0 varies from -5 to +22 doesnt explain the x3 experimental value though but comes closer. You said that the 2.0 part is advertisement. Since advertisements are usually played at a louder volume (good idea, like that I can just leave the TV and come back when that annoying background noise stops to see the film continue), I'd claim that this does fully explain it... _ FFmpeg issue tracker iss...@roundup.ffmpeg.org https://roundup.ffmpeg.org/roundup/ffmpeg/issue1153 _
