Register
Search

Forum

Forums Community Support Issues
CITP issues
You are not authorized to post a reply.

Erik Docktor
Basic Member
Posts:16 Basic Member

--
2015-09-04 00:48

    Hi - so I've got a fairly small previz system set up.

    (1) Macbook pro running Vx76 and a 276 wing. It has a network run from the back of the wing (Artnet) and a network run into the macbook itself (CITP/Mbox remote)

    (2) iMac running Mbox Studio. It's got three network hoses currently - 1x Artnet for Mbox control, 1x Mbox Remote/CITP (back to the Vx76 machine), and 1x CITP run for PixelBeetle.

    (3) Macbook pro running Capture. It gets a hose for Artnet and a hose for CITP/PixelBeetle.

    On a good day, if I connect ONLY the pixel beetle run, i can get mediocre CITP performance at 360p. This involves turning every other network interface off so that these two can talk. As soon as other interfaces get brought online, Capture and PixelBeetle both get really confused and stop talking to each other.

    After beating on the system for a while and bringing every interface up in what appears to be the right order, I got everything working for a bit. However, within a minute or two PixelBeetle or Capture will freeze up and just stop updating its stream. Is there any way to bind this stream to a particular interface? If I try to grab the stream by IP instead of "Automatic" in Tools, I get absolutely nothing ever until the end of time, but if i go with "Automatic" it somehow manages to find the stream but tries to jam it down the Artnet hose.

    How should I approach this system? How can this be made to work?

    Lars Wernlund
    Staff Member
    Posts:2018 Staff Member

    --
    2015-09-07 08:43

    Hi,

    This problem was discussed further in a support e-mail, but for those stumbling upon the question..

    In terms of trying to find the problem, use a process of elimination, starting with something that works. Ie. start with only one network or only one protocol and then add things until something breaks.

    In this particular case it seems that the console and Capture were requesting different qualities/framerates of video from the media server at once, so the media server took a decision to accomodate the console, which limited the quality of video in Capture.

    Technical Director
    Capture Visualisation AB

    Erik Docktor
    Basic Member
    Posts:16 Basic Member

    --
    2015-09-07 16:42

    In some poking around, it's even more fun that that, Lars - the media server tries its best to accommodate whoever's requesting a thumbnail at the moment, which explains why i'd flash between 100px and 240px repeatedly before it would attempt to serve 480px and fall over.

    Currently working off content thumbnails in the console, live citp is turned off at the board. ;)

    Lars Wernlund
    Staff Member
    Posts:2018 Staff Member

    --
    2015-09-08 09:49

    Hi,

    Ah,.. the media server really needs to track all current subscriptions and not let the last subscription request decide for all. Obviously. ;-)

    Technical Director
    Capture Visualisation AB
    You are not authorized to post a reply.