Development resumed on wdtvext - 1.05.04 supported !!!!!

[jumbalaya]

Shouldn't you guys be PMing these type of conversations?

Why? Things have been dull around lately. I almost miss my fits.

<grabs the popcorn>

couldn't agree more.

...and i also agree with recliq here. if you are gaining something through the hard work of the developers here then you should return the favor and make whatever work you've done freely accessible to them.

[pibos]

Development update (kind of)

I am currently moving to a new appartment and you can imagine where all my stuff is: in one of the many boxes.

I hope to get back on ext in 2-3 weeks, with news on debugger

[DJArty]

Hello!
Any news? Or may be last ver from update 20 Apr 2012..

[Markster]

With the assistance of Recliq (thanks much), I was successful at booting my live with the new wdtvext release.

I was pleased to see that "most" of my MovieSheets+ plugin worked. Great job Pibos!

I did however note the following differences\issues:

1. The "initial start-up" key passed to the PageKey event when first booting the WD is 141 on 1.02.21, but is now 144 on 1.05.04.


2. The "standard on/off" key passed to the PageKey event when turning on/off the WD is 252 on 1.02.21, but is now 57 on 1.05.04.


3. I am able to send a key (echo to ir_injection) from the PageCreate event on 1.02.21, but I am NOT able to send a key from this event on 1.05.04?


4. I am able to send a key (echo to ir_injection) from the PageKey event on 1.02.21, but I am NOT able to send a key from this event on 1.05.04?
I tested manually sending a key to the ir_injection at the linux command line and it worked, so either this is an issue with the executeCmd function on 1.05.04 or sending keys inside these events?

5. When manually sending a key to ir_injection, I noted that some of my key values have changed on 1.05.04 similar to my issues #1 and 2 above.

Key of 12 on 1.02.21 is now 13 on 1.05.04
Key of 20 is now 21
Key of 21 is now 12

I tested the other standard remote keys and they were all fine. I also tested some other custom keys like 30 and 82 and they were fine.


All of the standard Page events appeared to function normally (Create, Enter, Leave, Key, Timer) othen then the anomolly of not being able to send keys as noted above.

I have a very small Test Plugin I created which I can use on 1.02.21 to compare against 1.05.04. I can send it to you Pibos if it helps.

[Markster]

As an update on my issues #3 and 4 below, I enabled additional debug on the executeCmd function. I also passed a couple of additional values in the command to force some feedback.
The result was that the commands are certainly being executed successfully, however the PageKey event is not called.

Here is a snapshot of the executteCmd with more debug:

Lib: [executeCmd]
Lib: [executeCmd] cmd: echo '(' > /tmp/ir_injection;date;echo '(' > /tmp/ir_injection
Lib: [executeCmd] command executed.
Lib: [executeCmd] > Fri Jun 29 10:36:59 PDT 2012
Lib: [executeCmd] completed.


I am going to test sending keys from the PageTimer event to see what happens.

[Markster]

An additional update on issue #3 and 4. I was successful at using the PageTimer to generate the ir_injection command.

I sent a key command of 20 in the PageTimer and received a PageKey event with a key of 21, which is the other strange issue I reported, but at least we know the ir_injection works from the PageTimer event.

[Markster]

Sorry for all the thread updates. If I need to be using a different method to communicate let me know.

In an earlier thread a few weeks ago I mentioned a crashing issue in 1.02.21 that occurs when you try to refer to some key page variables used by WD.
There are a couple threads about this created by other users in this forum as well.

One key variable is called act-browselist-X where x represents a number between 0 and the total number of thumbs present on a given browse page (video browsing for example).

If the value is zero, it means the thumb is not selected. If it is one, it means it is selected.

In 1.02.21, referring to these variables to determine which thumb is presently active works "most" of the time but every so often it causes the DMAOSD to crash, requiring a WD reboot.
I got around this issue by writing some C code to examine the heap used by WD to locate the page variables myself.

I tested this on the 1.05.04 release and it crashes almost immediately (usually only takes a couple of references before DMAOSD crashes). The interesting thing is that if you try to read an undefined page variable, you simply get a NULL value but no crashing. For some reason, these special page variables cause a crash even when they do exist and are used by WD.

Here is a snippet of the plugin code that will cause a crash within a few references (when it does work it returns the right value):

Code: Select all

         zactive = Page.Top.getParam("act-browselist-0");
         if (zactive > 0)
         {
            this.debug.Log("In PageKey function and thumb 0 is active!", 1);
         }


[sailort]

Hi guys,
any news on new wdtvext?
Here is a new dl link for patched MNv4 as I been asked for repost: http://www.uschovna.cz/zasilka/J4E3V2U7CN2T22VI-FZE
T.

[DJArty]

Maybe some donations returned to us pibos?
(..ohh yes, looks like pibos (was) online .. )

[RavRob]

Hey Pibos
You all moved in yet? Any update on this? You still carrying on with the development? Maybe an update would be nice.

Thanks