Yes I think that we can merge the two projects eventually. Right now I am looking into replacing the event handler and listeners with twisted-matrix, since it seems like this will greatly reduce the code. However, all of other modules will still be used as is. So, if you make some nice feature-rich modules, we can merge them in with the twisted reactor!
As for making the GUI, I think it is best to get something simple that works first. For instance, a basic directory to navigate by movie /series title alphabetically first, all just text based. I think that is still a ways down the road though. We might want to look into python-qt bindings, as it might give better performance to use Qt over TK... though prototyping in TK might be easier?
I can help you with packaging up your module, though I'm afraid I defected from debian long ago, and have no interest in writing a .deb package. It should be reasonably easy to convert my ebuilds to debs though... I hope.
I suppose it might be prudent to start a wiki for this project. I will happily maintain the Gentoo port, but we will need someone to maintain the raspbian port. A good first step would be enumerating the dependencies, it is currently an incomplete list. Are you using X11 for playback? Are you using it with the fbdev driver? I am currently using DirectFB for performance reasons.
Btw, it seems when I updated my PMS server, I stopped getting transcode crashes and playback is much more reliable.
It seems that OMXPlayer doesn't support seek jumps in media streams unfortunately. It also seems that it will be very difficult to get "resume from XX:XX" functionality, as the OMXPlayer --pos flag doesn't work on media streams either. These present pretty severe usability problems right now... hopefully support will be added soon. I'll try pouring through their code to see if I can find a way to hack it to allow seeking in media streams.
Then again, it may be that the server must be told to adjust the stream, and the client has nothing to do with it (probably the case). I will try a packet analysis of traffic on the server while seeking through the web client, iOS clients, and any other streaming clients.
thank you.
I already solved the problem by uncommenting the hdmi_drive=2 line.
now that we have an official ubuntu release of the client and the the source files to compile I wonder if is it possible to use these source files to compile binaries for raspberry…
I have updated my fork with what I consider to be a very stable version at https://github.com/dalehamel/pyplex.
I will be making an installer for this soon, so that you can simply load it onto an SD card like you do with Raspbmc.
For now, if anyone wants to build this, they can use the ebuild with dependencies from my plex overlay https://github.com/dalehamel/PlexOverlay
CALLING ALL RASPBIAN USERS:
If you have pyplex building and running, what are the package dependencies?
Are you running it in X11 or DirectFB? What packages are you using? I can try making a .deb file so that people can install it more easily. I find the current debian instructions quick incomplete.
-Dale
Your fork look great! I'll get back at pyplex within a few weeks and then i will try to implement some of your features (like myplex, the new listeners and way you handle arguments) so we can move towards a merge.
I have no idea what to answer here, I can't remember installing x11 and or DirectFB. As far as i know I followed some instructions from the version i forked and moved on forward with that. Could you explain what a .deb file means? I have never made one, might want to look into it if it makes things work better.
I think its a good idea to label your version as stable and mine as "in development", what do you think?
I .deb file is a debian package. For instance, any time you use "apt-get" it installs a deb file.
What is really good about .deb files is that they contain information about their dependencies, so that those can be automatically installed to.
So, if you made a .deb file for pyplex that had all of the dependency information, all the user would have to do is type "apt-get install pyplex", and it would go and get everything needed to run pyplex.
As for labeling the two versions, yeah that seems like I good idea. I can pull your branch into mine as "development", and you can pull mine into your as "stable". Since I am a contributor on your repo, I could do both of these things if you like.
Sounds like a good idea you can go ahead and do it! Ah, now I understand the .deb file. So in short a text file containing instructions about all it needs to install+ the package it self?
This was my original approach to getting a client on the RPi. I went for option 2 - smashing all the stuff that enables XBMC to run on the Pi into the repo for the Plex client. I only got as far as you - it compiles, but Segfaults. You can see a brief log of my attempts starting at page 3 of this topic, before I ended up putting together a proof of concept for pyplex which then took off. My main problem was the new Audioengine in XBMC, which is totally different and is 22000(!) lines of code. I couldn't face that alone! I do have a repository of this at https://github.com/area/plex-linux , which probably won't prove helpful; from looking at your work at pyplex, I'm pretty sure your chops are significantly more qualified than my own!
I don't think a deb file is a text file: is more like an 'exe' file for windows. it contains the binaries to install the software and information about dependencies that can be satisfied by downloading trough repositories.
Here’s something to check out guys, Tobias has already created an expirimental Plex Home Theater for Ubuntu package (based off Frodo RC3), and it looks like linux is finally going to start being a priority since with the latest update the source compiles on Linux! 
http://forums.plexapp.com/index.php/topic/56099-experimental-ubuntu-package-for-plexht/
http://forums.plexapp.com/index.php/topic/56107-plexht-09971/
Additionally, as I mentioned at the bottom of this post, it looks as though Elan has several Raspberry Pis himself, so this is likely to become an official Plex priority:
http://forums.plexapp.com/index.php/topic/55803-raspberry-pi-plex-home-theater/
I have got it running on Gentoo without issues, but the raspberry pi is a totally different kettle of fish. There are two main challenges presented by the RPi
[list]
[*]No X11 Accelerated graphics driver
[*]Arm architecture
[/list]
Much of the build process does not properly take arm into account, and depends on X11 for plex right now. The solution to the X11 problem is to use DirectFB to reduce overhead, and to use a GPU Accelerated player (like OMXPlayer) for playback. As for the ARM build problems, that's just going to take a lot of blood, sweat, and coffee.
[*]No X11 Accelerated graphics driver
[Accelerated X driver testing](http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=28294)
[*]Arm architecture
This is probably hard but since PHT is based on Frodo that is availble for the RPI both directly from XBMC or from Openelec i guess it is fairly easy for someone who knows what they are doing to port it. Tobias wrote that he will probably have a look at it ass soon as he has another free sunday.
I actually don't think that we really want an accelerated X11 driver in any case, since XBMC manages to work without one using DirectFB.
As for the arm stuff, the hard part about smashing it in will be how divergent the two projects are.
I wrote http://github.com/pearswj/plexweb as a very simple web GUI to control the playback of media from my laptop. It's not hugely well written but I've been happily using it for a while. I've been planning on revisiting it since discovering the py-plex api. This functionality should probably be part of Plex/Web though.
Taking a look at the @plexapp twitter account suggests official Raspberry Pi support with PHT! (https://twitter.com/plexapp/status/288399464840982528) - I seems there is no need to port the "old" Plex Media Center!
This would be a great solution which (hopefully) even gets AirPlay support (because XBMC has some AirPlay built-in).
But pyPlex and Airplayer are still great solutions and should be seen as a thin alternative to a full blown PHT.
Hello again!
As I’ve said before I’m running Arch Linux and therefore I had to install a lot of packages that are already present in Debian systems.
I just cloned the megawubs git and managed to get the application launching on my Raspberry Pi, but there seems to be an issue.
Plex on my iPad successfully finds the media player and allows me to start playback, but I get no output on my tv, I just see the tty with its normal text.
Am I doing something wrong here, and why does it say that playback started but doesn’t show anything?
Thanks in advance, it would be really fun to get this working!
Check the output of omxplayer.log. It probably hasn't been built correctly. Also, verify you *have* omxplayer
I have had my Pi for a few months now and have got raspbmc and have installed Raspbian wheezy without any real trouble. I found this thread and being i love plex i had to try it.
I assumed that the bare bone wheezy build that is on Raspberry Pi’s site would work fine and i followed the steps on the Github page. Unfortunately i can’t seem to get my Ipad to see it. I have multiple plex clients on the network and they all work just fine.
I start the program like instructed in the GUI with a terminal window and it just goes back to a prompt.
Advise would be great, and all the work you guys are doing is greatly appreciated.
You have to have OMXPlayer and avahi (as well as a few other dependencies) installed. Which github page are you using? If you are using mine (https://github.com/dalehamel/pyplex) then there should be a log at /var/log/pyplex.log
The debian builds for omxplayer are at http://omxplayer.sconde.net/
-Dale
Also, I am starting work on porting plex HT to RPi. Sit tight : )
