Activity for MJPEG Tools
-
Debian Package created ticket #23
New release ?
-
Steven Schultz committed [r3517] on Svn
Sigh, revert getprogname use, it's presebnt on mac, etc but not linux
-
use getprogname() instead of __progname
-
Balló György posted a comment on ticket #43
All modern software use Git nowadays, so I think it would be the best choice.
-
Changgong Lee posted a comment on ticket #62
This error was discovered by a static analyzer, and trace was manually reviewed. I apologize that I can't provide a triggering testcase for this.
-
Sam James posted a comment on ticket #144
Thanks!
-
Thank you!
-
LTO type mismatch error
-
paatches applied
-
#143 patches
-
-Wimplicit-function-declaration in __progname configure test
-
patch applied
-
bug #144 fix
-
Systematic reencoding in second pass
-
Missing library when linking
-
LTO type mismatch error
-
-Wimplicit-function-declaration in __progname configure test
-
-Wimplicit-function-declaration in __progname configure test
-
I hit another issue with a 64-bit build: /var/tmp/portage/media-video/mjpegtools-2.2.1-r2/work/mjpegtools-2.2.1/lavtools/lav_io.c:37:12: error: type of 'AVI_errno' does not match original declaration [-Werror=lto-type-mismatch] 37 | extern int AVI_errno; | ^ /var/tmp/portage/media-video/mjpegtools-2.2.1-r2/work/mjpegtools-2.2.1/lavtools/avilib.c:57:6: note: type 'long int' should match type 'int' 57 | long AVI_errno = 0; | ^ /var/tmp/portage/media-video/mjpegtools-2.2.1-r2/work/mjpegtools-2.2.1/lavtools/avilib.c:57:6:...
-
Attaching patch.
-
LTO type mismatch error
-
gcc-15 build fix
-
patch applied
-
gcc-15 build fix submitted by trofi@users.sourceforge.net
-
Sergei Trofimovich created ticket #63
gcc-15 build fix
-
treating compiler warnings as hard errors would guarantee mjpegtools failure to build
-
Bernhard Praschinger posted a comment on ticket #62
That could be a problem. On a typically system the Int_Max it 4 byte, so width * height mus be larger than 4 bytes (2147483647) means that the resolution needs to be larger than 46340 (width) * 46340 (height) pixels. It's quite unlikely that this happens and I think that a lot of other tools in the encoding pipeline can handle images at that size. Can you give a practical example how that overflow can be triggered ?
-
Git is much better than SVN.
-
Git is supported by SourceForge, it should be easy to switch.
-
Switch from svn to git
-
This ticket is misplaced. It should be opened with Sourceforge. The active developers have voted to continue with svn until Sourceforge removes support.
-
Switch from svn to git
-
Potential Overflow at `pnm2y4m.c`
-
Require a version of JPEG library that implments pkgconfig. Version 9c or newer
-
fix mispelling
-
mplex will never create IFO files. similarily nothing will ever be done for SVVCD surroundsound support
-
patch submitted by randrianasulu@gmail.com to add 44100 and 32000 sample rate support for LPCM audio
-
cleanup - remove unneeded debug ifdef
-
check in updated auto* files
-
commit to celebrate meeting of developers in Jamestown ND - clean up some comments
-
minor cleanup
-
remove .h file only used in one place
-
-no-cpp-precomp hasn't been required my OSX / macOS for the last ten revisions of the operating system. It is time to remove the un-needed flag.
-
dga was used nowhere (has not been used for eons). Some general comment cleanup
-
MJPEG Tools released /mjpegtools/2.2.1/README.txt
-
bump truck micro version to 2.2.2
-
Create 2.2.1 RELEASE tag
-
-
-
-
-
-
-
-
-
A smal change to be able to generate the RPM
-
A for the project important person was missing.
-
Hallo, there is now a fix in the SVN that addresses that problem: https://sourceforge.net/p/mjpeg/Code/3496/ Take a look at it, lookes good for me and adresses the problem,
-
potential buffer overflow in audiolib.c
-
env variable could be too large for error_string - limit output in error message
-
Wooseok Kang created ticket #142
potential buffer overflow in audiolib.c
-
remove un-needed declaration
-
remove unused variable
-
remove unused variable
-
remove unused variable
-
properly conditionalize 'hn', remove 'frame_number, add <math.h> to fix these
-
remove unused variable res
-
properly conditionalize the vectorscope variables to avoid these warnings:
-
remove unused variable
-
remove variables identified by:
-
unused variables were producing warning errors:
-
sumtop_acc and sumbot_acc set but never used. removed
-
if pointer is null don't compar it to a 0 character
-
gcc 7 saw that a height_pad was set twice but never used. variable is
-
bump micro version number - the repository version now differs from the 2.2.0
-
Remove incorrect tag
-
Create 2.2.0 RELEASE tag
-
-
-
Create 2.2.0 RELEASE tag
-
-
go away
-
-
Create BETA 2.2.0
-
remove tag
-
another obsolete file goes away
-
Create BETA 2.2.0
-
-
-
-
one last time :)
-
last bit of restoration
-
restoring from backup
-
restoring from backup
-
continue recovery from delete error
-
what a mess but coming together
1 >
