Kona monitoring problems during capture

[Bob Zelin]

you are in some sort of feedback loop, as you have proved by disconecting the
Kona 2 output from the input of your HD VTR.

This is my professional suggestion. Go down to your car. Get the crowbar out of your trunk. Stick the crowbar into your wallet. Pry out about $250 and BUY A G#$ DAMN BLACK GENERATOR, and stick this into your Kona 2 Reference Input, and your HD VTR Ref Video Input, throw the Kona Control Panel into Ext Reference, and YOUR PROBLEMS WILL GO AWAY.

By the way, that will be $50 bucks for the advice.

Bob Zelin

[Sterling Noren]

Bob –

FYI I have done that already and yes – it works. However I should not HAVE to do this and it WAS WORKING fine for many months without doing this. The reason I am trying to get it to work without running external sync into it is that I was getting strange playback issues on occasion from the deck (during playbck the deck would occasionaly “hiccup” and anything encoded or dubbed would have a glitch in it) and the Panasonic rep suggested that I DISCONNECT EXTERNAL SYNC into the deck for awhile to see if that helped. By the way the deck was also serviced in the last 6 months with heads replaced.

Thanks for your response.

[Jeremy Garchow]

Maybe this will help you.

https://www.aja.com/pdfs/how_to_ref.pdf

Jeremy

———–
G5 Dual 2Ghz <> 4GB RAM <> FCP 5.02 <> Kona 2
ATTO 42XS <> Huge Systems 4105 Fibre

[Bob Zelin]

Mr. GlobeRider writes –

The reason I am trying to get it to work without running external sync into it is that I was getting strange playback issues on occasion from the deck (during playbck the deck would occasionaly “hiccup” and anything encoded or dubbed would have a glitch in it) and the Panasonic rep suggested that I DISCONNECT EXTERNAL SYNC into the deck for awhile to see if that helped.

REPLY – the Panasonic rep suggested this because if the Black generator (think ESE) was a piece of crap, it would cause all kinds of havoc in your system. The ESE black generator is notorious from preventing AVID Adrenaline systems from working. I too have run AJA, Blackmagic and AVID systems without external reference “in a pinch”, but when problems erupt, you DO THE RIGHT THING, and problems go away. A LONG TIME AGO in the linear days, I used to use a Sigma 365 sync generator that had SC-H problems that caused H-Shift problems. The edit controller company insisted that I use a sync generator with the proper SC-H (I got a meter to measure it), and I said “IT WORKED FINE FOR 6 MONTHS – how could it be the sync gen”. Sure enough, I got a better sync gen with locked SC-H, and the H-Shift problem went away.

If you continue to have “glitch” problems with your Panasonic VTR with your Black Generator hooked up to it, there STILL MAY BE a problem with your Panasonic VTR. Just because a Panasonic service person looked at your VTR for 10 minutes, and said “there is nothing wrong with this VTR” – this means NOTHING -and this applies to all VTR’s, all disk drives, etc. It is DIFFICULT to find intermittent problems, and most service personel (including me) are very lazy about sitting with a piece of equipment that “appears” to work fine, when it will produce the problem in 30 minutes.

I feel your pain.

Bob Zelin

[Gary Adcock]

[GlobeRider] “I was getting strange playback issues on occasion from the deck (during playbck the deck would occasionaly “hiccup” and anything encoded or dubbed would have a glitch in it)”

IF we are still talking about your HDSDI capture — that sounds as if there is too much on the FW bus. –even if you are using the 1200a over HDSDI but you kept FW cable attached.

Gary Adcock
Studio37
HD and Film Consultation
Chicago, IL USA

[Ron Thompson]

I’ve seen this issue with the KonaLH during analog (y/c) capture. Like you, It worked in the past, but now all of a sudden green garbage on the screen during capture. Capture is fine, normal editing operation is fine. Maybe something in the last update?

Haven’t seen the issue with SDI capture.

I run sync to all my equipment…new cables… KonaLH with IO…Configured LH for Y/C, so IO was not in the loop.

Ron