Closed GoogleCodeExporter closed 9 years ago
I can verify this. (or +1 if you like)
Linux - fedora 14
Original comment by dan...@stormstudios.no
on 22 Mar 2013 at 1:12
Crap, indeed. Add { "reel", "reel_name" },
in libavformat/movenc.c line 2958
I'll wait a little and release a rc9. Sorry about that.
I can give another fixed tar.bz2 otherwise
Original comment by baptiste...@gmail.com
on 22 Mar 2013 at 7:23
Hi,
I already have a workaround, so I'm safe for the moment.
Seriously HUGE thanks to the great work done till now on FFMBC, I really
appreciate it!
I was wondering if I could request a feature:
It would be nice to be able to specify the starting frame of an image
sequence like FFMPEG does it.
for example one starting at frame 0400:
ffmbc -i "/path/to/sequence.%04d.exr" -start_number 400 "output.mov"
I tried this with:
ffmbc -ss
but it seems to fail cause it's expecting to find the frames 0000 or 0001.
Alot of my sequences start at 1001.
Anyways, keep up the great work!
Original comment by heinen.o...@gmail.com
on 23 Mar 2013 at 8:45
Please excuse me i I'm double posting here.. Tried replying through email.
I tried adding { "reel", "reel_name" } as described above, but no luck.
Anyone else had success with this?
Thanks,
-Daniel
Original comment by flehnerh...@gmail.com
on 26 Mar 2013 at 3:58
-*Bump*-
I successfully applied the patch in issue #114 solving the color shift, but I
need the reel name to work as well.
Any tips are more then welcome :)
Thanks!
Original comment by flehnerh...@gmail.com
on 26 Mar 2014 at 11:56
Original comment by baptiste...@gmail.com
on 1 Apr 2014 at 4:34
Original issue reported on code.google.com by
heinen.o...@gmail.com
on 22 Mar 2013 at 11:13