jfk

WATCHOUT 7 requires GPU API Vulkan 1.3, OpenGL 4.4 and DirectX 11. i do not think Parallels is capable of one of those requirements.

7.2 was intended for release last Friday. However, the release candidate for 7.2 is available to Next Chapter members and it turned up some bugs. it was decided to delay the 7.2 release until the identified issues are corrected.

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.