Thursday, March 10, 2016

Re: [Avid-L2] Reference for HDCam and Mojo DX

 

Works until your Avid stall on digital cut and puts an irreconcilable glitch on the out point that can only be remedied with an assemble edit from that point on.  Makes punching in video fixes more dangerous when running reference to input video.  Of course in a pinch sometimes it's all you can do but from a plant/facility setup point of view there is no reason not to sort this out.  Termination has been mentioned and I've found that critical with HDSDI signals more so than sync.  AJA hardware is also very sensitive to unterminated sync.  I've found it helpful to take an old analogue waveform to check the sync signals at the point that is plugging into the equipment.  I've had hum and AC spikes upset the output of my NitrisDX sporadically when a power spike/noise was occuring in the machine room.  I know of one instance where a UPS was sending noise into the sync line, probably by causing some AC hum/spiky distortion.



---In avid-l2@yahoogroups.com, <mikeparsons.tv@...> wrote :

Just set the decks to lock to input and move on :)

On 3/10/16 8:41 PM, Mark Spano cutandcover@... [Avid-L2] wrote:
 
I have 10 bays and 2 SRW-5500 HDCAM/SR decks. The bays are on different floors of the building, so figuring out reference for all was a little work. I ended up using a single NTSC blackburst output of an Ensemble sync generator, to feed analog DAs to all the bays and decks, and everyone is happy.

Problems occurred prior to this when I had multiple sync generators in line, slaving to the master. This didn't always work. Replaced with DAs and everything is fine, even over hundreds of feet runs. The only real advice I can give is to make sure your editors are locking their video I/Os to external ref. This is the most common source of this type of error that happens here. Other than that, you might need to investigate your cabling and/or termination. There should be no reason why this doesn't work.

A workaround would be to make sure the video I/O is locked, and set the deck to reference incoming video input. It's not ideal, but it will get you by for the most part.

And yes, 525i/29.97 is all that is needed for any HDCAM/SR format except for 23.976 work.


On Thu, Mar 10, 2016 at 3:24 PM, 'Dave Spraker' avid@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:
 

L'ers

 

I know a lot of you have direct experience with HDCam and HDCam SR decks in your regular workflows.  Here's the issue. 

 

A client has an Ensemble Designs BrightEye reference generator that is feeding standard analog sync / black burst to a set of Harris DA cards in a frame.  That signal is then distributed to all decks and Avid editors (PC, z400s, 420s and 440s, Win 7, MC 8.4.x, Mojo DX).

 

Seems to work great on all SD decks as well as the Panasonic DVCPro HD.  The HDCam decks however see a discrepancy between the reference it is receiving and what is carried in the video fed from the Mojo DX interfaces.  This is not always clear cut, confusing the editor/dubbers.

 

The setting for this is in different places on the one SR and two HDCam decks.  It needs to be set back if the deck is to be used as a source.

 

My understanding is that tri-level sync is only required if you are doing something other than 720p and 1080i.

 

Thoughts, suggestions to resolve this?

 

TIA.

 

Dave Spraker

 

Principal, spraker.tv

Shared Storage Solutions  |  Consulting  |  Sports Audio

www.spraker.tv

 

Northwest Territory Manager, Western Rep Associates

Broadcast and AV Manufacturer's Representative

www.westernrep.com

 

New Address:

1100 SE 12th Ave., Suite #312

Portland, OR 97214

 

dave@...
(503) 897-0250

 



__._,_.___

Posted by: bigfish@pacbell.net
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (6)

Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? The Yahoo Mail app is fast, beautiful and intuitive.

this is the Avid-L2

.

__,_._,___

No comments:

Post a Comment