*Originally posted by playamarz *
First off… Chill the **** out man… No need to bring the level of this thread up beyond what it is suppose to be… A normal discussion.
Let’s answer to this first. My expression of “WHAT THE HELL ARE YOU TALKING ABOUT WILLIS?” was intended as a facetious remark. Ever seen the show Different Strokes? If you haven’t, I’m sorry you thought I meant this as an attack. But I’ve written many posts on this precise matter - the need to focus on the topic at hand and the detriment personal attacks cause. And you’ve read them… so you know I didn’t mean it like that.
No you’re right… it doesn’t mean the total “pixel” information would be gone but… There is a certain reason WHY flash is based on the floating point emulation system instead of just pixel by pixel. First off… When doing things mathematically instead of rasterising an image pixel by pixel it has to be done by floating point instead of rounding or else the desired result would look really screwed up.
Maybe I should have been more clear on this point. I’m not talking about rounding the position information… of course, that always needs to be kept. But I’m talking about drawing at whole pixels… then antialiasing if necessary. Not antialiasing to resolve some of these issues. When this happens, there’s a loss of definition, which is what I meant to convey with my example of pixeltext. Yes, it’s not entirely accurate, but I doubt anyone can notice a margin of error of half a pixel, even at 640 by 480.
Imagine the path a parabola would take if it just used pixel locations instead of an exact location as defined by Flash. It would look rather blocky and you could see the pixels depending on the area of view and zoom distance… Also… it would look differently on everyone’s screen! Having a screen at 800 x 600 would make the image look larger when compared with a screen at 1024 x 768. With Flash… Of course this is also going to change… But with it you still have the same object… Whether you zoom in 20000 times or zoom out 20000 times… You won’t see any pixels… Just smoothness. Photoshop can not do that. Because it is based on singular pixelised pieces of information.
I don’t really understand why you wrote this. If anything, it proves my position that photoshop should be vector based… Images would look as good as possible at different resolutions.
Yeah I have looked at the history palette. Would call you a smart *** for that comment but I’ll save it up for my explanations. And the fact is when you load up a .jpg it comes with a history palette that has absolutly nothing in it… Am I correct? Taking a floating point emulated vectorized graphic from Flash and using it in a photoshop oriented environment would cause the vector image to lose all of it’s floating point pixelized locations and require it be transferred over to the standard Photoshop non-vectorized locations.
The argument is not for taking vector information and putting into a pixelized environment. The argument is for photoshop to work in vector form. This doesnt mean that EVERYTHING needs to be vector-based. After all… flash handles gifs, jpgs, bmps, etc. pretty well. So does Illustrator… I’ll continue my response below…
Now… If you guys are trying to tell me that a photograph (because that’s the main reason photoshop is there) can be handled vectorized better than rasterized you guys are flippen crazy. Read my response below to find out why.
I’ll show you right now how much simpler it is to plot stored raster pixels than is to mathematically plot pixels for larger images. I will show you proven facts and how the computer works.
These are actual lines that a computer goes through to display a raster image on your computer. This is measured by clock ticks. Which I’ll explain below this.
- Tick 1 : The computer tells the program a graphic instruction is coming up.
- Tick 2 : The program tells the computer a pixel dra is coming up.
- Tick 3 : Your program tells the computer the x-coordinate of the pixel.
- Tick 4 : Your program tells the computer the y-coordinate of the pixel.
- Tick 5 : Your program tells the computer the color of the pixel.
- Tick 6 : The computer rendered the pixel.
- Ticks 7-12 : Uses overhead calculations the operating system has to perform to actually take the virtually rendeder pixel in the buffered state and throw them onto the real screen.
So… if we had a screen at 800 x 600… That would be 480,000 pixels. That’s a grand total of 5,760,000 clock ticks to fill up the entire screen.By the time your screen is filled it has done nearly 6,000,000 clock ticks… Now that’s alot… When running on a 600 mhz machine you will note that you can plot 600,000,000 clock ticks per second… Technically that would leave us with 104 frame per second… But it would actually be lowered down because of all the other applications running while your application was running…
Now that you know the set up for plotting to a screen and all the clock ticks it takes you will udnerstand why vectorized isn’t always the greatest thing to use.
Now… When a vector based program plots stuff on the screen… It first does a calculation to define where exactly the pixels are located and how they need to be viewed.
So… let’s do a small comparison… A box that’s 100 x 60.
Doing a box only would be great for vector… Pixels it would be this… 4 bytes per pixel (red, green, blue, alpha) would make this… 6000 x 4 or 24,000 bytes. 2.4 kb’s to round it off. That’s standard… Butfor vector it would tell the program firt… Okay it’s width is 100 and it’s height is 60… Just say… 100 times 60 and then do it that way… Easy enough… it would use the area calculation to define where to set up this place. But now… let’s take a larger example…
A photograph… Well… Every pixel would have to be defined by a certain formula to find it’s location in vector… But for raster… it would all be stored… No need to “find” where the pixel is placed… it’s already stored so I can just pull out the information and read it. With vector it would have to be like… Okay there is a small line in this… Let’s use the line formula to figure out how this line would display itself… let’s figure out the rotation for it and everything and what color it is… And then it’ll give you maybe… 20 pixels in that line.
Now… if you have the computer to do this… It would still be the same… But that’s just a line ina photograph… Imagine the rest of them… A small pixel would have to be found by using locations theories instead of formulas.
I never said photographs should be handled as vectors. And anyone who endorses that idea has lost his head. Precisely because of your argument. CLEARLY there is a dividing line for when vectors are better for drawing (which would be the realm for of gifs) and for when pixel-based drawing is better (the realm of jpegs). Saying that a program should be vector based does not imply that EVERYTHING should be handled vector based. After all… flash and illustrator are vector based… yet they dont convert jpegs into path info. And to tell you the truth, I feel kinda insulted that you should imply that I think describing a photograph with path info is better.
Plus, you use a jpeg as an example. But they don’t apply at all to what we’re talking about. Jpegs are analogous to vector drawings in that they are made up of formulas for drawing. JPEG is a standard that uses a compression method that uses the color information one pixel to determine the color of the adjacent 8 (that is not entirely right, but I really don’t want to get into it). Jpegs are used for permanent storage, and what we’re talking about is the ability of photoshop to create effects based on pixels. Photoshop doesn’t compress the information it works with. So jpeg should have never come up in this conversation.
I admit… vector makes it look better… And with the speed computers have now we can afford to waste a couple of extra clock ticks here and there… But the fact still stands that it’s better to handle photographs pixel by pixel instead of figuring out where the pixels are before placing them.
yeah, and I never said that photographs shouldn’t be drawn pixel by pixel.
And I never mentioned anything about Photoshop saving images with embedded vector information. Photoshop could save files as jpegs or bitmaps for all I care. But the advantage of Photoshop being vector based would be that everything would be easier to handle… you could specify the size of a new object, or the position of a photograph, to the pixel. Plus, it would take less memory.
You have to make sure to recognize the difference in these two topics. One is Photoshop working vector based. The other, which you were mostly talking about, was a file format with vector based information. The first one was what I was talking about… And everyone can recognize that it’s easier to manipulate the size and position of objects in flash than in photoshop, and that flash working files take less memory space (the reasons why I want photoshop to be vector based). As for the second topic… that would be the best format EVER!
Come on… let’s have a beer.