Okay I'll bite... and learn yah something.
PVD is basically by all rights very similiar to a website - it uses css and xml as for it's templates - I think we can agree on this.
It is well known the smaller you can make the weight of a page - the faster it will load. - we can agree on this as well I'm sure.
In the above example you show two images - okay lets take the last one - the heaviest one - the one you like and optimize it.
say at 65% and with an online optimizer as well.
With PS I can optimize it even better with better results and I'mm sure there are some good online sources to do the same.
Attached is the second image - opitmized at 65% as mentioned.
It came in at 119k versus your 200+k original
I saved you over 100k - which will load faster at full rez - the 119k of course.
Now PVD loads from what I've seen, at start-up all templates.
If I lighten the load of all the templates by say - 3 4 5 megs. Saving PVD the load time of those megs...
it will effectively load faster.
let me give another example - one I just did last night.
I had 166 files loaded with posters in a PVD database.
as it was - with no optimization - it weighed in at in total - 14megs
After optimization - with all the same size images - and pretty damn near the same clarity it weighs in at less than three megs.
So lets say you have 1000 images for a 1000 movies - each weigh say 200k each.
That comes to... what a mear 100 megs of photos - then add your database itself. that's a pretty heavy database.
So now you want to share it - so lets say with data base your at 120megs
Zip it up - say 4 files at 30 megs each or 2 at 60 - what have you. Not unreasonable this day an age.
But now look at my same 1000 movie database - optimized to have all images at 10k
and I'll be generous and say my database is the same 20megs
- My total is a mear 30megs of data including all the images. And i gave up nothing except a small amount of quality.
Most people will look at a preview - skim it. then open the file or aply it - they want to see what it looks like with their data in place.
Do you really go through your data base and look at all the preview images? Or more honestly do your preview images simple serve as a reminder of what the movie or song or album was? And then either play or go - "oh yeah, I remember what that song or movie was" and move on or play it.
Same with the preview of the template. At least for me - I skim through the previews and select the one I want to try.
Even if - you wanted full screen previews - there is no reason for the file sizes.
PNG for a preview image - the weight per image is way to big.
Go to a JPG and optimize it - add a tad of sharpening or clarity and you drop 50% or better off a JPG. Let alone what you save off a PNG.
You currently have templates with not a full screen preview that weigh in at 1meg. A full meg for a preview image... totally un-nessasary.
If you drop the weight of the contents of the app - it will run faster I gaurantee it.
image your 1.75 Terri database only weighing in at 750 megs or less once optimized.
Bet searches would be faster
- load times cut.
Faster all round.
just my two cents but - bet mine runs faster now it's optimized even with a mear 166 titles. Actually
- I know it does.
[attachment deleted by admin]