- Popular Post
jfk
-
Posts
1,805 -
Joined
-
Last visited
Posts posted by jfk
-
-
2 hours ago, John G said:
... There is one (not allowed) on eBay but the seller is quoting EUR 44 for postage which I feel is too much! ...
Isn't that simply a way for the seller to avoid paying some of the eBay commission? ie shipping is not included in the commission calculation. Tells you enough about the sellers ethics I suppose.
0 -
I have a pdf copy of the TN3758 MINIGUIDE for TN3326 TRANSPAX+, but I do not have the Case Book.
0 -
16 hours ago, Daniel Garcia said:
Hi,
I have two custom machines with two Quadro RTX 4000 Ada Lovelace cards (Connected with an SLI Bridge) and a Quadro Sync Card 2 for synchronization for each server. However, I am curious if Watchout is able to utilize the 8 total display outputs on each server (4 Display Ports 4K resolution on each graphics card) and sync the two servers for a total of 16 outputs.
Thanks.
No. Six outputs maximum from a single graphics card only. This is a restriction imposed by DirectX multi output mode.
0 -
1 hour ago, ElYugo said:
Hello, Just to confirm, because if I have to explain to our guys abroad, NIC = Network interface card?
That is correct. Ethernet NIC, WiFi NIC, etc. I have even seen FireWire NICs, but not recently.
1 hour ago, ElYugo said:These projects were working around a week ago and suddenly stopped. Could the autosave feature have anything to do with the file crapping out?
Thanks!
No. Using an autosaved file that is not stored in the same location as the original file will cause all relative file references to break. Move the autosaved file to the correct location to address that. But you are no longer seeing file not found errors. The autosave file would not cause the failure you seem to describe.
0 -
This really depends in how the production computer will be used.
If it is used for content assembly and editing, but not used for performance (displays in cluster mode for show playyback), then it is not critical. I have had good success with clean install of Windows 10 Pro and nominal tuning (firewall).
if you plan to use the watchmaker computer as a live show playback controller, then the production computer becomes critical. In that usage, i would recommend you treat it exactly the same as a display.
0 -
Best guess from what is described is multiple NICs in the production computer. WATCHOUT must use the first NIC in Windows NIC order / priority. If WATCHOUT is not on the first NIC, TCP traffic will still function (media and command transfer), but all timeline transport commands sent via UDP will lost.
0 -
The WATCHOUT software has no limitation on resolution. The hardware will determine maximum resolution. Not familiar with any hardware that can play a single video with 21,504 pixels as one of its dimensions. However, if you broke the video into multiple pieces that are recombined in WATCHOUT, that should work fine. So the question becomes what is your hardware’s capabilities. Typically the gpu buffer size will determine the limits. 16,000 pixels is typically as much you see in current GPUs. For example, you would need six 4k outputs to accommodate 21,504. Two WATCHPAX 62B could handle that job with the video split in two pieces.
0 -
8 minutes ago, thesw said:
So it will come pre-installed with Watchout 7 or will have the ability to install with Watchout 7? Is there a release date?
To be safe, specify WATCHOUT 7 on your WATCHPAX 62 order.
WATCHOUT 7 is available Friday this week.
0 -
3 hours ago, thesw said:
I have a large building mapping where i would like to use auto-alignment cameras with mpcdi. It seems like this is only possible on a homemade watchout machine? As far as i can see the only currently available dataton machines are OS locked and so the use of autocalibration isn't actually possible?
Probably true for WATCHOUT 6. WATCHOUT 7 no problem using Scalable Displays or Vioso on WATCHPAX 62. If you order today, you can get your WATCHPAX 62 delivered with WATCHOUT 7.
0 -
15 hours ago, Tartyla said:
Hi
we have set up the system for watch out.
The software we had was already used to connect 8 projection for an exhibition we had.We want to connect 4 projectors now. We have the same 2 PCs that operated it in the exhibition. And the Ethernet connected. And it goes online but we get errors and it wont connect to all the projectors so that we can have it on the media grid to play
Did the cables connecting the projectors to the WATCHOUT computer change? There is an issue with some AMD gpu that are sensitive to passive adaptors such as DisplayPort to HDMI adaptors. Passive adaptors are limited to a reduced number of outputs, active adaptors will allow the use of all outputs.
0 -
4 hours ago, mortenrud said:
… Btw, you write “Watchmaker”, my SW is called WatchOut. Is that different? …
No.
Dataton WATCHOUT refers to a family of applications.
- Dataton WATCHOUT Production
- Dataton WATCHOUT Display
- Dataton WATCHOUT Dynamic Image Server.
If you look on your drive, you will discover the executable files that starts each application are
- WATCHMAKER.exe (Dataton WATCHOUT Production)
- WATCHPOINT.exe (Dataton WATCHOUT Display)
- ImageServer.exe (Dataton WATCHOUT Dynamic Image Server aka DIS).
i.e. the application’s ‘nickname’ is derived from its executable file name. It is only slightly shorter to write watchmaker vs WATCHOUT Production. And I suppose I could just write Production instead. I picked up the use of the nicknames many years ago from communications with Dataton development staff.
0 -
One more screenshot please,
watchmaker - files - preferences - general
If you are at default output frame rate, it needs to be changed to 50
0 -
57 minutes ago, mortenrud said:
Hi jfk
It is a WatchPax 60, and the machine is able to output the correct resolution on the led screen.
??? How are you determining that? Is the startup logo screen showing up? Keep in mind, before you load any show, the resolution used for the logo screen is determined by the EDID the output sees from the display / LED screen.
57 minutes ago, mortenrud said:But when I try to start the Watchout show, I get the error.
Double check there is no typo in the resolutions specified in display settings.
Only when you load the show will WATCHOUT attempt to change resolution, and it only attempts to change resolution if the logo screen resolution is different than the resolutions specified in your shows display settings.
0 -
4 hours ago, mortenrud said:
Hi Walter.
I create the custom resolution in the Nvidia Control panel on my WatchPax node.
Note, only WATCHPAX models that run under Windows 10 offer the ability to manipulate EDID in the gpu. So WATCHPAX, WATCHPAX 2, WATCHPAX 4, and WATCHPAX 20 do not offer EDID editing. WATCHPAX 40, WATCHPAX 42, WATCHPAX 60 (all variants) and WATCHPAX 62 (all variants) provide access to EDID settings.
0 -
6 minutes ago, jfk said:
…. Note, after transferring the show, you could run the show in cluster mode, as the controller to cluster communication can be done with only TCP. WATCHNET, WATCHOUT Remote, Pixilab, AMX, Crestron, Medialon, etc., etc are potential controllers to accomplish that.
I include that because it is still valid to go online and completely transfer show resources without UDP. So you may remotely load / edit / update the show, but no useable timeline control from watchmaker. After transferring the show, remove production, restart your displays and you can cluster playback with local or remote control.
Yes, that is beyond the scope of the original question. But seperate networks, virtual or otherwise, same issues.
0 -
56 minutes ago, mortenrud said:
But I am in fact able to output the resolution from the WatchPax alone …
How are you confirming that? using the gpu control panel in window mode? When watchpoint first starts up, before a show is loaded, the initial logo screen should choose a resolution determined by EDiD.
0 -
The fact that newmethos returned normal operation by restoring the builders known good state, would beg the question “what software was added in the field?”. Software like VLC media player and some variants of VNC remote access software and some others mess with WATCHOUT a lot. That may be where you need to look. Also, the restore would eliminate any virus or some such if it were an underlying issue.
0 -
4 hours ago, mortenrud said:
Hmm. I thought that is was one of the main features of Watchout to output non standard resolutions to non standard displays....
The issue is not WATCHOUT, its the GPU and its software. I have used very odd nonstandard resolutions like a single WATCHOUT output of 7200x1080 without issues because the gpu was meticulously configured to support that resolution before WATCHOUT was even opened.
0 -
10 minutes ago, diskin said:
Yes, it's worked well.
As I wrote earlier, the same files work in an old project in the same PC
Ok, I read that as it used to work. Did not realise you were saying the old project works today with the “same” file. I use the quotes because each show has its own unique copy of the file on the display server. Note, the old project still has an old copy of the file, it would have no need to replace it. So you did not actually try the copy that is failing on WMP in watchpoint’s PC?0 -
I would be curious to know if that file plays ok without WATCHOUT running on the display computer that is crashing (quit wo and open in Windows Media Player)
0 -
5 hours ago, mortenrud said:
Hi jfk
Thanks for your reply.
I was in fact trying to convert displayport to hdmi, but using an active cable.
Now I have placed a screen right next to the WatchPax 60 and running displayport to displayport and with the same error.
Everytime I try to set the resolution to more than 1920x1080 I will get the error.
Not all active adaptors are 4k60p capable. Anyway …
Forget WATCHOUT for a minute. Quit watchpoint on the display computer and using the graphic card’s control panel, can you set the desired resolution?
WATCHOUT is simply asking Windows its current resolution. . If the answer does match the numbers you have entered in the display specifications, it simply initiates DirectX 3D rendering mode. If the answer does not match the numbers you have entered in the display specifications, WATCHOUT will then ask Windows to set the resolution you have entered in display specifications. If Windows comes back and says it can not do that, the message you see is the result. BTW make sure there is no typo in the display specifications.
0 -
- Popular Post
- Popular Post
This is typically caused by a hardware shortcoming in the connection from the graphics card output to the display.
I might add the most common cause that I have encountered for this issue is any adaptation away from DisplayPort. i.e. a DisplayPort to HDMI adaptor not capable of 4K resolution. Note, there are two kinds of DisplayPort to HDMI adaptors - active and passive.
A passive adaptor relies on the graphics card supporting a compatibility mode where the card internally switches from DisplayPort signal types to legacy HDMI signal types. This type of capability is often referred to as DisplayPort ++. The legacy compatibility mode often offers less possible resolutions when compared to native DisplayPort signals. So the graphics card recognizes the HDMI adaptation and switches to output legacy HDMI signals. Many graphics cards are unable to output 4K in the legacy compatibility mode required by passive adaptors.
An active adaptor on the other hand operates the graphics card in native DisplayPort mode. i.e. the graphics card only outputs native DisplayPort signals. An active adaptor isolates the graphics card from the adaptation, the card only sees native DisplayPort connection. The active adaptor then converts native DisplayPort to legacy signal types required by HDMI. Native DisplayPort often provides a much wider range of output resolutions when compared to legacy mode. And that is not just 4K. I once encountered this issue with an HDMI display operating at 1400x1050. This could not be accomplished with a passive adaptor, only with an active adaptor.
So if you are converting to HDMI, you may require an active adaptor rated at 4k60p to correct this error.
Note, active and passive adaptors often look the same and active adaptors are only slightly more expensive, often as little as $5-$10 more.
1 -
Need more information. Of course, the display computer must be running and displaying the initial logo screen for it to show up in the production network window. The initial logo screen should be showing the IP address it is using - (1) what is that address? (2) What is the IP address of the production computer? (3) Describe how the two are connected? (a network cable for each connected to an unmanaged switch or something else). Other potential issues include firewall on either station (both should be disabled).
0 -
While WATCHOUT is designed to allow multiple independent shows on the same network, it is required all shows be the same WATCHOUT version.
0
rudimentary countdown
in WATCHOUT FORUM
Posted
Recently worked with a customer who wanted use WATCHOUT production to simply play clips with a countdown timer. No other actions synched with video. This is an example ( Clip_roll.watch) of a rudimentary workaround that met the specific requirement. You still need to manually insert the total time for each clip and maximum timer time is 5 minutes.