I wish there was something we could do, but this is a limitation of the FPGA architecture on the original boards versus the new ones. There's simply much more power in the X series FPGA compared to the original series.
Original Message:
Sent: 01-07-2025 20:03
From: Jeremy Koch
Subject: Ultriscape
Thanks Joe, good explanation. As an 'early adopter' of the Hyperconverged platform, is there anything you can do to help those people get more from Ultriscape PiPs who have HDB-IO cards?
------------------------------
Jeremy Koch
Director
Innovative Production Services
Original Message:
Sent: 01-07-2025 19:36
From: Joe Davenport
Subject: Ultriscape
As to why all PIPs need to be the same across the frame, it has to do with the way we scale the signals. ALL signals are immediately scaled on input to the frame through the FPGA on each IO card, effectively sitting in a "holding bank" ready to be displayed on a PIP in any layout, regardless of where the MV outputs from(i.e. a different card than which the source signal is hitting). Because of this, we have to universally define what the PIP sizes are so that any head can display any of those signals, which allows us to have a totally non-blocking infrastructure and display signals from any board on any MV layout, regardless of which board the MV head is set to. This also allows us to follow outputs in the same manner.
While this design does limit you to a degree, this is a very cost effective way to have flexible MVs in a single unit.
The alternative would be to relegate each boards MV head to the sources and destinations specifically on that board, which would mean you'd have to purchase a MV license for each board you want to display. This would also mean you would have to have that many more MVs to display in general.
Also, as a point of clarification, the 3rd reusable PIP is currently only available on the HDX and MODX cards. The IPX currently does not support this feature.
------------------------------
Joe Davenport
Original Message:
Sent: 01-06-2025 12:51
From: Paul Whitfield
Subject: Ultriscape
All relative PIP sizes need to be the same across ALL heads in the frame....which makes no sense to me. I can see why they would all need to be the same size per card, but not per frame.
I love the ultriscape MV system, but it has many * asterix on it.
I have said exactly the same thing.
------------------------------
Paul Whitfield
Original Message:
Sent: 01-06-2025 04:56
From: Jeremy Koch
Subject: Ultriscape
Hi Boris, what cards do you have your Ultriscapes on?
This new 'extra PIP size' which is so desperatly needed for anyone with an Ultrix, is limited to those with HDX-IO cards and the IPX-IO cards i think.
In fact, version 6.x introduces a 4th PIP size. A+B+C should behave like normal and then you get PIP D which is only allowed one PIP per head.
All relative PIP sizes need to be the same across ALL heads in the frame....which makes no sense to me. I can see why they would all need to be the same size per card, but not per frame.
I love the ultriscape MV system, but it has many * asterix on it.
Always something that 'gets' you....
I would love to see some clearer information on the updates to Ultriscape with version 6 and what it means for 1st gen cards and x-gen cards.
------------------------------
Jeremy Koch
Director
Innovative Production Services
Original Message:
Sent: 01-05-2025 05:53
From: Boris salhaji
Subject: Ultriscape
Hello everyone,
before bothering Ross experts with something which seems to be not an issue I ask my question here…
we are used to Ultriscape operations and we were thrilled to discover in version 6 that we got an extra PIP size.
And precisely with this new feature we configured MV layouts with 3 pip sizes plus PIP X. It works fine even if we stuck with a very silly issue.
In pip C we can route sources, some are well displayed but few orhers are not displayed and we got the red message on the pip "invalid size".
if on the same layout we route the same source in an other PIP with a different size ( for exemple PIPA or B) it is well displayed…
I assume there is something I miss with PIP C…
when I troubleshoot all the corresponding sources are in 1080i50 some with audio embedded some not.. all the sources are gen locked (BTW I try to activate an ultrisync but it don't fix the problem).
I looked the user manual but I didn't found a solution.Could someone clarify the usage of PIP C and what "invalid size" mean?
and if someone have an idea on how to solve my issue it would be great!
thanks
------------------------------
Boris salhaji
EIC
France Télévisions
------------------------------