Welcome, Guest. Please login or register.

Author Topic: PPC Gif datatype  (Read 996 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline AmigazTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2004
  • Posts: 1959
  • Country: se
  • Gender: Male
    • Show only replies by Amigaz
PPC Gif datatype
« on: February 25, 2007, 10:23:38 AM »
It puzzles me why there's no Gif datatype for WarpUP pr PowerUP when there's lots of other pic datatypes for example WarpDT...is it some sort of copyright issue  :-?
-------------------------------------------------------------------
Amiga 4000T - A3640 '040
Amiga 4000 - CS MKIII
Amiga 1200 - Blizzard 1230 MKIV
Amiga 1200 - Stock
Amiga CD32 - TF360
A bunch of ol' A500's
 

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show only replies by Karlos
Re: PPC Gif datatype
« Reply #1 on: February 25, 2007, 10:47:42 AM »
If you think of the most common uses of gif, its probably the case that such a datatype would be pointless.

Image formats that are used for large, detailed images benefit from the horsepower. As you go down the data size / decoding complexity scale though, context switching alone probably becomes the dominant factor.

For images below a certain size for "simple" formats like gif (which let's face it, is used a lot for small images) flushing the datacache of your PPC and 68K likely involves moving more data than decoding this smiley :-D for example. In such cases, it would actually be slower to call the PPC than just do it on the 68K.

-edit-

In my opinion, smart datatypes for WarpUP / PowerUP should estimate the output data size and use a PPC or 68K decoder depending on that. There could even be a preference setting to determine that threshold, rather than hard coding anything.
int p; // A