![]() And I suspect that will mean I'm running Vision 2017 for a very long time at this rate. I've already suspended my subscription until this issue is fixed. I've been fairly patient on this issue but I'm currently evaluating Capture Nexum and Realizzer for purchase in my next project because Vision is broken for video. As a software company the phrase "renders the hardware question moot" should be of interest to you. Since this runs of TCP/IP it also renders the hardware question moot. Something like NDI which has converters for Blackmagic, Syphon, Spout, Capture Cards, Web Cams, Other media servers and CITP protocols. * Support for Virtual Webcams in general which would render all the above moot as you could use Syphon or Spout to make virtual inputs It bypasses the hardware chain entirely and is a simple shared texture. * Spout inputs on Windows (which is basically Syphon for Windows) ![]() This bypasses the hardware issue entirely so it seems like an obvious choice. Why? Because it is native to Mac OS and used in the VJ pipeline by basically every media server. * Syphon inputs on Mac (again, very well documented software and a simple texture-share given the fact you're rendering in OpenGL this is borderline trivial) Why? Because they are solid affordable capture cards that run on Mac and Windows * Blackmagic inputs (the SDK is pretty well documented) While I'm on the topic it would be nice to see you integrate: ![]() I could be wrong and a video patch is on the way but I downloaded the Vision 2018 demo today and I get the same broken interface with no available inputs for video projection. Mac OS ends up the closest with some bizarre pixelated green/magenta image of my webcam.Ĭonsidering the fact video is broken in Vision as it stands you guys might want to explore "universal" connectors like NDI as it seems your ability to support hardware is hampered at best. I have (4) computers that I can test against (a surface, a MacBook Pro 2016 Touch, a MacBook Pro 2010, and a box I built myself running windows 10 that's nothing fancy) and none of these have working video input. I'd also like to point out that video input has been broken in Vision 4, Vision 2017, and Vision 2018 with some, but not all, capture cards working in Vision 2.3. In order to display captions you will need a video license which you can rent or buy.As a developer myself I can understand the hurdles. QLab supports projection mapping and multiple surfaces to display captions which can be controlled with a keyboard, other instances of QLab, MIDI or OSC. Therefore it is recommended to have a clear design direction before you start programming with QLab. You will have to manually change each cue one by one. For example, if you decide to change a font or colour after programming each cue. Given the nature of QLab it can take a long time to programme each cue and you cannot make adjustments to multiple captions. In addition to designing captions, you can programme fade up / fade down / cut / swipe transitions for the captions. ![]() Each cue is directly editable with text-based editing for font, colour and size. ![]() These can be used to create caption based cues. QLab provides a text option for adding your text based cues to a show. QLab is a widely used macOS based software that supports sound, video and lighting cues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |