Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - phenigma

Pages: 1 ... 55 56 [57] 58 59 ... 80
841
Users / Re: What devices are you running Web orbiter 2.0 on?
« on: October 12, 2010, 10:00:34 pm »
You have edited the template for your amp to achieve this right? How do I go about changing this for the web orbiter itself, so that it works for all MDs (I don't have any amps)? Am I supposed to be looking in /var/www/LinuxMCE-admin/weborbiter?

This can only be changed in DeviceTemplates for individual AV devices.  There is no possible change to weborbiter to implement this.  Once implemented in the DeviceTemplate it does not matter what orbiter you use they will all function the same... for that device.  I don't know if there is a way to implement this functionality if you are not using an external AV device (like an amp), but orbiter would still not be the correct location to do it.

J.

842
I'm trying to export two templates i've created, but no luck.
The export shows errors and i cant find any file. http://www.pastebin.org/115322 shows it.
Question: how to export the templates and where are they stored, so i can backup them and submit to svn?
TIA


The script in the lmce distro does not function properly.  You may have better luck with one I posted earlier in this thread but I do not recall the state I left it in at this exact moment.  I will look at it again but don't have the time right this instant.

J.

843
Developers / TouchOrbiter - Auto-configuring new orbiter
« on: October 12, 2010, 03:14:59 pm »
I've been learning some c++ and I've spent the weekend hacking away playing with online sdl tutorials and the touch_orbiter_1.0 in svn and I have managed to create a linux touch orbiter that is working well for me using sdl.  Great learning experience.

What I would like to do now is add configuration setup like the padorbiter has.  From the I've tracked down it looks like there is a 'createorbiter' DCE command that padorbiter uses to create a new orbiter device on the core.

1) I'm assuming a new DCE command will be necessary to create the proxy_orbiter (and associated orbiter). 
2) It seems to me that if a new DCE command is required to create the proxy_orbiter then any device using touch_orbiter could utilize the same command for the proxy_orbiter creation and setup.  Anyone care to comment on whether I am right or wrong here?

Has anyone looked at this yet or begun any work towards this in any of the touch orbiter platforms?

J.

844
Developers / Re: Linux TouchOrbiter
« on: October 12, 2010, 03:11:35 pm »
Hmm, ooops.  Little tired when I posted that.  I'll repost unless there's a way to move it.  Thanks Hari.

J.

845
Developers / Linux TouchOrbiter
« on: October 12, 2010, 06:46:08 am »
I've been learning some c++ and I've spent the weekend hacking away playing with online sdl tutorials and the touch_orbiter_1.0 in svn and I have managed to create a touch orbiter that is working well for me using sdl.

What I would like to do now is add configuration setup like the padorbiter has.  Based on what I've tracked down it looks like there is a 'createorbiter' DCE command that padorbiter uses to create the device on the core.

1) I'm assuming a new DCE command is necessary to create the proxy_orbiter (and associated orbiter) instead...  at least that's what I think from what I see.  
2) It seems to me that if a new DCE command is required to create the proxy_orbiter then any device using touch_orbiter could utilize the same command for the proxy_orbiter creation and setup.  Anyone care to comment on whether I am right or wrong here?

Has anyone looked at this yet or begun any work towards this in any of the touch orbiter platforms?

J.

846
That's likely the most recent I have.  I had done more work and fixed a few more things and cleaned up the code a bunch as I learned more but I havn't had a chance to see if I've got anything newer backed up anywhere.  I'll have to look.

The actual 'insert' code may be commented out in the posted version of the script to avoid accidentally screwing up a database, you may have to uncomment it at the end of the .php file to get it to actually insert records into your database.  When you are viewing the insert statements it will show negative numbers as place holders for new Primary Key IDs that will be created when the actual insert statements are run.

J.

847
That's terrific.  Great work esev!  And thanks Thom as well (for all you do).

J.

848
I had done more work on it and had it working quite well and was moving my device templates around with ease from install to install.  Then I forgot to back it up one day and lost some of my recent work.  I'll have to dig it out again and see what state it's in.

J.

849
This has been a problem with the Titanium Skin since it was first rolled out and made the default skin.  The creator has not yet fixed it.  You can switch to the 'Basic' skin and the buttons are correct.

I'll give this a try too.  That way I have a baseline of the intended way the orbiter screens are supposed to work.

I'm kind of a noob with LinuxMCE at this point, but am very impressed with it so far.  I've done linux development in the past and am happy to contribute back to this project where ever it makes sense.

Welcome!

I checked svn after posting and it looks like there is a ticket associated with this: http://svn.linuxmce.org/trac.cgi/ticket/306.

J.


850
The other thing I noticed was the track/channel next and track/channel previous buttons were using the same icon (rather than opposite pointing arrows).  I figured this was a bug and wasn't intended.

This has been a problem with the Titanium Skin since it was first rolled out and made the default skin.  The creator has not yet fixed it.  You can switch to the 'Basic' skin and the buttons are correct.

J.

851
Users / Re: vbox + LinuxMCE 0810-alpha + ui2 = working
« on: October 08, 2010, 09:00:34 pm »
Don't you need to install "guest additions" on the MD for the graphics to work properly?

I think you also have to enable 'hardware video acceleration' in vbox for that machine.

J.

852
Installation issues / Re: First diskless MD boot
« on: October 07, 2010, 04:52:17 pm »
Ok so I’ve tried the network boot on my brother’s Gateway Netbook (ZA8) and SUCCESS!! A couple of issues are that when I use the touchpad LinuxMCE thinks i'm also pressing the number 1 button and MythTV appears for a second then crashes, but otherwise it generally works.

In the orbiter settings of webadmin under advanced there is a setting for 'ignore first press' or 'ignore first event' or something similar and I believe that may alleviate the '1' button issue...  Been a while, and I don't have a touchscreen MD, so I'm not certain if this will fix your issue. 

J.

853
Developers / Re: Clutter Exercise: Media List
« on: October 07, 2010, 12:40:23 am »
Unfortunately not I.  In the time I do have right now I am re-learning c++ and looking at the linux TouchOrbiter among other things...  trying to get my head re-wrapped around pointers (and pointers to pointers).

J.

854
Ah, I see.  I am in the same boat here and perform manual setups of my inputs because there is no 'standard' for cable broadcasters and no easy/legal way to receive satellite directly, only through settop boxes and capture cards.  It seems to me that the basic mythtv control information should still be setup for MDs even if the capture cards/input devices need manual setup...  I havn't tried mythtv on an MD since alpha.

J.

855
Users / Re: What devices are you running Web orbiter 2.0 on?
« on: October 06, 2010, 07:20:41 pm »
Increasing the image quality does increase the amount of data that is transferred to the web/touch orbiter and responsiveness can be affected.  The touch orbiter responds as quickly as the real orbiter on my webdt (800x600) at Image Quality of 70 and is just a little slower on screen redraws at quality 100.  I imagine that weborbiter will see similar changes in responsiveness.

J.

Pages: 1 ... 55 56 [57] 58 59 ... 80