UK: Wierd PAL/NTSC stuff with FX1- ideas!?
 

Hi all,

Just pruchased a Fx1 today- very happy so far. but there is a slight problem that seems a bit wierd to me.

1. Filmed in HDV.
2. Downsampled to DV when logging to the edition 5 timeline
3. When playing back from the timeline to my monitor using the FX1 as a s-video breakout box it displays 'ntsc' in the viewfinder and produces mickey mouse sounding garbage

?

Is it to do with the downsampling in camera upsampling when playing back? Is it because i have a ntsc camera? (I think not as I wrote a disk and it plays fine) When I replaced the FX1 with my Xm2 and played back through that, all was fine.

Is there anything to worry about here or just an irritation?

Stuart

Sounds like you have an NTSC FX1, it is outputting an NTSC signal, your disk player is outputting a PAL signal and so is your XM2.

Sounds like you need to exchange your FX1 for an FX1E.

Solved, if anyone is interested. Its is a FX1e.

The problem goes away if you pull the dv plug out and then shove it right back in again.

Technology, eh?

S

Stuart

Mine does the same, Im over here in Australia, I have been editing HDV but have just started to do DV and yes you have to turn the camera off and restart or pull the plug...It must be a bug. I can also play 4.3 minDV tapes as 16.9 displayed sometimes...stranged.

Im using it with Premiere Pro and firewire.

Paul

Hey I just got my PAL A1 and it does the exact same thing as my PAL FX1?

Must be a bug. I can turn the camera off, pull the firewire plug or shut down Prem Pro and restart to sort it out.

Paul

What the cameras are doing is just a signal reset. The best way to do it is to turn off the cam, then turn it on again.

Its like using a floppy disk in the older computers, where you can only access the disk in DOS, or when thecomputer boots.

So imagine pulling the plug and reinserting it is like the computer going to DOS because windows 95 doesnt recognise it. And turning the cam off and on again is like inserting the disk before you start.

Its not a bug, but just a parameter that Sony probably left in the cam to save money, and in the end, save you a few hundred in the RRP of the cam.