Sony MRC-1K compatibility with dvx102

[chanxj]

Hi All,

Just got the mrc-1k as recommended by u guys from the previous thread. But i seem to encounter an issue of my recording stops at intermittent intervals without my intervention. Ave time is abt 30sec. longest was 2 min b4 recording stopped. I did try different firewire cables, reset my dvx settings, reset the recording unit. Using a original 16gb sony cf card.

Any body have idea on this issue?

 

[jaegersing]

Only thing I can think of to try is to make sure you only delete files and format the card in the camera and not in a PC. I have seen several posts of people having card problems after using the PC for file management.

 

[DXNMedia]

Hmm given all possibilities eliminated, you may have a faulty CF card or even a faulty unit?
Have you changed a CF card and try it out?
Perhaps you may want to try it out on a sony camera.

I have tried many ways of feeding the MRC-1 unit via firewire (HDV & DV signals) without any issues.

From Deck to MRC1, from HDD recorders to MRC1 and I've even pumped out HDV signals via my FCP and used the MRC1 to record without any problems....so long as the input signal complies to the DV standard, i don't see any issues with intermittent recording...

One thing I've yet to try is to play back from MRC1 and try feeding the signal out into a deck, but I believe it should work alright too. :thumbsup:

 

[chanxj]

hmm ok. its very intermittent. playback to camera no prob, its output from camera to mrc-1k. the supplier said could be a firewire cable issue as they had it with the dr60. highly doubt so though as I have the same problem on a different cable. Waiting for their cable for me to test.

It works 100% well with the consumer canon hv30 though.

Will update when I find a solution.

 

[DXNMedia]

sometimes it could be a worn out FW port on the camera.
I get many intermittent connection problems with 4pin FW mini ports, not exclusive to the MRC1's connection though..

 

[chanxj]

hmm possible, but fw port is in fact seldom used as we normally digitise from deck. probably monday try with another dvx102.

 

[chanxj]

Problem solved!

Apparently the MRC-1K has to be switched on and fully booted up b4 switching on the dvx102. Somehow it works this way. Thanks to Chris from Expandore for spending the time to solve the issue.

 

[DXNMedia]

Problem solved!

Apparently the MRC-1K has to be switched on and fully booted up b4 switching on the dvx102. Somehow it works this way. Thanks to Chris from Expandore for spending the time to solve the issue.

Is this issue limited to the DVX102?
I haven't had any issues with either way of booting up my devices to work with the MRC1.

 

[chanxj]

Have only experienced it with dvx102 till date. Does not happen with other brands cameras i tested with.

 

[jaegersing]

Haven't seen this with my XH-A1. Glad you got it worked out!

 

[chanxj]

doesn't seem to have problem with canon. tested with a hv30. Time to find another panasonic to test.

 

[sundazz]

Hmm.. maybe is pana? :think:
We have similar issue with the Avid and pana DVCpro deck..
Have to fully start and launch Avid b4 turning on the deck.. if not can't do capturing and digital cut.. :dunno:

 

[DXNMedia]

Hmm.. maybe is pana? :think:
We have similar issue with the Avid and pana DVCpro deck..
Have to fully start and launch Avid b4 turning on the deck.. if not can't do capturing and digital cut.. :dunno:

Probably its the way the IEEE1394 controller works in Panasonic devices.
They probably need to detect who is the host device and when the decks/cams are turned on first, the data gets screwed up due to some conflict.

Anyways, according to my experience, i think it is always best to leave all devices turned on prior to connecting the FW cable, especially so with 6-pin FW cables that carry power via firewire....this way, you don't get any risk of power spikes/surge via firewire or any issues with which devices are being turned on first.

 

[chanxj]

Probably its the way the IEEE1394 controller works in Panasonic devices.
They probably need to detect who is the host device and when the decks/cams are turned on first, the data gets screwed up due to some conflict.

Anyways, according to my experience, i think it is always best to leave all devices turned on prior to connecting the FW cable, especially so with 6-pin FW cables that carry power via firewire....this way, you don't get any risk of power spikes/surge via firewire or any issues with which devices are being turned on first.

u mean turn off

 

[DXNMedia]

No, i actually meant turned ON before connecting cables.

I know many manuals indicate otherwise, but I had blowed off firewire ports following that instruction. So far my practice is always to turn on devices, then connect FW cables.

Same thing that you'd do to hot-plug USB cables....FW is technically designed for that as well....but don't quote me on that if you happen to blow your devices. ;p

 

[chanxj]

haha ok, interesting to investigate. had some 2.5" hdd from owc firewire ports blown b4 as both side were on when plugged in....... So abit paranoid these days.

 

[DXNMedia]

haha ok, interesting to investigate. had some 2.5" hdd from owc firewire ports blown b4 as both side were on when plugged in....... So abit paranoid these days.

Guess it's down to luck yeah?
Back in the old days, I tried following manual instructions by turning on devices while cables are connected, but blown a PD150 firewire port, a DSR-11 port, a dedicated FW card on a mastering deck, and a FW port on a mac.
:thumbsd:

Since then, I always fire up devices and plug in FW cables last.

 

[Jemhadar]

There is a device from Kramer, for eliminating damaging spikes and other problems on FW lines due to 'hot swapping'.

Kramer call it Spark-Guard Pro Firewire Line Protector, Model # PT-1FW.

 

[chanxj]

hmm interesting. pricing abit high though.