• State Not Answered
  • Date
    billy
  • Date
  • Replies 33 replies
  • Subscribers 6 subscribers
  • Views 6663 views
  • Users 0 members are here
Options
Related

CITP

I have a gen 1 Axon running 2.1.2 on the test bench. I have yet to get it to sync its custom content to the console (Hog 4 2.0). It shows up in the CITP screen when you hit patch media, and responds to control via artnet, so networking is good, but the refreshing icon in the media picker just spins and spins for hours. It eventually goes away, but the custom content never populates in the media picker. I know the media was loaded under 2.0.5 and earlier and 2.1.2 was installed later on.

Do I need to select the global fixture, a single media layer, all media layers, or all media and global before hitting update media? I think I've tried all those permutations with no success, I just want to make sure I'm doing it the right way.
  • 0
    The global layer has "Mask" associated with it and the graphic has "Object" and "Media" associated with it. If you DMX patch a DL v2 Global and DL v2 Graphic and then select the DL v2 Global and open the Media Picker window you should see a Mask tab. At this point the Mask tab is populated with the default masks from the fixture library. If you clear that selection and select the DL v2 Graphic and open the Media Picker window you should see a Media tab and an Object tab both populated with the default media and objects from the fixture library. At this point you wouldn't see any of your custom content from the media server.

    If you select the DL v2 Global and DL v2 Graphic in the Fixture Window and click Patch Media->CITP tab and select your media server the fixtures in your show will be associated to that CITP media server. At this point if you select DL v2 Global and click Refresh Media in the Fixture Window the Mask tab would be refreshed with data/thumbnails from the media server. If you select DL v2 Graphic and click Refresh Media the Object tab and the Media tab will be refreshed with data/thumbnails from the media server.

    So each fixture in the show has certain functions associated with them (Mask, Object, Media, etc.) which are in turn associated with a CITP media server and data/thumbnails are refreshed according to the selection you make.

    As a test you may want to select only one Graphic and hit Refresh Media which will refresh the Object and Media tab and should refresh pretty quickly assuming the Hog 4 Console can obtain the thumbnails.

    Hopefully that clears up what to select.

    When the refreshing icon on the Media Picker window goes away what do you see in the Media Picker window? Do you see tabs if so is there anything on the tabs? If you see the folders like "1 - HES_Core" with a bunch of black buttons or buttons with a triangle on them it means that Hog 4 Console could not retrieve the thumbnail for that piece of media. Do you see thumbnails for everything except your custom content?

    If you see thumbnails for everything except your custom content you may need to restart the media server. It may take a restart to generate the thumbnails or for the CITP server in the media server to cache the thumbnails.
  • 0
    I have done all these variations with the gen 1 axon, and I only get stock content in the picker. Multiple reboots of the Axon, tried making a new show file on the hog. Tried refreshing media on only 1 graphic, and on all 4. and global +all 4 graphic. I never get any custom content thumbnails on the Hog, but I always have stock content thumbs. Any ideas what to check?

    I'll try to upgrade a newer machine at some point and see if it spits out thumbs.
  • 0
    I have upgraded a SD SDI unit to 2.1.2 and still have yet to see any thumbnails in the console that are not part of the stock library. Anyone? I am able to see the axon in the patch media screen on the CITP tab, and patch it. When I refresh media the picker goes blank, the stock content comes back, and the refresh arrows just spin.... Restarted axon multiple times. Can send a log file if needed.

    Hog 4 v2.1.0 SD SDI Axon v2.1.2
  • 0
    What do you see in the Log Viewer when you do the refresh?
  • 0
    The hog 4 just went out the door on a gig, so I can't check for now. I may be able to hook up hog4 PC later and check that way.
  • 0
    I get a whole bunch of these errors in the Log viewer:

    [CODE]2006617673 2006617673 248 OB-2-0090a1070554 192.168.100.112 HogNet.Cloud.Protocol.Packets.Out Warning dp8kapp 2907650928 fps::ostream& cloud::Cloud::PacketBuilder::Pkt(cloud::Protocol, unsigned char, const Gut::Guid*, const std::vector >*, int) Cloud.cpp 1123 WARNING: packet size (1532) exceeds MaxUdpPayloadSize, forcing ReliableTCP[/CODE]right click and details gets me:

    [CODE]CallStack:
    [0xb7042964] cloud::Cloud::PacketBuilder::Pkt(cloud::Protocol, unsigned char, Gut::Guid const*, std::vector > const*, int) + 0x494 [0xb7042dbc] cloud::Cloud::EmitMessage(cloud::Cloud::PacketBuilder&, cloud::Protocol, unsigned char, cloud::Cloud::MsgDispatch*, fps::memory_stream*) + 0xfc
    [0xb706396a] cloud::Cloud::SendMsg(boost::shared_ptr const&, cloud::Guid const*, unsigned int, int, bool) + 0x3fa
    [0xb69aef8d] cloud::Object::Send(cloud::Message*, int, int) const + 0xad
    [0xb67ececa] GearBox::Fixture::CommitNodes() + 0x16a
    [0xb6820054] GearBox::ProtocolManager::SetMediaLibraries(cloud::Guid const&, GearBox::MediaLibraries const&) + 0x1a84
    [0xb67ff223] GearBox::CitpProtocol::processLibraryInfo(QString const&, CITP::Msg_MSEX_ELIN const&) + 0xc63
    [0xb6804114] GearBox::CitpProtocol::qt_metacall(QMetaObject::Call, int, void**) + 0x124
    [0xb7673c0a] QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) + 0x3a
    [0xb767fa86] QMetaCallEvent::placeMetaCall(QObject*) + 0x36
    [0xb7680cd2] QObject::event(QEvent*) + 0x342
    [0xb766d873] QCoreApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x73
    [0xb766df03] QCoreApplication::notify(QObject*, QEvent*) + 0x73
    [0xb766dfcb] QCoreApplication::notifyInternal(QObject*, QEvent*) + 0x7b
    [0xb767061b] QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 0x2cb
    [0xb769feea] QEventDispatcherUNIX::processEvents(QFlags) + 0x4a
    [0xb766ca79] QEventLoop::processEvents(QFlags) + 0x49
    [0xb766cefa] QEventLoop::exec(QFlags) + 0xfa
    [0xb7569b1e] QThread::exec() + 0x7e
    [0xb7569c0d] QThread::run() + 0x1d
    [0xb756cb69] + 0x6fb69
    [0xb77a4955] + 0x5955
    [0xb65e31de] clone + 0x5e[/CODE]
  • 0
    [QUOTE=Lekolite;72344]I get a whole bunch of these errors in the Log viewer:

    [CODE]2006617673 2006617673 248 OB-2-0090a1070554 192.168.100.112 HogNet.Cloud.Protocol.Packets.Out Warning dp8kapp 2907650928 fps::ostream& cloud::Cloud::PacketBuilder::Pkt(cloud::Protocol, unsigned char, const Gut::Guid*, const std::vector >*, int) Cloud.cpp 1123 WARNING: packet size (1532) exceeds MaxUdpPayloadSize, forcing ReliableTCP[/CODE]right click and details gets me:

    [CODE]CallStack:
    [0xb7042964] cloud::Cloud::PacketBuilder::Pkt(cloud::Protocol, unsigned char, Gut::Guid const*, std::vector > const*, int) + 0x494 [0xb7042dbc] cloud::Cloud::EmitMessage(cloud::Cloud::PacketBuilder&, cloud::Protocol, unsigned char, cloud::Cloud::MsgDispatch*, fps::memory_stream*) + 0xfc
    [0xb706396a] cloud::Cloud::SendMsg(boost::shared_ptr const&, cloud::Guid const*, unsigned int, int, bool) + 0x3fa
    [0xb69aef8d] cloud::Object::Send(cloud::Message*, int, int) const + 0xad
    [0xb67ececa] GearBox::Fixture::CommitNodes() + 0x16a
    [0xb6820054] GearBox::ProtocolManager::SetMediaLibraries(cloud::Guid const&, GearBox::MediaLibraries const&) + 0x1a84
    [0xb67ff223] GearBox::CitpProtocol::processLibraryInfo(QString const&, CITP::Msg_MSEX_ELIN const&) + 0xc63
    [0xb6804114] GearBox::CitpProtocol::qt_metacall(QMetaObject::Call, int, void**) + 0x124
    [0xb7673c0a] QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) + 0x3a
    [0xb767fa86] QMetaCallEvent::placeMetaCall(QObject*) + 0x36
    [0xb7680cd2] QObject::event(QEvent*) + 0x342
    [0xb766d873] QCoreApplicationPrivate::notify_helper(QObject*, QEvent*) + 0x73
    [0xb766df03] QCoreApplication::notify(QObject*, QEvent*) + 0x73
    [0xb766dfcb] QCoreApplication::notifyInternal(QObject*, QEvent*) + 0x7b
    [0xb767061b] QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 0x2cb
    [0xb769feea] QEventDispatcherUNIX::processEvents(QFlags) + 0x4a
    [0xb766ca79] QEventLoop::processEvents(QFlags) + 0x49
    [0xb766cefa] QEventLoop::exec(QFlags) + 0xfa
    [0xb7569b1e] QThread::exec() + 0x7e
    [0xb7569c0d] QThread::run() + 0x1d
    [0xb756cb69] + 0x6fb69
    [0xb77a4955] + 0x5955
    [0xb65e31de] clone + 0x5e[/CODE]

    These are ok and do NOT indicate an error.:cool:

www.etcconnect.com