#Let's use more JPEG
15 messages in this thread
Martin:
This is something I've been meaning to leave a message about for a while. I
applaud your use of JPEG for uploaded images. Why are we all still fighting
with hugh file sizes to download anything with any sort of decent
resolution/color depth with zipped TGAs or GIFs? I'll round up a couple JPEG
utils that I've dl'd from elsewhere and put 'em up for those what ain't got
'em, and we'll start a revolution, eh?
Dave
David,
Well said! My file is a lot smaller and looks a lot better as a JPEG then as a
.gif – the best of both worlds <g>.
David,
Sure would like an education on using JPEG, especially as a DLL in a Windows
app I'm trying to develope.
–TR
Todd:
You'd probably be better off asking/looking in the GRAPHDEV and GRAPHSUP
forums, but a company called OPTIBASE offers the Optibase OptiTools SDK
developers tool kit for JPEG and image processing. They also have something
called the JPEG Workshop which allows you to use JPEG images with any app
supporting DDE. You can contact them at OPTIBASE, Inc.
7800 Deering Ave.
Canoga Park, CA 91304
1-818-719-6566
1-800-451-5101
1-818-719-9028 BBS
They also have coprocessor boards to enhance speed and to do a lossless
version of JPEG.
Hope this helps.
Dave
David,
Thanks for the info, I'll give 'em a call.
–TR
Try calling LEAD Technologies (704 549-5532). They have a pretty good library
for imaging compression (JPEG and all). I have the library for DOS, Windows and
for PharLap (32 bit dos extender). It works great.
Gus, I just read your overview of the IPAS toolkit in the latest issue of 3D
Artist. I want to know more! Pyros gave me your home phone number, can I call
you? (Just kidding.)
Last night I installed the Metaware compiler and the Pharlap kit. And the IPAS
kit. I think there's a lot of forum members who'd love to have a thread where
IPAS-creating topics were discussed. Would you care to expand upon your
article? What comes next?
Next? I don't know. I'm still trying to fight through my daytime "formal" job!
(at least I get paid for that one)… This has been a lot of fun (in a warped
sense of fun, that is) but I still have to "deliver" a product by October.
'till then, I'm in worse shape than Gary's R3 shipping (and mind you, my PM
ain't nothing like Bob Bennett, shame, shame, shame…)
Call me? Sure, just make sure you do it between 9pm and 6am. Then I sleep from
6 to 9, go to work, back at home around 6, take a look at my family and around
it goes…
I'm not much of a thread starter (yeah, right…). I suggest you just pose some
questions and we start from there. If you just installed everything, it should
take you a couple of hours to get accquainted (sp) with the environment anyway.
I don't really want to call you… I was just kidding. If we start an
auction, I'm sure we could raise the price for your home number. 🙂
I'm still in that getting-to-know-you stage. I've been programming PCs since
before IBM decided to make one, mostly in C with a little assembler. And
although I've debugged Windows "thunks" and DLLs, all the implications of
32-bit DOS and extenders is making my head spin. I've never had to deal with
this area of PC-dom before. Actually, I bet the Yost Group programmers could
jump in here, too. They've had exposure to Motorola processors and flat
address space before. (What's that, a troll in the corner? No, it's just a
Tramiel. 🙂
I am primarily an assembler programmer. I use C for stuff too painfull in
assembly but I always find myself back to good old asm. It just hurts me to see
the junk code C generates when you demand speed. For user interface stuff C is
just fine. In my FILM.IXP routine, where over 4 billion calculatios are
performed, it was taking over 5 minutes per frame. It's now down to 35 seconds.
I did a lot of Windows device drivers and VxD's. That started before Windows 3
was released and now is NT (although I'm still not impressed by this behemoth).
This 32 bit DOS extender is actually a breeze to program due to the freedom you
have to do whatever you want. But because of that same freedom, you have to
take care of everything the OS would normaly do. I prefer that way because I
know what to expect. The only problem is that, because so few people use this
thing, not much of a "after market" exists in terms of tools. You've got to
write everything yourself.
Motorola processors are all right. What sucks are the OS' around them (yeah, I
know DOS ain't no spark of brightness, who said I care about DOS <g>. It's, in
fact, just a file system which you can do whatever you want on top of it or
disregard it altogheter). The biggest (and probably only) advantage I see in
programing PC's (and subsequently, DOS) is that there are 1 quazzilion PC's for
every McNerd or whatever out there. Which market would I prefer?
Oh, well, back to work…
Hey, I started my business in the Amiga market, you don't need to tell me about
market size. 🙂 When you say 32-bit DOS extender stuff is a "breeze", what
do you mean? And what sorts of tasks do you need to handle that the OS might
normally do?
All sorts of things. Handling exceptions, hardware contention, CPU state,
memory contention, memory translation (protected x real), etc. PharLap provides
a good deal of memory support (preallocated selectors pointing all over the
place) but is pretty basic when it comes to hardware exceptions and no support
whatsoever to multitasking.
Todd,
A recent PC Mag (either this issue or last) had a whole section regarding
compression types including JPEG. Does a pretty good job of explaining.
Ang
The Issue is Vol12 no 13 of Pc Mag, Page 371. ken
Todd,
A recent PC Mag (either this issue or last) had a whole section regarding
compression types including JPEG. Does a pretty good job of explaining.
Ang