[3.0.35] BUG - DMX recorrding from artnet in prduces lot of points at record stop on every channel

See image. I recorded a track from artnet IN (tried multiple times from multiple sources on same pc and from dfferent pc). Every time you stop recording, at the record stop point all channels receives all previous values alltoghether in a signle moment, creating a enourmous overload of dmx engine:

You see, @musicullum @Spork the yellow highlighted big vertical line full of dmx points (all previous values of each channel is saved also at the end of the recorded track) should’nt be there and is not on original dmx sent; that put dmxengine in overload and stutter.

Cheers, Ciro.

Hi @ciro1983811 ,

What were the sources to get it reproduced,
Michael.

Hi @Spork , it happens with every source, in this case I was transmitting artnet form another software on 192.168.1.255 (broadcast), and recording to VSTLive artnet in . But you can reproduce even by internal loop via virtual Dmx cables out from a track and in to another track. When you stop recording this final line full of Dmx points appear (the points are all previous values of each channel all togheter at the stop position, so to reproduce you need to record few channels moving up and down before stop recording, and that channels will show the problem at the stop point).

@Spork @musicullum any findings about this? I’m in the process of redoing all DMX on my 80+ songs in the main project and this causes me a lot of troubles … if I try to delete the final overload of DMX points vstlive freeze for long long time trying to delete it…

Hi @ciro1983811 maybe could help you too, pull back the clip end a little bit, to “hide” those dmx-events

Hi @fkalmus yes I do this but still, all these point are loaded at song change increasing exponentially the loading time at song switch… I still can’t understand how the DMX engine was n vstlive requires so much resources given that other DMX softwares (like DMXdesktop I’m using right now, developed by a single guy plus ai help) can manage 1024 art net universes in milliseconds time … I’m reaching stuttering and long load times with 120 channels on one universe… :weary_face:

Hi @fkalmus and @ciro1983811,

the improved DMX Playback Engine is expected to arrive next week. If you like, please save one of your stuttering songs (Menu // Song // Save Song… - including media assets) into an empty folder, zip it, and share it with me. That would help us verify how the new playback engine performs with your song/project.

Different DMX systems have very different architectures and priorities, so direct comparisons are not always meaningful. What matters most for us is how reliably we can handle real-world projects like yours - so your test files would be extremely helpful

Michael.

Thank you @Spork , I will send you one song with recorded DMX from art net in , so you will see all the events created at clip-end while recording!

I did not mean to criticize your work, it’s just a consideration by a user not aware of all the thecnical stuff behind creating a DMX engine like this!

Great, thank you - that will be very helpful!

No worries at all - I didn’t take it as criticism :slight_smile:

Comparisons are absolutely fine and helpful. I just wanted to point out that VST Live handles multiple domains at the same time (Audio, MIDI, DMX, Video, Tempo, Lyrics, etc.), which makes direct comparisons a bit tricky in some cases.

In any case, your project will help us a lot to improve things further.

Thanks again :slight_smile:
Michael

hi @Spork ,

here you can find a archived project, 2 complete songs, the first have manual edited small dmx tracks, the second have one 3,6 MB dmx track of 120 channels (and the error at the end with lots of points due to it being recorded via artnet in).

the second one takes ages to load at song switch, and if you try to open dmx editor, or worse, to move drag or resize the clip, it takes ages. If you try to delete all the datas at the end of the track, it freezes the software, etc etc.

https://www.swisstransfer.com/d/9e4d575e-58ac-4fb9-b395-8bf77a9f389c

Regards, Ciro.

hallo @Spork , I think you have enough recent files from me. Suggest testing with “Witer Waltz, Flirt Waltz, Sleeping Beauty”, … but pick any with visibly more intensive DMX events. (FolderTracked DMX’s under some songs… so expend them if not sure)

Hi @Spork @musicullum any feedback on this issue?

I need to redo Dmx of 80 songs by recording artnet input, but at the moment lagging and all the phantom events points inserted at recording stop makes this effort gigantic …

Thanks, Ciro.

… yes, this one has high priority and should hopefully coming with the next Pre-Release (3.0.39). Thank you for your patience,
Michael.

Thanks!! also because … it’s not my case because we will never manage such a stage by ourself, but testing dmxdesktop dmx engine limits … here we have 6 universes, 3050 channels running live on 3dviz … sent out on artnet, couldn’t imagine recording all that on vstlive at the moment …:smiley:

In fact i tried recording on a new project the 6 universes … recording was visibly quantized in 16th i believe, not smooth waves/lines for chnanels, and anyway it froze at stop press in this state.

After 10 minutes more or less, done

see quantization in main view, and also on one of the channels bleow. Then, at the end of every channel, at recording stop:

Did you already apply “Edit/Reduce selected Events” on your DMX clips?

Yes, not the point, I have to redo all 80 songs beacause I’m moving from hand written few channels setup, to ai generated many channels setup.

The problem is managing 1 or more full universes, expecially if recorded via artnet in, completely cripple the Dmx engine.

the 6 universes one, completely freeze for 15 minutes to load 6 Dmx tracks at opening.

if you need it I’ll send it.

Cheers, Ciro.