jfk

Could you share any detail on the step ... " 4) Remove any eventual remaining WATCHOUT or WIBU-key/CodeMeter parts on the computer " ? Do you delete the folder that the watchout apps were in and make a new folder for the fresh install? Are there other parts we should be looking for?

Not every setup needs that tweak, in fact, very few do. That is an adaptation of Windows 7 to make it work with older network switches that are not truly Windows 7 compliant. So why would you de-tune every WATCHOUT system to accomodate old hardware? A while back, I started to write a post on this, but discovered that different swtiches need different tweaks. Here is what I had so far, but decieded not to post originally. ==================================================================== Periodically we hear reports of very slow online / update times with WATCHOUT under Windows 7. XP machines in the same cluster do not exhibit speed issues. Research has shown this is not unique to WATCHOUT, the general Windows population has many similar reports. Apparently there are some subtle changes in Win7 in the way Windows IP networking is implemented. The change creates slowdowns with some network switches. It seems Win 7 offloads some network duties to the network switch. I see mention of Win7 certified switches. But even switches that were not Win7 certified could be accommodated with changes to adaptor settings in the Advanced tab for the network adapter. reference: Slow Network File Copy issues in Windows 7 caused by Remote Differential Compression ===== From a WATCHOUT user in Canada =========== Remote Differential Compression (RDC) But I see other references to the above fix with comments like: "This has been completely debunked by MS" The Storage Team at Microsoft - File Cabinet Blog Debunking Myths about Remote Differential Compression and System Performance

So to clarify, his source only provided an HDMI connection with both video and audio combined. OP was hoping to use the HDMI capture card in WATCHOUT to receive, breakout, and re-send the embedded audio signal to his sound system. As he discovered, WATCHOUT does not do that, so he found another product to breakout the audio from the HDMI to his sound system.

According to the Pro Tools product manager I spoke with, Pro Tools 9 or 10 can output proper multi-channel wav files. I am sure Pro Tools support can help you determine how to do this.

I agree it is not real easy, but it is possible. You do not do it in the driver per se. You hack the Windows registry. Show Sage offers custom resolutons poked into the Windows registry if specified at the time of a computer purchase. Customer still has to provide matching EDID from the display to make it active.

With the proper capture card - yes. And the DataPath VisionRGB E2S is such a card, it will provide 2 unique catprue streams simultaneously. We have tested two DataPath Vision RGB E2S to capture four streams simultaneously, that has worked well too. Although the challenge is selecting a motherboard that can accommodate enough PCIe x4 slots in addiion to the PCIe x16 slot for the GPU.

Timecode time does not equal stopwatch time. The timeline is calibrated in stopwatch time. I am sure if you ran those 27 minutes of timecode against a stopwatch, you would see the same discrepancy. Also, do not trust the automatic timecode setting, set the timecode type explicitly to avoid any calculaiton errors that would occur if the system automically sets the wrong timebase. I have looked for a good timecode calculator to convert timecode to stopwatch time. Have not found a good one for that specific task just yet.

Outputting 960 by 320 is a Windows challenge, WATCHOUT can not overcome Windows. You will need to find a way to add the non-standard 960 by 320 resolution to Windows AND you must provide EDID to the display card that specifies that resolution is valid.

Thanks for sharing your results. To clarify, the uninstall / reinstall forces a firmware upgrade of the card as part of the clean install of the driver? Does the installation process notify you the firmware upgrade is performed? Is there any way to query the DataPath hardware to determine it's firmware version? Thanks again.

Define shortly? aka

Yes, posted by Dataton support in the topic Mpeg settings. Look at the attached file in post 2.

Are you receiving any errors when going online or updating? Possibly a file is missing or no longer correctly attached to its media object? Would generate an error if so.

Been using command files with WO 5.2 to start cluster playback since the day it was introduced, no issues. Double check to make sure the setting that hides known file type extensions is not on, your file may have a .txt.txt ending and only one of those two .txt would show if that setting is wrong.

If there were to be a new timer / countdown cue, an option to target a control cue for duration would seem a flexible way to auto adjust a countdown when lengthening or shortening cues. In most cases that would be the pause for the next cue, but certainly not limited to that.

x2 We use the OCZ Vertex3 SandForce Controller MLC NAND Flash SSD drives (and lots of them) with no unusual issues going back to Q2 2011.

To be specific, the automatic cue count down is part of WATCHOUT Remote (WOremote), one of (WATCHMan) WATCHOUT System Manager's utiliities. That is supported by WATCHOUT Remote. With simple control cue tags in your timlines, you can mark any point for quick and accurate jumping from WATCHOUT Remote. Or you can jump to any time by simply typing it in. WATCHOUT Remote does that quite well. Of course, you define what a 'media clip' is in your timeline programming. Another of WATCHOUT Remote's strengths, it will adjust to such changes automatically. Everyone has there own concept of what looks professional. If you don't like the way WATCHOUT remote displays the information, you are free to modify the interface to your liking. WATCHOUT Remote is open source and a great starting point for a custom interface. And you can run multiple WATCHOUT Remote or similar apps on the network. In the Show Sage WATCHOUT Training seminar, when we cover WATCHOUT Remote, we have had as many as four WATCHOUT Remote connections active, and actions on one are reflected in all. If there is indeed a widespread need for such customization, sounds like a marketing opportunity for someone.

I think that my be a difference in the implementation of the MIDI standard. If you read the published protocol, there is no MIDI Channel 0, they start at 1. The published protocol states that MIDI channel 1 has a hex value of 0, so Korg may be interpreting things a bit differently. There are sixteen MIDI channels available. Some vendors choose to incorrectly label them 0-15 while others choose to correctly label them 1-16. So if your Korg offers 0-15, then likely Dataton MIDI channel 1 = Korg MIDI channel 0, etc.

There are workarounds to trigger the main timeline from ArtNet/DMX - but do not do it. Best that is going to give you is a blind Go, and latency using that type of trigger is inconsistent. DMX is not a good choice for cues, it is a level based protocol with no direct correllation to cues. Does the lighting board you are using support MIDI Show Control (MSC)? MSC is a cue based protocol. That would be the best way for a lighting board to control a WATCHOUT Timeline. It works very well, is very consistent, and each triggering lighting cue is matched to an exact position on the timeline, way better than a blind go.

I had the same thought. What cloning software did you use to make them exactly the same?

All display computers are managed through the connection to a single display computer. That single computer is known as the "cluster master". When you choose a show to load, the cluster master looks in the show file and determines the addresses of all the other computers in the group. The cluster master then contacts all the other computers on its own and manages their following along. So if your show file contains 12 display computers, all 12 computers are managed through the single connection. Any computer within the group can act as a master, does not matter which one you choose, they all contain a copy of the show file.

I assume by the 'main computer' you mean WATCHOUT Production. The WATCOHUT Remote control app talks directly to the display(s), production must be turned OFF (or at least offline) to use WATCHOUT Remote.

Well yes, they should. But the video codec settings can have an impact on that. With mpeg, wmv or h.264/mp4 set to CONSTANT bit rate (CBR) they will stay in synch. A movie encoded with variable bit rate (VBR), maybe not.

This is a known BlackMagic bug that originates from the BlackMagic driver install. Please report it to BlackMagic. Maybe some day they will address if they hear about it enough. The bug is specific to PhotoJPEG movies. For whatever reason, BlackMagic is installing a PhotoJPEG codec. The codec installed by BlackMagic does not behave properly, i.e. it will not show up when a codec list is obtained from the OS, even though it should. And as a result, WATCHOUT can not blacklist that codec. Still, when the movie is played, the pita BlackMagic PhotoJPEG codec intercepts it. There is a technical workaround that is not for the faint at heart. It involves removing the BlackMagic installed PhotoJPEG codec from the Windows registry. Contact Dataton support for assistance. Unlikely it is from overheating. Just the same, if a WATCHOUT 5 License key has become intermittent, it is under warranty. (There are no WATCHOUT 5 License keys old enough to be out of warranty yet.) Contact your supplier and arrange free of charge replacements.

MPEG Settings

It could be the 'default enabled layer' feature, more info is needed. How is the layer disabled? From external control (WATCHOUT Remote, professional control system, etc.)? From WATCHOUT Production?