INTERACT FORUM
More => Old Versions => Media Center 12 (Development Ended) => Topic started by: scthom on September 05, 2006, 09:08:42 pm
-
Just wanted to let you all know I updated the Wavpack decoder plugin for v12. New version is 2.0.0. Website is below.
-
Hello,
When I drop wv files into Playing Now, I get the analyzing dialog for awhile.
When I am playing wv and hit next, there is a noticeable delay before the next track begins.
There is also a burst of sound at the track change when using next.
At a normal track change there is no delay nor noise.
This is using either wv or wv+wvc
-
It's probably related to the delays you noted before. I was unable to duplicate the problem during my (admittedly limited) testing. It's an odd situation because in a lot of ways I have no control over some of that (MC does most of it).
Just to confirm - these are local files, not NAS?
The tagging should be improved from the v1 versions since I basically dropped the Wavpack standard tag functions and switched over to the Monkey's versions.
-
Hi Scot,
Yes, they are local files, same drive as my other music, just a different folder. No antivirus looks at any of these folders. I have no similar problem with MP3, MPC, or APE files. Maybe I'll give a few FLAC a try and see what happens.
If you'd like a couple of my files, I can make them available to you, just PM me. Or if that is disabled, temp1 at ghammer dot net Maybe my encoding is different than others. I use this for Wavpack: -clmthb320
Update- I tried a couple of FLAC using the 2.0.2 decoder and they are added to Playing Now as quickly as APE/MP3/MPC. So it is something peculiar to Wavpack.
-
I'll try encoding one with that setting and see if that's part of it. It may also just be something in the Wavpack SDK. The PM looks disabled.
I'll let you know.
-
Thanks Scot
-
When I install the plugin, my track display is not working properly:
On all audio files, (MP3, APE, MPC, WV) I just get Buffering... instead of the info selected.
[Remaining Time] // [Total Time] - [Bitrate (labeled)] [PN Position] of [PN Tracks]
Also, MC has a filetype of Wavpack (wv) already. Of course it will not play wv but has the type.
Then after this plugin is installed, we have 2 filetypes that claim the same extention.
I'm going to post this in the current MC 12 beta thread too just in case.
-
A follow up.
If, after import, I close and run MC all is well with the display.
Something gets confused after Otto does his thing making the display info unavailable.
This also causes the MC last.fm plugin to not submit played files. Doesn't even know anything has been played. No matter the file type.
-
I have started to have a problem with Wavpack files in MC 12.
The problem is explained in this thread:
Info Display Thread (http://yabb.jriver.com/interact/index.php?topic=37011.msg252719#msg252719)
-
Sorry, I've been really busy at the regular job and haven't been keeping up. I'll try to take a look this weekend.
-
I haven't had any of the problems that Hammer has been seeing, but I do know that trying to update wavpack tags from the library will lock MC up solid. I don't know if it's already a known issue, but if not, here you go.
Thanks for all the work you're putting into this stuff.
-
No problem Scot. I found a workaround, but thought one side or the other should take a look because it should not happen.
-
OK, I've been playing with the plugin for a while, and here are some things that I have found that may help you in tracking down problems.
First off, I haven't seen ANY of the problems that GHammer is having. Navigating and importing work, and tags seem to be added to the library. Playback is fine with and without using the WVC file. So far, so good.
As I said before, though, trying to update the tags in WV files will lock up MC solid. Even when it seems to update the tags, if you exit MC, you get a dialog box that the tags are updating and THEN it locks up. The only way out is to kill the process in taskmanager.
Burning CD's works as expected, assuming that it decoded the WV + WVC when it decoded for burning.
And as a nit, when WV files are imported, existing tags for DISCNUMBER and CONDUCTOR aren't imported. All other tags seem to be read fine.
Hopefully some of this helps.
-
Thanks for the info. I still was too busy to actually look at it, but hopefully this week ;D Our submittal got sent out and now it's back to a more regular schedule.