mirror of
https://github.com/WarmUpTill/SceneSwitcher.git
synced 2026-03-21 17:34:57 -05:00
Created Exporting and importing individual macros (markdown)
parent
1dbcad5de0
commit
de82fb5b9f
25
Exporting-and-importing-individual-macros.md
Normal file
25
Exporting-and-importing-individual-macros.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
Exporting / importing individual macros can be useful if you want copy individual macros across different scene collections or OBS instances.
|
||||
|
||||
## Workflow
|
||||
First mark the macros you want to export and right click in the macro list to select the "Export" functionality.
|
||||
|
||||

|
||||
|
||||
Now copy the contents of the dialog that pops up, which will contain the information about the selected macros.
|
||||
|
||||

|
||||
|
||||
In the scene switcher instance / scene collection you want to import the macros in right click anywhere in the macro list and select "Import".
|
||||
|
||||

|
||||
|
||||
Now paste the content you copied earlier in the dialog that opened up and click OK.
|
||||
|
||||

|
||||
|
||||
The macros will now be added to your macro list.
|
||||
In case a name conflict with an already existing macro comes up you will be asked if you want to rename the new macro or skip its import.
|
||||
|
||||
## Limitations
|
||||
|
||||
If an imported macro is referencing scenes, sources, transitions, variables, or similar items, which do not exist in the scene collection, this information will be lost upon import. So, for example, an action switching scenes might no longer have a transition type selected if the particular transition type does not exist in the scene collection into which the macro was imported.
|
||||
Loading…
Reference in New Issue
Block a user