Beta 2 Data View Anomaly & Sound Plug-in Bug

[johnh]

1. I have a beta two db converted from 2.5.5.996, and this anomaly occurs on mixed-genre albums. In 3.0 Beta 2 when I open genre view, then open a genre, and scroll in the main panel to the artist, it only shows album tracks for the genre, but if I open the genre tree and select the artist in the tree, it shows all album tracks of all genres. In 2.5.5.996 in the genre view it always shows only the tracks for that genre.

2. This applies to wma and wma lossless, but not mp3. In 3.0 Beta 2 when using the MediaMonkey DirectSound Output plug-in (out_mmds.dll), if crossfading is enabled it cuts off the track instead of fading out. If crossfading is not enabled it plays properly to the end of the track. Other output plug-ins seem to fade out aok on the wma files.

Thanks for all your hard work.

[jiri]

1. It probably depends on the point of view what's better. I think that the new behavior of MM 3 makes more sense.

2. I tried but can't reproduce it. Do you use the standard WMA plug-in? Can you reproduce it with any WMA track? Any specific settings of the output plug-in?

Jiri

[Guest]

1. I guess the MM3 behavior for a genre view doesn't make sense to me. It seems each successive level of a tree should a subset of the level above (as it is with directory folders). The way it is in MM3, opening a genre presents all tracks for all artists which are that genre, but highlighting one artist under that genre in the tree reverts to the same view one would get more directly by opening Artist at the second level of the tree.

Example: Many artists perform more than one genre within an album. In MM2.5.5 I can open Genre, Pop, Josh Groban, it only presents the pop genre tracks from all his albums in the right panel, which play and stop at the end of his pop tracks, or by going one tree level lower I can do the same for a single album. I lose this simple approach with MM3.

2. If you're referring to the input plugin, it is the MediaMonkey WMA Player V1.2 (in_wma.dll) (although I guess the software makes the selection). This issue isn't posing a problem for me, because everything plays fine with other output plugins like DirectSound Output V2.2.7 (out_ds.dll). I just noticed the behavior when trying out out_mmds.dll, which appears to be new with MM3. It affects wma and wma lossless, which I have ripped with both WMP and Easy CD-DA Extractor. Settings I have tried for out_MMDS.dll are:

Either Primary Sound Driver or Sound Blaster Audigy
Hardware Acceleration - Enabled or Disabled
Either Crossfade or Crossfade and Fade In
Remove Silence - Enabled or Disabled
Smooth Pause - Enabled
Smooth Seek - Enabled
Smooth Stop - Enabled

I've tried tracks with high and low volume toward the end. When it starts to fade it cuts off and moves to the next track, and the orange progress "blob" doesn't even make it to the end of it's track.

If you or others can't duplicate this behavior I'd be happy to follow up on other suggestions.

John[/quote]

[johnh]

Sorry, I got called away while writing my response, and it must have logged me out. The previous message was my response.

Thanks, John

[jiri]

1. Will check it out in more details...

2. Strange, it doesn't happen to me. Is it really with all WMAs? You can try to e-mail me a sample one (or two), but I'm not sure if it will help. Maybe a debug log could reveal more...

Jiri

[johnh]

Could this be a buffer issue? I noticed that all the other output plugins I have provide a way to adjust the buffer. In fact, when I was testing the fade settings for DirectSound Output (out_ds), I pushed the fade time beyond the buffer length, and received a message asking if I wanted to automatically increase the buffer. MediaMonkey DirectSound Output (out_mmds) doesn't seem to have a way to adjust the buffer.

John

[rusty]

Note that item 1 will be fixed for beta 3.

-Rusty

[johnh]

RE: Item 1...You folks are awsome!

John