Jump to content

Josef Swanberg

Moderator
  • Posts

    56
  • Joined

  • Last visited

Everything posted by Josef Swanberg

  1. In version 6.2, and later, you can move the corner points with the arrow keys. Just select a point and then hold Ctrl while pressing the arrow keys.
  2. You can find your answer in the user manual. There is a section about "Rounded Corners" on page 135: https://cdn.dataton.com/Files-PDF-etc/userguides/WATCHOUT_Users_Guide_6.1.pdf?mtime=20170725121436 <excerpted from WATCHOUT 6.1 User Guide, page 135> ROUNDED CORNERS Applies a corner radius and/or feathered edge to an image. Note that for still images, this tween track is only available when “More Effects and Capabilities” is selected (see “Optimize For”).
  3. Although virtual displays were not mentioned in the original post of this thread, I am commenting on them here. If you read the WATCHOUT manual, you will see that virtual displays were originally meant mainly for two usages: Management of LED wall modules Dynamic texturing of 3d objects Using them for other things, especially when using virtual display media on other virtual displays, may not yield the result you are expecting. When using a virtual display media on other virtual displays you get one frame delay on the result. This is due to how the virtual displays work internally. Think of virtual displays as cameras, with displays connected to them. If you have two cameras, and camera 1 films some moving object, and then camera 2 is filming on the display showing the image from camera 1. Then if you view the images of the two cameras on two displays next to each other, you will see the image from camera 2 has a delay compared to the image from camera 1. The attached image is a sketch of a top-down view on this scenario. If you keep adding a camera 3, filming on display 2, and a camera 4 filming on display 3 and so on, each display will get a more and more delayed image. Virtual displays work the same way. I hope this explanation makes sense. As a side note, virtual displays are quite heavy to render, each of them requiring a separate render-loop. Therefore, having too many of them may have an impact on your systems performance.
  4. A few questions: 1. What is the video format that is supposed to be played on the virtual display (codec, resolution framerate etc)? 2. Does it show up in the production software and not in the display software, or does it show up in neither? 3. What if you swap the video for a still image, does that have a different result?
  5. Watchout gets the output numbers from the graphics API. There isn't necessary any correlation to the output numbers shown in Windows, or in the graphics card control panel.
  6. Hi Arun, It would be useful if you could provide us with a little more information. What version of WATCHOUT are you using? Can you describe a little more what you where doing, and what result you got, compared to what result you where expecting?
  7. Hi Tomas, This is a known issue, and it has been fixed in an upcoming release of WATCHOUT. /Josef
  8. Hi, It would be interesting to know more details, what part in the workflow failed? Was it the importing of 3d-objects into WATCHOUT, or the management of how 2d media is mapped onto the 3d objects? Or (most likely) was it the calibration of the projectors using the calibration points, or the soft edge management of overlapping projectors?
  9. We need to know what error you are getting, top be able to help you. Is it a specific error message? /Josef
  10. Not composition, but a virtual display will do!
  11. Added download links to 6.1.3, 6.1.4 and 6.1.5 here: http://forum.dataton.com/topic/1126-dataton-software-earlier-versions-archive/ However I would recommend using the latest version 6.1.6, as it contains some important improvements and bug fixes.
  12. Added download links to 6.1.3, 6.1.4 and 6.1.5. However I would recommend using the latest version 6.1.6, as it contains some important improvements and bug fixes.
  13. Since version 6.1 you have been able to control the geometry points with the keyboard arrow keys. You can do this using the Rounded Corners tween (available since version 6). Can be applied to both video and image cues, but images need to have "More effects and capabilities" enabled in their corresponding media. Tip: Just make the dialog window larger! =) Have been able to since version 6.1. Otherwhise you have some good points!
  14. The simple answer here is that rotating, or otherwise moving, 3d mapping objects is not supported by our software. What this depends on is the blending masks, that you need to blend the images together from your multiple projectors. These masks are not dynamic, or calulated in real time, but they are static. This means that you can construct blending masks that look good from one direction, when you have calibrated your mapping projection, but when you start rotating the object, even though you may manage to synch your rotation of the 3d object in WATCHOUT, the blending will not change, and it will not turn out a good result. I'm not saying it's not possible, there may be ways of working around this problem. But there is no easy solution.
  15. You can always copy and paste stage elements from a show, either into another show, or into a text editor to use them later on. This may not be exactly what you are asking for, but can be useful in some cases.
  16. Tiers is the way to go, if you don't want the displays to see the same media cues. But then, as you say, you loose the blending. One way to work around this could be to create inactive "dummy" displays, essentially copies of the active ones, on each tier. That way the active displays blend to the inactive ones, even though they are not really used.
  17. What version of WATCHOUT are you using? I believe this bug was discovered and fixed for version 6.1.3, and has been working since.
  18. What display framerate have you set in the WATCHOUT preferences dialog? There was some change done in this area for 6.1.5, that the display software should always attempt to set the framerate as specified in the preferences, if it is available. Before this value was more of a recommendation.
  19. Sorry for not answering this earlier, but there is your problem. You need to isolate those cues (normal cues or 3d objects) rendering the contents of the virtual displays, so they are not visible to their corresponding virtual displays. This can be done either by putting those cues on a layer that is limited to only one tier, or as Mike mentioned above, limit a whole timeline. For example: I usually solve it by putting the 3d object on the main timeline, and (IMPORTANT) limiting that layer to only render on the base tier. Then I place my projectors on the base tier, looking at the object from different directions. Then I create a second tier, lets call it Virtual Tier. There I place all the virtual displays, and make sure that all media cues that are visible on them are only rendered on the Virtual Tier. Then I assign the virtual displays media as textures on my 3D object. If done correctly, it doesn't really matter how the virtual displays are placed in relation to the 3D object on the stage. But of course it helps the workflow if they are somewhat separated. Hope this late answer helps.
  20. Hi, The second "3" means just what the message says, "Not enough video memory". What production/display computer setup are you using? What video file formats are you playing? What version of WATCHOUT are you running? Perhaps you could try the new version 6.1.5? I believe things have improved in this area, as we have switched to newer video codecs. /Josef
  21. This issue will be looked into for a future release of WATCHOUT. In the meantime, a workaround can be to map the video indirectly using a virtual display. As a bonus you then get more control of your video playback, such as looping and free-running.
  22. The user's guide for WATCHOUT 6.1 has now been released. It can be downloaded here, and on the download page. Any feedback is welcome!
  23. The user's guide for WATCHOUT 6.1 has now been released. It can be downloaded here, and on the download page. There you can find a description on the hittest-command, and how it is used with the interaction name.
  24. Please send the show file to support@dataton.com. Shows made with 6.0.x should definately be able to open in 6.1.x, but after saving it there you can not go back to 6.0.x.
×
×
  • Create New...