Jump to content

bbudzon

Vectorworks, Inc Employee
  • Content count

    65
  • Joined

  • Last visited

Community Reputation

10 Good

About bbudzon

  • Rank
    Apprentice

Personal Information

  • Location
    United States

Recent Profile Visitors

444 profile views
  1. Thanks Dan! I got your email, downloaded your files from dropbox, and will take a look into the issue!
  2. You can email me directly at bbudzon@vectorworks.net 🙂 Thanks again for your report, gives us a better starting point! Just to reiterate my point, the more details you can give us about this file the better. What fixture was breaking? What was it's unit number? What are some of the DMX Addresses Vision has "burned"?
  3. This is a VERY detailed write up. Thank you very much for you investigations into this issue. We have had similar reports in the past, but never with this level of information. Hopefully with this added knowledge, we'll be able to tackle this issue once and for all. I'd love it if you could post your files and any additional information you may have such as what specific universes/addresses are hosed and the unit number of the fixture your having problems with in your file. It may also be beneficial to contact technical support and have them open a ticket for you if you don't have the ability to create one yourself in JIRA.
  4. bbudzon

    Video Capture Cards in Vision

    We have posted a Tech Bulletin which should hopefully answer some of you system requirement questions. I'd also refer you to the online documentation for workflow related help. http://www.help.vision.vectorworks.net/ Capture cards are what you want to search for and it all starts by assigning a capture texture to a MeshShape. Hopefully this will get you started. http://app-help.vectorworks.net/2018/Vision/index.htm#t=2018_Vision%2FVision%2FSpecifying_Textures.htm%23XREF_12646_Specifying_Textures&rhsearch=capture card&rhsyns= Lastly, Vision does not currently support CITP, but it has been highly requested feature; along with NDI. The best way to get multiple inputs into Vision is through a multi-input capture card, multiple capture cards, or a single hdmi feed that combines video into a grid form. Once Vision sees this single hdmi grid feed, you can crop it into individual live video streams.
  5. bbudzon

    Crash - Cameras

    Hey Richard, I apologize for the inconvenience. It appears there are some bugs in this code that had not yet been reported. So thank you for your feedback and we will look into resolving this issues asap. The cameras will take a little bit more work on our end to fix than the ambient, but I can at least give you a work around for the ambient in the mean time. It appears ambient is causing issues when it tries to update the Global Properties UI with the new DMX value. What seemed to work for me was selecting anything other than ROOT in the Scene Graph Dock when adjusting the ambient this way. (Since the Global Properties are only visible when ROOT is selected in the Scene Graph, selecting something else so the Globals aren't displayed works around the issue.) Thank you again for running through the software and reporting these issues to us so we can resolve them.
  6. Good @tddesigner I'm glad this worked for you. My apologies for it being broken in the first place but now we know it is broken so we can fix it! Thanks again for your feedback and let us know if you have any other concerns.
  7. Hey @tddesigner This is definitely a bug. We can fix it for SP4, but we need to get you a work around for the meantime. This bug is related to static vs dynamic caching of geometry. The static cache is broken. One way to resolve your issue is to move the models you want invisible into dynamic cache to work around the issue. To do this, first select the MeshShapes or Layers you'd like to be invisible. Assign an XForm Universe and an XForm Address to these objects. Assign an XForm Delta Y of 5000 (inches) or something very large that will move the objects out of view. Now on your light board, ensure you are sending zero DMX to the XForm Universe and Address. To "hide" the geometry, send a value of 255. This would mimic flying out the set piece on a fly rail.
  8. bbudzon

    Video Screen bug

    This bug is in VW 2018 SP2, not Vision 2018 SP2. We will try to figure out if this broke in a VW SP and why. Fortunately, there is a fairly easy and straight forward work around. Simply don't assign video from VW until this bug is resolved or use an older VW releases. I would recommend using VW 2018 SP2 to export your video screen with static images for the texture, such as color bars or the VW logo. This will bring the screen over as one mesh shape. This mesh shape can have its video assigned once in Vision and things should work fine. I wanted to get you an updated file that had only one mesh shape for the screen, but it's harder to remove a video file attached to a screen that I would have thought. We will discuss this internally and try to make that workflow easier. For this reason, I'd recommend you try to follow my steps above so you don't end up with multiple mesh shapes for your screen in your file. That being said, if you don't mind the extra mesh shapes, I've attached a zip that contains an updated v3s with video working for all mesh shapes. I hope your video screen issues are resolved for the mean time and that you enjoy the new features in Vision 2018 SP2! Video bug.zip
  9. bbudzon

    Video Capture Cards in Vision

    Everyone, We have flushed out the implementation and workflow for capture devices. We are in the process of getting a beta together to verify customers are not experiencing issues before we release the Vision 2018 SP2. Hopefully we've gotten this issue resolved and we can get you guys pointed in the right direction! I'm working on getting a Tech Bulletin together to flush out the details. Keep your eyes peeled!
  10. All, Keep an eye on this thread: We will be keeping it up to date with the latest information. I would hold off on buying capture cards until we can make some cheaper recommendations (a $3k capture card is unrealistic), but at the very least if you have a capture card already, you can verify that it either does or does not meet the requirements we believe are necessary for capture to work properly.
  11. bbudzon

    Feature Request: NDI Support

    @Daniel B. Chapman Keep an eye on this thread: We will be keeping it up to date with the latest information. I would hold off on buying capture cards until we can make some cheaper recommendations (a $3k capture card is unrealistic), but at the very least if you have a capture card already, you can verify that it either does or does not meet the requirements we believe are necessary for capture to work properly. And to address your last post a little more directly, it appears that so long as your capture card supports UVC and YUYV422/YUV420P, then we will use Windows Media Foundation and AV Foundation libraries to get them to work with Vision.
  12. bbudzon

    How to get media server into Vision

    @Anthony LeeKeep an eye on this thread: We will be keeping it up to date with the latest information. I would hold off on buying capture cards until we can make some cheaper recommendations (a $3k capture card is unrealistic), but at the very least if you have a capture card already, you can verify that it either does or does not meet the requirements we believe are necessary for capture to work properly.
  13. Hello all, There has been a slew of problems surrounding video capture cards and Vision. A large part of this is due to the number of manufactures that are out there and the number of proprietary drivers required. Some capture cards explicitly state that they only work with certain software suites. We have been doing a lot of investigation into the capture code to figure out why some devices were working and some weren't. As it turns out, this was more a matter of how the operating system handled the capture device rather than how Vision handled it. What we have found, and tested to a limited extent, is the requirements you should look for in a capture card. First and foremost, all capture cards must be supported natively by Window/OSX; meaning no drivers are required (they can be recommended, just not required). The way these devices work is through a universal driver for video capture called UVC. UVC drivers ship with Windows and OSX so again, no installation required; UVC ships with your OS. Lastly, video can be output in several formats; RGB24, RGBA32, ARGB32, ABGRA32, UYVY422, YUYV422, YUV420P, H264, MJPEG, and many more. Currently, Vision only supports YUYV422 and YUV420P. Once we were able to determine what the Operating System's requirements were for video capture cards, we were able to make educated guesses as to which devices may work. We happened to have a AV Bridge MATRIX PRO lying around (http://www.vaddio.com/product/av-bridge-matrix-pro) that we were able to determine supported UVC. We weren't sure what pixel format it was sending out, but we decided to give it a shot anyway. Turns out, it worked!! We will be purchasing more cards over the weekend that we believe meet the Operating System criteria to test them out. Once we have those cards in house, we should be able to determine that most (if not all) UVC compatible / YUVY422 capture devices will work with Vision.
  14. bbudzon

    Sort Scene Graph?

    This was something that was highly requested and highly considered for our 2018 release. Please stay tuned for updates.
  15. We definitely need to get a better way to find Vision fixtures in VW. A little developer secret, in 2017 the Inst Type can _sort of_ be used as a search box for populating the fixture mode. In 2018 Beta, this was moved to the Fixture ID field.
×