What a drag - anything to do with your new 2-monitor setup, Grazie?

Tom - Maybe maybe maybe . . .. .

Frenchy- It can't be!!! Surely? It's only a monitor....

...... from a less than happy Grazie.....blah!

Hey ho.....
Little hi Little lo, sorry watching my son's Stuart Little DVD

look at this website .....
http://www.film-and-video.com/broadcastvideoexamples-greenscreen.html#GREEN%20SCREEEN%20ARTICLE.html

Also like Chromatte system but thats another thread.

what do you mean blue screen????

as in PC CRASH?

auggybendoggy!

Imagine this:

You spend something like 2 weeks, 3weeks or 6 months putting together a project.

You have it neatly arranged on your hard disc/s

You now wish to Print To Tape

You do everything you need to do to this

You set up your cammy or device to Print To Tape and off you go.

Every so often you get a "blue-screen" appearing on your cammy. This can range from 1 to 2 seconds in length - when viewed on a TV it will apear as a minute/small jump in the progress of the video - This break happens in different positions: Maybe 10 seconds in to a say 60 min project; maybe at the 54 minute mark; you get a sprinkling of these throughpout the 60 mins at no predetermined or logical - ie file related - point in the progress of your PTTing. - Y'know I can sit there holding my breath for nearly 30 minutes in and then . . .then . . . a ?@&@* Blue Screen for about 1 second!!!!!

That's Blue Screen - AND I HATE IT!!!! - It makes a nonsense of the hours and hours and hours of work I do within V4 - my beloved V4 - and makes me a nasty person to live with - AAaawrrrgghhh ! !

auggybendoggy - No it aint a crash or a blue screen on the PC monitor - It's a blue screen on the cammy or tv monitor if you are PTTing to a VHS tape device and you are using a TV monitor to . .. . monitor your latest creation's progression to VHS tape.

Ahem: Peace & Love

Grazie

Is the blue actually recorded on tape? The reason I ask is that we have one XL-1 that will do exactly what you are saying - periodically it will flash blue on the screen and then come back to the image. However, the tape made is always fine. Otherwise, I would try and different cable and/or card.

Definitely sounds like an interuption in the data stream to me. Blue is what the cam will record when there is no signal present. I'd be checking your system for some TSR or perhaps a driver that is mucking things up.

I had this problem when I upgraded my mouse driver. Something about it caused it to sap my resources for a smidgen of time - long enough to randomly cause the blue screen about which you complain.

Doubtless you know and practice ending background aps before you try PTT, so, I won't suggest that obvious step.

I doubt your problem really has anything to do with Vegas software. It's likely some little system glitch that, once pinpointed, will be easy to fix.

In the meantime, I know it can be frustrating to no end.

Good luck in locating/correcting the problem.

Caruso

Hi Grazie, sorry to see this thread topic again.

I gather something has changed that must be linked with the reoccurance of BS. Can you go back one step in your system evolution (monitor refered to by Frenchy?) and see? I know you've been down this road in depth, but I agree with Caruso - even updating a mouse (or, in my case, unplugging a USB mouse) can make a diff with BS.

Instead of stamps, well, that's another thread.

BTY, Grob

Grazie,
Dude what about a DVDRW?
I know, I know, it doesn't solve the problem but it will mean you can avoid it all together.

auggy

You reckon??? I wont get Blue Screening when I burn a DVD??? - Betcha I'll be the first person to achieve it . . . . .

Anyway - Developments: Grazie Is Going To Upgrade!!! - I've had enough - See new thread. - Presently I'm watching my team, Southampton, trying to get back a 1-0 down halftime score in our FA Cup Final. I'll get a thread going in about an hour's time - yeah?

TOO much pressure . . .

Grazie

Grazie -

Changing power management fixed it for me.

Change all turn-off settings to NEVER.

Cheers,

XOG

XOG - Do you mean when "Plugged In" AND/OR batteries?

Here's mine:

Power Schemes: Home Desktop office

Plugged In
Turn off monitor: Never
Turn of Hard Discs: Never
System Standby: Never
System Hibernates: Never

Running on Batteries:
Turn off monitor: Never
Turn of Hard Discs: After 45mins
System Standby: After 2 hours
System Hibernates: After 4 hours

Stupid question here BUT: If I'm running on Mains doesn't that tell the Inspiron NOT to take notice of any "Battery Power Setting" - 'cos if it don't maybe just maybe it's looking for a battery setting at the same time? What do you think?

Please answer XOG - this could be quite vital! - Oh yes, where did you get this gem from? Hmmm?

Thanks,

Grazie

There are blue screen errors, and there are blue screen errors.

1. the dreaded BSD (blue screen of death) so named because Windows pops up some cryptic error message with a bunch of RAM addresses and some exception error, generally meaning you need to reboot using white text on a pretty blue screen.

2. a blue screen as someone else said can flash by for a fraction of a second or so if the feed to/from your camera gets interrupted.

3. a blue screen (more likely green) shown as frame(s) of varying length (may need to zoom way in on timeline if only a single frame or so) is an indication of a corrupt file and usually in a MPEG source file, frequently having artifacts and pixelation blocks. You can generally cure it by snipping out the offening frames.

If its number one, and your using XP, you could look in the event log (start/control panel/administrative tools/event viewer) and see what if anything Windows logged when the error happened or try to capture more info by setting up a Dr. Watson which is suppose to save a memory dump.

Blue Screen hangs were just a fact of life in earlier versions of Windows. They haven't totally gone away. While XP is more stable, the boys of Redmond actually pulled a fast one. The default setting is for Windows to rnow eboot, rtather than show the blue screen so if you get a lot of forced reboots, you're still getting the dreaded BSD's, just that they are masked and unless you look in one of the event logs, you'll never know what's causing it. Even if you do look and Windows says such and such is wrong, something you can't do anything about it. Ah... computers.

jetdv - yes the tape "Stops" and then "Starts" .5 sec or 1.5 sec - this gives a "Blue Screen" on the Canon preview LCD screen. You say - "the tape made is always fine" - but I can see/notice a slight jump at the place where it momentarily hesitates. And no, it doesn't "record" a blue screen - it only previews a blue screen. Ed, go back and look over your tape where there is/was a bluey - betcha y'll see this hesitation now.

Now that I've got a DV cammy I can PTT to DV tape. When I used to PTT straight to a VHS recoder via my Dazzle Hollywood Bridge, yes I recorded a "gap" - but, with the DV cammy I don't register a gap, only this slight jump or hesitation.

I don't think I'm being too fussy - surely?

Grazie

Grazie, want to hear a good one??? After solving my blue-screen problem in January, I did the unthinkable. I decided to purchase a WD 200GB IDE drive with a "free" controller. Since I've installed HDs before, I thought this would be a piece of cake, and I got such a good price (HAH!)... Long story short, after installing it as slave to my 40GB Maxtor, I have now rejoined the blue screen club. Ain't that a hoot?

When will I learn, if it ain't broke, don't fix it......

TomG

Tom is it one of the newer IDE 133 drives? If so do not make it a slave to an older drive! It needs to be on its own controller card. They are suppose to come with a controller card, (maybe at your bargain price it didn't?) and it will overlay its own BIOS to allow the drive to go as fast as it does, Could be that's what' causing it to burp. Same principle like changing oil. You can add one quart to your car, but if you haven't changed the oil in awhile all you ready have is 5-6 quarts of dirty oil. With hard drives, the slave can't run faster than its master. So if your master is a older, slower drive and you put a new hot rot on it as slave it will crawl along at probably mod 3-4, instead of mod 6. I've got several of the newer ones, all smaller buffers, but they fly off their own IDE interface card. Just did a little test. Moved a 900MB file from Drive D to E (both 133's and it moved it in just under 41 seconds.

Nope, the final recording was fine on that camera. In this particular case, it seems that camera had problems with the pass-thru signal. A different camera (same make and model) didn't have that problem. However, now we have switched to a deck.

I had this about two weeks ago, I was using a 40Gb external drive on a high spec PC, at random points I would get dropped frames on output.

I tried everything, de-frag, closing all items, giving higher priorty to the progtam all to no avail.

In the end I coppied all the files onto a new IBM120GB and then played it out with no problems at all.

Wiered but it worked..

BillyBoy,

That's interesting. I put my old (2 yr 40GB) as a master on the new Ultra ATA controller and the WD as the slave. Wanted to keep the big drive reserved for Video/Audio. Also didn't want to relocate the OS. Do you mean that my new WD will only go as fast as the old Maxtor? Would this cause a hiccup when PTT? Can you use two controller/master configures on the same system?

Thanks,
TomG

I've spent a large part of my life as a computer engineer, right back to the days of core memory.
The thing that always amazes me is how little they do crash!
The average PC today has close to 100 million devices in it and that before you add in the vaguarites of all that code written by so many different people using a wide variety of tools that themselves are still more software.

Guess that doesn't help much but it doesn't hurt to reflect on it when your thinking about buying some new hardware. VV4 gives us great choice in what we run it on unlike a lot of its competitors so you're not going to see it offered so much as part of a package. The downside is of course that when the wheels fall of its hard to know who to blame.

Even if all the hardware and software is perfect, PCs use DRAM and lots of it. This stuff will loose data from time to time due to radiation knocking the charge off its tiny capacitors. Unless your using ECC RAM this loss of data will either cause code to crash or data to be corrupted.

You can really load up a system if you want/need to. I have a pair of IDE controllers. The original primary and secondary master/slave that almost all motherboards now come with allowing up to 4 IDE devices, plus another IDE controller card that came with the 133 drives, (you can buy the cards seperately too, about $30) which gives you a second pair of primary and secondary controllers. So in my case I can have up to 8 IDE devices on one system. I have it for some time and it works flawlessly. If you do it, remember you also need the newer IDE cables (the round ones are nice) that have double the wires, every other one is just a ground to cut down on crosstalk, they still terminate in regular IDE connectors.

Oops... almost forgot. The reason to get the 2nd IDE controller card is so the drive can run at its top speed (mod 6) and it can't without the newer controler card, which is why they usually come as a freebie with the newer 133 drives. However I've seen bare bone drives being sold without the card, so while they problably will work on the older IDE channel or as a slave, they won't run nearly as fast as they were designed too since the older controllers don't support the higher bandwidth.

As far as having a newer drive as a slave to an older one, while it can work, generally not a good idea. The fastest drive should always be the master and mixed drives running at different mod (see you BIOS settings) can cause problems. Better still, put the new super fast drive on its own controller and you remove all roadblocks and the puppy should really fly.

Hello Grazie,

I found the turn-off solution, in my case, by accident -

I am running Vegas on a laptop and have found blue screens to be caused by a couple of factors when printing to tape.

1. Waking laptop screen up after it has gone dark. (Resuming from a screen saver might have the same effect).

2. Switching to another application during print to tape.