jfk

That looks like a MIC 3 starter kit, complete with one MIC 3+, one PAX, four PAX SAV Adaptors and fitted ata carrying case. very nice offer

i believe he is suggesting using the URL still image proxy instead of Dynamic Image Server.

You must load the show from a display server to send the UDP commands without a production computer. So, power down ALL WATCHOUT computers. Only start the display computer(s). Load the show on only one display computer without production (any additional display computers will be managed by the display computer that loads the show). The display computer that successfully processes a load will then send the UDP commands.

No! The driver for Focusrite Scarlett interfaces is already installed. The newest WATCHPAX 62 image has a Focusrite Scarlett driver gen 4, the original WATCHPAX 62 configuration includes the driver for Focusrite Scarlett driver gen 3. Your assumption is correct, but there is No need to install anything.

failing memory? virus?

WATCHOUT 6 or WATCHOUT 7? There are USB hardware options that can provide 16-20 channels that work with both major versions. How many channels do you require?

Isn’t Rainer suggesting that your external output may be a different channel number than 2? Have you tried other output numbers? Seems Rainer had to go all the way up to 5 to find his second output.

Yes However, since the asset manager is now a seperate component, you may choose where it resides. Furthermore, the license may be shared among components on the same computer. So the asset manager can be placed on the renderer computer.

Yes, it is true, in both v6 and v7, embedded audio is not recommended. However, in v7, the new asset manager pre-processes all media. If there is embedded audio, the v7 asset manager will automatically split this into separate video and audio components and place them in a composition. Once that is done, you may specify which audio renderer plays the audio component.

I was under the impression that NotchLC playback is available to individuals royalty free. When a software vendor adds NotchLC support, the software vendor must pay a per usage royalty. That would explain why a NotchLC movie would play in QT and error / require a license for WATCHOUT asset manager. Now that is baffling. Could you provide an example of a NotchLC file that plays in QT but errors in a licensed WATCHOUT asset manager?

The codecs may be an issue as well. The movie frame rate and the output frame rate have an impact. This may be on the edge for ProRes, should be no issue for HAP. While 24 fps may make smaller files, the added workload of converting 24 fps to 60 fps on the fly may play a role as well. Frame blending setting also may have an impact.

please always indicate WATCHOUT version!

The SMARTPAX is documented in the TRAX 3 User Manual. The SMARTPAX QC is documented in the TRAX 3.6 Addendum. The SMARTPAX QC Miniguide is found in this collection of Miniguides. I can not seem to find the Miniguide for the original SMARTPAX.

wow, very old version. Anyway, i would make no further attempt to open the file that crashes when you attempt to open it. i would instead go to your watchpoint / display machine and attempt to retrieve a valid show file from there using this procedure:

WATCHOUT version? can you open a new show in watchmaker / production?

and thank you for taking the time to reply back with the resolution. You will probably mostly get away with that when there is only one watchpoint computer in the cluster. Some messages from the watchpoint computer may still be sent to the watchmaker computer since that is where the last successful load came from. If there were more than one watchpoint computer in the cluster, the watchpoint computer receiving the command would not relay it to the other cluster members since a successful load is required to redefine the cluster master.

Been thinking about this one. Question - when using watchmaker/production do any errors appear in the message window? A load on watchpoint encountering a same error may get stuck where watchmaker has its error messaging subsystem to deal with it. Also, you mention a watchpoint software restart, … so the issue is after a watchpoint computer power up, no watchmaker session since power up, while hanging on the logo screen with progress bar, triggered from an IP load? Also, and I hesitate to re-iterate this but are you certain watchmaker and watchpoint are attempting to load the same show? For example “Main show” and “Main Show” are two different shows.

If you are redefining a keypress, 0 on the numeric keypad is a positive play (no toggle) . If you are already playing, pressing number pad 0 key will not interrupt play. … Spacebar Start timeline (toggle) Esc Pause timeline (no toggle) NUM 0 Start timeline (no toggle) NUM * Jump to last start position https://www.dataton.com/watchout-users-guide/appendix/f-keyboard-shortcuts/timeline

The WATCHOUT 6 corner tweens function is not yet included in WATCHOUT 7. It is intended to be added in a future release.

fyi Microsoft Media Foundation was introduced in Windows Vista as the replacement for DirectShow. aka. Media Foundation, Windows Media Foundation https://learn.microsoft.com/en-us/windows/win32/medfound/microsoft-media-foundation-sdk

It is always useful to indicate the WATCHOUT version when inquiring. Potentially media related. If you start a new show with no media and simply place a control cue on main timeline to start a blank timeline, does the issue still occur?

As to your original question, editing the IP address of a WATCHPAX or WATCHPAX 2 running version 5.5.x is a bit complex. A WATCHPAX or WATCHPAX 2 running v5.5.x ALWAYS uses DHCP to determine its IP address. That cannot be changed. The setIP command in a startup script of a WATCHPAX running version 5.5.x sets a virtual IP address in addition to the address determined by DHCP. That can result in some unexpected behavior. (This is changed in v6, in v6, the setIP command does in fact set a fixed IP address.) If you want to set a fixed IP on a WATCHPAX or WATCHPAX 2 running version 5.5.x, the recommended method is to provide a DHCP server with IP reservations. IP reservations reserve IP addresses for a specific MAC addresses. (I personally use a simple router DHCP server with the needed IP reservation function.) Related to that, always use WATCHOUT name when assigning the stage displays to a WATCHPAX, never use the IP address. (WATCHOUT name is assigned to a WATCHPAX or a display server using the WATCHOUT Production Network Window.)

No. All stations in a WATCHOUT system must be the same version.

I would t check that, There have been no confirmed reports of that being an issue.