Hi! Will perform as guest 2 songs on Friday with a band using VL too. I planned to receive [song dial] then PLAY from main VL computer to my gear’s VL to fully automate my performance while their system is the main system. However can’t get song playlist order values OUT from VL (tried assign fixed values, tried NoteOn and CC Actions w.o. success). What am I missing to do? Thanks for any hints.
what is that?
What exactly are you doing, and what would you want to happen?
Hi Felician,
If the band accepts, they could add a Layer to each Song you play in their Setlist. These Layers would send Program Changes to your VL.
Hi @Jihem thx 
! We solved it or course with TMP workaround, but reported in any case. It’s up to the team decide to fix or wipe out that setting for future.
@musicullum this is an another computer&project w.o filled settings, but I think will make sense:
Actions / Project / Select Song "Dial >> OUT
expected, that dialled value will be forwarded to OUTPUT
Like changing to SONG#2 and $Value#2 will be sent OUT
coming today.
Thank you! tested quickly and can"t find it’s working. Was it finally pushed to the today’s build?
I just tested like:
A&S:
Project / “Select Song” → ActionOUT → NoMIDIOut detected by my setup
oh! Found the culprit .
While - in my experience - with Actions the case is listened (regardless of stopping PLAY with Spacebar, or SongEndStop, or whatever reason playhead STOPped, I get a stateOUT). Seems with SongDial - unless dialing song via MIDI - won’t send stateOUT.
Example:
Your example above
Example:
My example: WHEN clicking songs by mouse or song GETs selected
(because of e.g. previousSongEnd->Nextsong)
Pre-defined ActionOUT for “Song Dial” is not receiving midiOUT on any of my two MAC’s.
It’s not really supposed to work like that…
“Select Song” means it gets an index (number) which Song to select. Next/Previous, or mouse selection are a different action. There also isn’t really a computer keyboard shortcut for indexed selection like “Select Song”, “Select Part” etc which require an argument (parameter) for that index.
For instance, what should we do if you engage a “Next Song” action which has a Midi Out by itself?
I understand the specific user cases where people willing to address songs with fixed-values, therefore I would just use the same logic as currently coded for SongDial (dynamic “playlist position” or {if defined, use defined value} , exactly as currently working, no?
Then me - e.g. me, who letting VL dynamic$ SongDial will get the increasing numbers and people are using [fixed-$values] will get the same exact $output they pre-defined.
repeated question
User can decide which to use (define actionOUT for song navigation “Prev/Next” or rather defining actionOUT Playlist/Song values).
Btw if [next song] fired… new song’s value is probably coming thereafter, no? I mean if Playlist is arriving to “Song#3” by a [NextSong#CC from Song#2] then VL is - currently - omitting SongDial “Song#3” anyways. Tested just a second before, doubled dial does nothing at all, seems to be practically-omitted.
So I’m not sure I could answer your question, let me know if I still didn’t get to the point.
The problem is that actions are actions and they trigger exactly and only what their purpose is. If you engage action “Next Song”, the action “Select Song” knows nothing about that.
I do see your point though, and we could try and send a “Select Song” output whenever a Song change happens, but it breaks the strictness of action rules, and whenever that happens, we already envision hundreds of users “it outputs weird MIDI data all by itself”
Ok, that would only happen if you assign MIDI output to “Select Song” in the first place, so let us check how it can be done.
exactly, user can decide currently anyways which and what actionOUT to send THX
coming next version.
oh! Thank you :)) I belive - that will be useful for different scenarios when VL is the HOST, e.g. having a 2ndary VL computerbackup, or sending Cuelist select to LightingDesks, or Column select to ResolumeArena, etc…
//
if re-dialling current song, SongDial() seems to be ignored, so there must an IF statement in the SongDial() function long time ago anyways:
IF dialled song == current song
return,
Did I reach the wrong conclusion?
//
roughly 50.000
/*
ok… yes… meant it specific: in case “if dialed Song$ is already active, incoming re-dialSong$ Action won’t be executed”
*/