• April 19, 2024, 02:17:33 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Why filter/block filetypes in the Server?  (Read 3538 times)

slyder

  • Level 2 Member
  • **
  • Posts: 34
Why filter/block filetypes in the Server?
« on: February 04, 2009, 04:33:17 AM »
Since this unit does not decode video, only serve the files to other devices/applications, what is the purpose of filtering/blocking file types?.  This unit does not serve exampleMKV, Matroska container file types using the AV Server.  Why is this filtered since the unit is NOT expected to decode files anyways, but simply make them available to whatever device is accessing?.

I run twin DSM-750's (MKV Compatible) and yet this format is prevented from being accessible when served by the AV Server in this unit negating the whole point of buying it and am forced to continue with Tversity to access this format from the NAS. Why is this necessary?..and why is it not stated in the documentation that this form of limitation exists?????

Would it not be simpler to let the external devices/applications determine file compatibilities  and simply server all files placed on the unit?

Can someone point me to a hacked bios for this device that opens the file types table to enable something akin to a *.* compatibility list?.. Or perhaps a quick maintenance update to the bios to address this quickly.

Logged

mig

  • Level 3 Member
  • ***
  • Posts: 217
Re: Why filter/block filetypes in the Server?
« Reply #1 on: February 04, 2009, 07:19:02 AM »
You don't have to load a hacked BIOS, but if you do a google search for
"dns-323 hack" you should find some information that could be useful to
your problem.
Logged

D-Link Multimedia

  • Poweruser
  • Level 7 Member
  • **
  • Posts: 1066
    • D-link Systems, Inc.
Re: Why filter/block filetypes in the Server?
« Reply #2 on: February 04, 2009, 02:00:47 PM »
It doesn't necessarily 'filter' the MKV format, it just does not recognize the extension. The UPNP AV server inside has a list of file types to look for when indexing and if the file type is not hard coded in (this happens when new extensions come out) then it will not be added to the index file. Perhaps we can look at a different way of going about adding extensions in a future firmware but for now until we have developed that system it all has to be manually added to our customized server.
Logged

ttmcmurry

  • Level 4 Member
  • ****
  • Posts: 438
Re: Why filter/block filetypes in the Server?
« Reply #3 on: February 04, 2009, 04:40:40 PM »
I had a prior post about this as well..

http://forums.dlink.com/index.php?topic=3938.0

It may be a wise idea to allow users the ability to specify what kinds of files they want UPnP to share via the 323's web interface (provided the indexer can parse the files).  Naturally there should be a default "factory" setting (and a default button to reset the choices).  For example, sharing MKV files would be useless to PlayStation3 owners, so that could be unchecked, yet allow .AAC and .M4A files to be shared, which the current 1.06 firmware doesn't allow, though technically possible.
« Last Edit: February 04, 2009, 04:43:35 PM by ttmcmurry »
Logged

slyder

  • Level 2 Member
  • **
  • Posts: 34
Re: Why filter/block filetypes in the Server?
« Reply #4 on: February 05, 2009, 03:20:54 PM »
Allrightythen!.
Linux OS.. cool..
Which now drives a whole whack of other questions filled with "Whys?" when it comes to the bios and the constraints it places on filetypes, various other settings etc.

For another day... Seems the only real solution available right now since Dlink isn't offering one is to Hack it and use a 3rd party media serving app to solve the problem.. which is available out there already..

Thanks for the tip!
Logged