but then the program should be epic too![]()
but then the program should be epic too![]()
Epic is from Simoncelli:
----------------------------------------------------------------------
--- EPIC (Efficient Pyramid Image Coder) ---
--- Designed by Eero P. Simoncelli and Edward H. Adelson ---
--- Written by Eero P. Simoncelli ---
--- Developed at the Vision Science Group, The Media Laboratory ---
--- Copyright 1989, 1990, 1991, 1992, Massachusetts Institute of ---
--- Technology. Copyright 1993, 1994, 1995 University of ---
--- Pennsylvania. All rights reserved. ---
----------------------------------------------------------------------
Encode, you can name it PicPack, Picomp, Imaginator, ImgPack...
Maybe u can use some of the HEVC intra-picture predictors, which are not patented, for further compression improvements?
http://en.wikipedia.org/wiki/FELICS maybe this too?
Last edited by thometal; 14th October 2012 at 17:04.
I was too lazy to think up a good name for my last compressor, so that's what I called it![]()
I think I will keep it as BIM. What is BIM? Firstly, BIM sounds like "beam" - a beam of light - something related to the light and a light as a part of a beautiful and natural picture. Secondly, this is an algorithm name. And hence, things like superpack,imagepack,supersmasher not work here. So, B stands for Blended predictors and IM stands for Ilia Muraviev.
I wish I release it very soon, since its development took me to the matrix - for a past few days I had no sleep - experimenting and testing it overnight and then all day long. I may not recall any of my program that I worked so. Anyway, I developed very interesting things like shape detection, smoothness/edgeness detection, noise detection etc. BIM is really smart. I pushed the compression to a new level, current version with all its whistles and bells beats BMF nearly all the time. And BIM is relatively simple, this makes me think like BMF is old and outdated. Anyway, I forced to keep it simple and fast, so I will keep only mean compression components - which are the most important in terms of compression ratio gained vs computational complexity!
![]()
could be a screenshot of infinity from space =P) but nice can i get a view for linux too =P
New results (slower, but better compression)
No code has to be inserted here.
Squeeze Chart
No code has to be inserted here.
GARTEST
No code has to be inserted here.
![]()
Just wrote a simple CRC64 calculator to test Win2K/WinXP compatibility and Unicode support.
Compiled using Visual C++ 2012 + Intel C++ v13
Windows XP / Windows 2000 users, please test both executables (crc64.exe - 64-bit EXE, crc6432.exe - 32-bit EXE).
And to all users, please test both executables on non-English named files!
Thanks a lot in advance!
Output example:
Code:D:\crc64\x64\Release>crc64 * C6237DEEE5156A9F *crc64.exe 0B28CDD4DE446909 *crc6432.exe 9E79F0CE0D898DBB *ENWIK9 0000000000000000 *New Text Document.txt ; Elapsed time: 1.84s D:\crc64\x64\Release>crc6432 * C6237DEEE5156A9F *crc64.exe 0B28CDD4DE446909 *crc6432.exe 9E79F0CE0D898DBB *ENWIK9 0000000000000000 *New Text Document.txt ; Elapsed time: 2.137s
Dear Mr. Encode,
both programs (crc64.exe and crc6432.exe) produce same wrong output "This program is not valid 32bit application." I use Win XP SP3 Czech version (32 bit).
Sincerely yours,
FatBit
Very sad, but such thing was expected. Visual C++ 2012 is not compatible with Windows XP. Actually, this forces me to skip back to Visual C++ 2010.
The support for WinXP has been re-added, redist: http://www.microsoft.com/en-us/downl....aspx?id=30679
Visual Studio 2012 Update 1 notes: http://blogs.msdn.com/b/vcblog/archi...available.aspx
I only saw some websites so I don't know if it's practical to use, but it looks at least promising.
I am... Black_Fox... my discontinued benchmark
"No one involved in computers would ever say that a certain amount of memory is enough for all time? I keep bumping into that silly quotation attributed to me that says 640K of memory is enough. There's never a citation; the quotation just floats like a rumor, repeated again and again." -- Bill Gates
Changing Platform Toolset is the same as changing actual compiler/build tools. As example, if you have different versions of Visual C++ (2008/2010/2012) or Intel C++ installed, you may choose which compiler to use. If you'll choose Intel C++ or Intel C++ alone, I'm not sure which libraries Intel compiler will pick. Note that provided executables were compiled with Intel C++ v13. I guess the only way is to uninstall everything and install previous versions of Visual Studio/C++...
CRC64 Visual Studio 2010 compile
Dear Mr. Encode,
mesage from me: crc6432.exe works on WinXP SP3 Czech edition (32 bit). CRC64 produces message "This program is not valid 32bit application." I will test more on awful file names.
Sincerely yours,
FatBit