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 ... 58 59 [60] 61 62 ... 84
Users / WebDT 366LX PadOrbiter Image
« on: November 06, 2010, 02:43:40 am »
For those who own the WebDT 366LX Model and are unable to use the webpad-gamma installer you can try this image:

This is the padorbiter installer that Thom created for the 366GX but modified with an LX sized image.  Extract the image file from the archive and use dd to put the image on a USB drive.  Put the USB drive into the WebDT 366LX and turn it on.  60 seconds later it will overwrite the WebDT's flash memory hard drive.

Orbiter is updated to svn 23395.

A squeezeslave player is installed and accessible by pointing to 00:00:00:xx:xx:xx where xx:xx:xx are the last three parts of the wireless card's MAC address.  Ex. if your WebDT's MAC address is: aa:bb:cc:dd:ee:ff then the squeezeslave player is at: 00:00:00:dd:ee:ff

WEP and WPA both working.

Known Issues:
  • After entering the network configuration the webpad isn't joining the selected network.  Solution: Power down by holding the power button > 5s and power back on to join the network you configured.
  • There are some small lines visible along the top of the lcd screen in X windows.  No solution for this and they are hardly noticeable, I'm open for suggestions.

I will try to help and answer any questions that come up.

If you find this useful then please thank Thom for creating the padorbiter in the first place.


Developers / Re: N900 PR1.3
« on: November 04, 2010, 05:50:19 pm »
I'll check this out on the weekend.


I can confirm this.


Users / Re: DivX problem
« on: November 04, 2010, 05:31:09 pm »
could this be a solution?

My experience, and others in many, many forums, is that these settings remove the majority of the tearing but do not completely fix the problem.  It fixes things enough that video becomes watchable and some claim to no longer see the tearing but it is still there and really annoying with a discerning eye.  This is covered in hundreds of forum topics on dozens and dozens of forums and everyone reports differing degrees of success.


Installation issues / Re: MPlayer and m2ts problems
« on: November 04, 2010, 05:26:18 pm »
I don't completely disagree with you Zaerc, but there are *some* cases where mplayer achieves things that (I havn't figured a way..) can not be achieved with xine.  I am specifically referring to playing of files encoded with AAC audio when connected via S/PDIF.  With mplayer I can easily on-the-fly re-encode to ac3 to get proper 5.1 sound.  With xine the files either down-mix to stereo or only play the R/L tracks and drop the remaining C/RL/RR/Sub.  This is only a problem with >2 channel AAC encoded audio when using S/PDIF.


Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: November 04, 2010, 05:18:07 pm »
I'll have to find somewhere to upload it to.



Developers / Re: Touch Orbiter and Web Orbiter speed improvements
« on: October 23, 2010, 06:38:40 am »
Excellent idea!  I'll try to test this against the linux based touch orbiter(s) as well.  The n800/810/900 could probably benefit from this.


Installation issues / Re: MPlayer and m2ts problems
« on: October 23, 2010, 12:31:45 am »
I belive there is a bug in mplayer_player (I think that's where it is) that doesn't send the 'Media finished' command to dce_router when the media finishes playing.


Users / Re: DivX problem
« on: October 23, 2010, 12:29:30 am »
If you set 'vdpau' in the webadmin then xine and mplayer will use vdpau acceleration if it exists.  Xine (in lmce) will automatically fall back to opengl playback for media that vdpau does not accelerate.  I think that mplayer is setup to do the same but I don't recall. 

If you search around on the internet there is generally no 'cure' for video playback tearing in linux.  There are many things that can be done to somewhat mitigate or reduce the symptoms but there are fundamental changes required to how the linux kernel and opengl and compositing managers interact and sync to vertical.  The problems are well documented around the net and it seems they can only be solved by changes made from the kernel down to x drivers and compositing managers...

Until then you can reduce the amount of tearing that you see on your screen by not using alpha blending (where v-sync issues are most noticeable) and by using the lowest level of 'de-interlacing' you can live with in your webadmin settings.  The de-interlacing setting can have a significant effect on the amount of tearing you see.

Some TVs also have 'tearing' as the source material and actual refresh rate of the pixels is not in lock step.  My plasma has an 85Hz refresh rate in it's hardware but it is fed with a 60Hz video signal.  I actually experience a very little bit of tearing on my tv with other types of media as well (BR, DVD, PS3 games can be bad) during fast motion scenes.


Developers / Re: TouchOrbiter - Auto-configuring new orbiter
« on: October 23, 2010, 12:07:35 am »
Anyone interested in touch orbiter auto-configuration should really follow along with  That's the ticket documenting the development/changes Merkur and I are working to implement which makes it relatively quick and painless to incorporate this feature.

I've been following along, great stuff so far.  I plan to try it.  I have heard from others working on a touch orbiter and they will likely try to use this as well.  Thank you so much for all the work you and Merkur have been doing.

To help us all re-orientate ourselves and get this thread back on-track again... could you summarise where your at or what your planning for Auto configuring new Touch Orbiters? As step by step description what should happen would be useful. This will also help anyone developing a Touch Orbiter variant to get their head around what needs to be added (if anything) to their Apps.

Well my initial thoughts of the process went a little like this:

1) check if device exists/is defined in database, based on say a .conf file (like maemo) or a MAC (like padorbiter or windows orbiter)
2) if device exists in database then connect to it's defined port #, if it fails proceed to 3) else proceed to 9)
3) detect the native display resolution of the device
4) ask the user if this is a new orbiter and therefor if a new device should be created (a la padorbiter)
5) create the new device -> proxy_orbiter, perhaps an orbiter to go with it if creating proxy_orbiter doesn't do this
6) query the user and set orbiter template attributes for: Language, Room, User, available Skin, etc...
7) query user for display resolutions that are <= native resolution of device and set template attributes
8) regenerate
9) use...   if selected resolution == native resolution would trigger a fullscreen display (no window dressing)

and then 10) should be 'profit' or something like that but I havn't figured out the origin of this little inside joke yet to know why....  <:-P

I may have missed something there but that was the general idea of it.  I'm hoping for something fairly generic that runs (or at least compiles) easily on multiple systems: mini2440, maemo(s), debian.  The functionality exists in Orbiter and I wanted to mimic the behaviour/code in Orbiter that padorbiter uses to auto-configure.  My issue was, more or less, with the backend code required to implement the auto-creation of proxy_orbiter as I havn't really had a chance to explore the dce commands that Orbiter uses to do this.  los93sol seems to have documented these commands somewhat in the code referenced in the ticket above (thanks!).  I'm am really busy right now but I am going to try to use them.

The maemo build env isn't too difficult to setup. I don't know if you are happier on a windows or linux box. There is a VM image available ...
Then from the scratchbox env you can either symlink to your existing LinuxMCE src or do an svn co from within. I have a script that builds the other necessary libs for the orbiter, I'll attach it here once I get home.
p.s. Oops, just noticed this is under Touch Orbiter - if this discussion continues maybe we should break it out under a PadOrbiter topic?

Thanks coley.  Yes we should start a new thread for this.  I'll try to set up a build-env and see what happens.  I'd love to access any scripts/changes you already have.  You could PM or e-mail me what you have (phenigma at hotmail dot you know) and I'll post a new thread with my progress.


Hi J.,
yes, the devices templates were exported, manufacturer pointed as: "FK_Manufacturer";s:4:"1057", model indicated correctly: "Description";s:14:"SoundBridge IR".
I submitted both templates and am waiting for an answer if they were accepted or not.
Let's wait to see how it goes....

Your templates will not be accepted if they are submitted in this format.  This was a mechanism that was attempted when sqlCVS was less reliable and for people testing devicetemplates across installs before submitting them properly.  If you want your templates accepted into LMCE then you will have to submit them using sqlCVS, I think the wiki has a howto you can follow.

Thx again.

P.S. It would be nice to be able to set the effect (and if effect is to be used) for the given source, like files defined as movies, selecting DTS, files defined as audio and jazz, selecting Jazz Club, audio and rock, selecting Rock Concert, TV selecting Theater..
Most of the middle to to range audio/video receivers and amplifiers has multiple effect modes.
I could not find how to set it, so i do it with the amp remote.. selecting the effect mode.

Search around, there are a few threads that discuss this topic and I know the IR codes are accounted and I think the fields are provided and available in the database but I don't think the relevant code has not been created to enable these settings to apply automatically during use.


Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: October 22, 2010, 10:41:24 pm »
I ran the bad unit through a bunch of tests and it ended up failing a MemTest86+.  It has been put in the mail to be returned and he says he'll ship me a new one.  I will admit that he hasn't been the most prompt of individuals to respond but he has been dealing with me and my problem.

I'm incredibly happy with these LX units vs my old GX.  They are MUCH faster.  With the increased processing capability and the 802.11g they easily run Orbiter and stream from .flac or .mp3 files to squeezeslave wonderfully.

It was not a simple 'plug n play' to get this up and running with the padorbiter distro.  The drive size was the biggest issue to overcome.  I tried resizing the image multiple times and never got the partition defined quite right.  Had to do a fresh debian install to get a proper partition defined and imaged.  Then the video was a bit of a pain as the vesa framebuffer causes white pulsing on the LX's screen.  The framebuffer driver has to be set at boot and it works great in the console.  Once booted the LX framebuffer doesn't wake-up from suspend properly under X, not sure why but it's not pretty, so I switched to the geode driver in X and it resumes just fine.  The IPW2200 firmware had to be copied onto the webdt before the wireless would operate.  The wireless card doesn't seem to wake up as quickly as the cisco card in the GX (at least that's the best I've come up with) and consequently Orbiter takes a bit before timing out and restarting.  As a simple solution I kill Orbiter on resume, which restarts Orbiter in a couple seconds rather than 10 or 15.  USB2.0 on the LX vs USB1.1 on the GX makes installing an image 5x faster.  Took me a little over a week to figure out what to do and learn what I needed to do to make it happen.

If there is enough interest I will post an image of what I have, but that should be reserved for another thread.


Users / Re: Problems with Denon 2310 - Video source drops
« on: October 22, 2010, 09:53:09 pm »
phenigma,  thanks for the reply.... I am using a zotac ion n330 board.

Welcome to the Forum and thanks back.

@phenigma My core uses the AN-M2HD with optical out (for surround sound) to the Denon and HDMI out to the TV. Don't think HDMI sound supports surround sound. I have also used the Acer Revo with the same setup (optical plus hdmi).

HDMI does support surround sound, it's part of the appeal of HDMI, only 1 cable is required for all video and audio.  The newer HDMI standard (1.4 if I remember correctly) actually incorporates a tcp/ip communication mechanism so that each device can share a network connection as well.  I have yet to acquire an HDMI receiver to confirm that LMCE supports surround sound over HDMI... but I would assume that it would.  Thanks for the info on the motherboard.


Users / Re: Screen blanking during playback
« on: October 22, 2010, 09:43:11 pm »
Your welcome. :)


Which installation media did you use?  The Beta2 DVD is quite old and you should use a recent snapshot from or do a net install following as a guide.


Pages: 1 ... 58 59 [60] 61 62 ... 84