Was there a limit on the file size for the MX-3000 contest? I didn't have access to a remote and the Editor program never did limit the size of the complete file however I did get a pop-up that one single page was too large. There was nothing in the fine print on the contest page, MX-3000 programming manual, or Universal website as to the size file the MX-3000 will accept. I'm just learning on this forum that the size limit is only 12MB??? I figured if the programming was smart enough to know that one page was too big it would have limited the size of the entire file as well. There's even a pop-up when you save that reads "Calclating Memory".

Don't feel bad, I sent them the wrong file. I didn't see in the fine print where they wanted IR codes attached to every button. I may have missed an active state or two, leaving the box checked for reverse image.

It's very minor but I don't know how exactly how they are judging them. They are going to post all of the entries for download from what I understand so the size of the file may come into play. I made sure mine was small enough for the older remotes with 32MB and the new ones with 64MB.

Yipes.

Noel

p.s. I didnt go for a lot of crazy graphics and animations, mine is very easy to follow and pretty straight forward with a nice clean look

Noel,
I hope you are referrring to this quote from the contest entry page. Because in that case, I wouldn't worry too much: it is not mandatory to put an IR code to every button, a delay will do just as fine... I hope...
André

I was under the impression that the emulator would not work if the file size was too large to download to an actual remote (I assume you're using the emulator to test) but now that I think about it, I never did actually test that theory. If anybody can shed some light on this it might help.

The rules state that they are judging on many parameters (and hopefully not just on who used 'inverted states' of bitmaps for their active buttons) but for the record as a Crestron developer I actually LOVE this feature, as I don't need to create active states myself. The inverted state does exactly as it should...it shows feedback that the button was pressed, and the split second 'box around the button' that doesn't match the background is a small, small, small price to pay (better than making 2 versions of each button in an external editor). If the active state stayed active longer than the time your button is physically pressing (and blocking) most of it, then I would see the need for 2 states of every button that both match the background.

Now I only hope that whomever is judging reads that :)

On 05/03/05 18:37 ET, RobZ said...
|

That's what I assumed as well but I didn't have a remote to check it out.

I also found it odd that I couldn't find anything "official" on the size of file the remote would accept.

I am just curious to see what other people came up with. There isn't a whole lot in the files section for the 3000 and this should help out everyone looking for a nice, free layout. The styles usually vary so there should be enough free .rcc files to make just about anyone happy.

Noel

I thought I would chime in and say that the emulator WILL run a file MUCH larger than the remote can actually accept. Example, just in testing, I have run files well above 40MB in the emulator, and the average max for the newer remotes is around 12.5MB.

One problem I see with making the emulator know that the file is too big would be that it wouldnt know which version of the remote you have, the 32MB or the 64MB. OR the MUCH NEEDED 1GB version ;-)

-Bracken