Jai Menon jmeno...@gmail.com added the comment:
we don't parse uslt frames. doing this would probably involve factoring
out the text parsing code from read_ttag and storing the lyrics along side
the corresponding AVMetadata key.
FFmpeg issue
Jai Menon jmeno...@gmail.com added the comment:
yeah, we need a png parser to split incoming packets into frames. iirc
someone submitted one too. dunno what happened with that though. try
looking through the ML archives.
FFmpeg issue tracker
Jai Menon jmeno...@gmail.com added the comment:
the crash should be fixed in r22711
--
status: open - closed
substatus: open - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1848
Jai Menon jmeno...@gmail.com added the comment:
This is the last review in that thread :
http://article.gmane.org/gmane.comp.video.ffmpeg.devel/98581
Either ping and hope that justin has a new patch. or clean it up and
submit.
FFmpeg issue
Jai Menon jmeno...@gmail.com added the comment:
no. of planes is hardcoded to 3 all over the place in snow and will
require a somewhat intrusive patch (one might even call it a feature).
till then, i suggest that we disable pix_fmt gray as input to the encoder
Jai Menon jmeno...@gmail.com added the comment:
@reimar : did you get around to committing this?
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue1753
Jai Menon jmeno...@gmail.com added the comment:
would it be possible to upload a complete sample? either that or dd'd from
the original at the start of a access unit/major sync header. I got the
sample to work (we just need to skip the lpcm header which is variable for
mlp) but i need to make
Jai Menon jmeno...@gmail.com added the comment:
correct status.
--
status: new - open
substatus: new - reproduced
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1731
_
Jai Menon jmeno...@gmail.com added the comment:
Limit has been increased so should be fixed at next major bump.
--
status: open - closed
substatus: reproduced - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Jai Menon jmeno...@gmail.com added the comment:
iirc it was agreed it should be done dynamically.
--
status: new - open
substatus: new - reproduced
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup
Jai Menon jmeno...@gmail.com added the comment:
done, but you will have to wait till next lavf major version bump. also
updated the title.
--
title: 20 streams limit - Allow dynamic creation of a/v streams and remove
MAX_STREAMS usage across lavf
Jai Menon jmeno...@gmail.com added the comment:
adding myself to the nosy list.
--
nosy: +jai
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1026
_
Jai Menon jmeno...@gmail.com added the comment:
Works as expected with current trunk.
--
status: new - closed
substatus: new - works_for_me
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Jai Menon jmeno...@gmail.com added the comment:
it might speed things up a bit if you can report which _exact_ past
revision worked
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1703
_
Jai Menon jmeno...@gmail.com added the comment:
config.err missing.
--
substatus: new - needs_more_info
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1701
_
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r21083.
--
status: open - closed
substatus: reproduced - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1299
_
Jai Menon jmeno...@gmail.com added the comment:
correct status.
@Anantharaman : please reopen if you feel this isn't fixed.
--
status: open - closed
substatus: needs_more_info - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
Jai Menon jmeno...@gmail.com added the comment:
this and a few other issues on roundup lead me to ask - should
max_analyze_duration default value be bumped up/calculated dynamically? or
should we just ask users to try out different values before reporting
bugs
Jai Menon jmeno...@gmail.com added the comment:
correct status
--
status: open - closed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue641
Jai Menon jmeno...@gmail.com added the comment:
correct status
--
status: open - closed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue641
Jai Menon jmeno...@gmail.com added the comment:
Yeah, sorry about that. I'll commit a buffer size check in a bit.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1624
_
Jai Menon jmeno...@gmail.com added the comment:
Yeah, roundup also replicated one of my edits 4 times :)
Is something like the attached patch what you had in mind? It fixes the
issue in this thread anyway.
_
FFmpeg issue tracker iss
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r20889.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1624
_
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r20886.
--
status: open - closed
substatus: open - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1310
_
Jai Menon jmeno...@gmail.com added the comment:
Should be fixed in svn now.
--
status: new - closed
substatus: analyzed - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue641
Jai Menon jmeno...@gmail.com added the comment:
Should be fixed in svn now.
--
status: new - closed
substatus: analyzed - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue641
Jai Menon jmeno...@gmail.com added the comment:
Should be fixed in svn now.
--
status: new - closed
substatus: analyzed - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue641
Jai Menon jmeno...@gmail.com added the comment:
Should be fixed in svn now.
--
status: new - closed
substatus: analyzed - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue641
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r20810.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1591
_
Jai Menon jmeno...@gmail.com added the comment:
hooking it up to yuv411p is wrong. this isn't a planar format. attached patch
might be more correct though i dont see the point since we dont accept yuv411
packed as input in the swscaler. i guess a complete patch would be welcome
Jai Menon jmeno...@gmail.com added the comment:
Please post a capture showing what a correctly decoded frame looks like.
--
status: new - open
substatus: new - needs_more_info
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Jai Menon jmeno...@gmail.com added the comment:
The output looks correct to me. If you want to reopen, please give comparative
screenshots which show decoding problems.
--
status: open - closed
substatus: needs_more_info - invalid
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r20758.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1593
_
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r20741.
--
status: open - closed
substatus: open - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1387
_
Jai Menon jmeno...@gmail.com added the comment:
Attached hack should fix it. I have no better ideas sadly.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1387
Jai Menon jmeno...@gmail.com added the comment:
I should've mentioned that I tested it against mpeg, mjpeg, mpeg4, jpeg2k and it
seems to work fine. Also tested with png and some other images which dont
support lowres and it just resamples to the requested resolution. Also
regression tests pass
Jai Menon jmeno...@gmail.com added the comment:
Hopefully correct output uploaded.
out.wav decodes to pure noise on my machine. Can someone confirm if that is what
was intended.
Thanks.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r19859.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1386
_
Jai Menon jmeno...@gmail.com added the comment:
People can always build libavcodec with whatever they want. Anyway, you might
want to propose something on ffmpeg-devel.
This is a feature request.
--
type: - feature_request
_
FFmpeg
Jai Menon jmeno...@gmail.com added the comment:
crashes are important.
--
priority: normal - important
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue839
Jai Menon jmeno...@gmail.com added the comment:
Fixed by Alex Converse in r16978.
--
status: open - closed
substatus: reproduced - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Jai Menon jmeno...@gmail.com added the comment:
The attached fix is wrong imho. I think this is a side effect of r19275 and
proper fix should include reading frame size as 32bit syncsafe integer, which
was what the earlier code used to do
Jai Menon jmeno...@gmail.com added the comment:
Support has been added as of r19222.
--
status: new - closed
substatus: new - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1109
_
Jai Menon jmeno...@gmail.com added the comment:
Support was added in r18818.
--
status: new - closed
substatus: new - fixed
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue751
Jai Menon jmeno...@gmail.com added the comment:
Support was added in r18818.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue751
Jai Menon jmeno...@gmail.com added the comment:
I think this is the same as issue 1106, and there is a known workaround.
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1202
_
Jai Menon jmeno...@gmail.com added the comment:
But as Justin said previously, there is no eac3 stream. So, if nothing else, we
should leave it alone and not create invalid AVStreams. How do we do this?
_
FFmpeg issue tracker iss
Jai Menon jmeno...@gmail.com added the comment:
The audio is pcm mulaw. patch sent to -devel.
--
status: new - open
substatus: new - reproduced
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Jai Menon jmeno...@gmail.com added the comment:
Fixed in r19166
--
status: open - closed
substatus: reproduced - fixed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1178
_
Jai Menon jmeno...@gmail.com added the comment:
FFmpeg output+bt+valrind output (if possible) missing, also this is not
critical. If you can reproduce the crash with FFmpeg, then probably it can be
changed to important.
--
priority: critical - normal
substatus: new - needs_more_info
Jai Menon reality...@gmx.net added the comment:
valgrind output is mandatory when reporting memleaks.
--
substatus: new - needs_more_info
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg
Jai Menon reality...@gmx.net added the comment:
patch posted to devel.
--
status: new - open
substatus: new - open
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1119
_
Jai Menon reality...@gmx.net added the comment:
change title.
--
title: jpeg2000 + lowres option = crash - jpeg2000 + lowres option doesn't
work with ffmpeg
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org
Jai Menon reality...@gmx.net added the comment:
I think I know what has to be done here
--
assignedto: - jai_menon
nosy: +jai_menon
substatus: reproduced - analyzed
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https
Jai Menon reality...@gmx.net added the comment:
nobody claimed they won't fix this.
--
substatus: wont_fix - open
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1125
_
Jai Menon reality...@gmx.net added the comment:
Fixed in r18955. Please try with ffplay instead of ffmpeg.
Something like ./ffplay -lowres 1 AVI-MJ2C_MP3.avi
I'm not closing the bug because this doesn't work with ffmpeg yet. I'm assuming
lowres handling is broken there. Please correct me if I'm
Jai Menon reality...@gmx.net added the comment:
nevermind, reproduced.
--
substatus: needs_more_info - reproduced
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1097
_
Jai Menon reality...@gmx.net added the comment:
for crashes, a gdb backtrace is required.
--
status: new - open
substatus: new - needs_more_info
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup
Jai Menon reality...@gmx.net added the comment:
I did send a GSoC application for this :) Anyway, if nobody else cares and I get
some samples to test, I'll probably work on it at some point.
FFmpeg issue tracker iss...@roundup.ffmpeg.org
Jai Menon reality...@gmx.net added the comment:
Is there any player which actually detects the audio stream or plays the file
correctly?
_
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/roundup/ffmpeg/issue1000
_
60 matches
Mail list logo
