Jump to content

Jesse Cogswell

Member
  • Content Count

    31
  • Joined

  • Last visited

Everything posted by Jesse Cogswell

  1. Jesse, we almost have the same name. That's kind of neat. When I was exporting the video on the project, I was always rendering out a still before rendering the video to check camera shots, since my monitor in full screen was different than my rendering aspect ratio and always saw the full rig in the still. But you are quite correct, there is a large number of emitters in the file. So I stripped out everything except the D60 top light from the file and made a quick cue stack to easily check the timing. The lights all flash on for one second, off for one second for five minutes, with them flashing red every 10 seconds, and at each minute, a different column stays on in blue.I rendered out a file at 24 FPS and one at 30 FPS. The DMX file comes in right at 5:05 in length, but the 24 FPS video is 5:03 in length, and the 30 FPS video from the same DMX file is 5:08 in length. This is a similar amount of "drift" that I saw during the show exports. I was able to get around it by placing a "blip" cue (top light at full in a 0 count, out in a 0 count after a 0.5 follow) at timecode 00:00:05:00 and a similar one at the end of the cue stack. In Premier, I make sure the first blip lines up exactly at 00:00:05:00, then use the stretch time feature to make the end blip line up with the timecode in the console and re-render the video. The good news is that the "drift" is at least a consistent rate. The v3d file is attached. I can't attach the video or DMX files to this, but assuming you're able to access Google Drive links, the DMX file can be found here, and the 24 FPS video can be found here. Notes on the video: you'll see the starting "blip" at 00:00:04:12. This lines up with timecode 00:00:05:00, the timing check begins in earnest at 00:00:09:12 in the video, which should line up with timecode 00:00:10:00. As originally recorded in the console, at timecode 00:05:05:00 the lights will cut to black, which occurs at 00:05:02:02 in the video. These tests were done on Vision 2020, version 25.0.3.534518, DMX provided by ETC Eos version 2.9.1. While I have your ear, as a feature request, could we get a DMX trigger channel for the DMX Recorder? CueServer, DMX King, and Alcorn McBride Light Cue all have a way to do this, and it makes streaming DMX a lot easier since I can sync it to a cue in my console rather than starting timecode and pressing a button in the software to start recording. Thank you for taking the time to look through this. - Jesse Timing Check.v3s
  2. Good morning, all. I've been working from home trying to get some programming done. I've done a timecode show using an ETC Eos, and rendered out a DMX file but have run into several issues. The biggest issue is that when I render out a full video, the timing of the video is much slower than the original programming. IE, a song might be 8:03 long, but the rendered video is 8:08, so when I pair the video up with the sound file in Premier to render out a finished video, the video is out of sync and only gets worse the longer the video is. I've tried rendering at different frame rates, different resolutions, and different levels of quality in both Vision 2019 and 2020 and on multiple machines, but never once gotten the lighting to sync with the original sound. In the process of trying different export options, I also had a problem with trying certain frame rates. Any time I chose 48 frames per second and clicked "Render," the dialog box would close but would not start rendering. I have only been able to render at 30 or 60 frames per second. I've also had several problems where some fixtures don't render in the video in some renders. When I playback the DMX stream, everything matches the console output as originally recorded, but the video rendering doesn't have the D60 back light, the Colorforce 72 cyc lights, Lustr 2 front lights, or X4 Bars. But the Axiom Beams, Quantum Spots, Mac Vipers, and Magic Panels all work flawlessly. After the rendering is complete, the fixtures that did not properly render stop responding to DMX until I restart the Vision software. It's a bit of a bummer in that I don't know whether or not all of the lights are properly rendered until after I've spent the couple of hours it takes to render. My system is a Surface Book 2 with an Intel Core i7-8650U CPU, 16 gb of RAM, and an NVIDIA GeForce GTX 1060. - Jesse
  3. I was able to find the .webarchive backup files of the Vectorlab articles on List Browsers, which did not include the example script above but answered all of my other questions. I ran into a bug where I was not able to populate a solid rectangle cell outside of the SetupDialogC case (my plugin includes an "Add Row" button, which opens a dialog box to set options for the row, and executes the instructions for the new row after pressing 'OK'). All other cells would properly update, but I could not get the solid rectangle to show up (but could affect existing rows with the SetLBItemFillForeColor function). The only way I was able to get around this was to have the Add dialog box update the arrays that the List Browser used to initially populate, then use a GOTO command to a label in the SetupDialogC at the top of the List Browser InsertLBItem code to repopulate the existing List Browser window. I understand that this isn't exactly Nemetschek's highest priority, but is there any way we could get a proper set of documentation for List Browsers and Object Events? Both sorely lack examples in the Function Reference and some of the Object Event functions even lacking descriptions. These both provide ways of making incredibly powerful plug-ins, but their implementation can be fairly obtuse and it's a shame that the only useful documentation is on a now-defunct website.
  4. Hello there! I am doing my damnedest to write a List Browser but the documentation available on the developer.vectorworks.net for List Browsers is borderline non-existent. The example that the OP posted above looks like it would answer all of my questions, but vectorlab looks to have closed down and the WayBackMachine didn't snag snapshots of the List Browser articles. Is there any chance that someone saved the scripting example and would be willing to share?
  5. I don't think this bug is drawing specific. While building Marionette networks, every 20 minutes or so this happens where the OIP stops updating/responding. Whenever I encounter this, I immediately save, close the document, and reopen it (not restarting Vectorworks) and am able to keep working.
  6. I just did a show last month with Encores and can confirm that the zoom is backward from both the ETC Eos profile as well as reality. For the previs, I built a custom profile for the fixture that inverted the zoom range, but had to correct it when I got in the space. Also, I don't think an option to invert zoom within Vision would be a great idea. Pan and tilt should be inverted because a fixture might change orientation from the plot to where it's hung based on cable runs, power, etc. Being able to change pan and tilt quickly to match reality without having to rotate or move the fixture within Vision is great. The only time you would need to invert the zoom is if the profile within either the console or Vision were wrong.

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...