Why do I have to start a song twice before a programmed DMX tracks turns on the lights/does what it is programmed to do?
That is the settings in my preferences
After doing some more testing I found that if the channel (in my case Channel 1) is set to zero at the start of the song in the automation and then to something > than 0, I have to start the song twice. If I set it to something > 0 at the start of the song then it is working just fine.
So, in many cases this is not a big deal, but where I want to start the song blacked out and bring in the lights a few seconds into the song, it doesn’t work correctly.
So, I restarted VST Live and what I said in the previous post did not work this time. Very inconsistent.
@SDF affraid u’re using outdated version while complaining ![]()
If you experience problem with most recent version, then it worth to report ![]()
I upgraded to 3.0.19 and still having the same issues
I didn’t know reporting issues was considered complaining. WTF
//OFF
English is not my native lang, please rather feel the voluntary help I gave to you saturday evening ![]()
//ON
- So are you sure, faders not get back where saved?
- Is the orange button clear what it does and why you don’t need it to be recalled?
Sorry about that.
The faders do not save their position unless I put in an automation track and program settings. I thought I should be able to just use the faders and save their position.
I assumed it was the read track automation button, similar to Cubase. So what is it’s purpose??
Absolutely! And it does on my computer correctly. Can you shoot a screenrec, that shows a very simple project, no data, just position DMX faders to random positions. Save and recall project? What are we missing? It’s working to me.
The orange button is - as mentioned - say “monitor”… shows incoming DMX activity. Just use when recording external DMX signal.
Here is a test project and screenshots with Faders in different position and saved.
Same project; I saved it, closed it and reopened. Faders are back in their default position at 127.
VST DMX Test.vlprj (15.5 KB)
oh yes, that’s normal, expected.
You posted with this picture:
So meant that fader / dimmer on the photo (linked above).
To fix / move these channel dimmers, you need to create at least an event and record or draw some happening. You can do it by hand by recording-input the DMX-MIXER (the coloured dimmers on the right the photo).
Somehow similar to MIDI events… think on like these are notes with different velocities (they are different, but just giving you some idea). Without a saved CLIP with EVENTS inside, VL can’t recall data, because no data has been saved.
Hi,
If you want to save/restore the active state, you need to configure VST Live for it. Open the Preferences …
… and tick “Save Track Monitor Enabled”
That’s right. The fader-states of the DMX Input Mixer is not saved. You would expect that?
Can you please give us an example project which shows the problem? Use the Archive project if the project is ready. “Menu / File / Save Archive…”.
Thank you,
Michael.
Oh, forgot… I keep my “Save track mon enabled” DISABLED for purpose
Thx @Spork reminding me, it’s scope is not only for MIDI/AUDIO, but all kind of tracks (even FOLDER-trk)




