The Oophalumgum Bird does visit me from time to time, yes. "Pesky little critters" is an understatement, indeed.

I don't think it's a clash of plugins. I don't really have any, other than Noise Reduction 2 and MBL, and neither of those is being used in this project, nor any FX for that matter.

If this is all it ever does, I don't find it too disturbing. I can live it, if I have to. Hopefully, SCS will get to the bottom of it.

Jay with me its Prodad plugs


I e-mailed them so many times and got nothing Then I sent 1 mail off to Digital Juice regarding Prodad and within 1 hour I GOT 4 MAILS from Prodad

Anyway its better but there is an issue with license checking system with Prodad

Prodad software is really very good but there customer service is not so hot

Rory

Yes, I think 9.0c has an issue with red frames again, which I have reported before.
Interesting thing I found though is that I updated to Windows 7 (Ultimate) last night, then tried to run Vegas.
It was running very sluggishly and a number of red frames showed up.
I found out that my network would drop every now and then.
After some searching on the net found out that I had to get the Windows 7 NIC drivers from the board manufacturer as the windows 7 driver microsoft installs gave me the problems which resulted in red frames (dropping of the network)
After installing correct NIC drivers Vegas (9.0b) ran quite snappy.
Not sure if this helps you but thought worth a mention.

Ted

so red frames could be due to the system not feeding vegas fast enough?

Yes, I think that could very well be one of the issues.

My fix for this was to reduce the amount of RAM in Vegas preferences to 2gig. Worth a try.

"Do we know what causes this?"

No and it's most frustrating. Clearly the presentation of a red frame is the result of a conscious decision in the software. An explaination of the conditions under which a frame of red is returned would be of immense help to users trying to diagnose the problem. Why SCS have not seen fit to explain themselves is more than a little frustrating. At least when a M$ app throws me an error I can dig thought their knowledgebase and get a hint where to start looking.

Bob.

Point well taken, Bob.

Thanks!

EDIT:
And for what it's worth, this does not happen every time I open the project.

"Clearly the presentation of a red frame is the result of a conscious decision "

I agree Bob. However I think that the representation of a red frame may not be a single reason or decision made by the software.
I think it may very well be a.... oops I dunno what happened to my data, so I now will show a red frame.
In other words, I think there are many factors that could cause this.

I know for sure that if you have a problem or slow path to your data drive with the pic or video on it, you'll end up with red frames instead.


Ted

i doubt it's red frame because it's an error-message like design. In 3d games if you look in to an area where nothing exists it displays the last thing in memory. Now multiply that by your frames per second & things get weird fast.. We seem to have the exact same issue here but the complete lack of data is manifesting in a red image vs a double frame. I'm betting that's by vegas design (ie it knows it's not on frame X because it just displayed frame X, so it has to be X+1). For all we know it's a red 1x1 pixel that's filling the whole screen or some basic part of the OS that stores color data..

Nah, nice try Happy. But I'm still not convinced. Whatever you say my theory still holds: The Oophalumgum Bird!

Y'know sometimes, just sometimes, Happy, you just have to embrace reality and the staunch rigours of Maths and Physics and computer engineering: The Oophalumgum Bird!

Listen to one who has seen the avian. Oh yes!!!

And the only way to "remove" the results of its visit, is to don the the magical "Cloak of Thandor" - or, as we Vegasites like to call it, in Public places "the process of rebooting Vegas". I slipped into the aforesaid garment twice yesterday.

Grazie

Here is what happens on my system.

I opened a project done with 9b 64 bit in 9c 64 bit.

Starting with a graphic towards the end of the project all graphics from it on to the end are red. Even a duplicate of a small one that I have at the beginning which is my logo.

If I turn on Auto-Ripple for all tracks and slide all of the graphics that are after the first one with the red frame they will all become normal and no longer be displayed as being red.

The first one will not play and show as black on the time-line no matter what I do.

I loaded the source graphic *.jpg into Adobe Photoshop Elements 7 and change the format to *.bmp and put it on the time-line and it also shows up as red.

I should have tried the problem graphic at the beginning of the project but went back to 9b before I thought of that.

With 9b 64 bit, all is good again with no more red frames!

Must be something in the graphic that 9c 64 bit can’t work with and thus the red frame.

Maybe they did a bug fix that causes this? Looking through the list I see a few that might cause this but not very likely.

I uploaded the file that 9c 64 bit has problems with to my web page and it is called “end.jpg”.

http://www.vidmus.com/end.jpg

You guys might check this on your system(s) and see if you get a red frame or not. I have no idea what it does on 9c 32 bit because I did not try it. Only tried 9c 64 bit on Windows 7 Ultimate 64.

Danny Fye
www.vidmus.com

"the process of rebooting Vegas"

Have you tried closing and reopening the project?

Dang, Jay! You MUST be "The Lost Wizard of Stangfrop"! I didn't know you still had the powers? You are, of course, speaking of the "Napkin of Stenmuir" otherwise referred to as the Vegas Project close<>open. It is the smaller version of the "Cloak of Thandor", but none the less effective too.

Go in Peace, dear Wizard!

Grazie

It's the timeless tactic still used by support personnel the world over ...

" Have you tried switching it off and on again?"

... and even with such a sophisticated product as Vegas - it still works!

- seriously, I don't know this technically, but I'm pretty sure it's to do with freeing up memory.

Interesting question - is anyone with 8Gb of Ram still getting red frames?

I have a project started in 9b 64bit. I continued it in 9c 64bit. I added a 1280x720 PNG image and it immediately went red. Restart and reboot didn't fix it. Finally went to 9c 32bit and it worked fine. As a bonus, my 720p60 AVCHD footage previewed MUCH more smoothly in the 32bit 9c vs 64bit 9c. So much for the advantage of 64bit. I'm thinking that only the 32bit AVCHD libraries were updated in the 9c release.

jerry

Has anyone had a red frame turn up in a final render?

I've only had red frames appear in the thumbnails, not even in the preview window. Mostly simply zooming in / out of the T/L is enough to clear them. Depending on how you've setup Vegas to respond to loosing focus simply taking focus away from Vegas and back again may clear them.

Bob.

i've never even seen them, I've only ever seen black frames once.

Has anyone had a red frame turn up in a final render?
As RED?? Anyway, I DON'T render until I have a sane Timeline non-blank Events . . .

"I've only had red frames appear in the thumbnails, . . "

What can I say - don't be jealous?

" . . not even in the preview window." They AREN'T red in the Preview - they are just BLACK. On the T/L RED within Preview BLANK=BLACK


"Mostly simply zooming in / out of the T/L is enough to clear them." - Nope.


"Depending on how you've setup Vegas to respond to loosing focus simply taking focus away from Vegas and back again may clear them." - Nope.

Bob, if you haven't witnessed these irregular happenings, I would also think to put forward your suggestions too.

Grazie

TeeTime says, " So much for the advantage of 64bit. I'm thinking that only the 32bit AVCHD libraries were updated in the 9c release."

Apparently they might of left out/forgot a number of things in the 64 bit version!

I backed up my system today and tried the 32 bit version and so far it works flawlessly!

As for all the suggestions of opening and closing Vegas, so far, nothing worked with the 64 bit version.

Since this seems to be a 64 bit version problem, I loose the benefits of the 64 bit version if I have to use the 32 bit one.

My playback on 9c 64 is poor compared to 9b 64. Playback on 9c 32 bit is much better!

I think they need to double check their work between versions.

Danny Fye
www.vidmus.com