Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C100 : script HD-SDI Gatewe and Multiviewer - redundancy - nmos Is-08 - PTP #5

Open
yboujraf opened this issue Jan 19, 2020 · 0 comments

Comments

@yboujraf
Copy link

Dear @erlinghedkvist , @HenrikHalvorsenLawo

This message is not intended to criticize your product, it is only the observations experienced during several projects using your wonderful ip gateway.

PTP

Which is the best PTP brand to use with C100.
Today most of my customers using tektronics, Evertz but always missing something for different manufacturer.

We heard Meinberg but too expensive. I have some design where manufacturer propose Evertez in main and meindberg in backup or vice-versa, with REd & Blue network,... but this is unclear for me and for customers.

What Lawo recommand with Vmatrix and how to setup clearly the script for C100 gateway to be sync without any delay. Today we have 17 horzontal lines delay from all the equipements.

QSFP 40Gb

Which brand is supported by Lawo.

Last time we got issue with some C100 because the QSFP were overheat and reboot. Now fixed by changing manufacturer but ideally is to give a list of the QSFP supported.

Topic : C100 HD-SDI Gateway to SMTE2110 & Multiviewer

I am using C100 for HDSDI gateway to IP and as multiviewer for many projects. All closed with great success.

I have some remarks and hope to get some answers.

Compatibility of the script in the github with the C100 - vMatrix

I 'd like to know if the script you provided here are 100% compatible with all version of the C100 or only compatible for a dedicated firmware version.

C100 REST API or other

We have seen the web browser from C100 card are not supporting all the API commands as informed by the freelance or support to dedicated project and we heard the API is always enhanced each time there is a new firmware version. that's good

One issue is : For routing control only Video is available on the web browser but not audio routing and needs to use EmberPlusViewer for that but unfortunately Lawo said don't compare EmberPlusViewer with vsmstudio (that's right) one of the product supports most of the Ember+ specifications than the other and now we heard that possibility to have nmos also without to use gadgetserver. Is it true?

There is a way to get the full api of the C100 (with or without NDA) to support the wonderfull C100 gateway and VMatrix.

Last time just to manage a multiviewer layout we took 20 days and finally we finalized the layout with EmberPlusViewer :-( using ember parameters. but not able to backup the script.

FSYNC supported but never be able to link the source to the FSYNC

The Freelance we got (nice guy and smart) was not able to link FSYNC to a source, then no sources are sync with PTP and all the infrastructure :-(

Probably missing something in the script or need to do something in the web browser.

From my side I suspect the the way to setup the C100 was not respected, that means Step1, Step 2, Step 3, ....

C100 Scripts

The way you propose to split script is the best way to configure the C100 gateway and Easy to manage versioning.

The issue today we are not able to download the existing script pushed into the C100 or multiviewer to update it later.

Vmatrix Training

Is there a full training to follow at Lawo to take the control of the config (admin). Creating script, all setup, testing, ... to be independent.

IGMP - REdundancy - Dash7

We discovered in a C100, when using ONLY one NIC RX/TX IP.
IF the source converted in IP (TX) needs to be used by a Rx (hd-sdi output) on the same card doesn't work.

Then we used the first NIC for RX & second NIC to TX but now if we would like to use DASH7, or redundancy, we are not able to do that :-(.

Do you have any idea for that because the IP stream has 2 multicast ip (1x video + 1x 16 audios) per source but for target most the equipment are not supporting 1x audio stream with 16 audios then we need to split into 2x till 8x audio stream AES67 multicast?

Do you think the C100 gateway is able for TX stream to generate different flavors that means 👍

  • 1x HD-SDI video + 1x 16 audio stream
  • 1x HD-SDI Video with 4x 2 audios stream

Today to fix the issue : All the Ravenna AES67 audio stream encoded by the C100 are decoded by a Nova73HD and then recoded into Ravenna streams to be compliant with all the equipment to support it. The number of layers in vsmstudio is amazing.

nmos IS-08

Finally why going to IP? We know nmos -IS8 could manage audio routing but last JT-NM or last sony event (following AWMA, BBC, SONY, EBU repositories), all people lost most of their hair or switched from black to white ;-) without to imagine the time to switch a new source on the air, sometime we need to wait 3 till 4 seconds.

I am here to help you , not critic the best team in the Broadcast.
I started with L-S-B 15 years ago and make for them most of the projects including integration of Lawo products and before RTL customer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant