iPeng support thread

[Bryan Jan]

Sorry, this has to be a different issue. There has been no change between 1.2.5.1 and 1.2.7 that could cause something like that.
What do you do to power it down that doesn't work?

if there is no change between 1.2.5 & 1.2.7 then how to explain the situation, it worked before and now it doesn't. Nothing has been changed in the server, the only change was the iPeng.

As I said the server has been shut down, only the Touch seems still playing song. I use the Touch remote to turn off the Touch display.

[pippin]

if there is no change between 1.2.5 & 1.2.7 then how to explain the situation, it worked before and now it doesn't. Nothing has been changed in the server, the only change was the iPeng.

As I said the server has been shut down, only the Touch seems still playing song. I use the Touch remote to turn off the Touch display.

But what exactly do you do in iPeng (step by step) for which the behavior has changed?

[Ikabob]

Pippin, is there a remote available for a Droid? Thank you.

[MillmoorRon]

OK, this looks like WOL needs explaining Note to self: update manual.

If you enable WOL, the default is to permanently send WOL packets on startup and then every 30s or so.
If you do NOT want that, there's also a "manual WOL" setting. If you enable THAT one, NO WOL packets will be sent automatically. Instead, you get a "Power" button on the server item in the MultiPlayer screen. Whenever you press that power button a WOL packet is being sent.
Use this if you only want to wake up servers incidentally.

I guess I'll get used to stopping iPeng first eventually

Out of interest, why the change from once at startup to continuous?

[pippin]

Pippin, is there a remote available for a Droid? Thank you.

Try SqueezeCommander

[pippin]

I guess I'll get used to stopping iPeng first eventually

Out of interest, why the change from once at startup to continuous?

There has NEVER been once at startup... Well, not sure, at least not for the last 12 months.
The manual option is new, which is quite similar to "once at startup" with the sole exception that you can choose when to turn on the server.

"once at startup" is problematic:
1. It's a nuisance to stop an app under iOS4 so you typically won't start up often. Ok, it could be "once at wakeup"
2. Packets do get lost.
3. Packets do especially get lost right after startup, there are still issues with WiFi startup times especially on iTouch.

[SubLo]

I beg someone (and will pay) to port iPeng over to or develop from scratch a Blackberry version now that OS6 (Torch first) is out. This sucks. I'm stuck with these things from work

[Bryan Jan]

But what exactly do you do in iPeng (step by step) for which the behavior has changed?

Hi Pippin,

Nothing has been done except upgrade it to 1.2.7 via iTune.

Using iPeng to start up the server, as I said no problem.

at the end of my listening session (in the middle of a song), I run the iPeng from the iPad, go to More-->Extra-->Server Power Control-->Shutdown the server.

the server did shutdown, but the Touch is still running, the status bar in the display is still moving. I did wait until that song is finished while the server already shut down, the pointer go back to the beginning of the song and stay there. The screen won't go to sleep mode nor stop mode (I got different screen saver for each mode so I know), it just stay there, with the album art and the details of the song.

Any hint?

[mherger]

> I beg someone (and will pay) to port iPeng over to or develop from
> scratch a Blackberry version now that OS6 (Torch first) is out. This
> sucks. I'm stuck with these things from work

Blackberry imho is closer to an Android implementation in that it's using Java as the development language.

--

Michael

[pippin]

Hi Pippin,

Nothing has been done except upgrade it to 1.2.7 via iTune.

Using iPeng to start up the server, as I said no problem.

at the end of my listening session (in the middle of a song), I run the iPeng from the iPad, go to More-->Extra-->Server Power Control-->Shutdown the server.

the server did shutdown, but the Touch is still running, the status bar in the display is still moving. I did wait until that song is finished while the server already shut down, the pointer go back to the beginning of the song and stay there. The screen won't go to sleep mode nor stop mode (I got different screen saver for each mode so I know), it just stay there, with the album art and the details of the song.

Any hint?

Ok. That's what happens if I shut down my server, too.
Did you configure SvrPowerControl to do something different? Sorry to be dense but I don't use that plugin (can't get it to work) and so I don't exactly understand what you expect to happen.
iPeng doesn't do anything but send a command to the server.
That command is already being created by the plugin.
But more importantly: from what I see the command is successful (the server shuts down), the difference seems to be in the behavior of the plugin itself.
The only way iPeng could affect this is by changing any parameters etc. But I don't think I made changed to the parameter handling in 1.2.7.

I'll see whether Gordon can help out with an idea.