Macro: Fire Static Playback 1

[karali]

Hello!

Today I wanted to ask if there is a macro that allows to run Static Playback with any number? Alternatively, are you able to help write such a macro?
I will be very grateful for your answer.


Greetings Daniel

[icke_siegen]

What exactly do you mean with

run Static Playback with any number

?

Please have a look at https://avosupport.de/wiki/macros/examp ... seplayback which should give you some hints.

Essentially it would be something like

Code: Select all

<step>Playbacks.FirePlaybackAtLevel(userNumber:111, level:1, true)</step>

where the 111 is the usernumber of the playback you want to fire, and 1 is 100% for the leven (or e.g. 0.85 for 85%)

Note that you'd also need something like

Code: Select all

<step>Playbacks.ReleasePlayback(userNumber:8111,  Playbacks.MasterReleaseTime, true)</step>

in order to stop the playback. If, however, 'run Static Playback' means something else for you then the command might be different. So, please explain what you want to do.

[Gregory]

Perhaps macros akin to the factory macros Fire First Playback, Kill First Playback Page 1, Release Tenth Playback (9 macros in total for all combinations) are what is being requested. These use the location of the playback rather than the user number. As an example firing the 10th static playback could be done as follows:

Code: Select all

<macro id="Avolites.Macros.FireStaticPlaybackIndex10" name="Fire Tenth Static Playback">
  <sequence>
    <step>Playbacks.FirePlaybackAtLevel("Location=StaticPlaybacks,10", Math.AbsoluteAdjust(1), true)</step>
  </sequence>
</macro>


Note that Math.AbsoluteAdjust(1) is just the older way to writing level:1, the former is used in the factory macros to make them compatible with as many versions as possible but the latter is probably the easier one for people to use. There is also a similar cast for location which looks like location:("StaticPlaybacks", 10) however this isn't one I have tried.

[karali]

Thank you for your answer.
When writing "run Static Playback with any number" I meant the Static Playback with numbers 1-20 in the case of Titan Mobile, or 1-12 in the case of T3 (physical button regardless of what Cue / Cuelist is there and on which page) similarly as in the case of the FireFirstPlayback macro, FirePlayback tenth

Thank you @Gregory - this is the direction I was looking for. I couldn't find anything in the documentation regarding Static Playback apart from changing the page, hence the question.

"Location=StaticPlaybacks,10" I think that's the command I was looking for

I'll check in the evening if it works properly
Thank you for your help and interest in the subject!!!!

[karali]

Hi!

I made this macro in the following way, but today I discovered a problem.

What is my intention - I would like to do something similar to a setlist, but triggered from a macro.

StaticPlayback1 on a separate page is a Cuelist for subsequent songs (I have duplicated the lower macros _song1..._song25 and only the StaticPlayback page changes)
I have added all Cuelists that are under this button in Playback Groups so that the rest are automatically released.

When I run the macro, the page changes, the Cuelist from StaticPlayback1 is launched, but the effect is as if Release was pressed twice and the devices return to the home position for a moment.
Nothing like this happens when I switch only between playbacks from the group - only when I add Playbacks.ReleasePlayback do such things happen?
Is there a way to fix this - I would like to get rid of the movement to the home position when switching, but in such a way as not to change the Power On/Release state

Code: Select all

<!-- Song 1 macro -->

<macro id="Avolites.Macros.Song1" name="_Song1">
<sequence>

<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,2",0,true)</step>
<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,3",0,true)</step>
<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,7",0,true)</step>
<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,8",0,true)</step>
<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,9",0,true)</step>
<step>Handles.StaticPlaybacks.ChangePage(0)</step>
<step>Playbacks.FirePlaybackAtLevel("Location=StaticPlaybacks,1", Math.AbsoluteAdjust(1), true)</step>
</sequence>
</macro>

[Gregory]

If you don't want the attributes to release to home you could:

• Use Playbacks.KillPlayback instead of Playbacks.ReleasePlayback, kill will leave all LTP attributes at their current values (HTP values would go to zero if no other playback includes them).
• Change the Release To Home user setting so that playbacks will only release back to other playbacks and not to home values.
• Put all the playbacks into a Playback Group and use that to release the other playbacks (assuming only one should be active at a time). If the Kill Point is set to Fade Complete it will only kill/release the old playback once the new one has faded in (avoid values dipping out before coming back in again).
• Set release mask, either globally or on the individual playbacks so that only attributes matching the mask will be released.
• If you wanted to emulate a playback group in the macro you could release the other playbacks after firing the new one, potentially putting a pause on the macro step to allow the fired playback to fade in first:
  

  Code: Select all

  <step>Playbacks.FirePlaybackAtLevel("Location=StaticPlaybacks,1", Math.AbsoluteAdjust(1), true)</step>
<step pause="1">Playbacks.ReleasePlayback("Location=StaticPlaybacks,2",0,true)</step>
<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,3",0,true)</step>


[karali]

If you don't want the attributes to release to home you could:

• Use Playbacks.KillPlayback instead of Playbacks.ReleasePlayback, kill will leave all LTP attributes at their current values (HTP values would go to zero if no other playback includes them).
• Change the Release To Home user setting so that playbacks will only release back to other playbacks and not to home values.
• Put all the playbacks into a Playback Group and use that to release the other playbacks (assuming only one should be active at a time). If the Kill Point is set to Fade Complete it will only kill/release the old playback once the new one has faded in (avoid values dipping out before coming back in again).
• Set release mask, either globally or on the individual playbacks so that only attributes matching the mask will be released.
• If you wanted to emulate a playback group in the macro you could release the other playbacks after firing the new one, potentially putting a pause on the macro step to allow the fired playback to fade in first:
  

  Code: Select all

  <step>Playbacks.FirePlaybackAtLevel("Location=StaticPlaybacks,1", Math.AbsoluteAdjust(1), true)</step>
<step pause="1">Playbacks.ReleasePlayback("Location=StaticPlaybacks,2",0,true)</step>
<step>Playbacks.ReleasePlayback("Location=StaticPlaybacks,3",0,true)</step>


Thanks for the quick reply - tomorrow I will check Playbacks.KillPlayback how it behaves and let you know

I intentionally want to have Release To Home enabled because I have most of the Cuelists saved as channels and some parameters remain from previous cuelists even though they are released

As I wrote above, I have created Playback Groups for cuelists with the correct mask etc. so I don't have to emulate it - it's more about creating a working setlist but based on StaticPlaybacks because having 10 faders in T3 I have all of them occupied.

For now I have simplified this macro by entering one "Release All Held Over" instead of several Playback releases - it's better but not entirely... I still have to check the Playbacks.KillPlayback option