Jump to content
Dataton Forum

jfk

Moderator
  • Content Count

    1,330
  • Joined

  • Last visited

Everything posted by jfk

  1. Does the sound card show up in watchpoint's audio input menu? You have to select it there before it can work.
  2. There are two types of NDI streams - NDI (which is essentially uncompressed, for example 1920×1080@30 fps NDI stream ≈ 125 Mbps) and NDI | HX (aka high efficiency - which is h.264 compressed, 1920×1080@30 fps NDI | HX stream is from 8 to 20 Mbps). Sounds like you may be using NDI | HX. Long delays in acquiring an NDI | HX stream are normal due to the compression used in that stream type.
  3. Simple answer is no. There is an undocumented experimental cluster control command that allows interactive adjustment of playback speed. It would require a control system to achieve any useful function. This adjustment effects all playback (i.e. the timeline speed is adjusted, not just an individual piece of media's playback speed). The experimental function is limited to ±20%, which may not be able to achieve what you describe. And keep in mind, this function is cluster mode only, it is not available when watchmaker is online.
  4. This appears to be some kind of hardware issue. We have not seen any other reports of this nature. If you would like to have Dataton evaluate this, please send a simplified sample show file, media and description of how to reproduce the issue to support@dataton.com. We would test it on our hardware to see if it is reproducible. The loop setting solving the issue is very strange. It is exactly the opposite of what we would normally observe. Looping loads a second copy of the media which increases the work load - often movies that play ok standalone begin to stumble when looping is enabled. Again this points to some sort of very unusual hardware anomaly.
  5. Original WATCHMAX or WATCHMAX 2.0? Do not know of anyone who has ever tried it. Seems odd they call it a "Pro" device, but they do not support the most common professional audio standard - ASIO. Just the same, WASAPI is supported in WATCHOUT 6.2+. According to their web site ... Data Compression: Software compatibility: Windows XP/Vista/Win7/Win8/Win10 and Mac OS, Sound file compatibility: WDM, MME, CoreAudio, DirectSound, WASAPI and .WAV
  6. You might be surprised how often that has come up. Two matched audio sources many times appears as an echo or reverb effect. Glad you got it sorted. Very much appreciated that your reported back with the resolution.
  7. File transfer communication between watchmaker and watchpoint is TCP. No file sharing OS services are used and should be disabled. Since its the two watchout family software packages talking to each other, i suspect the protocol is irrelevant.
  8. Are you sure the original is not a HAP Q Alpha? (an unsupported codec in WATCHOUT)
  9. Essentially correct. It would be more correct to say ... watchout can only output 8 bits and no more ,unfortunately... i.e. In some cases it can play movies with higher bit depths, but those will be reduced to 8 bit for output.
  10. ectoplasmosis, your statement could be misleading. I assume the SFP+ qualifier is how you arrive at the statement "No 10Gb SFP+ NICs that support WoL ..." MS was looking for a PCIe interface and he indicates he is aware of a 10 Gb NIC compatible with Wake On LAN that is experiencing long delivery times, just looking for alternatives that are more readily available. BTW, the WATCHPAX 60 includes a 10 Gb NIC that provides Wake On LAN function.
  11. No. It is important that the network interface used by WATCHOUT be the highest priority in the NIC priority Widows settings. So no, you can not set it in WATCHOUT, but yes, you can set it in Windows.
  12. I do not know how your control product sends its strings. All commands to WATCHOUT must have a carriage return at the end of the command. When typing a command from telnet, this is accomplished by hitting the return key. Control products use various methods of sending the carriage return at the end of the command string. Some use /r. Some send the the two digits representing the single byte hex value with some hexadecimal value indicator, , I have seen 0Dh, etc - for example, WATCHOUT itself uses a dollar sign ($) to indicate the next two digits are a single byte hex value, so in a WATCHOUT output cue, you would type $0D to send a carriage return. The method used to define hexadecimal bytes is determined by your control product.
  13. Yes, change the output device port number to 3040 for use with production and you can skip the authenticate command. Also, be sure to enable IP control in File - Preferences - Control.
  14. Yes, I did miss he was cycling on the standby state. Not my first choice for accomplishing that result. How is the standby state being triggered to make the images alternate in the first place? Things get a little messy putting non-media cues on standby layers, personally, would avoid standby for this application altogether. Since he is cycling stills, there is a clean way to run the still cycle using a control cue 'goto and and run' on the mainline timeline. Once an aux timeline is triggered, a control cue to reposition and pause the main timeline at the head and another to run the main timeline at the tail of each aux timeline should accomplish this cleanly.
  15. Yes. Before you can send any commend (except ping) you must first establish an authentication level. For cluster commands, it is best to set level 1. i.e. authenticate 1 terminated with a carriage returned (hex 0D). Otherwise, you are not authorized.
  16. Two things that might be worth a try. In the media window, for the .png file causing an issue, change the Transparency setting from automatic to the correct setting for your image type. On the timeline, place the pause cue 0.1 seconds before the png cue ends. The 0.1 second delay it would cause when triggering the next cue should not be a big issue. This protects from an overrun condition that can occur from various network UDP conditions. After a pause is encountered, a second TCP gotToTime is automatically sent by the master, which can cause a jump back after an overrun. Note: another way to test for this is to run it in cluster mode vs production mode. If cluster mode cures it on the cluster master, than an overrun condition is likely.
  17. Stick with your current setup. No need to mess with opacity to achieve best result. " ... is there a way to change the trigger at different points of the main timeline? ..." Yes, you need to have WATCHOUT talk to itself. There is not built-in method to do that. You need to get a little creative to arrive at a solution. We will use WATCHOUT;s IP commands to accomplish it. Technique varies for production mode or cluster mode. I will describe the cluster mode solution. Setup an Input object as Generic type and name it Active_Image, set its Limit to 2. For the purpose of this exercise, we will assign values: 0 = video playing / no active image, 1 = Image A, 2 = Image B. In your trigger field (assuming your pressure pad input is name Ppad) use the formulas: run video A - Ppad && Active_Image=1 run video B - Ppad && Active_Image=2 Setup a string output object with name of Set_Image_Status , an IP address of 127.0.0.1 (localhost), port set to 3039 and protocol TCP.. There will be four cue objects to setup for the Set_Image_Status object. authenticate 1$0D setInput "Active_Image" 0$0D setInput "Active_Image" 1$0D setInput "Active_Image" 2$0D Run the authenticate command before displaying the images and sending the commands to designate the current image. When running a video, using the Set_Image_Status output set the Active_Image to 0 so random inputs from the pressure pad will not interrupt the videos playing. I suspect you can determine where to put the other two Set_Image_Status output cues Note: do not place the Set_Image_Status output string cue to setInput "Active_Image" 0$0D before time 0:00.300 on you auxiliary timeline. Placing them to close to 0 will result in them being skipped / ignored. Same goes for the videos on that timeline, although the video will not be skipped, it would start late and stumble / skip on startup if it is to close to 0 time. The TCP connection will timeout if no cues are sent for a period of 60 seconds, so you may need to send output Set_Image_Status the authenticate 1$0D command again if the connection closes. i.e. if your movie run is over 60 seconds, then you will need to send authenticate 1$0D again before the next Set_Image_Status output command used to change the Active_Image value.
  18. If it is urgent, then work with your hardware vendor to determine why it does not comply with the minimum requirements for WATCHOUT. With the complete lack of information provided, it is impossible to even guess what is wrong with your hardware. msi gp75 means nothing. 99% of the time failure to open the WATCHOUT software is an OS configuration error, sometimes resulting from conflicts with other software installed. Manufacture's bloatware is often impossible to overcome. The only sure way is to wipe all drives clean, install OS, install all correct drivers, and then follow the tweak list at the top of the forum. The tweak list is a guideline and is provided "as is" .
  19. when i first read this post it appeared as if the Original Poster was not actually using WATCHOUT. So, OP, what version of WATCHOUT are you encountering this problem with? If you are running Windows 10, did you follow the Dataton guidelines (aka tweak list referenced by mindopera) for running WATCHOUT under Windows 10?
  20. audio has no impact on synch in WATCHOUT.
  21. jfk

    NDI Audio input

    Seeing as WATCHOUT does not support audio input in any form, I would not get my hopes up.Seems it may be a major thing to add a feature which currently does no exist.
  22. FYI the issue with audio looping is now a confirmed bug. With the summer break in full swing it may be a little while before it is addressed, hopefully in the next update.
  23. Sounds like a Windows question for a production computer. (You should never see the task bar on Display in full screen mode). Windows version?
  24. jfk

    PC move

    Most likely. This might help: https://forum.dataton.com/topic/3633-everything-i-think-i-know-about-dataton-v5-and-v6-license-keys/ Yes, install the correct version, no do not copy the files. (While it may be possible to just copy the files over, success is fully dependent on the organization of the original programmer). Watchout includes a function, "Consolidate To ...", specifically for moving shows. This function automatically adjusts file references to ensure portability. The User Guide gives a good description on use of the consolidate function.
  25. I am a little confused. PC2 is a different scan rate than the other two. How can you scan lock different scan rates - did not think that was possible? Always thought you could only scan lock matching scan rates.
×
×
  • Create New...