Nathan, I would like to test those instructions if you have the patience. In the next few days a new version of the firmware should arrive that has SSH access. When you upgrade, would you care to try the steps mentioned on the link?
PLEX_HOME is /usr/local/plexroot/lib on the Linkstation but I will give you detailed instructions on what to do.
GaryTomato? Is that tomato as in the tomatousb tomato's? Or are u just a fan of the soup?
Hehe, good try, but no. My name came earlier than the TomatoUSB firmware, although I use that firmware for my router and hats off to its creator, it's a nice piece of firmware.
I just ate too much tomatoes in a camp when I was a kid... Kinda' dumb, but a bunch of people still call me that and it stuck on me on the Internet too. :)
TomatoPlex mmm.. tasty.. I guess it would Open-Plex-wrt not as tasty, sounds like something you'd take valtrex to get rid of. But is there any technical reason your package couldn't be reworked as ent/optware? A Linksys EA4500 seems to be running the same hardware but in 1.2mhz trim as the duo..
Personally I'd LOVE it if someone would put together a modern media server that would run on a router. I don't know enough about the inner life of plex to know if my problems with are fixable at your level, ie populating dlna directories, hit/miss many times I'll have to open a dir multiple to get it to populate.
Channel transcoding or at least an accurate compatability filter, CBS for example is using flash/silverlight (not sure which) and needs to be transcoded for me to watch it, people claim that this is possible, but I've never figured it out, I guess their could be some supper secret dlna decoder ring, but overall I'd give plex 0 stars for dlna admin setup, see media browser with it's user friendly dlna profile select page..
From a "cut & paste" programmer like myself I'd like to see a standalone modular approach. If I had skillz it would be the ■■■■■■■ child of minidlna, plex channels and webmin on the backend and sorry plex but media browsers frontend, while not perfect it's very slick, features like "play to", metadata management and report generation, and if they were compatible with plex's channels, it would be a total knockout victory for media browser..
Transcoding in itself is a big problem with any router. There's no codec processor in the router and the built-in ARM processors are way too weak for any kind of video work.
I was wondering why there's no proper chip in these devices or why haven't someone built something that would be able to do transcoding and other stuff but then I look at the expensive Thecus and NetGear NASs and I realize there they are, it's just way too expensive.
I was also looking at all kinds of mini PCs to see if I could use them better for multimedia but by the time you add everything (decent processor, changeable hard-drive(s), a little battery so you don't lose everything in the first electricity blip), it's cheaper to buy a laptop in Walmart and put a decent linux on it.
Also Plex is proprietary, so we shouldn't just hack at it, yet. Maybe we could, it seemed some of the pages are just Python, but I didn't look at it in details yet.
My channel transcoding peeve is about the desktop version, I've tried all the linux/windows permutations to the same result, heck I'd build a hackintosh if I thought the results would be any different.
As far as the router mindlna/xupnpd get you the open source bones for the backend, as for the frontend, I think most are Xbmc branches but Plex Home Theater is open as are Mythtv, Media Portal, GeeXboX etc..
I absolutely will test the instructions for you. Detailed instructions will be helpful as I have only a very limited understanding of SSH access. The only complication is that I leave for Canada for 6 weeks tomorrow and won't be taking the hard drive with me. Happy to give it all a go when I get back though.
If you have a strong understanding of BASH scripting, head over to GitHub and have a look at the files 0-vars and 5-addplexbinary. That's exactly how I did it. In short: you have to put some of the libraries like GCC, libc, etc, into a folder and run plex using chroot. (The link is a scripted method on how to create a Linkstation firmware so you have to extract the information from there and apply it to your case.)
The hard part, (as discussed in another thread) is that the newest Plex requires newer libraries than what the Linkstation can offer so you have to force it to believe it got the newer libraries. There's a quick summary also on my blog about it. You'll have to put it together yourself from there. You can also head over to NAS-Central to get more help.
I absolutely will test the instructions for you. Detailed instructions will be helpful as I have only a very limited understanding of SSH access. The only complication is that I leave for Canada for 6 weeks tomorrow and won't be taking the hard drive with me. Happy to give it all a go when I get back though.
Cheers,
Nathan
Hi Nathan,
So the new version of the firmware is out, dubbed "Chris" and SSH is integrated so you don't have to install a developer's version.
Here's what to do:
1. Upgrade to 1.69-3.59-Chris
2. Enable SSH (the shortcut on the left will take you there, look for Network service)
3. Log in using PuTTY (user: root, password: password) - don't forget to change the SSH port to "2222" from "22"
