Jump to content
Dataton Forum

RBeddig

Dataton Partner
  • Content Count

    340
  • Joined

  • Last visited

5 Followers

About RBeddig

  • Rank

Contact Methods

  • Website URL
    http://www.presentation-technologies.de

Profile Information

  • Gender
    Not Telling
  • Location
    Berlin - Germany

Recent Profile Visitors

1,261 profile views
  1. If you set all inputs with a ramp of 0, why don't you use the setImputs command instead? setInputs (page 183 of the current manual) This command is functionally equivalent to the setInput command above, but allows you to set multiple inputs with a single command. This is useful in the following cases: • When it is important that several inputs are set simultaneously, because their values are used in an interdependent way. If you use two separate setInput commands, it is possible that the commands will not be executed on the same frame. • When setting a large number of inputs, as it is more efficient to handle this with a single command than a number of separate commands, allowing you to set a larger number of values within a single frame.
  2. Hi Quim, Hope you're fine despite the situation on your end. I just tested a WP2 with NDI and WO 6.6.1 and this works fine. Regards, Rainer
  3. Unfortunately I do not understand this question. The space bar starts and stops the active timeline (toggle). If you just want to start it without the danger of stopping it with the same key, use the "0" (zero) on a numerical pad of your keyboard. In theory, you can connect any number of display computers to a production computer as long as your network is set up correctly. In practice, it might be difficult to work with hundreds of display computers in one project file due to handling aspects in your stage window etc.
  4. I'm not saying that using a cue instead of a time to jump to is safer but that is what we normally use and we have not seen a situation where the loop didn't work. It's still worth a try I guess.
  5. The only moment where you need a higher bandwidth is when you transfer your media to the display computers. During playback the data rate is very low. The cluster master sends a heartbeat which is timing critical but does not really produce data traffic and the cluster members send a short string every few moments to show their existance in the network (that's what you see when opening the network window). I don't have data rates but it is very low. The only moment when the data rate is higher is when you push content to the display computers or when you use NDI, Artnet or streaming sources. The moment when you establish the cluster is also slightly more critical since the master has some timeout and if the players do not report back in the given time the cluster might not work as expected. This is usually only critical in very big installations with many display computers.
  6. WIFI could be possible BUT do not expect frame accurate sync between devices on a wifi network due to the data packet overhead and uncontrollable data rates in wifi networks. Also you'd need to take into account that only three 2.4GHz networks can live together without interfering each other. I assume that there are many people using wifi in such an environment and in the end they all share the bandwidth. There are wifi access points with high power and beam transmission which you would use for longer bridges (two ap talking to each other) between networks. They are very strong and focused but not legal in every country.
  7. Haven't seen this for 10 years or so. Back then it could happen if too many control cues would sit at the same time in a timeline. What is controlling your cluster? Have you tried to loop back to a named cue instead of jumping to a time? It's my preferred way to loop sonce you can easily adjust it by just moving the "target" cue.
  8. In our market, a media server is commonly referred to as a playout computer for a mulit display presentation software, like WATCHOUT. While a server in IT terms is usually a central computer holding the data for a wider network of workstations or personal computers, we (and other manufacturers) call our display computers "media servers". Here the content is actually sitting on one or more media servers which are connected to physical displays, like projectors, led screens etc. Click on the discover button on the website www.dataton.com to understand the WATCHOUT structure. We're also currently working on an introduction video which should give you some more ideas of how WATCHOUT can be used. Keep an eye on the website or the forum where you'll probably see a note once the video is ready.
  9. Hi Mahesh, domeprojection has a couple of tutorial videos on their website. They show you how to use the calibration software itself. https://www.domeprojection.com/support/tutorials/ Once the calibration is done, the export to WATCHOUT is very simple. You just select the exporter and import the file from WATCHOUT. WATCHOUT will then create the correct screen rectangles and shading files (soft-edge). If you have access to a small webcam, like the Logitech C930e, and some projectors, you can try their demo software which you can find here: https://www.domeprojection.com/support/tutorials/ It does not include the export to WATCHOUT but this is the least complicated thing in the whole process. We actually plan to make a small video of how to use the demo version of the software but can't yet say when this will be ready. BTW, the latest version of the ProjectionTools PRO AV also supports calibratiion for 3D projection mapping. Hope this helps.
  10. RBeddig

    WATCHPAX4

    You can use audio interfaces which are supported by Windows natively. This should be the case with most USB audio interfaces with two outputs. If you connect an audio interface to a normal Windows 7 computer and it does not ask for drivers, it should also work with a WATCHPAX 4. You should also be able to use the Audinate AVIO USB I/O adapter for Dante. It appears as a stereo WASAPI interface on our WATCHPAX 40 and doesn't need drivers on this machine. Since the C drive of all WATCHPAX servers is write protected, you can't install any extra drivers on such a server.
  11. Looks like a good choice, but make sure to uninstall all unneccessary bloatware from DELL since those might influence the stability and perfomance of a computer. Depending on the number of outputs and codecs used in your show, the videos might still stutter a bit in your stage preview. This is normal since the stage window also acts as a "display computer" and needs to read all videos from your SSD, push the pixels through CPU and GPU , scale it down and render it. So in a larger show, which maybe uses 4 servers with 4 outputs, your production computer tries to simulate the load and performance of those 4 big servers. You can turn the video preview off and set it to thumbnails once your timing is correct.
  12. Hi Orf, I did some research on it on my production computers and I agree that this seems to be a bug. The thing is that WATCHOUT does not use UTC but the actual difference to UTC depending on the timezone x2. I.e., if you're in Arizona, which is UTC -7:00, the offset is -14 hours. If you're in Abu Dhabi, which is UTC +4:00, the WATCHOUT time says +8 hours.
  13. If you're using a virtual screen mapped onto your 3D object, you can play any sort of media with full timeline control. You just need to make sure to keep your content in the correct UV mesh area.
  14. RBeddig

    Mark Watzl

    Very sorry to hear. My thoughts are with his family and friends. Rest in Peace
  15. Are you sure that the display server is set to the correct time zone? Are the messages sent from the display server or from your production computer. I've noticed very often that the time set in BIOS is different from the time used by Windows and WATCHOUT uses the Windows time.
×
×
  • Create New...