split screen view with clipboard is red

set wrote on 2/6/2013, 7:24 PM

Yep, it is happening too in my system, looks like a new bug.

Set

wikksmith wrote on 2/7/2013, 6:19 PM

Same problem here. It occurs on both of my PCs, which differ in all components, but are both running Windows 7 Pro 64-bit.
Donald

OldSmoke wrote on 2/12/2013, 6:51 AM

Confirmed here too. Has this been reported as a bug?

wikksmith wrote on 2/14/2013, 8:38 AM

I submitted a request for help on this on Feb. 7. Not a word from Sony.
Donald

vkmast wrote on 2/14/2013, 8:52 AM

Don't expect too much too soon. Last time I reported an "incident" (replicated on the forums inside a few hours), it took 82 days to be "logged as a bug". Not fixed yet though.

Satevis wrote on 2/14/2013, 9:24 AM

Looks like a bug, indeed. I'll pass this along.

vkmast wrote on 2/15/2013, 3:21 PM

It took only 3 days from tech support this time to response to this issue thus

As a troubleshooting step, please navigate to C:\Users\**username**\AppData\Local\Sony\Vegas Pro\12.0\Media Pool Thumbnails (where **username** is the actual account name on your machine) and delete the contents of the folder named: Media Pool Thumbnails. Then restart Vegas.

Pity that it did nothing to solve the problem...
Maybe this week's stock reply.

OldSmoke wrote on 2/16/2013, 1:23 PM

I switched back to build 394 and the split screen is working fine. Not what I wanted but it will have to do for now until it gets fixed again.

Peter Riding wrote on 2/16/2013, 4:07 PM

I had the red screen in different circumstances but the cause and solution may be the same.

I found via Creative Cow threads that the red screen is an indicator of "your resources are too low".

Tried a few things but in the end switching off GPU acceleration in preferences did the trick.

I am running Vegas 12 Pro build 486, with an i7 processor, 12gb ram, Windows 8 Pro, Nvidia 570 card with 310.90 update, etc etc etc In other words there was no good reason for it to crash but that just seems to be the way of things with GPU acceleration - a lottery.

I was getting the crash when trying to run stills slideshows using PNG images of the same spec I have used many times in multiple projects in pevious builds. I was not getting it when running just video files. Also I was not getting it on my laptop - which is also high spec but does not have GPU acceleration.

Pete

OldSmoke wrote on 2/17/2013, 5:08 PM

I doubt I am low on resources with a i7-3930K and 16GB of RAM and a GTX570. Switching OFF GPU acceleration didn't help either for Build 486. Any other tricks you know off? Btw, Vegas doesn't crash; it just shows a red preview screen when I want to compare against the image in the clipboard. I installed a Windows Clipboard Viewer just to confirm that the image is actually captured in the clipboard and I can see that it is. Build 394 is working fine.

Peter Riding wrote on 2/18/2013, 8:07 AM

I doubt I am low on resources with a i7-3930K and 16GB of RAM and a GTX570

Thats what I thought of my own system as well. Doesn't make sense.

I've installed the latest driver from Nvidia - 314.07 - which I think only came out today, but no joy.

I resent now that paid £260 for the 570 card over a year ago and in that time Vegas has promised so much and delivered so little when it comes to GPU acceleration. I might as well have saved my money.

Pete

OldSmoke wrote on 2/18/2013, 11:32 AM

Pete

I am extremely happy with my GTX570 which is about 30% faster then my old GTX460. GPU acceleration does work very well here and provides a more then 100% improvement over CPU only, even when compared to VP10e on the same system. I can render SCS own VP11 benchmark project to AVC/MC 1080p in 38sec with GPU on but it takes close to 120sec on CPU only. The drivers make a huge difference too. Anything higher then 296.10 and it will slow down dramatically; with some drivers up to 50%. My recent project was a 3 camera setup (2x HDV, 1x AVCHD) with a total of 7 audio tracks, color correction to equal the three cameras and many transitions too and I have realtime playback @Good(Full) in Multi-cam View from the timeline to a full size 40" HDTV... I cant ask for more.

OldSmoke wrote on 2/22/2013, 6:45 AM

I am just wondering if anyone got a reply with regards to the red preview window from SCS; I haven't.

vkmast wrote on 2/22/2013, 7:08 AM

Old,
see my post above 2/15/2013. I got another useless response 2/20/2013.
(Please disable Startup applications and Background Services.)
Still trying to get this issue logged as a bug if nothing else.

OldSmoke wrote on 2/22/2013, 7:49 AM

But... you got a response. I wonder who is responding because even one with simple knowledge about computers and windows would give a better response or better none at all.

vkmast wrote on 2/22/2013, 8:05 AM

Old,
PeterDuke nailed it in another thread recently.
Eventually with a bit (lot?) of luck you will convince someone to actually try your test that you specified in the original email.

OldSmoke wrote on 2/22/2013, 8:48 AM

Well said! I am also surprised that not many others have jumped on that issue. Is it really that it only effects a few users or a true defect... I hate the word bug. Maybe I am just doing too much for clients getting every shot to look the same? That is also my first serious issue I have with a new build and the first time I am trying to get help from SCS; lucky me I didn't erase the build 394 which works fine.

rs170a wrote on 2/22/2013, 8:57 AM

lucky me I didn't erase the build 394 which works fine.

Even if you did, you can still get it from the Sony archives.

Mike

OldSmoke wrote on 2/22/2013, 10:48 AM

Mike

That is a great link! How did you come to know about it? Is that public knowledge? I couldn't find anything on Sony's website that would point to it.

vkmast wrote on 2/26/2013, 11:24 AM

Tech support responded with this today

This issue is currently logged into the known issue database, to be resolved in a future update of the application. Thank you for reporting this issue.

OldSmoke wrote on 2/26/2013, 12:21 PM

Great! Did we get anything for having spent our time to prove there is such an issue?

Just kidding.