Production Switchers

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!

#CarboniteUltra
------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------
​​

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management
------------------------------

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Good day, Masimiliano. In addition to Les' suggestions, also be sure you check the Inclusions and Attributes in both the Store and Recall Memory sections.

------------------------------
Tedd Tramaloni
Ross Video
------------------------------

Original Message:
Sent: 09-20-2022 12:53
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Les' option 2 definitely works well. We did this for years on our Carbonite. It only had two chroma keyers, so we needed to do it this way. We set up customs that recalled the appropriate memories that would then go into Preview. If you want to reserve your MiniMEs for other things, I definitely recommend option 2.

------------------------------
James Hope
Technical Director
3ABN Australia Inc
Australia
------------------------------

Original Message:
Sent: 09-20-2022 17:20
From: Tedd Tramaloni
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Good day, Masimiliano. In addition to Les' suggestions, also be sure you check the Inclusions and Attributes in both the Store and Recall Memory sections.

------------------------------
Tedd Tramaloni
Ross Video

Original Message:
Sent: 09-20-2022 12:53
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Guys, thank you all for the inputs.
The all store/recall area is the grayest for me :_) I usually tend to store everything and recall what I need, but I'm confused by the difference between the "As stored" and "Recall" state of an attribute. Plus, should I use the Memory AI when storing or when recalling?
Sorry for the rookie questions...

------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Original Message:
Sent: 09-20-2022 21:10
From: James Hope
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Les' option 2 definitely works well. We did this for years on our Carbonite. It only had two chroma keyers, so we needed to do it this way. We set up customs that recalled the appropriate memories that would then go into Preview. If you want to reserve your MiniMEs for other things, I definitely recommend option 2.

------------------------------
James Hope
Technical Director
3ABN Australia Inc
Australia

Original Message:
Sent: 09-20-2022 17:20
From: Tedd Tramaloni
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Good day, Masimiliano. In addition to Les' suggestions, also be sure you check the Inclusions and Attributes in both the Store and Recall Memory sections.

------------------------------
Tedd Tramaloni
Ross Video

Original Message:
Sent: 09-20-2022 12:53
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Recall Attributes "Override" the Stored Attributes.

They have No Recall - Recall - Memory (Grey / Blue / Orange)

If you are too set those they will force and override what ever the individual Memory has stored with those.

Memory Store Attributes are set before you store the memory and each memory stores a sett -- No Recall and Recall (Grey / Blue)

95% of the time you should have the Recall all set to Orange and then each memory can individually be assigned to recall the parts or the Modes that are required on a memory by memory basis...

The other 5% might be during a special instance .. like needing a special key for a show so you disable the changing of PGM ME Key 3 and even a Media Store channel so that you can load a graphic into it...  So instead of editing all of your other memories you just over ride the Recall attributes to prevent those from changing..

------------------------------
Les O'Reilly
Director - Switcher Product Management
------------------------------

Original Message:
Sent: 09-21-2022 09:43
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Guys, thank you all for the inputs.
The all store/recall area is the grayest for me :_) I usually tend to store everything and recall what I need, but I'm confused by the difference between the "As stored" and "Recall" state of an attribute. Plus, should I use the Memory AI when storing or when recalling?
Sorry for the rookie questions...

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 21:10
From: James Hope
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Les' option 2 definitely works well. We did this for years on our Carbonite. It only had two chroma keyers, so we needed to do it this way. We set up customs that recalled the appropriate memories that would then go into Preview. If you want to reserve your MiniMEs for other things, I definitely recommend option 2.

------------------------------
James Hope
Technical Director
3ABN Australia Inc
Australia

Original Message:
Sent: 09-20-2022 17:20
From: Tedd Tramaloni
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Good day, Masimiliano. In addition to Les' suggestions, also be sure you check the Inclusions and Attributes in both the Store and Recall Memory sections.

------------------------------
Tedd Tramaloni
Ross Video

Original Message:
Sent: 09-20-2022 12:53
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Thank you all, we ended up using memories because we're still learning how to properly use MiniMEs [ and that would probably be another thread :) ]
Cheers!

------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

Original Message:
Sent: 09-21-2022 09:54
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Recall Attributes "Override" the Stored Attributes.

They have No Recall - Recall - Memory (Grey / Blue / Orange)

If you are too set those they will force and override what ever the individual Memory has stored with those.

Memory Store Attributes are set before you store the memory and each memory stores a sett -- No Recall and Recall (Grey / Blue)

95% of the time you should have the Recall all set to Orange and then each memory can individually be assigned to recall the parts or the Modes that are required on a memory by memory basis...

The other 5% might be during a special instance .. like needing a special key for a show so you disable the changing of PGM ME Key 3 and even a Media Store channel so that you can load a graphic into it...  So instead of editing all of your other memories you just over ride the Recall attributes to prevent those from changing..

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-21-2022 09:43
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Guys, thank you all for the inputs.
The all store/recall area is the grayest for me :_) I usually tend to store everything and recall what I need, but I'm confused by the difference between the "As stored" and "Recall" state of an attribute. Plus, should I use the Memory AI when storing or when recalling?
Sorry for the rookie questions...

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 21:10
From: James Hope
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Les' option 2 definitely works well. We did this for years on our Carbonite. It only had two chroma keyers, so we needed to do it this way. We set up customs that recalled the appropriate memories that would then go into Preview. If you want to reserve your MiniMEs for other things, I definitely recommend option 2.

------------------------------
James Hope
Technical Director
3ABN Australia Inc
Australia

Original Message:
Sent: 09-20-2022 17:20
From: Tedd Tramaloni
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Good day, Masimiliano. In addition to Les' suggestions, also be sure you check the Inclusions and Attributes in both the Store and Recall Memory sections.

------------------------------
Tedd Tramaloni
Ross Video

Original Message:
Sent: 09-20-2022 12:53
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------

For understanding and using MiniMEs here is a link to the Ross U video on it

https://www.rossvideo.com/gallery/minime-configuration-operation/

Les

------------------------------
Les O'Reilly
Director - Switcher Product Management
------------------------------

Original Message:
Sent: 09-30-2022 03:39
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Thank you all, we ended up using memories because we're still learning how to properly use MiniMEs [ and that would probably be another thread :) ]
Cheers!

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-21-2022 09:54
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Recall Attributes "Override" the Stored Attributes.

They have No Recall - Recall - Memory (Grey / Blue / Orange)

If you are too set those they will force and override what ever the individual Memory has stored with those.

Memory Store Attributes are set before you store the memory and each memory stores a sett -- No Recall and Recall (Grey / Blue)

95% of the time you should have the Recall all set to Orange and then each memory can individually be assigned to recall the parts or the Modes that are required on a memory by memory basis...

The other 5% might be during a special instance .. like needing a special key for a show so you disable the changing of PGM ME Key 3 and even a Media Store channel so that you can load a graphic into it...  So instead of editing all of your other memories you just over ride the Recall attributes to prevent those from changing..

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-21-2022 09:43
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Guys, thank you all for the inputs.
The all store/recall area is the grayest for me :_) I usually tend to store everything and recall what I need, but I'm confused by the difference between the "As stored" and "Recall" state of an attribute. Plus, should I use the Memory AI when storing or when recalling?
Sorry for the rookie questions...

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 21:10
From: James Hope
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Les' option 2 definitely works well. We did this for years on our Carbonite. It only had two chroma keyers, so we needed to do it this way. We set up customs that recalled the appropriate memories that would then go into Preview. If you want to reserve your MiniMEs for other things, I definitely recommend option 2.

------------------------------
James Hope
Technical Director
3ABN Australia Inc
Australia

Original Message:
Sent: 09-20-2022 17:20
From: Tedd Tramaloni
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Good day, Masimiliano. In addition to Les' suggestions, also be sure you check the Inclusions and Attributes in both the Store and Recall Memory sections.

------------------------------
Tedd Tramaloni
Ross Video

Original Message:
Sent: 09-20-2022 12:53
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Wow, that was fast :) 
I will definitely try tomorrow, thanks.

------------------------------
Massimiliano Mati
Graphic designer
TV Prato

Original Message:
Sent: 09-20-2022 12:43
From: Les O'Reilly
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

You could setup all 4 on a MiniME each so that they are Pre Keyed and then can be selected like a normal source by placing the MiniMEs on your Bus Map.

Alternatively you could use the Memory method but change them to Memory AI ..  Store all 4 using Key 1 over their different Media Store Channel and background.  Then it will recall the memory and place it on PV so you can transition between the two.. it will move the keyers between Key 1 and the next available Keyer automatically.

------------------------------
Les O'Reilly
Director - Switcher Product Management

Original Message:
Sent: 09-20-2022 12:37
From: Massimiliano Mati
Subject: Best practice to setup and store multiples chroma keys with different cameras/backgrounds

Hi everyone,
first time poster here so first of all thanks for this huge and helpful community. I work in a small tv network (in Italy) and we recently switched to Carbonite Ultra and we're just beginning to grasp on its power. In few days we're recording a show that features an anchor and two guests, a total of 4 cameras, all on a green screen stage. We're trying to setup an easy workflow for all the technicians to follow but we're having some hard time to find the best way. Looking around the forum I came across a post with a similar question but I'm frankly struggling with the whole setup. 
What I'm currently doing is :
- setup key 1 to be CK1 with cam1 and M1 as background. The key1 is on-air
- store the current state on mem 1 of a bank
- setup key 2 to be CK2 with cam2 and M2, cut the key on-air 
- store on mem 2 
- repeat the all process for all the keys up to the 4° key

What I'm getting instead when I recall the memories is that only CK1 is used on any key and only the camera source of its parameters is switched between the various cameras, plus the background doesn't change.  Are we doing it correctly? Maybe it's something in the way we're storing and recalling memories?  I've attached our current store/recall settings for reference. We would really appreciate any help on setting up a step-by-step procedure!

Thanks!


------------------------------
Massimiliano Mati
Graphic designer
TV Prato
------------------------------