Jump to content
C4 Forums | Control4

dgbrown

c4Forums Member
  • Posts

    1,419
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dgbrown's Achievements

  1. A reinstall of MM Collection Management over the top of the existing install, and selecting "repair" seems to resolve the issue as well.
  2. The EV driver - I switched for the reasons in post #6. Thanks Cody. Must have missed that.
  3. Out of curiosity are you using the EV driver or the certified C4 driver ?
  4. No advantage that I'm aware of. Just register at the MM .dk site, buy your points, and download and install the software -- and you're off to the races.
  5. Will - Thanks for getting back ! I think I have that sorted now, it's working as advertised. I did run into one use case you might be interested in. I had a multi disc set (5 discs one MM title). The first disk had a prefix of "Disk 1" which caused it to be sorted below disc 2-5 (note the k instead of c in disc). I then changed the "Disk 1" to "Disc 1". The driver started complaining about a collision between "Disc 1" and "Disc 2". I re-saved the title. Same results. In MM, the first disc in a multi disc is usually cataloged as an "Online Folder", with the rest being "Online Files". This was the case in this instance. The only way I could get the error to go away was by changing Disc 1 to an "Online File". If you'd prefer a case to be opened let me know. I thought since MM was not a dealer tool, the in's and out's of this might be useful here.
  6. EV - any chance you can filter out disks with no network location ? Multi disk sets look like they're syncing - each one showing with their own cover art (limitation of c4's interface) - if theres a missing disk 2 for bonus material for instance, it shows in c4 but is not playable.
  7. +1 I like some of the Apple products and their networking components may in fact work. IMHO, they're extremely basic and offer no real tuning options - in short useless.
  8. POE will come from your network switch not the transmitters, assuming your switch supports POE. If not you will need injectors.
  9. First a little history: 3Q 2009 - HDMI over IP "launched" at CEDIA 2009 4Q 2009 - Rackmount Transmitter added to the HDMI over IP family Seems to me it would be a good idea to keep trying to add another new HDMI over IP product each quarter. PoE for 1Q 2010 sounds like a winner to me! Please stay tuned to this channel. Thanks Ed .... a POE receiver and modular cards (blades) to slide in that rack mount would make this a pretty finished line with near infinite expandability and low cost of entry. Best, Dave
  10. Ed - I actually haven't been back through the entire thread but has there been any discussion around a POE version of the JAP receiver ?
  11. Everything we are doing is what the Managed Switches are designed to do. No modifications or hacks to the factory settings are required. We are just using their standard features to achive a superior result. Manipulating the switch config to achieve what you're trying to do in the way you;re trying to do it is a hack. Having duplicate IP's on a network to support this is a hack. The IGMP publish and subscribe model is not supposed to work in the way you've engineered your product.
  12. Interesting yes. But having to play games with the switch config to get this to work leaves much to be desired seems like a hack to me. Does anyone recall how Netstreams is/was doing with their IP based media distribution system ?
  13. I have an update on Bridging VLAN's when you want/need to expand an HDMI over IP Matrix beyond the capacity of the first switch. If you want to use Just Add Power HDMI over IP Matrix switching across multiple switches, it is reccomended that the switches you select are ones that support the Network Standard IEEE 802.1Q VLAN's. This is because the 802.1Q VLAN's allow static port based VLAN's to commumicate across a shared backbone connection. Otherwise you would have to use additioanl dedicated ports on each switch for bridging each HDMI over IP Transmitter. For those of you that enjoy technical details, there is a good document covering this topic at ftp://ftp.hp.com/pub/networking/software/AdvTraff-Oct2005-59908853-Chap02-VLAN.pdf (pages marked 2-5 and 2-6 illustrate the concept). The Netgear FSM726 $240 switch does list 802.1Q in the product specifications online, with support for up to 64 VLAN's (reference http://www.netgear.com/Products/Switches/FullyManaged10_100Switches/FSM726.aspx?detail=Specifications ). Theoretically, you could bridge 11 FSM 726's together to support a 64 Input by 200 Output HDMI over IP Matrix. Depending on the nature of the traffic, it may be more practical to "limit" this hypothetical HDMI network to about 20 Inputs for heavy duty applications. On the other hand, The IC Intracom switch does not specifically list the 802.1Q specification in the online documentation. Some of the other IC Intracom switches do appear to support 802.1Q, so it might just be an omission in the online documentation. I should have some of the IC Intracom switches in my hands on Tuesday. At that point we can test them to see if they are "limited" to HDMI over IP applications that can can live within the 26 port limitation (i.e. build your own right-sized whole-house HDMI over IP matrix with any combination of TX and RX units and up to 26 total allowed such as 16 TX HDMI channels and 10 RX HDMI display devices). If you are in the mood for some power shopping, you can browse a listing of over 1,600 Network Switches and Hubs that support IEEE 802.1Q VLAN's at http://www.epinions.com/Networking_Hubs_and_Switches--ieee_802_1q_qos/sec_~product_list/pp_~1#list ! Here's the tech notes from Cisco that pertain to this issue: http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008059a9df.shtml
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.