Mike Fahl
-
Posts
721 -
Joined
-
Last visited
Posts posted by Mike Fahl
-
-
Either should work and be solid. The HAP version will require more disk bandwidth, but be less CPU intensive. So "whatever floats you boat", I guess.
0 -
Can you post a simplified show showing what you mean? Then perhaps someone can take a look. Otherewise it'a hard to guess.
0 -
Well, the fix in v9 is on the encoding side of things in relation to v8. I get the impression that the OP has trouble decoding the video in WATCHOUT.
What settings are being used when encoding?
0 -
As Jim says, a simple start-up script to load the show will likely make it work. There's an example of such a script here:
http://academy.dataton.com/wo6/Cluster%20Protocol.xhtml#toc_marker-14-2
0 -
You may want to look into whether the PS4 outputs/expects a HDCP compatible device in the other end. Many conslles do, in which case I doubt you can make it work with capture. The fact that it shows up in Black Magics app would make you believe that's not the case here, though. But I've had trouble with this in the past with some consoles and capture cards.
0 -
You may get close, and WO6 has some new abilities to program such logic internally. But it's hard to give hard guarantees that there will never be a "double fire" if the two buttons are pressed at the very same time. So if you want to make 100% sure, I would add some logic in front of WATCHOUT that arbitrates this, then triggers timelines as appropriate. It can be a quite simple program.
0 -
It's not that it can't run on the same computer. As you found out, it most likely can. I think Jim's answer is more along the lines of whether this is a good or a bad idea. In general, running anything else on a display computer may interfere with the timing precision and other performance aspects of that display computer, and should therefore be considered a Bad Idea.
If you're happy with the result, I'd say go for it. But I would still not recommend it, for the above reason.
Mike
0 -
The global origin affects only the default optimal vantage point for 2D displays. It affects the look of 3D objects viewed on 2D displays. If a 3D object is placed left of the vantage point, you'll view if from front-right side. Likewise if you move it to the right if the vantage point, you'll see if from front left side.
This determines only the default perspective vanishing point. It is possible to apply local vanishing points, for instance if you want to have a display off to the side, and not have its content affected by the global vanisning point.
The vanishing point does not affect how 3D objects are viewed/projected by 3D cameras/projectors. Here each camera/projector establishes its own view point and perspective (i.e., its own optical axis and lens angle).
Hope this helps.
0 -
The panel should be accessible to any visitor with any smartphone just by logging into the WI-FI.
That functionality isn't part of WATCHNET. A URL will need to be entered somehow (possibly using a QR code or similar). Since the server is local, the URL likely need to specify a fixed IP address, rather than a domain name.
0 -
Agreed. In that case, having the ability of controlling display positions would help with such set tracking scenarios, when different displays move in different directions.
0 -
Use the -ShowsPath command line option, as described here (it's also available in v5):
http://academy.dataton.com/wo6/Command%20Line%20Options.xhtml#toc_marker-15-1
0 -
Nope. But you can control positioning of media on those displays, which could acommplish a simialr effect.
0 -
I think so, but never actually tried.
0 -
Perhaps you mean you want to enter 8-bit component values (0...255) rather than a percentage? Yes, then a simple scale factor needs to be applied. If so, you may want to submit a feature request to allow those values to be entered as 0...255, or possibly even as hex values (e.g., #FF2055), as both are common formats to describe RGB color components.
0 -
Look under the "HSB." heading a bit down in this document:
http://academy.dataton.com/wo6/Cues.xhtml#toc_marker-7-4
You can specify color as HSB, RGB or CMY values.
Mike
0 -
Thanks Mike for some fun holiday reading!
Remember "Launch day"!
Jonas, someone asked me if there was a video from the launch event. I recall seeing a fairly poor video at one point, but I don't remember if this was from the launch or from the later London event. Let me know if you have something, as I know you're a collector of all kinds of odds and ends.
0 -
The texture resolution need to be hight enough for the area it is to cover, once displayer/projected. If it's too low res, it will look pixelated. If it is unnecessarily high res, youäre wasting resources (memory, and possibly CPU if this is a video texture). There's really no direct relation between the size of the model and the resolution of the texture. The fact that WATCHOUT shows the size of the model in "pixels" may be somewhat misleading here, but it's just a "unit of measure" in this case, really, as there are no "pixels" inside the 3D file itself.
0 -
I believe you can also trigger the timeline with the 0 key on the numeric keypad. This is not a toggling key, which is often useful when you want to wire it up from outside, and want to make sure that the keypress only starts (but never stops) the timeline.
0 -
If I double-click such display and close its pop-up settings window, UI will crash too.
That's definitely not normal. As I have not encountered this myself. nor heard of anyone else, I have to suspect something's "different" with your computer. Since the error points at Windows' GDIPLUS subsystem, my best guess is something graphics or driver related.
I also noticed this settings window do not have a OK button nor a CANCEL button at its bottom, is this correct?
Yes, that's normal. The display settings dialog is now "modeless", meaning you can leave it open on screen whiule you continue working in other windows. This makes it easier to work with multiple display dialogs simultaneously (such as when tweaking geometry correction), and also allows it to be used as a "pre-viz camera" off to the side. Since it's now "just a window", it doesn't need the OK/Cancel buttons any more.
Mike
0 -
Here, at the end of 2015, after leaving Dataton a couple of months ago, it felt like a good time to summarize things. If you're interested in the background of WATCHOUT, and how it came to be, here's a holiday treat for you:
http://fahl.se/the-story-of-watchout/
Enjoy!
Mike
0 -
According to the log, the crash is an "access violation" in the GDIPLUS Windows module, and not in WATCHOUT itself. Since this is not a general problem in WATCHOUT (i.e., you don't seem to be doing anything out of the ordinary from what I can tell), my guess is there's something wrong with the display driver configuration on the computer, and how it interacts with windows' GDIPLUS API.
You're stating the crash happens not when you open the Display Settings dialog box, but when you close it. Correct? Do you add the display using one of the presets on the menu, thus making it appear in the Stage window immediately. Or do you chose the "Other..." menu item, which displays the settings dialog box right away (i.e., before the display rectangle shows up in the Stage window)?
Mike
0 -
No, I was referring to external control of the tween track through the Input window in WATCHOUT.
0 -
Set WATCHOUT's refresh rate in Preferences to 30 Hz. Set the displays resolutions in WATCHOUT to the desired resolution. If you set the resolution and refresh rate manually also on the computers before starting WATCHOUT display software, it should leave those set as is, without attempting to change the resolution. This all assumes that your graphics card and display device supports the desired refresh rate and resolution in full-screen Direct3D mode. In some rare cases, computers may support a resolution/rate in GDI mode, while not supporting it in full-screen Direct3D mode. If that's the case, there's nothing WATCHOUt can do about it, and launching your presentation will cause the graphics card to switch display mode to whatever is preferred for full-screen Direct3D use by the driver.
0 -
The live video isn't enabled as long as it's invisible. The small stutter you see may be a side effect of the live video being activated. You may be able ti improve this by making sure the live video is activated eariler, when there's less activity in the scene. Are you fading it up with a tween track or by external control?
0
WATCHOUT in Windows 10
in WATCHOUT FORUM
Posted
The Win10 problem seems confined to the display software.
I'm not aware of any "media drag&drop" problem. Do you mean that dragging media files into WATCHOUT from Windows Explorer doesn't work for you under Win10? Does it work for you under other Windows version?