… it’s Friday and a new version 3.0.51 is available.
You can download it here.
The version history is available here.
See you,
Michael.
Alllright, going for the hard testing way, gigging directly with .51 this evening 
@Spork @musicullum please can you take a look at the DMX recoding bug ?? been months , no replies at all…
thanks!!
… will be added to 3.0.52, sorry.
Will that polishment reduce/avoid filling up memory with DMX data from non-loaded songs maybe? 
Thanks Guys, downloading now.
Will report back with an update shortly.
Cheers, Johnny 
Hi Guys, The previous issues are fixed with 3.0.51, will continue testing over the weekend.
Thanks again guys.
Johnny
Hi Guys, had an issue last night with 3.0.51.
Lost all Audio inputs, no response in stacks at all for any of our inputs, i checked all the connections physical and in the software, no solo`s active, rebooted my computer, nothing. I went back to 2.2.54 and all ok again with audio but i lost all USB DMX connections on each of my lighting tracks for each song. the output was set back to nc, so i had to reassign all lighting tracks back to USB DMX. I think @ciro1983811 had this same issue in one of the other pre releases.
Thanks, Johnny
Stacks: were both audio input (Devices/Connections) and stack input set ok? Then it looks like a harware (connection) problem, did you try “Devices/Reset Audio”?
DMX: same question, were both track output and device output assigned correctly?
@musicullum joining this thread.
I’m facing with such issue that my vMIDI ports are somehow “slipping -1”.
Example under “connections / MIDI”
MIDI out ports:
vMIDI 1 – vMIDI 1
vMIDI8 – vMIDI 8
save…
then before gig… not working, hmmm, checking connections and find:
vMIDI 1 – nc
vMIDI8 – vMIDI7
Not sure if reproduceable immediately, but facing with this issue a lot and frequently need to fix it right before gig
cannot reproduce it with your repro, but there are certainly many more ports involved.
Could you send us the .vlprj file (nothing else needed) that loads wrong?
Hi @musicullum , So all inputs and outputs were assigned correctly and dmx input and output all correct, but did not work. I reverted back to 2.2.54 and all connections untouched and the audio worked again but as i said before it removed the usb dmx output from every track in my project around 100+ songs even though the usb was still plugged in and untouched from 3.0.51. Once i reassigned the dmx all is working again on 2.2.54. I will try tonight’s release and see if it makes any difference and report back.
Thanks, Johnny
Searched for hours for output configs, this is very complicated to follow through.
It looks very much like you are talking about MIDI Inputs, not Outputs (as you said), right?
So I got to start all over…there goes my weekend again
Hi @musicullum so just an update, it seems the loss of audio for me was because i have 4 songs in the setlist that has recorded tracks that output to the input stacks upon playback using the monitor button. On playback the tracks perform with the recorded parts playing through their respective stack ie, vocals, guitar.. with no problem. after playback has finished, i activate the monitor on each track that goes through the stack and i get sound on the channel’s inputs, but when i load in another set from the setlist i have no sound coming into vstl. I then have to reboot the software and then the sound returns.
Still the problem persists with the dmx track output reverting back to nc when reverting back to an older version of vstl, so to clarify, open project with 3.0.52 and dmx output on each track is set to usb dmx which is great but if i load vstl 2.2.54 which is the version we gig with after using 3.0.52, all the dmx track outputs show nc and have to be reassigned or reset with a backup project.
Hope that all makes sense.
Thanks, Johnny
This reply was for FKalmus…
Mee? My issue was described:
Dont’t think I can describe it more precisely 
I wrote “OUT” ports, and meant OUT ports.
Anyways “reseted the connection pairing” as you suggested and will keep my eyes open
You are correct, sorry. There are multiple issues in this thread and I got confused.
To be precise, at my last gig-soundcheck , I needed to fix OUT’s (wrote my report afterwards), but true what true happened sometimes with input ports too, you’re absolutely right about!
Correcting: that happened me both with I / O ports in the past. And more importantly fixed portpairing, saved, gigged and you received a “fixed file” so basically you should see the right pairing (because gigged/saved with the right pairing).
Did u find something suspicious maybe?
// Currently went out for 3 days, and was not allowed to bring else then my phone 
will play on Th & Fr, will check ports pairing then //