I copied a logo from a web site and stored it in explorer as a .png file. When I import it into the timeline, instead of being a primarily red logo it is now primarily blue. It appears the red has been replaced by blue. Can you help?
I think that Eugenia is referring to an image editing application such as Photoshop, PaintShop Pro etc. If you import the png into a program like these they will allow you to save a png file that is reliable and which conforms to the png standards etc. It sounds like the png you downloaded was not in a format that Vegas was happy with.
If you haven't got an image editing application I believe that there are some online sites that will allow you to convert to different image types (but it would really be better to do it in an application which you have got installed on your computer as I daresay you're gonna be wanting to create more images for Vegas etc).
is the link to the logo. The logo in question is the red Force logo with the screaming flying soccer ball.
One other piece of data. I'm using Movie Studio 6. When I pull the same logo into either Studio 9 or Vegas Pro (both demo downloads) it is fine. Maybe there is something weird about 6.
Thanks for all the help and the input. I am filming soccer games for the Force for the purposes of training so my output doesn't need to be amended with a ton of bells and whistles but since I have the SW I figured I might add a few things.
Or is it as simple as the Preview overlay being set to Blue?
Click on the drop-down icon that looks like # and see if Blue is selected. If so, change it to Safe Areas or just click on the # to disable the overlay.
I've been around here for quite a while (but not as long a Kelly) and I do remember a post a long time ago about somebody having trouble with PNG's coming into VMS with the wrong colors -- not just a color shift, but a strange color "swap" as you are describing. I searched the forum ("png bug", "png wrong color" etc.) but have not found that thread. It may have been 2 or 3 years ago.
Anyway, at the time I think we concluded it was an actual bug. Also I *think* (but can't confirm) that the poster might have gotten a response from Sony that confirmed it as a bug.
The fact that it works correctly in newer versions might back that up.