Hiya,

I've been testing this.

I have a samsung note.

I went through setup ok and then encoutered a few problems.

Firstly, the room is not being persisted, I had to set that in the admin site.   
Secondly, the screen seems to go black quite regularly, needing a router reload before I can launch the orbiter and see the screen again (I can't divine the pattern, but is happens quite quickly with me)
With the black screen, the menu is still active, and the little ticker icon appears when I touch, so the screen is there, just being rendered blank.
The steps I went though are to register, set the room, set the screen resolution, set the UI to normal horizontal 16:9 (I tried 3:4 too), set the skin to basic, quick reload the router.
The screen will then display on the touch orbiter, but there is no room/ user selector visible (the bar is at the bottom, just no selector on it...) and when I click a ui element, say VIdeo, the screen goes black.

There's no way to select the correct resolution for the device (1200x800) in the orbiters settings, instead you have to use the admin.

The black screen thing is getting me, as I can't use it while its doing that.

This looks to be cool though, enough until qOrbiter is stable, and enough to let me hammer on with my deployment.

Cheers,

David.

Donation sent :-)

btw, the paypal page is in german, even though I view it from the UK.  I wonder if there is a way to make it more ... international somehow?  Show english for english speaking peeps.

I can see that being a little off putting.

ah yes, I remember now.  Its not quite finished.  I hadn't decided whether to stick with the compile against database approach used in the normal C++ devices (so you have constants matched with IDs in your source code generated from the database), or whether to load them at runtime.
Anyway, its not in a slick, finished state.

Hey, not been around for ages.

There's a probably working Java DCE implementation here

https://github.com/dawsonsystems/JavaDCE

And a half built Java DCE device here  -> https://github.com/dawsonsystems/linuxmceagent

I'm not quite in a position to pick this up, but if anyone is interested, it'd be a good motivation to get myself set up again. My linux mce project died a death when my little girl started walking.  Now she's in nursery...  well, the possibilities open up a little again.

Howdy.

I bought a remote from maplin the other day and wasn't watching too closely. So I ended up with a maplin branded 'Vista MCE Remote' that is actually an Ortek VRC-1100 in drag.
Rather than return it, I thought I'd try to get the thing working with LMCE.

Following instructions found here --> http://wiki.xbmc.org/index.php?title=HOW-TO:Configure_VRC-1100_remote_for_Ubuntu
I've got commands coming through in irw from the remote nicely, although the update was a little invasive (adding udev rules, installing inputlirc)

However, actually getting the wee beastie to control the orbiter on the core is another matter.  I've tried various things, but nothing seems to have any particular effect, so I'm at a loss where to properly start..

Also, a 'USB Game Pad Remote' is being continually installed. and re-installed with a few minutes if I remove it, anything to do with this?

David

Also, because I like to make people's lives hard, I have some quick questions if you dont mind.

*How do you view the path of cross compiling qt (necessitas) vs flushing out the JavaDCE?
*Do you envision a method the two apps could talk to each other. Is there some type of interface i would need to provide on the Qt side?

The main thrust of the questions is I like to have a big picture view of things in my head. With desktop variants, i have a fairly defined idea of the involved parts. Android is still something thats in flux from that perspective and im just wondering if its time to start learning some java on my end.

Thanks for all your hard work on this and qOrbiter, its really appreciated.
-golgoj4

Howdy.  Congrats on the job!!

Not sure what you mean by flushing out?

As for comms.  dunno really. maybe via DCE?   It might be cool to have that anyway so that qorbiter can be embedded/ controller in a media director.  might be a similar interface.  Not sure I'm getting where you're going .... ;-)

I wrote this to run on desktop ubuntu.  I wasn't really thinking much further along than that, although given the correct dll for libvlc, it'd work on windows too with no modification.
It was me playing at an implementation for the 'desktop agent' that thshak has mentioned that we looked at a while ago.   

Once this is done though, and it media wise it can be controlled via the orbiters, and you add qorbiter into the bundle, it does seem a pretty good addition.

David

Java DCE Implementation.

https://github.com/dawsonsystems/JavaDCE

Functional (and suprisingly slim!), but very hardcoded on event/ command ids.  Not something I want to keep and as soon as I can, I'll break that to make the lib agnostic to the ids that are present in the current system

This is inspired by a bit of code that someone at pluto wrote and then documented to an extent.  I forget the exact details, but I rewrote the lot in late 2010/ 2011 before life sent me south for a year.


Simple device that will boot and then sit in the taskbar doing nothing.

https://github.com/dawsonsystems/linuxmceagent

• Presents a UPnP interface to act as a Media Renderer, built using the Cling library
• Presents a DCE interface to play media.
• Uses libvlc (via a snazzy java wrapper) to do fullscreen video playback
• Has a simple java based image viewer for static pictures, so can display those to

The UPnp implementation is full of holes.  The DCE implementation only has one function, to play media.
The device template I'm going for implements the "Media Player Commands" and "Smart Media Player" command groups. Thats the idea anyway.
Currently it only responds to 'Play media' (37) when you pass it a MediaURL.

This is all dreadfully hard coded and semi developed... so please don't think it will work (esp the libvlc compilation, as i did it myself and its not very likely to function anywhere else than ubuntu 64 bit)

Anywho.  for those who are interested, I will continue development on my github account.

Good good.
I'll clean it up and put it on github when I get a moment, sometime in the next few days.

Oh, I'd be happy to share or contribute that if you think it may be useful.

I'm a java dev, so the language choice came naturally, C++ still isn't really comfortable for me.   

That said, I'm not offended if not, I know this is C++ project.. 

:-)

Might it not be more appropriate to have a second, media playing device that happens to be bundled with many (/ most) qorbiter installs?

That way you aren't giving qorbiter to much to do, and could have completely seperate implementations for android, desktop etc.

I had fun a wee or so ago prototyping a java based app using libvlc that could do that job (its presenting UPnP Media Renderer and basic DCE interfaces at the mo, and plays any media I have when passed an MRL, which is all of it as its on a UPnP accessible NAS).

Kind of clunky, but it did highlight that a simple media playing device doesn't appear to be that involved compared to the likes of qorbiter, as it just isn't doing a lot in comparison.

Dunno, am I talking crap?

oooh.  I understand now.

Right, well, that sounds very nice indeed.

Heh, wasn't clear.

Basically, one thing I'd like to be able to do cleanly is to watch CCTV and videos on my handset controlled via the orbiter interface. 

This seems to be a similar idea to the workstation agent (although it would obviously need a significantly different set of tech, probably for each device type)

David.

Hello. posting to old thread for fun and profit.

Did this go anywhere?

I like the idea as I understand it.

It'd be very cool to take that idea and apply it to the mobile devices qorbiter is being ported too as well desktops.

Eg, on an android handset, have a video/ CCTV be able to be accessed/ controlled via the qorbiter interface.

Hi,

I would put the device on the core if it does not really need to be on the MD.
I would always try to expose the audio as a stream, this allows us to seamlessly send audio to both squeezeboxes and MDs.
There is a spotify library iirc? Is that what you intend to use. Either way, it should be possible to implement several spotify clients within the same Spotify device, right? So it might not be necessary with several devices.

If possible, I'd use xine to play the stream on MDs, and then there be no reason for the spotify device to be on the MD itself. All of this is depending upon a spotify device that allows us to access the audio stream in some way, ofcourse.

Don't know the exact process of adding screens, but they need to be added in the Screen table in the database. I think this is used, at least as reference, in qOrbiter too.
After adding an entry in the table, and committing it to sqlCVS, you go ahead create a new Screen_xx.xml file in qOrbiter (from how I understand qOrbiter).

br,
sambuca

Yes, I'm planning to use libspotify.

Apparently libspotify delivers audio as PCM data.  I suppose that this will need to be converted to proper digital in some way and wrapped in some streaming protocol to make it network accessible (any idea?). 
hmm, sounds a fair sized task. Thats definitely my aim though, anything else seems weak.

On using xine.  I suppose that there would need to be some scenario set up that would startup the spotify stream and direct xine to play from that.  So the constraint on the network format is really what xine can consume (and what the squeezeboxes can support, and my ability to convert PCM data to a network stream, blah).
This is something I'm interested in, how would the architecture of that hang together?   I mean, on the orbiter I'd press a button that will trigger a scenario (I imagine) that will send a command to both the spotify device and a xine device on a particular MD.  Right?

I like the multiple accounts within a single device.  I'll work towards that I think.

If I wanted to direct the audio across multiple media directors/ zones, how would the scenarios work for that?

Sorry for mixing a few idiot questions in.  I'm still full of holes when it comes to how bits of the system work (learning fast though :-))

David.

Howdy.

So, following on from my foray into qOrbiter, I'd like to have a crack at a DCE device proper.   As I've wittered on at length about on the dev IRC, I'd like to make a device that can play spotify stream music and control it via qorbiter.

Before embarking on a coding adventure (some time later this month or likely in March), I'm gathering some information on what approaches to take. So, a few questions if anyone has an idea.

Spotify is based on user accounts.  I'd like to be able to have multiple devices to play differnt music in different areas, but that requires more than one spotify account. We have 2 accounrs, one for me and one for my wife.  So that fits into a device per user model, but I'm not sure if thats the best model.  You can't have a single user account in use by more than 1 device at a time.

My questions :-

• Where should this device live (core, media director), and should I have it being a device per user account?
  
• Might there be a way to have the device on the core, and expose the audio as a network stream?  If this is possible, it'd be cool, as then non media directors could tap into the stream, and stream could be played over multiple zones from the same device.
• Is there a preferred mechanism to output sound (eg, alsa, phonon etc)?  (although some networked solution does seem preferable...)
  
• This is going to need a UI in the orbiter.  I've no real interest in adding to the current orbiter, only qorbiter.  Given that, whats the outline of the process to add a totally new set of screens? small single numbers thereof. (feel free to RTFM me on this if there's an entry somewhere I haven't found yet)

So, any ideas welcome.

David.