ML3 Nightly testing

[Dave72]

Here is an update which provided some changes in .cue file browsing. When I added support for them I did not include support or the one big file method with tracks marked by time. GBPVR does not provide a means to navigate in music files so I didn't think people would use this.

Not for current release, but maybe something in the future..

What if, for a regular mp3 file (no cue file exists), if the user presses ff or rew then a virtual cue file is created dividing the current mp3 up into some equal number of segments (10 ? 20 ?) and jumps ahead (or back) to the next virtual cue index.

[mvallevand]

@tkgafs I've seen some code about the function you are talking about but I didn't test it because I didn't know if psycik ever implemented it what is your config.xml setting for <JukeboxWaitTime>0</JukeboxWaitTime> ?

@pz1 from the log ML3 is doing what it is supposed to, really playlist playing is passed to GBPVR and ML3 just get notifications on the song change and it definitely sounds like that worked. What is failing here is the MVP doesn't seem to respond after the request

2010-02-03 08:58:18.149 VERBOSE [7] Song ended. Checking if there are more songs to play.
2010-02-03 08:58:18.149 VERBOSE [7] Playlist size: 20 current index: 6
2010-02-03 08:58:18.149 VERBOSE [7] Sending audio playback request: F:\eyso\JACOBO~1\CHANSO~1\8INSTR~1.MP3
2010-02-03 08:58:18.165 VERBOSE [7] CurrentAudioTrack
2010-02-03 08:58:18.165 VERBOSE [7] CurrentAudioPath
2010-02-03 08:58:18.165 VERBOSE [7] MVP STOP complete

Shortly after this the MVP should request the song but it doesn't. This is really out of ML3's control.

@Dave72 I will be starting a wishlist thread sometime so refresh my memory on this later, especially if I implement mpgsplt on cue files.

Martin

[tkgafs]

@tkgafs I've seen some code about the function you are talking about but I didn't test it because I didn't know if psycik ever implemented it what is your config.xml setting for <JukeboxWaitTime>0</JukeboxWaitTime> ?

it is set using the config app

my config.xml setting is <JukeboxWaitTime>20</JukeboxWaitTime>

the number is the number of secs to wait before automatically starting a random playlist if the user has not pressed anything on the remote

It did originally work in ML2 but I seem to remember that at some point it stopped working after an upgrade

the intention behind it was to add the simplicity of the jukebox plugin ie you started the plugin working and if you didnt do anything it would simply choose the music itself.

I had been a keen jukebox user, but at that time it didn't really cope very well with large music collections and would often timeout reading a large folder structure.

psycik started touting his ML2 app and I asked him to add the functionality which he happily did and hence tkgafs mode was born, but somewhere along the line it seems to have changed into random all/all which was not the original idea, I would be pleased if you could get it to work again, as its a real struggle to click another couple of buttons when the plugin starts

Tkgafs

[Jaggy]

the number is the number of secs to wait before automatically starting a random playlist if the user has not pressed anything on the remote

the intention behind it was to add the simplicity of the jukebox plugin ie you started the plugin working and if you didnt do anything it would simply choose the music itself.

psycik started touting his ML2 app and I asked him to add the functionality which he happily did and hence tkgafs mode was born, but somewhere along the line it seems to have changed into random all/all which was not the original idea, I would be pleased if you could get it to work again, as its a real struggle to click another couple of buttons when the plugin starts Tkgafs

Now that "tkgafs mode" makes total sense to me as opposed to the random all/all & is something I would use as I now have it setup to default to a collection that doesn't have my classical, humor (talking) etc. in it.

[mvallevand]

Funny Random All/All makes complete sense to me. I don't consider random play by Artist useful but hitting red to select randomly from my library is very logical.

I'll still have a look tonight to see how easy a fix this will be. I will weigh the time against the effort users have to expend in pushing the red button.

Martin

[Jaggy]

Perhaps I should explain a little bit as to why all/all "didn't" make sense to me.

Firstly I can do that from the built in Music Library & for me "all/all" meant just that as I have all my music under one directory. I just couldn't see why I would want to (or enjoy) listening to something from The Who from the Tommy album followed by something from Julie Andrews off the Sound of Music album? But it all has to do with how you have your music setup & with different collections I now see things a bit differently & with a few more enhancements to the way the database is used I can see it being even better in the future.

The auto-start random play is more for when I have visitors staying than for my direct use.

[psycik]

Perhaps I should explain a little bit as to why all/all "didn't" make sense to me.

Firstly I can do that from the built in Music Library & for me "all/all" meant just that as I have all my music under one directory. I just couldn't see why I would want to (or enjoy) listening to something from The Who from the Tommy album followed by something from Julie Andrews off the Sound of Music album? But it all has to do with how you have your music setup & with different collections I now see things a bit differently & with a few more enhancements to the way the database is used I can see it being even better in the future.

The auto-start random play is more for when I have visitors staying than for my direct use.

That is exactly how I listen to music, no order no rules. I have no problem listening to Yanni one minute and Pantera the next.

I did remember that the way tfgafs described it is how I originally set up the jukebox mode. After x seconds it would start playing music randomly chosen from the current collection.

I doubt that has been implemented in ML3, and it sounds like there have been some changes to how the buttons were used.

As far as I recall, hitting the red button would generate a random play list based on what was selected in the large left hand list box. So if All was selected it could choose from the whole collection, if Pantera was selected (and therefore displayed in the other lists) then it would only choose pantera. There also was a flag Random All/All that ignored this behaviour and always selected from the full collection.

This is how I remember it being set up.

[mvallevand]

psycik, the way you describe it, is the way it works now, I tried not to intentionally change functionality that people like so much. Autoplay was definitely disabled.

Martin

[psycik]

I wasn't accusing martin, I hadn't investigated that option (jukebox I mean), and I hadn't see noticed any difference with the red button, so I'm happy. I was just trying to describe what I remembered I'd been asked for.

[mvallevand]

Ok, if you want you can give the timed jukebox mode a whirl. If you set a Jukebox time in config.xml after you enter the ML3 plugin screen if you don't hit a key in the set time tkgafs mode Random All/All will start.

Note it shouldn't kick in if you hit a key or stop a playlist. However once you awaken from the screen saver or exit ML3 and come back in, the JukeBox mode will be back on.

Martin