Hello!
For both issues, I need some more detailed informations, what you want to do or what you did do - maybe also in combination with your project, with them you have the issues. From the current point of view, it's almost impossible to give you an helpful answer.
Stefan
When i switch timecodes one after one the DMXC3 crash on the 5th or the 6th timecode and then i have to reopen it again, i tried this thing and its doing the same always.
Ah ok. This is some sort of known bug which we currently can not handle. The problem is that DMXControl 3 is running out of memory. We have to load all the images of the soundfiles into the memory. And we tried to force the UI to throw them away if they are not in use anymore. However, we had no luck with that so they remain in the memory (is some sort of a known issue for the framework we use). We will be only able to address this issue when we have replaced enough window modules of DMXControl 3 to have one common framework basis (and not a mixture of three like currently). So unfortunately, this issue will continue to popup if you load multiple timecode shows in the timecode player.
However, some users reported that if they keep the timecode player closed during the show, it will not load the files and thus will not crash DMXControl 3. So you can trigger it with commands (like you already do) and keep it closed and this should do the trick.
LightningBrothers Is there any chance that these bugs are going to resolve soon?
We try our best but I think this will take some time. We have to replace at least three major window modules (Input Assignment, Stage View, Programmer) in order to kick out one of the three frameworks (and subsequently can switch to a 64bit version). So as you can see, those modules are larger ones and we will need some time to replace them. So unfortunately, there is no quick fix for that. If we would know one (for our some sort of special structure), we would try to implement that.
Hello. I just wanted to mention that I found the out of memory issue causing the crash when there are multiple timecode shows in the project and you switch between them. It will be fixed in our next release. Unfortunately there is no date yet for that release.
Regards
