Ben, how 'bout posting YOUR current list

[QuickCarl]

That way, we don't have a bunch of people reporting things that you already have as needing work?

[Ben S]

My list of bugs is a little short. Not because they're not there, there are -plenty-, but because they're hard to diagnose.

Media Jukebox / Media Center
* Media Jukebox / Media Center bombs without files in playlist [Resolved in next version of WebRemote]
* Media Jukebox / Media Center image issues.
* Media Jukebox / Media Center playlists sometimes lock up NetRemote
* Media Jukebox / Media Center communication with NetRemote is not totally stable.

NetRemote
* Active image doesn't show until 2nd "loop" of action (due to windows message processing) [Resolved in next version of NetRemote]
* Timeouts should default to 10000 millis
* Resuming from suspend sometimes has messed up header/footer graphics.
* Switching skin requires NetRemote restart
* On Brohebus's pocket pc, mute button doesn't "stick".
* Starting NetRemote with invalid skin file in registry bombs NetRemote [Resolved in next version of NetRemote]

Girder
* Image feedback not stable. Certain size files don't work.

Everyone, even if you've told me previously, please post the bugs you've had (diagnosed or not) here so we can make NetRemote more stable.

[brockgr]

Ben,

Not serious but:

* Panel change feedback from girder to NR
* URL feedback to embedded IE windows

Gavin

[Ben S]

What do you mean by URL feedback to embedded IE windows? Do you mean the mini-browser being able to post events to drivers? Or something else?

Panel change feedback will be resolved in next release (0.98 hopefully!)

[brockgr]

For URL feedback, what would be cool would be being able to send a URL from Girder to the mini-browser, which would then open up that page. I would use it for LDJ to allow you to select a DVD, and then jump to an associated web page (IMDB or similar). However in combination with your "netremote:" URI's we could build entire web based front ends into NR too.

Gavin

[Ben S]

I don't know if that's a bug as much as a feature request :), but it's been noted, and I'll look into it.

Thanks Gavin.

[brockgr]

As always, you are correct Ben. My ideas keep getting ahead of me.
Gavin

[Ben S]

I've fixed the jump to Home/Device/Macro functionality from Girder, and added to it a little bit.

Probably unneeded, but you can now not pass a panel name (in which case it goes to the first panel for the device) or not pass a device name (in which case it goes to the last selected device or macro).

This will be available in the next release (which should be shortly to resolve some outstanding bugs).

The IE stuff I'll take a look at shortly. :)

[brockgr]

Ben,

Just to confirm - what is the current syntax of a panel change message?

Gavin

[Ben S]

Jump Home
[optional]payload [panel name]
GOHOME

Jump Device
[optional]payload [device name][optional :panel name]
GODEVICE

Jump Macrogroup
[optional]payload [device name][optional :panel name]
GOMACROGROUP

[brockgr]

Thanks - I'll knock out a new feedback module with wrapper calls tonight. Gavin

[brockgr]

Uh - having some fun with godevice. What if the device or panel name contains space or ":". I think NR will have a hard time parsing it. Do you want to put the the panel name on it's own 'optional' line?

Gavin

[Ben S]

That's a great idea. Why didn't I do that in the beginning?

Duh. Thanks again, Gavin. I'll add this to the queue.

[esajesa]

Hi, this is actually in the Girder Forum as well, but I figured I'd put it here too. Feel free to delete it if that's not fit


well no luck yet. Been playing around a bit more with timeouts, reinstalling etc, but nothing changes. I've done it all on two different PCs as well, but I get the same problem. Perhaps I'm doing something fundamentally wrong, I don't know..

This is what I get in the script window:

Example Event Logger:
203
Incoming connection
192.168.0.100
Example Event Logger:
203
Accepted connection
192.168.0.100
Registering 192.168.0.100:1023
Connected
Registering 192.168.0.100:1023
Connected
Registering 192.168.0.100:1023
Registering 192.168.0.100:1023
Registering 192.168.0.100:1023
Registering 192.168.0.100:1023

And then it just continues... I did try with different IP addresses, but no
luck. Seems to me like the event keeps coming from Netremote, and it just never stops, unless I kill Netremote of course.

What I've noticed is that I need to increase the timeout either in Netremote, or the script for Girder to get back with the Connected message. But once it's connected, it starts pushing the Registering... event once every 1-2 seconds or so.

I did remove Netremote from my ppc and reinstalled it with the RC2 installer, then upgraded to the RC4, but still the same. Also tried different port numbers.

Getting annoyed now, I'm so close and this is like the last part of my truly to be cool HTPC project, so I'm dying to get it to work!

Cheerio guys,
Jens

[Ben S]

I thought I'd update everyone on the status of these items from long ago.



Media Jukebox / Media Center
* Media Jukebox / Media Center bombs without files in playlist [Resolved in next version of WebRemote]
* Media Jukebox / Media Center image issues. - Resolved
* Media Jukebox / Media Center playlists sometimes lock up NetRemote
* Media Jukebox / Media Center communication with NetRemote is not totally stable. - Somewhat resolved, still debugging

NetRemote
* Active image doesn't show until 2nd "loop" of action (due to windows message processing) [Resolved in next version of NetRemote]
* Timeouts should default to 10000 millis Resolved, changed back to 1000 millis now that millis are actually millis
* Resuming from suspend sometimes has messed up header/footer graphics.
* Switching skin requires NetRemote restart
* On Brohebus's pocket pc, mute button doesn't "stick".
* Starting NetRemote with invalid skin file in registry bombs NetRemote [Resolved in next version of NetRemote]

Girder
* Image feedback not stable. Certain size files don't work. Resolved (I think)

Everyone, even if you've told me previously, please post the bugs you've had (diagnosed or not) here so we can make NetRemote more stable.

[slickrock22]

Just a few issues :wink: :

1. If I (my girlfriend) attempts to PLAY all songs from NetRemote it tries to place about 12,000 songs in the Playing Now listing which totally kills performance :-). Maybe have display top 100 or 200 or something.

2. Occasionally it just hangs on LOADING... in the library and never displays the songs. Also when you open an artist it list other artists instead of that artist's songs.

Thanks

Ryan

[Mastiff]

12 000, Ryan? You whimp! Try playing close to three times that! :twisted: And if you try to play or add anything while the library branch is still loading you'll get that problem with misplaced entries. They'll even show up under playing now, with a plus sign next to them!

[brockgr]

Images are fine ad far as I can see. Knock that one off.

However, as "TheEdge" mentioned, I'm seeing crashes after leaving NetRemote running idle for long periods of time. Looks like it's leaking somewhere.

Gavin

[slickrock22]

Mastiff

:roll: Did I write 12,000, I meant 120,000 :D

[Ben S]

However, as "TheEdge" mentioned, I'm seeing crashes after leaving NetRemote running idle for long periods of time. Looks like it's leaking somewhere.


Are you running Media Center, Gavin? Is this on panels that are receiving feedback from Girder all the time?

I'm trying to narrow down where the leak may be.

It seems to be on PPC only, not on Win32. Would you agree?

[brockgr]

It's worse on PPC - but I wouldn't promise Win32 is 100% fine (more memory on the PC may mask teh problem).

I'm not running any Media Jukebox - the tests recently have been on my Zoomplayer panel. Also I do not believe that I'm sending any feedback to the NR or using it, so it seems to be related to idling/polling.

Or maybe the wireless card going to sleep annoys NR.

Hope that helps a little.

Gavin

[Ben S]

I'm pretty sure this is resolved. Can we all double check in RC5?