An update on Jukebox. I guess inactivity here means that the app has been working for everyone. I've been makeing a few changes however, and should shortly have an update.

lrhorer has requested a lyrics retrieval feature, and although I was a bit reluctant, I have been working on it. I actually was just about completed with it when it stopped working altogether. I looked into why it was failing and discovered that the site I was using - azlyrics.com - was not responding. Thinking the site had crashed or was having other problems, I just stopped for the night. Over the next day or two, I noticed that I could access the site from work, but not from home. When I queried them about it, they stated that my IP address had been blocked because of what their bot determined was malicious behavior. I think something along the line of 10 requests in a minute or 100 in 15 minutes (which is probably what I exceeded) is considered malicious and the ip address is blocked for a week. If repeated, the block could be permanent.

Well I was finally unblocked just today and was able to work through the last couple of issues. I just want to run with it myself for a few days to make sure it holds together. And of course since I don't want to be blocked again, I am pacing my testing

I just put version 1.0e of Jukebox up on git. This has the lyrics retrieval feature requested by lrhorer. I also fixed a little bug. In the past, I have been constantly concerned about jukebox being a memory hog. So much so that when the app deactivated, I went so far as to actually destroy my cache, thinking that I could somehow hasten garbage collection. Well that was all well and good until I was requested to pre-load the cache. When the cache is pre-loaded, I obviously don't want to destroy it, so I made this fix.

A Note about lyrics retrieval - be aware of the restrictions of azlyrics.com that I discuss in the previous post. When I first saw it in operation, I thought it was cool, so I went crazy requesting lyrics for song after song. If you do this too, you will likely end up with your IP address blocked.

The player won't play a file by .38 Special. I suspect it is because it takes the leading period in the file name to mean the file is hidden. Of course, there aren't a lot of files with leading periods in the name, but renaming the file breaks the convention of <artist> - <Song>.mp3.

The player won't play a file by .38 Special. I suspect it is because it takes the leading period in the file name to mean the file is hidden. Of course, there aren't a lot of files with leading periods in the name, but renaming the file breaks the convention of <artist> - <Song>.mp3.

I assume the filename is something like ".38 Special - Hold on Loosely.mp3"?

I'll look at how the logic breaks down on this one - sound's like it might be pretty simple.

BTW in my collection, .38 Special is listed as 38 Special - without the leading period. I did this a while ago - not sure why, but that's why I didn't hit this issue.

The player won't play a file by .38 Special. I suspect it is because it takes the leading period in the file name to mean the file is hidden. Of course, there aren't a lot of files with leading periods in the name, but renaming the file breaks the convention of <artist> - <Song>.mp3.

Fixed.

Version 1.0f is now up on git - see my signature.

This was a simple change - one line had to be removed. The issue wasn't that files wouldn't play - they never even made it into the cache. Therefore, you will still be unable to play these songs until you rebuild the cache.

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. | To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

NAS: To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts., To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts., To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts., To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

...
Is there any way to prevent the sudden return to Live TV that sometimes happens when the music is done playing?

pyhme delivers an "idle" event to the app periodically when there is no remote control activity - I'm not sure what the timer period is. While music is playing, I dismiss this event in a way that keep the app active. If no music is playing, it allows the idle timer to kill the app and return to live TV.

I guess it's possible, based on the specific timing, that an "idle" event may arrive shortly after music finishes playing. If this happens, then yes the screen will be quickly dismissed.

I can, if you want, add an option to keep the app active when the idle event arrives, but this will mean that the app will never time out. Alternatively I can add logic that requires the receipt of two (or more) "idle" events before it times out.

I can, if you want, add an option to keep the app active when the idle event arrives, but this will mean that the app will never time out. Alternatively I can add logic that requires the receipt of two (or more) "idle" events before it times out.

I'd prefer an option to always ignore the idle events - Galleon had a similar setting. Thanks!

NAS: To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts., To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts., To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts., To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Version 1.0g is now on git. A new option has been added: ignoreidle, default value of False. If set to true, jukebox will not time out; you will need to explicitly exit from the app. I also changed the normal timeout logic to not react to the FIRST idle event, but to wait until the second such event before it times out. As always, the application will NEVER timeout if music is being played.

pyhme delivers an "idle" event to the app periodically when there is no remote control activity - I'm not sure what the timer period is.

Just as a point of information... it's the TiVo that delivers the event over HME. pyhme is just passing it along and doesn't handle the timing. If I remember correctly, you get one every 5 minutes of idle time.

__________________
EnterWebz.tv To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. + Radio Auricle + air qual / lightning maps, 1p/2p games...

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. David.Blackledge.com Solitaire/FreeCell, Calendar, Map...
hmedev.wikidot.com To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

I didn't picture you as a karaoke type but if you have the vocal cords you might as well use them. I joined the choir at Church and they changed practice night to one when I worked then made a rule that you can't sing on Sunday if you didn't make rehearsal.

Thanks for getting this out so quick. All the non ASCII characters look great and sort properly. Now I have a new problem though, it's not playing any tracks. The progress indicator just stays at 0:00 and it doesn't move. Any suggestions? Is there a log somewhere I can look at?

Quote:

Originally Posted by jbernardis

I just put version 1.0h up on git. This adds support for unicode-encoded metadata.

ricosuave - I don't have a lot of metadata that isn't ASCII, so I couldn't easily test this without using contrived data. I'm hoping you'll let me know if you have any issues with this version.

Try rebooting the TiVo? This happens pretty regularly with the HMO version of the MP3 player; I'm not sure if the HME streamer is similarly affected, but I wouldn't be surprised. It's a TiVo-side bug (at least the HMO version is).

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

There is a new version of Jukebox on git - I introduced a bug in the lyrics retrieval code when I added the support for unicode. Version 1.0i.

ricosuave - I hope wmcbrine's suggestion got you going again. This sounds likely. Jukebox plays no real active part in actually playing the file. It creates the stream, and thereafter just reacts to status messages that the TiVo delivers. It sounds like your TiVo was, for whatever reason, not sending these messages, so hopefully a reboot solves it.

Do you have the proper ip address and/or port specified for the pytivo server. Somewhere in the output from jukebox there should be a line like "Server address = %s:%s". Make sure this points to pytivo. You can specify both of these in your jukebox.ini file (serverip= and serverport=). If you do not specify serverport in your ini file, it gets it from your pytivo config file. But make sure it points to pytivo, and NOT to jukebox/pyhme.