Jump to content

Gaspar Potocnik

Member
  • Posts

    140
  • Joined

Posts posted by Gaspar Potocnik

  1. You need something that outputs dmx, depending on the brand of consoles you get some free Chanels, but I believe there is no console manufacturer that will let you output unlimited channels...

     

    That being said, for MA Lighting you have two options, if you want to use GrandMA 1 or 2 OnPC you need to download the ESP Vision Connection Driver from MA website (https://www.malighting.com/downloads/products/grandma2/) which only runs on Windows (so your Vision also has to run on Windows), and allows you to use MA NET to connect to Vision and has no limit in the amount of fixtures you can control. The other option is to use GrandMA Dot2 onPC, which has one free universe through Artnet or sACN. 

     

    I believe Chamsys also has a free universe, not sure on the rest of the manufacturers.

    • Like 1
  2. One option is to export as separate .esc (which is what I usually use) but what happens is VW exports everything that has the same texture together or if it has no texture then everything with the same color fill. So assigning different textures or color fills make separate meshes in Vision.

  3. Coming back to this topic after a few years...

     

    So I’ve redone symbols so that everything is uses classes that work for me, but I still haven’t been able to change de default class of the label. I’ve edited the string in the plug in but still it isn’t changing, what am I missing?

  4. 2 hours ago, Carl Burnett said:

    I am using 4 screens but want to show image across all screens (not four images)

     

    For this you have to create a renderworks texture with an image from your content (or print screen of your output), apptly it to your four screens, an then with the attribute mapping tool "map" the screens. I usually use the actual raster file for the production. Afterwards in vision some cropping is always needed, but not time consuming at all.

     

    Regarding the capture device, here are some specs and options.

     

    • Like 2
  5. On 1/30/2019 at 12:10 PM, scottmoore said:

    You can do that by dragging the symbols into a blank file, making sure they are actually in the drawing and not just the resource browser. Then edit the class names. Note that every symbol you want to use would have to go through this process. The upside is that then they work as you are used to working. The downside is everyone else will be used to working with the original class settings so if you are sharing a drawing, an explanation is in order. 

     

    I would like to know of there is any coding coding in the background that might be negatively impacted by changing class names. Any issue with Braceworks, worksheets, etc.?

    That’s a good workaround, but I am just creating new custom libraries that way... maybe the ability to edit the root class can be added into vw2020...

  6. The big drawback with this workflow is vision and lightwright.. Personally I'm pretty happy with 3d Label legends. but they are still not quite there. Hopefully we can get 2d info in 3d symbols views in spotlight too, that would also make a difference...

  7. I've tried importing different molefays and all of them render a much higher CT than what they are supposed to. Comparing them toa generic P64 really makes you see the difference. I've tried lowering the candela with no difference in color and changing the color temperature which makes vision crash (already generated a report). None of them have the possibility to add a color so that workaround is no good.

     

    Getting nostalgic with the way Vision 2.3 rendered molefays 😞

  8. 4 hours ago, bbudzon said:

    About the 640x480 thing; you will need to make sure the device outputting content is configured for 1080p as well as the device inputting content. As far as I know, we don't limit the resolution of live video content. The webcam on my MBP streams 720p content into Vision without issue (720p=1280x720, which is a higher resolution than 640x480). So, it would seem there is no limit on this content in Vision or the capture library we are using.

     

    @bbudzon my MBP 2016 camera is also being limited to 640 x 480 (I'm assuming this because of the coordinates of the crop raster). The content is 1080 and so is the config of the output. I can't configure the input since it is a driverless card (actually that resolution isn't event listed in the specs of the UVC grabber) I've trie3d two different computers and have the same issue.

     

    And I completely agree with the limit, I wanted to know if this was a known limit, since it is not listed anywhere, and if could be changed anywhere, just to know the limits and how it works...

    • Like 1
×
×
  • Create New...