0

CSV and touch screen programing clarification

LFKerr

February 13, 2009 01:39

None

Follow

I've been tasked to put together a fairly large, but relatively simple touch-screen interactive, and I'm wondering if (a) the HD2000 will work for me, and (b) if I understand the touch-screen and CSV-based programming properly.

As I understand it, in the CSV file, you build a giant matrix table, with ALL of the touch-zones you're ever going to use across the top, and all of the graphics/videos down the side? And where they "overlap," is where those buttons work on those pages?

Potentially, if I go this route, I believe I'm going to have nearly 50 touch-zones and a time-out column, and then ~380 STATE pages.

Apart from having to modify the DIM eloev(15) and DIM State_Table(100,25), can the HD2000 support this many pages/buttons?

And, in the new State_Table dimension, would that need to be, say, (400,50)?

And if this does work, would there be any performance liabilities from working with such a large filesystem?

Apart, of course, from the obvious of trying to accurately construct this matrix!

Leo Kerr

• Facebook
• Twitter
• LinkedIn

9 comments

• 0
  
  RokuLyndon February 13, 2009 03:00

  
  
  You are correct.
  
  Those are the values you need to modify.
  
  
  
  And, other than possibly taking a little longer to start playing the verify first file at bootup, there shouldn't be any performance issues.
  
  
  
  Yes, you can define that many touch areas.
  
• 0
  
  LFKerr February 13, 2009 03:43

  
  
  Excellent!
  
  
  
  At least, I think it's excellent -- it might mean that a really ugly bit of programming gets dumped into my lap, but the platform seems more stable than the alternatives..
  
  
  
  Leo
  
• 0
  
  LFKerr April 22, 2009 23:30

  
  
  Lyndon,
  
  
  
  as you've suggested, it does take longer with a big state table like that.
  
  
  
  I just clocked it at 365 seconds (6 minutes, 5 seconds.)
  
  
  
  Do you have any speculation as to which parts might be taking longest?  I estimated and rounded up, so there may be more touch-zones dimensioned, and there are probably some extra states dimensioned.
  
  
  
  Alternatively, is there a way to jump from CSV file to CSV file?  For example, the basic menu-pages -- of which there are 14 -- have 40 or so touch zones and a time-out defined.  The remaining 366 pages have three touch zones (forward, back, home) and a time-out.
  
  
  
  Generally our start-up is far enough ahead to allow for the boot-up time, and, in the grand scheme of things, this is probably the worst I can imagine us throwing at such a player, but it would be nice to be able to cut the start-time down.
  
  
  
  (Although since the project started, it's likely that the final installation will be on a 1010, not a 2000.  Is the 1010 mostly a form-factor change, or does it also include different hardware?)
  
  
  
  Leo Kerr
  
• 0
  
  RokuLyndon April 24, 2009 09:33

  
  
  I'm checking to see what we can do about the boot time. I'm wondering if debug is turned on in your autorun file, as that could lead to longer load timeas it outputs lots of info to the shell.
  
  
  
  We can't go from one csv to another currently.
  
• 0
  
  LFKerr April 25, 2009 23:04

  
  
  debug does not appear to be turned on.  
  
  
  
  It occurrs to me to wonder, I'm using Autorun 1.3.0.7, on Firmware v2.0.94 HD2000.  I've just down-loaded 2.0.0.43 and will give that a try.
  
  
  
  Leo
  
• 0
  
  LFKerr April 25, 2009 23:36

  
  
  okay, changing the autorun script did not help.
  
  
  
  It may have actually slowed it down by 5-10 seconds, (up to a boot time of 6:10 or so).  Or I may have been a little more accurate in this timing pass.
  
  
  
  I did also make sure that the dimension variables were closer to the actual CSV dimensions.
  
  
  
  Leo
  
• 0
  
  RokuLyndon April 28, 2009 11:24

  
  
  Can you send me your interactive playlist, at <!-- e --><a href="mailto:lallydice@roku.com">lallydice@roku.com</a><!-- e -->?
  
• 0
  
  LFKerr April 29, 2009 02:30

  
  
  Will do.
  
• 0
  
  RokuLyndon May 02, 2009 07:13

  
  
  Currently we don't have a solution for this issue. It appears to be due to the large size of the csv file. We duplicated the problem on the HD2000 and on one of the compact units as well. It's not clear currently if any improvement could be gained by modifying how the autorun processes the csv file.