Jump to content
Dataton Forum

Mike Fahl

Member
  • Content Count

    658
  • Joined

  • Last visited

1 Follower

About Mike Fahl

  • Rank
     CTO, PIXILAB AB

Contact Methods

  • Website URL
    http://pixilab.se/

Profile Information

  • Gender
    Male
  • Location
    Linköping, Sweden

Recent Profile Visitors

1,364 profile views
  1. Why would it matter if it gets the command twice? They should both say the same thing pretty much at the samr time anyway, shouldn't they? Mike
  2. I see there's a "UDP/TCP Generic module" as well for Companion. Assuming this module can receive data (to trigger commands or "stacks" in Companion) you should be able to use that one, as WO can send TCP and UDP command strings quite easily. Mike
  3. If prod sw and WN runs on the same PC, you should be able to just put localhost into the address field. If they're on separate PCs, put the IP address of the WO prod PC in this field.
  4. This error message translated to its hexadecimal form is 0xC0000005, which makes it easier to google. It's an "access violation", meaning that the program has attemped to access memory it's not supposed to touch. This is usually a bug (e.g., a null pointer access). Not much you can do about it, except perhaps trying to see if you can reproduce it at will, and if so let Dataton know how to reproduce the error in order to fix it. Sometimes, the Windows event log provides more details when such a crash has occurred, which could also help in pinpointing it: https://www.digitalmastersmag.com/magazine/tip-of-the-day-how-to-find-crash-logs-on-windows-10/ Mike
  5. Contrary to what's said above, looping and/or free-running videos are synchronized across computers. Or, at least that was the case when I was involved. I doubt it has changed since. If looping or free-running video gets out of sync across computers, I would have considered that a bug. Mike
  6. m.2 is usually preferable over SATA-based SSD. Beware of the various types of m.2 sockets though, as the number of PCI lanes can greatly affect the performance. Mike
  7. MP4 is a subset of MOV, using the same atom-based file structure. So it can be confusing. It's really what's INSIDE the file that matters, not its file extension most of the time. Mike
  8. Here's a complete list of QT error codes: http://mirror.informatimago.com/next/developer.apple.com/documentation/QuickTime/APIREF/SOURCESIV/errorcodes.htm The error you see is "noCodecErr", indicating the file uses a codec that can't be found. Since HAP codecs are built into WATCHOUT, QuickTime isn't needed to play such files. But if your file is using an unsupported odec (or an unsupported flavor, as Jim suggests), WO likely falls back on attempting QT (if available), which then fails with the above error. If you have QT on the machine, you can open the file using the QT app, and it may be able to rell you more about what's in the file. If you know it is some form of HAP, it may likely be the "HAP Q Alpha" flavor, which, as Jim says, isn't supported. Mike
  9. Not that it helps you with your WATCHOUT issues here, but we've used those monster NUCs with PIXILAB Blocks for driving up to six displays in various configurations. Works suprisingly well. We're using our own player software here, which isn't based on Windows, so of course driver behavior may be different too. Mike
  10. I would consider that a bug, to be dealt with separately. The method I suggest is the only one possible today, AFAIK. Although one could of course wish for a simpler method of doing this, Mike
  11. You can get close by moving the cues into a Composition, which is then brought into an Aux timeline as a cue, to which you apply opacity and volume. These tweens will then affect everything in the Composition. Not as convenient as what you suggest, but doable. Mike
  12. I believe WO is still 32 bit only, so throwing more than 16GB of RAM at it shouldn't make much difference. Just make sure you have RAM installed in an optimal way for the motherboard (some mobos benefit from parallell channels if modules installed across all RAM lanes). Mike
  13. Sounds like you have some video content that causes WO to lock up. To figure out which one, remove video one by one, and try to "update" between each, until you found the offending item, then forward that file to Dataton. Such problems are sometimes caused by rouge codecs, but since you've just installed the machine according to the guidelines, that shouldn't be the case.
  14. The Instagram API I used back then is no longer available, so this function wouldn't work now anyway. PIXILAB Blocks has built-in support for Instagram feeds, but even that has been quite constrained by the latest round of Instagram API restrictions. Mike
×
×
  • Create New...