Other updates coming soon, like render to texture instead of window.just working on resizing issues UPDATE v1.11 – new/prettier icon from awesome user Simas Gineika. UPDATE: v1.1 – camera stream now resizeable. Let me know if you have issues or suggestions! Currently tested with t1i, t2i, t3i…and will hopefully work with 5D and 7D I also can’t release the EDSDK and you would have to grab it yourself from Canon’s developer website. I will be releasing the source soon, but it is literally just taking Kyle McDonald’s of圎DSDK and the ofxSyphon addon and putting them together if you want to make something yourself. This lets you use your DSLR live in VDMX, Modul8, MadMapper, and any Syphon enabled app! Unfortunately, I have no plans to support this app any longer, so I’m going to have to leave it up to the next person to take the Canon SDK and mash it up with Syphon…Ī sort of beta release for using your Canon DSLR with the amazing Syphon framework. To be fair, when Vmix crashes, Studio Monitor will as well.UNFORTUNATELY – I’m getting reports that this app now crashes in macOS 10.13 High Sierra. I'm fairly certain it has to do with some sort of HDMI error not being properly handled by the Flex (which it should be, of course), but it should also be properly dealt with by the receiver as well. What do you want me to do the next time my BD Flex crashes Vmix? Last time it was in that state that Vmix would crash EVERY time it tried to receive from the Flex was just a week ago. We are happy to be proven wrong if someone can point us to an example NDI source that crashes consistently on the latest version, but so far no one has been able to demonstrate that. This would appear to confirm that the faulty hardware is likely the cause in all other cases. We have numerous systems running on NDI 24/7 with various types of sources and have not seen any issuesīesides 1 and 3, which can both be permanently solved. In all the cases we have seen, the cause is likely one of the following: We can do our best to report any bugs we find to the appropriate vendor for you if this can be replicated on our systems. There has unfortunately been a lot of misinformation online that these issues are somehow specific to vMix, which is not the case as we use the same NDI SDK as all other software, but (Perhaps by unplugging/plugging in sources on the NC1 for example) I would advise as a test to run vMix and Studio Monitor at the same time with the same sourceĪnd see if you can trigger the issue repeatedly. However in order to do this, we need to be able to replicate the issue. In both cases we can either submit a bug report to have the encoder fixed or to NewTek to have the NDI SDK updated. When an issue like this has occurred in the past it has either been due to an NDI SDK bug or a faulty encoder. Sorry to hear you are still having trouble. sometimes it's 15 minutes into a show, sometimes never, sometimes at the end. We are really at our wit's end because there is no rhyme or reason when this will happen. There's really nothing we can do at this point and it's very frustrating. We have even simplified the network to where there's only the Tricaster into Vmix, and even with that simplified approach, vmix crashed on a show today.We make sure everything is updated to the latest software. We have NDI coming from our Tricaster NC1. We do not have any other programs running. Like everybody else on this thread, we have had the software crash without explanation multiple times. We keep sending our reports to Vmix, but they don't seem to be able to solve the issue. This problem is happening to me repeatedly as well.
0 Comments
Leave a Reply. |