Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - RonInSD

Pages: [1]
Developers / Idea of using a D-Link DSM-320 or DSM-520 as a media directors
« on: December 10, 2007, 07:14:07 pm »
I have been kicking around the idea of using a DSM-320 or DSM-520 as a media director.  I have found that a group has developed a SDK for the DSM-320.  Information can be found at:
English site but some link go back to TW site.

Some information can also be found at D-Link's web site under the GPL:

The other option is getting one of Sigma Design's new Media Extender Development kits MCX-8622L.  This has a full Linux SDK (API and documentation, includes applicable source code).  Not sure of the costs of the kit but this would get a full SDK and make the development a little easier.

I am still at the research stage so there are a lot of questions yet to be answered.

Since I am just getting started with LinuxMCE some of the questions I have are with the MCE UI interface creation on the media director and the video streaming from the core.   

I understand that most of the overlay for the UI2 is done at the media director and take a good bit of processor power on the video card.  I am not sure if these units have enough power to perform the needed tasks.  I am wondering if this can be done on the core and just the mixed overlay stream can be set to the media director.  I may have to just stick with basic UI for these units.

I also have a question on how the media director gets access to content on the Core.  I believe that the media director uses xine to play the saved media files on the core via NFS and streams live content from the core using videolan.  Am I correct?

I have three ideas on how to use these units. 

1) Have the overlay done on the core and stream everything out to the unit via videolan for all content.  This will put more load on the core.
2) Have the media extender just do the video and audio and use a full orbiter for the UI/Remote interface.
3) Upgrade the UPnP services to support the RemoteUI part of UPnP.  I am still doing some research into the UPnP RemoteUI specs.  I know that some of the newer Media Extenders have some support for UPnP RemoteUI. 

This would give me a fanless solid state unit at the TV with full HDMI support at a sub $200 cost point.  I know I will need to put the extra money towards the core.

Not sure how this is going to work with HD feeds.

Pages: [1]