Media Library not working on Network Shares

Regarding the earlier poster’s comment about it being a “streaming” device.  The devices is marketed as a media streamer.  So, I would expect that to be the typical use case vs. USB-attached storage.

The the media library works with media on the USB filesystem, but not with network shares.  How do they not catch that bug in testing, before release?  Without a functional media library, the dashboard, filtering, metadata retrieval, etc. do not work.

It implies they never tested those options with network attached sources?  Or they did and knew it didn’t work.  Then, decided to ship anyway.  The customer not being aware of the limitation prior to purchase.  The first scenario seems very unlikely.  The second scenario is a bit disingenuous.

DigitalHype wrote:

 How do they not catch that bug in testing, before release?  

Well, I can tell you, without a doubt, you don’t know what you’re talking about.

The ABSENCE of that function is *NOT* a BUG.    The absence is DUE TO a bug.

As WD has said, they DID catch a serious bug before release that was related to this functionality.   That’s why it has been temporarily removed.

And what I was saying is that the absence of this function has absolutely *NO* impact on its ability to play streamed files.   It only affects organization and display.

TonyPh12345 wrote:


DigitalHype wrote:

 How do they not catch that bug in testing, before release?  


Well, I can tell you, without a doubt, you don’t know what you’re talking about.

 

The ABSENCE of that function is *NOT* a BUG.    The absence is DUE TO a bug.

 

As WD has said, they DID catch a serious bug before release that was related to this functionality.   That’s why it has been temporarily removed.

 

And what I was saying is that the absence of this function has absolutely *NO* impact on its ability to play streamed files.   It only affects organization and display.

Sure.  The absence of some functionatliy isn’t “the bug” here.  That is the result of the bug.  No need to discuss the semantics.

Your response confirms it was the 2nd scenario I posited.  They were aware of the problem, disabled the media library, to prevent the “serious bug”.  Then shipped.

I understood what you were saying.  I was making another point.  I feel they should have prioritized the fixing of the bug, prior to putting the device on shelves.

OK, sure, the unit can still stream content from the network but it can’t do what WD clearly indicated it’s supposed to do. To me this makes absolutely no sense. Let’s say you buy a new GM car and the radio doesn’t work. The dealer tells you that at some undisclosed later date GM will release a “patch” that will be sent down via OnStar which will enable the radio to work. Otherwise the car IS fully functional so I guess you wouldn’t have the right to complain? I don’t think most would accept this nor would GM dare to sell a car with a “disabled” feature (to be fixed at a later date).

DigitalHype wrote:


TonyPh12345 wrote:


DigitalHype wrote:

 How do they not catch that bug in testing, before release?  


Well, I can tell you, without a doubt, you don’t know what you’re talking about.

 

The ABSENCE of that function is *NOT* a BUG.    The absence is DUE TO a bug.

 

As WD has said, they DID catch a serious bug before release that was related to this functionality.   That’s why it has been temporarily removed.

 

And what I was saying is that the absence of this function has absolutely *NO* impact on its ability to play streamed files.   It only affects organization and display.


Sure.  The absence of some functionatliy isn’t “the bug” here.  That is the result of the bug.  No need to discuss the semantics.

 

Your response confirms it was the 2nd scenario I posited.  They were aware of the problem, disabled the media library, to prevent the “serious bug”.  Then shipped.

 

I understood what you were saying.  I was making another point.  I feel they should have prioritized the fixing of the bug, prior to putting the device on shelves.

 

 

    • *> I’m guessing you’ve never worked in the corporate world. When you sell a product to say best buy (or walmart, or any of those places) you have to sign a contract saying you’ll have X number of units on the shelf by Y date. If you don’t you pay a huge fine, and they have the right to re-sell the shelf space to someone else. Because of this, devices are often shipped months before the “final” firmware is ready. Even if they can delay it, they have a date that they MUST be shipped by or they face this fine and possible loss of shelf-space. This is even worse this time of year as this is the “pre-holiday” season.> Thats why most devices have a “Day-1” patch, so they can continue working on the software side of things while the device is being shipped and produced. > My guess is the devices shipped either before they found the bug, or right-after and they assumed it would be resolved for the “Day-1” patch. Maybe it was more complex than they thought, or something else happened.> This is all hypothetical of course, but my guess is it’s not too far off- i’ve seen the same story over and over and over again from almost every manufactuer. The real villian here is the big retail chains who put these kinds of constraints on their customers and suppliers.

Ardvark wrote:> * * *> I’m guessing you’ve never worked in the corporate world. When you sell a product to say best buy (or walmart, or any of those places) you have to sign a contract saying you’ll have X number of units on the shelf by Y date. If you don’t you pay a huge fine, and they have the right to re-sell the shelf space to someone else. Because of this, devices are often shipped months before the “final” firmware is ready. Even if they can delay it, they have a date that they MUST be shipped by or they face this fine and possible loss of shelf-space. This is even worse this time of year as this is the “pre-holiday” season.> Thats why most devices have a “Day-1” patch, so they can continue working on the software side of things while the device is being shipped and produced. > My guess is the devices shipped either before they found the bug, or right-after and they assumed it would be resolved for the “Day-1” patch. Maybe it was more complex than they thought, or something else happened.> This is all hypothetical of course, but my guess is it’s not too far off- i’ve seen the same story over and over and over again from almost every manufactuer. The real villian here is the big retail chains who put these kinds of constraints on their customers and suppliers.

Plenty of experience in the corporate world. No need for the ad hominem stuff.

So, because Western Digital doesn’t want to incur fines from thier retailers, or lose potential shelf space, the customer pays for a product that does not function according to specification.  Where the firmware is, as you correctly pointed out, not ready.

According to TonyPhy12345, WD caught the bug before it release, and temporarily removed the media library functionality.  That being true, WD couldn’t have shipped first.   Else, there would be some models on the shelves with the bug, and media library still enabled for network shares.

Yes, I’ve also seen this story before.  Chances are I didn’t enjoy it last time, either.

DigitalHype wrote:


Ardvark wrote:> * * *> I’m guessing you’ve never worked in the corporate world. When you sell a product to say best buy (or walmart, or any of those places) you have to sign a contract saying you’ll have X number of units on the shelf by Y date. If you don’t you pay a huge fine, and they have the right to re-sell the shelf space to someone else. Because of this, devices are often shipped months before the “final” firmware is ready. Even if they can delay it, they have a date that they MUST be shipped by or they face this fine and possible loss of shelf-space. This is even worse this time of year as this is the “pre-holiday” season.> Thats why most devices have a “Day-1” patch, so they can continue working on the software side of things while the device is being shipped and produced. > My guess is the devices shipped either before they found the bug, or right-after and they assumed it would be resolved for the “Day-1” patch. Maybe it was more complex than they thought, or something else happened.> This is all hypothetical of course, but my guess is it’s not too far off- i’ve seen the same story over and over and over again from almost every manufactuer. The real villian here is the big retail chains who put these kinds of constraints on their customers and suppliers.


Plenty of experience in the corporate world. No need for the ad hominem stuff.

 

So, because Western Digital doesn’t want to incur fines from thier retailers, or lose potential shelf space, the customer pays for a product that does not function according to specification.  Where the firmware is, as you correctly pointed out, not ready.

 

According to TonyPhy12345, WD caught the bug before it release, and temporarily removed the media library functionality.  That being true, WD couldn’t have shipped first.   Else, there would be some models on the shelves with the bug, and media library still enabled for network shares.

 

Yes, I’ve also seen this story before.  Chances are I didn’t enjoy it last time, either.

Sorry about that - a lot of people honestly don’t know.

So let’s assume they caught it, were working on a fix, and had to ship or would miss the deadline. By that time the manuals need to be completed, translated into umpteen languages, boxes printed, etc. - no way to “remove” the feature from the litature, and no way to not ship the product. When I say these fines are huge, i mean HUGE - sometimes 7 figures. For a $100 product, it might not even be worth selling when you consider that these contracts are likely all going to give the same or a similar date. Remeber that a company is beholden to its stockholders- they can’t do anything that will lose them money or risk the wrath of wall st.

Also, it’s a minor feature - it’s not like the remote is non-functional, or 1/2 the codecs supported don’t work. It would be a very bad busness decision not to ship due to this one thing not being ready. Especially since it will be added in the near-future (I’m almost certain we’ll have it before christmas- they will want to minimize returns durring black-friday sales too so likely even before thanksgiving). Also consider this - if the drive doesn’t get good shelf-space less people will buy it. If less people buy it, they will be less focused on adding new features and support in the future.

That shelf-space is also very expensive and it’s loss could be paramount in helping to sell the product.

Another solution would be to configure PlexApp server on your PC and use a Jailbroken Apple TV2 with the Plex Client. Covers and descriptions *just work*.

Added benefit is that the PlexApp Client for iPhone/iPad allows streaming movies to your iPhone/iPad both locally and over the internet. LG are also building PlexApp client functionality into their new TVs and a client for Samsung TVs is being developed.

WD really need to build a PlexApp client into their TV Live range!!

In the interim, is there any way to generate the metadata yourself? I assume it’s some sort of xml file that would sit on the nas somewhere.

Totally agree… It is unfair for wdc to hurl an imperfect product in the market just so that they can, i think, meet a production deadline. Theybhave no idea how many man hours are wasted byntheir customers trying to figure out why media files stored in NAS is inaccessible. I even came to a point where i started to question my basic understanding of network technology! Caveat emptor !!! Could this be another example of CORPORATE GREED?

Clemmor wrote:
Could this be another example of CORPORATE GREED?

Yeah.   I’m sure that’s it.

Just registered so that I could post in this thread.  Like everyone else, I’m waiting anxiously for the next firmware which re-enables the Media Library functions over a NAS share.  

Anyone who hasn’t already should visit this WD page to vote this issue and bring it to WD’s attention.  

The Media Library functions over a NAS share was one of my main arguments to buy the new WDTV.

Would be nice if WD could re-enable the feature soon. 

leftpeg there is a program on this forum to do just that.

I am also frustrated with the lack of media library functionality as I was expecting the same features as the WDTV Live Hub minus the hard drive. However all is not lost as you can get most of the visuals by using WDTV Live Hub autogenerator.

http://community.wdc.com/t5/WD-TV-Live-Hub-General/v2-0-released-WDTVHubGen-Looks-up-Movies-TV-Shows-and-creates/td-p/160548

I have my media library organised in a way that suits this program and it works really well for me.

Plenty of posts explaining how to use it.

Just to add I have the same problem. Very annoyed as this is the reason I got this new live.

There’s a new firmware that has been released today (or maybe yesterday) and in the release notes, it says specifically that this issue has been corrected. However, after applying the update this morning, the problem still exists using a NFS share. Can anyone else confirm this?

Thanks

Yan

1 Like

I upgraded last night.  Media library was not working for me with the new firmware, on nfs shares.  My shares are writeable by all.  I didn’t have any time to troubleshoot or investigate though.  I can check this evening if it is working over SMB/CIFS shares, too.

It’s not supposed to work with NFS, just SMB.

I just upgraded the firmware and deleted my network connection settings under setup and then when rejoining the smb share I got prompted to add to media library

At the moment it says compiling media library

Fingers crossed it works from here on in, :wink:

Tony,

Do you know the reason why it cannot work with NFS shares? The only reason I use NFS is because I don’t like to see the default system shares on my Window server (netlogon and sysvol for examples). Is there anyway around that with SMB?