Truly independent multi-zone

**justchat_1** · 11-06-2010, 01:00 PM

Originally Posted by Punky

i guess i don't actually know, because most media player (WMP mostly) does not play more than 1 video at a time. Most of the forum are probably using atom 330 with a few having the ION in it. Assuming i'm right with my statistic, i'd say most atom processors would have problem keeping up with running 3 avi video (center console + 2 rear screens).

I doubt this is any problem with any desktop running i7 + GTX460 or something. I see this is a great piece of software for future carpc, but with current carpc spec it seems rather tough to run smoothly.

WMP is limited to a single instance.... thats mainly an issue for older front ends. Were only limited by the capabilities of the hardware. Anything with a modern graphics card will offload all of the decoding (transcoding is for htpcs) to the GPU so the CPU really sees very little hit. I can load up 5 720p videos on my 5yo laptop and they play with about 15% CPU usage on a core2.... Even on an atom 330 to get 3 zones they would need an extra graphics card which would take care of the decoding.

Were not targeting the minority here.... omap processors for at least 5 years now have been capable of video decoding by GPU. Any real graphics chipset since about 2002 can do it (except for HD which is more of 06-07 era cards). Developing based on the 5-10+year old technology of a few forum members would really not make sense. The goal here is to innovate...

Originally Posted by jmullan99

Another question: can zone 1 force-feed audio to other zones?

Not a requirement for me, but as I build up multi-zone, and start with additional audio zones, they will have no screen for a short bit. So wondered if I can pick something for them.

If not, no worries.

Cheers,
John

Yup

Originally Posted by jmullan99

In my future scenario (building zone 2 in the rear seats), usually a keyboard won't be present, but the user could plug in a usb keyboard on occassion. Will OM be able to distinguish that after many plug / unplug events that this keyboard belongs to zone 2?

John

plug in the keyboard...go to settings and map that keyboard to zone 2...from then on anytime its plugged in OM automatically maps it to zone 2.

**RipplingHurst** · 11-06-2010, 01:01 PM

Oh yeah, provided it has enough video out ports.

Now that you mention it, the GTX460 is for sale on newegg today for 129.00 (with $20 reabate and -$15.00 EMCZZYR24 coupon)...The GTX460 is no.12 best video card here, very close to the top ones...mine is around 90 or so...LOL...very tempting, since the same card sells for at least $190 at Amazon).

**Punky** · 11-06-2010, 01:05 PM

definitely innovative!

**justchat_1** · 11-06-2010, 01:11 PM

Originally Posted by RipplingHurst

Oh yeah, provided it has enough video out ports.

Now that you mention it, the GTX460 is for sale on newegg today for 129.00 (with $20 reabate and -$15.00 EMCZZYR24 coupon)...The GTX460 is no.12 best video card here, very close to the top ones...mine is around 90 or so...LOL...very tempting, since the same card sells for at least $190 at Amazon).

tempting but serious overkill lol

Might as well go for 4 zones:
http://www.newegg.com/Product/Produc...82E16814139055

or 6:
http://www.newegg.com/Product/Produc...82E16814102888

or even 4 outputs-low profile:
http://www.newegg.com/Product/Produc...2E16814139054R

**tripzero** · 11-06-2010, 05:17 PM

Linux already has support for multiple pointer devices (xinput2/mpx), does OM take advantage of it or is this one of those windows only things?

http://ao2.it/en/blog/2010/01/19/poo...iple-mice-xorg
http://www.youtube.com/watch?v=FFp69hgNKac

**jmullan99** · 11-06-2010, 05:34 PM

Originally Posted by justchat_1

Originally Posted by jmullan99

Another question: can zone 1 force-feed audio to other zones?

Yup

Originally Posted by justchat_1

Originally Posted by jmullan99

...Will OM be able to distinguish that after many plug / unplug events that this keyboard belongs to zone 2?

plug in the keyboard...go to settings and map that keyboard to zone 2...from then on anytime its plugged in OM automatically maps it to zone 2.

A++

Originally Posted by punky

this is an awesome idea, but wouldn't your cpu take a massive hit if >2 screens are playing videos? Reminds me of the plane's entertainment back in the days when the system would be super slow and unusable.

I think dual core atom will handle two zones just fine. As justchat_1 mentioned here (and in response to one of my other posts) most GPUs will handle most of the decoding. I am currently (albeit slowly) upgrading my ICE to have two screens in the rear as a zone2 (then eventually split them into zone 2 and 3). Although my current single core atom may handle it, I will feel better upgrading it to Atom 330.

Cheers,
John

**RipplingHurst** · 11-06-2010, 08:17 PM

Originally Posted by justchat_1

tempting but serious overkill lol

Might as well go for 4 zones:
http://www.newegg.com/Product/Produc...82E16814139055

or 6:
http://www.newegg.com/Product/Produc...82E16814102888

or even 4 outputs-low profile:
http://www.newegg.com/Product/Produc...2E16814139054R

That is tempting as well. However, the Jaton reviews are not that great, lots of drivers issues I fear? (windows 7).

I would buy the AMD/ATI for my desktop. But I think a Zotac Mini-ITX plus with onboard nvidia card + PCIe graphic card (with a pci xpress riser to mount the card sideways (on a case like this) on a should be enough for 4 independent zones and potentially less issues?

I wouldn't like to be the first one to try this, so who else did something like it (in a car pc, not a desktop/test machine).

**justchat_1** · 11-06-2010, 08:27 PM

Originally Posted by tripzero

Linux already has support for multiple pointer devices (xinput2/mpx), does OM take advantage of it or is this one of those windows only things?

http://ao2.it/en/blog/2010/01/19/poo...iple-mice-xorg
http://www.youtube.com/watch?v=FFp69hgNKac

MPX builds on XInput2... it actually cripples it though. It allows you to manually create and/or map cursors to individual mice (no plug and play or easy GUI) but provides no way for an application to distinguish one pointer from another so its pretty much useless. We build off xinput2 as well but do it properly- multi-touch support, individual device mapping, automatic plug and play mapping and of course a nice friendly GUI to manage it all.

The only difference between windows and linux is some of the device names-but thats out of our control and due to different names in the windows/linux drivers. Otherwise identical support and functionality on both platforms (including multi-touch gestures).

**tripzero** · 11-06-2010, 11:51 PM

Originally Posted by justchat_1

MPX builds on XInput2... it actually cripples it though. It allows you to manually create and/or map cursors to individual mice (no plug and play or easy GUI) but provides no way for an application to distinguish one pointer from another so its pretty much useless. We build off xinput2 as well but do it properly- multi-touch support, individual device mapping, automatic plug and play mapping and of course a nice friendly GUI to manage it all.

The only difference between windows and linux is some of the device names-but thats out of our control and due to different names in the windows/linux drivers. Otherwise identical support and functionality on both platforms (including multi-touch gestures).

not sure i understand... why does an app need to distinguish between the two inputs? It's not like input from touchscreen2 will ever show up on touchscreen1's screen if calibrated correctly. I can see why other input devices like keyboards could be a problem though.

**justchat_1** · 11-07-2010, 12:09 AM

Originally Posted by tripzero

not sure i understand... why does an app need to distinguish between the two inputs? It's not like input from touchscreen2 will ever show up on touchscreen1's screen if calibrated correctly. I can see why other input devices like keyboards could be a problem though.

Not to get too technical but MPX assigns devices to virtual pointers (called master pointers) not to screens. Each pointer (cursor) needs to be moved to the indended screen it wants to be used on (and is in no way limited to it). For devices like touchscreens, which use absolute coordinates not relative motion, this isn't even an option. So two more reasons that implementation is completely useless.