ML3 Nightly testing

[pz1]

I have updated a couple of blue skins today. It should help somewhat with text wrapping issues.

This helps a lot. I guess the list of the actually playing queue remains to be done in a similar fashion?

Edit:
Random (Red button)
- I first queued one track with the yellow button. Next I pressed Red, and a couple of random tracks are started palying. However in position one I still have the information of the track selected previously with the yellow button and also its album art. The music is from a completely different track which is shown nowhere. (in build 20990)

[mvallevand]

This helps a lot. I guess the list of the actually playing queue remains to be done in a similar fashion?

Sure, I hadn't thought about it but it probably needs two lines the most.

Edit:
Random (Red button)
- I first queued one track with the yellow button. Next I pressed Red, and a couple of random tracks are started palying. However in position one I still have the information of the track selected previously with the yellow button and also its album art. The music is from a completely different track which is shown nowhere. (in build 20990)

I can't duplicate this, are you using tkgafs mode? If you can duplicate this I would like to see the logs.

Thanks,

Martin

[pz1]

I can't duplicate this, are you using tkgafs mode? If you can duplicate this I would like to see the logs.

Shame on me, I should have tried to duplicate before posting here.
Yes I am using tkgafs mode. (As an excuse I can say that in the early phases of ML3 testing I had seen similar behaviour with playlists and generating new playlists. So I guessed this was a remainder of those problems.)

I will try later to see if it reproduces and under what conditions.

[mvallevand]

Here is the latest update

- Messages updates in PVRx2 now show during the updates
- Generic popup now can accept text fields
- Display last scan date on the Library Update screen
- "Nuke" in config.exe would not reset the scan time

"Full Update" finds the changes in the library since the last scan, but I need psycik's help in explaining what "Fast Update" is supposed to do.

Martin

[psycik]

"Full Update" finds the changes in the library since the last scan, but I need psycik's help in explaining what "Fast Update" is supposed to do.

There are 3 modes of update AFAIK.

• Full you've found, which uses a last update time and only checks files changed (last modified date)
  
• Might be a MLUpdater or Config.exe only option, but another variation on the Full that ignores the last modified date
  
• Fast update uses a file system watcher - it sees when files are added, modified and deleted and stores them up, then based on the fast update time (1 hr etc) it will update just those files. Runs in the background of PVRx2 (or in the service version of MLUpdater) and updates each fast update time. - Have a sneaking suspicion that this is busted - something done in the loading of tracks from m3u files.
  

[mvallevand]

Thanks psycik that Fast Update mode is great, it will be good finding out how it is broken, because I will use it all the time. I took a file from a test folder and put it in a new folder and it worked perfectly. Fast it is!

Code:

2009-12-28 19:49:27.779    VERBOSE    [7]    Database connection opened.
2009-12-28 19:49:27.780    VERBOSE    [7]    MusicLibrary3: Start fast Updating files...
2009-12-28 19:49:27.780    ERROR    [7]    Start Fast 2 1
2009-12-28 19:49:27.780    VERBOSE    [7]    MusicLibrary3: Updating Deleted File: C:\mp3\test\martin.mp3
2009-12-28 19:49:27.781    VERBOSE    [7]    Opening Database connection
2009-12-28 19:49:27.782    VERBOSE    [7]    Database connection opened.
2009-12-28 19:49:27.782    VERBOSE    [7]    MusicLibrary3: UpdateDBDeleteFile:C:\mp3\test\martin.mp3
2009-12-28 19:49:27.800    VERBOSE    [1]    UiStatic.SetArgs() is setting forceRefresh, and will return true to needsRendering()
2009-12-28 19:49:27.826    VERBOSE    [7]    MusicLibrary3: Updating files...
2009-12-28 19:49:27.826    VERBOSE    [7]    MusicLibrary3: Updating Changed File: C:\mp3\fsw\martin.mp3
2009-12-28 19:49:27.828    VERBOSE    [7]    Opening Database connection
2009-12-28 19:49:27.829    VERBOSE    [7]    Database connection opened.
2009-12-28 19:49:27.829    VERBOSE    [7]    MusicLibrary3: Update DB - update: C:\mp3\fsw\martin.mp3
2009-12-28 19:49:27.835    VERBOSE    [7]    MusicLibrary3: UpdateDb - insert to db:C:\mp3\fsw\martin.mp3
2009-12-28 19:49:27.850    VERBOSE    [1]    UiStatic.SetArgs() is setting forceRefresh, and will return true to needsRendering()
2009-12-28 19:49:27.908    VERBOSE    [7]    MusicLibrary3: Fast Update Complete.

Martin

[pz1]

Here is the latest update

- Messages updates in PVRx2 now show during the updates
- Generic popup now can accept text fields
- Display last scan date on the Library Update screen
- "Nuke" in config.exe would not reset the scan time

"Full Update" finds the changes in the library since the last scan, but I need psycik's help in explaining what "Fast Update" is supposed to do.

Works fine. Does need some fine tuning in skin to get things properly placed.
Collections were very messy in my system. So I threw away and rebuild the database. It is Ok now.

Added:
- If one or more tracks are added to an existing queue the position counter underneath album art is reset to 0. (error in build 29319)

[mvallevand]

Pieter there were several skin updates in this update too, I forgot to mention. Th screen look okay at low and high res here. What isn't working for you?

Martin

[pz1]

Pieter there were several skin updates in this update too, I forgot to mention. Th screen look okay at low and high res here. What isn't working for you?

-From the top of my brain it was a minor thing in the update screen. The feedback was a bit close to the buttons on MVP.
-One other thing: I have been fiddling with the playlists.xml to try to get the composer information displayed. If I fill in @Composer (as I do in ML2.7) the field remains empty.

[Fatman_do]

I don't believe Composer was a valid field in ML3, but I left it in the CS skin files for you "just in case" as it was still beta.

I have started updating the CS skins, so maybe will be current by this weekend.