On 02/06/2011 03:32 PM, dumbiggie wrote: > > > --- On Sun, 2/6/11, stuart<[email protected]> wrote: > >> Did you find a solution to your situation? > > Nah, I'm just dealing with it as-is. I set up a parallel Squeezebox > Server on the same LAN as my MVPMC. > > My biggest problem is that any time I turn the MVPMC off, or use it to > stream video, the music client can't re-establish a full playing connection > to the Squeezebox Server unless I reset the player from the Server web page.
That's odd. I don't remember having that problem. Maybe I should fire up my system again. There has always been a problem with the Happauge MediaMVP hardware (or I probably should say the IBM processor chip). I could never figure out how to start music w/o either cutting off the first few seconds or have the first few seconds repeat. Consecutive tracks play fine. It's just from a STOP when the problem shows up. Is that what you are hearing? >> As for the port number, the slimserver, or as it is now >> known SqueezeCenter, uses specific ports (and I think >> different ones) for audio and control. I can only >> assume you are using some sort of port forwarding > > No, Squeezebox Server (Logitech's latest name ;) lets you set up alternate > ports for establishing the initial player connection and even add plaintext > password protection. I expose my primary Server to the public Internet so I > change all those attributes using the Server web I/F. I also have a > Squeezebox Radio and that interface supports specification of the alternate > port and password, but apparently the MVPMC client doesn't. That's the main > reason I added a parallel local Server. You are starting to see the problems (actually differences) between different generations of SqueezeBoxes. The mvpmc / mclient is setup to emulate the 1st generation SqueezeBox plus some extra album cover stuff. I would have to do some research, but I think some of the things you are looking for come with a price. You might have to emulate a newer generation SqueezeBox to get some of these features like changing ports or password protection. But newer SqueezeBoxes use different Ethernet protocols. So you might have to start over and write the mvpmc / mclient Ethernet methods from scratch. >> look up what's what. If you look in the code it should >> be fairly obvious where the port values are set up. If >> you go to the trouble of creating enough code to allow for >> defaulting to the current values when none are specified I >> could submit your code to the git repository. > > Ah... that's an idea. I hadn't planned to root around through the MVPMC > code but there's no reason I couldn't. I haven't pulled the GIT repositories lately. But at one time the project was very very automated (i.e. just download and make). I see some recent traffic about compiler problems. Hopefully these are not serious. Memory is tight on the MediaMVP last I checked. I would entertain removing the mclient VFDisplay routines if necessary. I think I might be the only one using them. > Thanks for the tips! > > Ron > > > > > > ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
