mokaByls thanks for the debugging and finding the issue on mac os.
Here is a version that works on mac os as well:
mokaByls thanks for the debugging and finding the issue on mac os.
Here is a version that works on mac os as well:
a plausible workaround could be to create a new tilt-only preset that references the sky preset, by using the store option /Embed
set your tilt filter
call your preset sky
store new preset using /Embed option
a screenshot after the first call does not tell me much...
I assume then, that a second call still crashes the mac ?
try if this alternative way of getting the time works better on mac os:
local socket = require('socket')
local Time = function() return socket.gettime() end
return function()
local timestamp = Time()
Echo(tostring(timestamp))
end
if so, copy the two first lines into the beginning of the spinal tap plugin
and second run crashes ?
rightclick in empty tile in plugin pool
press onscreen AddLuaComponent button
press onscreen Edit button
paste the lua code in the component text editor
press save
close plugin editor
call plugin
maybe there is a os related bug with the grandMA API function Time().
if you run this simple script
return function()
local timestamp = Time()
Echo(tostring(timestamp))
end
does it also crash ?
if not, does it in the system monitor display the same time as the online time, but in seconds ?
e.g.
LUA 2m15.123 : 135.123456
or something else e.g.
LUA 2m16.543 : nil
Even if the speculations are right, and there actually is (or has been) a hardware emulator in use as some point during development (I have no clue about this), there may be numerous valid reasons for not including this (and other tools used during development), when compiling the final builds:
e.g. os-compatibility, hardware dependencies, security, 3rd party licensing, realtime performance etc
Nevertheless, assuming the roll-out of v1.9 goes as planned, you will in the near future be able to press the MA-key via commandline-syntax
12th gen.is a hybrid CPU with both low and high performance cores
maybe the following article can give some helpful tips.
not exactly what you request, but possibly close enough:
Lua "Cmd('Grid 0/%i',select(2,SelectionComponentY())+1)"
a Tempfader is a timeline-fader that will distribute the transition into next cue along the travel of the fader, just like the crossfader does,
the difference is what happens when this transition-fader reaches 100%
Crossfader:
1. transition toward next cue with all cuetiming distributed along the fader-travel,
2. when transition is completed, load next cue to prepare for a new transition toward another cue when fader is lowered again
Tempfader:
1. transition towards next cue with all cuetiming distributed along the fader-travel,
2. when transition is completed, do nothing, just wait for the fader to be lowered, to reverse the transition.
In both scenarios, jumping to other cues via Go, Goto etc will as expected cancel any ongoing transition, thereby resetting the fader representing the transition.
That being said, i totally agree that there is a valid feature request to have a fader that can scale the overall impact a playback has on output.
This is however something totally different than a timeline/cue-transition fader like the cross and temp fader
From my point of view, such fader would need to be either a totally new fader type (scale/impact/weight/size) or a mode for the existing Masterfader, to optionally apply to all attributes. instead of dimmer attribute only, as currently implemented
no this is not possible. selected layout follows the userprofile, which is the same on both screens
try changing the layout-viewer to not follow selected, then replace the layout-pool with a view-pool, then store duplicated views with different layouts assigned to the layout-viewer
Don't know if there is any issue with mac.
It is not a complex plugin, hopefully someone else can chime in if it works on their mac or not.
yes, is this a problem?
the offcue is triggered no matter if you switch off ( = release the Temp button) while in cue 1 Odd, or while in cue 2 Even
or do you now want to have different fadeout times for the Odd bump versus the Even bump?
set the fadetime of the OffCue to 0.2s
Workaround 4:
CueZero: Lua "last_time = Time() - 1"
Cue 1:Lua "local diff=Time()-last_time Cmd('FaderTemp Exec 201 At %.0f', 50*math.sqrt(1/diff)) last_time = Time()"
OffCue: Lua "last_time = nil"
set Cue 1 to Time trigger of 1 second, and link the sequence rate to your speedmaster.
your tempfader should update its position for every beat, when this sequence is toggled on.
In a real world implementation, you should add conditions to only move the fader if time-difference actually has changed, scale appropriately the fader range and be careful of global namespace.
Don't understand what you mean with "offcue - either 2 or 4" and "That has values at zero"
In my suggested solution there are only two cues, and neither of them contains any zero values.
this works for me:
Cue1: spots Odd Full
Cue2: spots Even Full
Cue 1 property Release: Yes
Cue 2 property Release: Yes
Executor Key function: Temp
Sequence property RestartMode: NextCue
- or did I misunderstand what you want ?
you could use the same workflow for your scenario.
consider screenconfig 2 (combined with a view call) as your dialog, then collect the action within that dialog, then do whatever you want with that collection:
e.g Macro "ColorFX"
ScreenConfig 2
View "myViewShowingColorFXpool"
Collect [execute = No]
ScreenConfig 1
Assign Collection At Sequence "mydefinedseq" Cue "mydefinedcue" Part 0.1
Go+ Sequence "mydefinedseq"