Import 4000x2122 JPG = BLACK | Inconsistent

gordonmcdowell wrote on 1/27/2010, 9:30 AM
I can only assume someone else has posted this question and I can't find it via forum search... I'm trying to import photos into Vegas 9.0 64-bit, and some of them render black on the timeline (that includes preview scrubbing).

This has happened only recently with my current install, but I can't imagine what I might have done to muck up Vegas on my Win7 box, unless it was a system update (I have allowed Microsoft to update the OS recently).

Is anyone else seeing this? It has impacted 2 projects, each with under 10 photos imported. None of the photos are crazy high rez. And by taking a photo which which appears black on the timeline, exporting it (using Paint.NET) to another format and/or size, that image can be imported but then another image renders black.

It is like whack-a-mole.

I ended up rendering the project in pieces (render each photo at a time with needed panning into uncompressed video, then replace the photo in timeline with pre-rendered video snippets), and compiling it. That's the exact same madness I was dealing with Vegas 32-bit, except the whole program would crash instead of render missing photos. (And that was only with LARGE projects... right now I'm working on very simple projects.)

Sometimes I can make a photo visible by altering the panning & zooming motion of the video event. But just like importing an alternate version of the photo, that too often makes another photo turn black when scrubbing/rendering.

To make a project stop showing all its video, I import an .m2ts (AVCHD) video clip, and adjust the panning on the photos. Photos that were previously solid now flicker or turn black when scrubbing. There's nothing particularly odd about the video clip (one 26 minute clip). And I can't guarantee it is THAT clip... this is impacting 2 projects right now, which share zero photos or video.

I'll submit an error report to SONY, but if anyone has noticed this and knows a work-around or fix, please let me know. I can say it doesn't matter if the photos are JPG or PNG or small in size, as I've tried to find the limitation and work around it by exporting different types of photos.

Comments

R0cky wrote on 1/27/2010, 10:49 AM
I have similar behavior to this happen all of the time. I have a couple of support requests in. Sony told me they reproduced problems I have with large stills as you described.

Do you have generated text in your project? I have noticed lately that seems to make it worse.

Rocky
xberk wrote on 1/27/2010, 11:10 AM
There's a known problem with JPEGs and PNGs of any size with 9.0c 64 bit. I don't see the problem in 9.0b .. Sony has promised a fix in 9.0d ..

JPG problem

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

gordonmcdowell wrote on 1/27/2010, 1:34 PM
Ah! Good to know. How did YOU know there was a problem? I couldn't spot it... just from monitoring these forums?
gordonmcdowell wrote on 1/27/2010, 1:37 PM
In one of the projects no generated text at all. xberk replied it is a known issue in 9.0c, so... I sure hope they fix it in 9.0d.

I don't consider myself a big budget environment, but I wonder what it is like when there's hundreds of thousands of dollars at stake, and a project gimps up like this. If it drives me crazy, it must drive people working on big budget productions nuts (nuts > crazy).
xberk wrote on 1/27/2010, 7:52 PM
Gordon --- When 9.0 64 bit came out I was an "early adopter" -- 8.0c was very solid -- many here are still using it. . I paid the price for "early adoption" and did some posting here to warn others. But even I was careful not to work in 9.0 for something I really didn't want to screw up. Most of the problems I cared about got fixed in 9.0b. I know the limits of 9.0b 64bit and 9.0c 32 bit and what I can safely use each for. This takes experience.

Big budget folks generally should not work with any software or equipment that they don't trust based on a proven track record. That's common business sense. -- hence they generally are conservative and use the "the devil they know" versus the "new devil they don't know". Vegas 8.0c would be the "devil they know" right now. And I think it is true that this forum helps many decide when it's "safe" to upgrade to a new version for important work.

Keep reporting the bugs you see with as much clarity and brevity you can muster. It helps us all.

Paul

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

R0cky wrote on 1/27/2010, 10:58 PM
I never thought 8.0c was solid with HDV. Std def maybe but I do nearly all hdv and/or large stills. I went to windows7 x64 and Vegas x64 to try and leave a few bugs behind. It helped some but nearly all of my plugins only work in 32 bit so I have to go back to 32 bit, render out and back into 64. So I have all of the 32bit render issues still.

The problem with large stills has existed for me in Vegas 9a,b,c, 32 and 64 bit.