Connectivity

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.

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.

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.

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.

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. 

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.

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.

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?

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. 

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.

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.

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.

How does one upgrade to v6? Is this a firmware for the router/cards?

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.

Hi Boris,

The Extra PiP size is only available when inputs come from an HDX or MODX blade.  If you have an FR 1 or 2 with the integrated "MIO" boards or any other I/O card such as an HDB-IO-A then you don't get PiP C.  The invalid Size message is likely because that source is coming from an input not from an HDX or MODX board.  Only PiP C Sizes from non HDX / MODX boards will show an invalid size message.  As a side note, you can still place an Ultriscape head on any output on any blade and see all the pip sizes, it is only inputs routed to pip C that have the limitation.

Hi Brandon, 

Thank you ! Axel from Ross France just gave me the trick few hours ago :)

I didn't know this limitation... so that's why i had the issue it is now solved ! I was sure it was me doing wrong and not Ultrix ! it is never Ultrix btw.

Thanks again !

Have a nice day,

Hi Boris,

The Extra PiP size is only available when inputs come from an HDX or MODX blade.  If you have an FR 1 or 2 with the integrated "MIO" boards or any other I/O card such as an HDB-IO-A then you don't get PiP C.  The invalid Size message is likely because that source is coming from an input not from an HDX or MODX board.  Only PiP C Sizes from non HDX / MODX boards will show an invalid size message.  As a side note, you can still place an Ultriscape head on any output on any blade and see all the pip sizes, it is only inputs routed to pip C that have the limitation.

Hello everyone, 

To add to the topic...

We recently upgraded another system composed of an FR5 and Ultrix Acuity. So now in V 6.3 we have access to PIP C and PIP X.

When we try to assign a ME output of the Ultrix Acuity we got the same warning message "invalid size" but we can route Auxes ( but ME output through an Aux is not working).

Is that a known limitation making impossible to assign a Ultrix Acuity ME output into PIP size C ? 

Best regards

Hi Brandon, 

Thank you ! Axel from Ross France just gave me the trick few hours ago :)

I didn't know this limitation... so that's why i had the issue it is now solved ! I was sure it was me doing wrong and not Ultrix ! it is never Ultrix btw.

Thanks again !

Have a nice day,

Hi Boris,

The Extra PiP size is only available when inputs come from an HDX or MODX blade.  If you have an FR 1 or 2 with the integrated "MIO" boards or any other I/O card such as an HDB-IO-A then you don't get PiP C.  The invalid Size message is likely because that source is coming from an input not from an HDX or MODX board.  Only PiP C Sizes from non HDX / MODX boards will show an invalid size message.  As a side note, you can still place an Ultriscape head on any output on any blade and see all the pip sizes, it is only inputs routed to pip C that have the limitation.

HI Boris,

the SDPE card (Ultrix Carbonite and Ultrix Acuity) Doesnt support the third pip size C yet. The Extra PiP size is only available when inputs come from an HDX or MODX blade directly to the multiviewer. 

Hello everyone, 

To add to the topic...

We recently upgraded another system composed of an FR5 and Ultrix Acuity. So now in V 6.3 we have access to PIP C and PIP X.

When we try to assign a ME output of the Ultrix Acuity we got the same warning message "invalid size" but we can route Auxes ( but ME output through an Aux is not working).

Is that a known limitation making impossible to assign a Ultrix Acuity ME output into PIP size C ? 

Best regards

Hi Brandon, 

Thank you ! Axel from Ross France just gave me the trick few hours ago :)

I didn't know this limitation... so that's why i had the issue it is now solved ! I was sure it was me doing wrong and not Ultrix ! it is never Ultrix btw.

Thanks again !

Have a nice day,

Hi Boris,

The Extra PiP size is only available when inputs come from an HDX or MODX blade.  If you have an FR 1 or 2 with the integrated "MIO" boards or any other I/O card such as an HDB-IO-A then you don't get PiP C.  The invalid Size message is likely because that source is coming from an input not from an HDX or MODX board.  Only PiP C Sizes from non HDX / MODX boards will show an invalid size message.  As a side note, you can still place an Ultriscape head on any output on any blade and see all the pip sizes, it is only inputs routed to pip C that have the limitation.