Jump to content

Jonas Dannert

Member
  • Posts

    939
  • Joined

  • Last visited

Posts posted by Jonas Dannert

  1. DirectShow API: no, there is nothing to check.

     

    Hardware config: I would not run WATCHOUT 5 on this. Too low spec.

     

    What kind of graphics card is used?

     

    Which driver for HDExtreme?

     

    Are we talking about Preview in the Stage Window of Production OR capture in a Display computer?

     

     

     

     

     

     

    (null)

  2. Hi Neil,

     

    Out of Osprey 230 and Intensity Pro, Intensity Pro is the better choice.

    It's faster than the Osprey, but still slower than a progressive, digital capture card.

     

    Most settings in the driver, can be left alone, WATCHOUT do not use them,

    instead capture is done through the DirectShow API.

    The main thing to use the cards own capture software for, is to see if the signal is

    present at the cards input, before capture test in WATCHOUT.

     

     

    "Because I have to capture a PAL source would I be better to run WO at 50fps?"

     

    It might be, but setting WATCHOUT to 50Hz, without using an EDID on the output at 50 Hz,

    will not help much.

     

    Capturing interlaced, analog LIVE signals, will never be as good as a progressive, digital signal, HDMI or HDSDI.

    1280x720p, HDMI or HDSDI is a good choice here, cards are not so expensive, not cameras either,

    at least not HDMI-based ones. There are HDSDI-cameras from 4-5000 USD, an example is Canon XF-105.

     

    1920x1080p (3G HDSDI) is still a bit out of reach for mere mortals, otherwise it's the best solution.

     

    Even 1920x1080i, interlaced, digital (HDMI or HDSDI) is better than standard analog video, composite or component.

    Interlacing artifacts & tearing can of course still be visible, especially in fast movements.

     

     

    "anything I could do to improve the delay time?"

     

    Not in the settings in WATCHOUT, no.

     

    The delay in WATCHOUT from input of capture card to the output of the graphics card,

    on a properly configured system, is approx. 2.2 frames, assuming a digital, progressive signal.

    Osprey and Intensity with analog, interlaced signal, is slower.

    I don't know by how much, though.

     

    Using progressive, digital will of course help.

     

    Any devices inserted in the chain between camera and capture card, will affect the delay,

    for example a vision mixer.

     

    Hope this helps,

     

    /jonas

  3. And this card has 2 "legacy" outputs, DVI and/or HDMI, and 2 MDP outputs?

     

    Then I think I was correct earlier, that if three outputs is connected,

    and two of those are MiniDP, they will both have to be ACTIVE.

    OR, one have to use the 2 "legacy" outputs first, before using MDP outputs.

     

    This is more a Windows setup issue, than a WATCHOUT one, I think.

    WATCHOUT does not run in the same graphics mode that the Windows desktop do.

     

    "when I connect the Watchout App from the ipod (the way this installtion is operated) the third output (now the HDMI one) drops its sync signal monetarily, causing the projector to drop out. This only happens when the ios app connects, and then it returns back again"

     

    This I've never heard of before.

     

    As always, if you require more detailed research, please compile as

    small show file and send it to us, at support@dataton.com

  4. Some questions:

     

    - why three outputs connected to the card, if you only use two?

    - which AMD Radeon HD6950 card specifically? They are not all the same...

    - 1 x Mini DP to DVI, this is the ACTIVE adapter?

     

     

    I would guess that if three outputs is connected, and two of those are MiniDP, they will both have to be ACTIVE.

  5. Just to state the obvious, ALL projectors throw light when showing a black image.

     

    LCD technology is inherently worse than DLP in this area, especially high-brightness ones. (that was you I meant, Sanyo... ;-) )

    Color/brightness uniformity over the image area and using wide-angle lenses also affect this.

     

    Using projectors with built-in edge blending capability, could be better,

    if there is Black Level Compensation for the areas surrounding the blend.

    One thing though, there will be a hard-edge issue between these areas, that has to be dealt with, too.

     

    Only way to get a "real" black is, as suggested above, to use projectors with real shutters or external ones.

    Nicest is to use a dowser/dimmer type like in Barco HD8, this gives you dimming instead of a straight cut.

    Both ways will of course give you total blackout.

     

    Good thing with WATCHOUT is, that these can be controlled from within a timeline, if needed.

  6. Hi Lloyd,

     

    Since black is "a little light" no matter with which technology you project with, it will always be a

    "black level build up" in the blend area, there's no easy way around that fact. DLP technology is still

    the preferred platform in this regard, I think. LCD technology:s black level is better these days,

    but not on par with DLP.

     

    There are of course ways to counter this issue, some more expensive than others:

     

    - using special processors, that can raise the black level of the areas surrounding the blend.

    Used in simulators and similar areas, often combined with warping tools etc.

    One example can be Projectiondesign:s MIPS-boxes. This kind of solution is not cheap.

    http://www.projectiondesign.com/products/multi-image-processor

     

    - old school way, it's optical blending by placing masks, mechanical or optical, in the optical path of the projector/s.

    This is a simple, in-flexible solution to the problem, but it will give you a complete "black" level.

    Could be cheap, but not so easy or practical to implement/use.

    An example : http://www.barco.com/en/simulation_virtualreality/product/1451

     

    Hope this helps,

    /jonas

  7. Some thoughts on this subject:

     

    - Always use audio for video files, separated from the video file for better stability/reliability.

    Preferably .wav-files

    - .mp4 with embedded AAC-audio or AAC-audio is not supported within WATCHOUT:s codec.

    - QuickTime is not involved in the playback here, hence if it plays in QT Player does not tell you anything.

     

    If the file plays in Production but NOT in a Display computer, there must be a difference in what codecs

    that are installed.

     

    Recommended is to ONLY install WATCHOUT and latest QuickTime and turn off Windows

    Media Center Features. All other installed codec-packs, DVD or Media-players will potentially affect

    stable WATCHOUT playback.

  8. Hi Daniel,

    I would recommend you to NOT use Adobe Encoder.
    Instead use a separate encoding program as it gives you many more options
    and yields a better result for WATCHOUT use.

    Some suggestions:

    - Telestream Episode 6 (MacOSX/Windows)
    http://www.telestream.net/episode/overview.htm

    - Grass Valley Procoder 3 (Windows only), a bit old now, but generate good results still
    http://www.grassvalley.com/products/procoder_3

    - TMPEnc (Windows only), freeware/commercial versions available
    http://tmpgenc.pegasys-inc.com/en/index.html
    http://www.tmpgenc.net/en/index.html

    Please also see the enclosed document for some guidelines on settings and codec choices.

     

    WATCHOUT-Codecs_for_stable_WATCHOUT_playback-2012.pdf

×
×
  • Create New...