Hi! It meight be hard to describe, also can’t reproduce it with BLANK project, also rather happens under WIN (exept **)
But my experience is
anyhow I set Video track to Video1, stepping between songs it creates itself a new video connection-port exactly name “Video: Video1”
when deleting (e.g. second or third auto-added Connection):
- some songs, where video track set to Video1 (vidPort #1), gets back to < nc > state, despite of track is set to Video1==vidPort#1 and vidPort#1 not touched ).- when deleting 2nd, 3rd video-port under Connections, VSTL crashes.
** Crash on
-
on WIN happens so fatal, app can’t write/finish crashdump
-
OSX crashdump created / attaching here:
vstlive-2024-02-18-185738.ips (76.1 KB)
monday’s one:
vstlive-2024-02-19-092815.ips (88.9 KB)
Happens me to my production project, can’t reproduce with blank proj. I can provide anything that meight help
Just to give some picture, what I’m doing, or trying to do (set all video tracks to Video1 == vidPort#1 == my HDMI out)
and finally, after navigating back and forth, switching output-ports, video renderer (WIN only!) can get completely confused and renders content from different songs even if currenct song has nothing to display… looks like this