Emplode 'Created' Column Doesn't Adjust For +-GMT

I've already let Roger know about this, so I'm posting it here just in case, so it doesn't get overlooked. I don't know if it's on the internal bug list or not.

The 'Created' column in Emplode doesn't subtract/add the GMT offset. A tune I added at 4:00pm shows being added at 10:00pm (my GMT offset is -6). The 'Last Played' dates are showing up correctly though, played at 1:00pm shows 1:00pm. My player's time zone is set at GMT.

-Chuck

(my GMT offset is -6) [...] My player's time zone is set at GMT.

Are you sure this isn't the problem? What happens if you set the correct timezone on your player?

Peter

Setting the timezone on the player yields the same results. Just double checked it to make sure.

Setting the timezone on the player yields the same results. Just double checked it to make sure.

Just to make double sure, are you saying that tracks downloaded while your player was set correctly still get the wrong time? Tracks downloaded while the player was set incorrectly will stay incorrect.

To me what you describe sounds like normal behaviour. If your player is set to timezone GMT, but the clock looks right to you, that means the player's internal GMT clock is set wrong by six hours. When you do your downloads at 4pm your time, it is indeed 10pm in London, and your player is faithfully telling you so.

Peter

Edit: I'm not saying there definitely isn't a bug here, I'm just saying we've not proved it yet.

Triple checked.

1. PC set to local time zone
2. PC clock set to correct local time
3. Empeg set to local time zone
4. Empeg clock set to correct local time
5. Power off/on player and check settings are as above
6. Add tune at 4:00pm (Emplode 'Created' column displays '10:00pm')
7. Sync
7. After sync, Emplode 'Created' column displays '10:00pm'

4. Empeg clock set to correct local time

OK, it's a fair cop. I'll find and reopen the bug. But if your original bug report had said this, we'd have fixed it for 2.0!

Peter

But if your original bug report had said this, we'd have fixed it for 2.0!

That's no excuse!

Seriously though, I'm just grateful that you guys are still working on this.

-Chuck