Messages

1

Bug Reports / OK, so a bug with the current XML export

« on: July 06, 2016, 12:40:33 AM »

So... since my ask for a generic XML export is a "wishlist" item, I present a bug.  I don't see a way to attach a file, so I've put the file here: https://owncloud.eicat.ca/index.php/s/Dq1ZQP68QKQTuBT

... it ends like this:

      <dict>
         <key>Name</key><string>000-limp_bizkit-the_lowdown-2cd-2011</string>
         <key>Playlist ID</key><integer>52300</integer>
         <key>Playlist Persistent ID</key><string>F7CABFD834E41101</string>
         <key>All Items</key><true/>
         <key>Playlist Items</key>
         <array>

... which isn't valid XML.  A python XML parser also complains that it has a non-ASCII character in it and emac's XML parser complains about a single quote on the first page.

I don't have itunes, so I can't tell if this passes itunes, but it strikes me that it doesn't.

2

MusicBee Wishlist / The easiest and most globally helpful way to also help me.

« on: July 05, 2016, 10:45:45 PM »

So... I've been doing some thinking about the track scanning problem.  The dozen or so tracks in that directory aren't the only ones not scanned... but I'm thinking that figuring out a list of tracks not scanned will vastly help.

To that end: a database dump (possibly in XML format, or whatever you like) would be most useful to a lot of people and most helpful to me.  I read that you have a dump to itunes somewhere --- and I can't find where that file ends up.  It says the caveat is that multiple tag values are not supported.  I would like, say, a similar XML dump with all tags included.  This would allow me to compare my list of files with the ones that the library has ingested and find the culprits.

3

Bug Reports / Re: Repeatable fail to scan files.

« on: July 05, 2016, 10:39:29 PM »

I figured out the inbox a couple of days ago.  Might be a future FAQ item... as it's not entirely a familiar concept (at least for me).  What's not familiar is the idea of a separate quarantine zone for tracks that is not part of the library proper.  I suppose, if we're being strict about our metaphors, it makes perfect sense.  My whole collection over all these years might be more coherent if I had more of this, but heh.  So... the FAQ bit might be to introduce this concept more explicitly to new users.

On the CUE sheet, they're not CUE sheets, but CUE and BIN files.  Or CUE files without BIN files.  I recall that some ripping software used them to represent how a CD was built especially for non-music tracks.  You might just want to recognize said files.  I can dig up a few if needed.  IIRC, CUE files are text format.

4

Bug Reports / Re: Repeatable fail to scan files.

« on: July 04, 2016, 10:18:10 PM »

Hrm.  Didn't notice this.  More info in the error log today, but no indication of which file is causing the error:

7/4/2016 1:24:33 PM - 10.0.10586.0 - 3.0.6015.32455 - System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at #=q_X0iP5bdFG69OE7aKRFCjnsvVI3PHE6$e_TwcB3IE_w=.#=qdBXO4OC814uydyOMLkGpDQ==(#=qoGy1pLzPA2UyzwUc90g9TBRtHIOu79EgCuLnDF91pCM= #=qYJ_aUzO3k7dFzYwcpczsjg==, Int32 #=qoZEB0W0yrK5SwiwU7Nv8_iFtvQnVzell_qnGK0V3cM4=)
   at #=q2_koF6zNk0Ag5ej71Ckjkyb8$2lDrOIq_Ao04zbrhKA=.#=q3qHpyw2TcOyWP0h93zearzxrF4BtV4L$u470KbaEBwA=(Stream #=qV0zM2nLRZxKcrpsn49Mdpg==, List`1 #=qzGoXV4Wu6Tsl1G1a6aHMwg==, Boolean #=qG_mnswk6w617O_bAE4U8uA==, Boolean #=qksm0751a0q_1BH$Tb_NYUA==)
   at #=q2_koF6zNk0Ag5ej71Ckjkyb8$2lDrOIq_Ao04zbrhKA=.#=qj4A75Zb0Zl0Kjyj0UNYpD64l8w6so_ieF7_vilf$DIs=(Boolean #=qBKUXkvRES6ekYYjd7RZLmw==)
   at #=q2_koF6zNk0Ag5ej71Ckjkyb8$2lDrOIq_Ao04zbrhKA=.#=q$HiwLdsxl8OuYakTFsEibQ==(IList`1 #=qHgUlyjBRzl57gJvFp1DsrA==)
   at #=qVX7rZd6TOU_zZ0WRxhEA03_IjTa5NQYZKcZicnh2GuE=.#=qNQ3c7ZFbbNElJ7TfJqzgKQ==.#=qoTIgjAZ9_K3CUoDSEcsQpg==(IList`1 #=q5vtmqsFzv9uQgRyzon2ojQ==)
   at #=qESylPAVRhqb7nJWEwtg$0b1HvhDQsXISNNLxVzoJY$A=.#=qfisU4ymk3hXqxeQ9YxwEj8GeAUtjY3MJSwCyF2ezuZk=(List`1 #=qMPlayKB64_0DtcfTvTJBzQ==)

5

Bug Reports / Re: Repeatable fail to scan files.

« on: July 04, 2016, 10:05:05 PM »

I get that and I'm willing to do the legwork with a debug version of the scanning code.  I will, however, pm you a link with the directory full of files.  I can't tell exactly which file causes it other than what I described above.

6

Bug Reports / Repeatable fail to scan files.

« on: July 04, 2016, 06:50:24 PM »

So... more of my problems with scanning files.  This one more concrete.  I have a directory with a CD I ripped myself (probably 15 years ago or more).  Title "Gold City -- Cathedral A Capella".  It has 22 tracks.  The first 9 are scanned and in the library.  The remaining 13 are not in the library and refuse to be added on re-scan.  mp3info2 finds them all to be valid and if I play them, they all play.

Obviously, due to copyright, I can't just post these for y'all (nice album that it is).  How would we like to go about debugging this.  It's reproducible as heck .

7

Bug Reports / UI hang observed.

« on: June 21, 2016, 07:53:01 PM »

So... in other news, I'm beginning to try to sort my music with Music Bee.  I've come across a pretty common interface hang when I'm manipulating small groups of files in a large (10k items) playlist.  The UI will hang for 10 to 45 seconds or so and the resume.  My first guess for this bug would be that something I'm doing with that pulldown menu is causing a full scan of the playlist (to be more clear, I'm pulling down the menu on a selection of several playlist items where the playlist is 10k in size).

8

Bug Reports / Re: How do I get MusicBee to output Useful Debugging Information?

« on: June 20, 2016, 07:49:10 PM »

Despite the fact that what you say is pretty rubbish: unless someone played with the functions that are called to look at files during a scan, it's pretty unlikely to have any effect; I get the knee-jerk reaction to having the latest copy to attempt to weed out people who are sub-par at debugging.

What exactly am I saying that you consider rubbish?
Also, I never said the latest patch would fix your problem. But one never knows unless one tries.  It's always best to have tried the latest version, updates, and patches one reporting issues.

If I'm dealing with software that is (say) a year old... or a major version back and I'm dealing with a complex system with 100's or even 1000's of changes over that time, then it's very valid to say "checkout the new version" ... because the number of changes is just so vast that nobody truely comprehends it anyways and the people who are closest to comprehending it are a year away from the code.

But when we're talking a week or two and a small dev team, this is hardly the case.

Anyways... is there a source tree for this thing?  Can I just suck it into M$ Studio and build it?  I can probably get what I need from that, if it's available.

9

Bug Reports / Re: How do I get MusicBee to output Useful Debugging Information?

« on: June 20, 2016, 06:33:32 PM »

are you using the latest patch version from the first forum topic?

What version are you using?

The help->about calls it 3.0.5995 which is the version I get from the above-referenced "latest" download.

Steven asked if you were sure you're using the latest -patch- version, which currently is 3.0.6014 and found via my sig or here: http://getmusicbee.com/forum/index.php?topic=18462.0
At the time he asked you the latest patch was 3.0.6011. So you're using a version that's about three weeks old. Steven is releasing patch versions every day or two until the dust settles on 3.0.  So give the latest a try and see if there's any improvement.

Despite the fact that what you say is pretty rubbish: unless someone played with the functions that are called to look at files during a scan, it's pretty unlikely to have any effect; I get the knee-jerk reaction to having the latest copy to attempt to weed out people who are sub-par at debugging.

That said, I _did_ download that file.  I _did_ put those binaries into my install directory and ran them.  I _did_ just that again and found your 6014 version.

That newer version finds only 9845 of 60k files and leaves no log lines in the log file.

10

Bug Reports / Re: How do I get MusicBee to output Useful Debugging Information?

« on: June 20, 2016, 07:06:25 AM »

are you using the latest patch version from the first forum topic?

What version are you using?

The help->about calls it 3.0.5995 which is the version I get from the above-referenced "latest" download.

One good suggestion in this thread is to ask for a "more debugging" build.  How do I go about that?

If Steven feels a debug version will help, he'll offer one.

Well... this problem isn't going to solve itself.  I have a pretty good idea the class of problem that's causing this, but the debugging in the stock program is insufficient to narrow it down.  I have roughly 60k files.  I need to know which file is crashing the add files process... then, while a fix would be cool, I could just eliminate that one file for now.

11

Bug Reports / Re: How do I get MusicBee to output Useful Debugging Information?

« on: June 20, 2016, 12:00:57 AM »

One good suggestion in this thread is to ask for a "more debugging" build.  How do I go about that?

12

Bug Reports / Re: How do I get MusicBee to output Useful Debugging Information?

« on: June 17, 2016, 06:40:09 PM »

are you using the latest patch version from the first forum topic?

Not the most helpful question as the patch topic doesn't give a version.  When I replace my binary with that one, the verstion stays the same.

Anyways... still phails.

13

Bug Reports / Re: How do I get MusicBee to output Useful Debugging Information?

« on: June 16, 2016, 07:19:51 PM »

Ask Steven for a debug build and then check %AppData%\Roaming\MusicBee\ErrorLog.dat

How do I do that?

As for your issue, are you sure your Y: drive is up and running?

I'm positive there.  MusicBee (on the status line) talks about seeing 40k odd files but the result of the scan is only 4700-odd are found.

14

Bug Reports / How do I get MusicBee to output Useful Debugging Information?

« on: June 16, 2016, 02:53:06 AM »

How do I get MusicBee to output useful debugging information?

My problem is this.  I have a large library.  Somewhere between 40k and 60k files and about 505 Gigabytes of files.  I even know that some of these files are bad.  I have been dealing with all the files that MusicBee flags as bad.  Now I am down to one line of output from MusicBee:

6/15/2016 9:31:07 PM - Unable to scan folder 'Y:\Audio\cds\'
6/15/2016 9:31:35 PM - Unable to scan folder 'Y:\Audio\cds\'
6/15/2016 9:33:26 PM - Unable to scan folder 'Y:\Audio\cds\'
6/15/2016 9:34:54 PM - refresh library failed: Thread was being aborted.
6/15/2016 9:37:59 PM - Unable to scan folder 'Y:\Audio\cds\'

... that is the result of multiple runs.  It just quietly says it can't.  Doubly fun... I've tried unchecking 'cds' and checking everything else in Audio ... and that just results in the same message (I did restart, yes).

It seems to have defied any attempt of debugging.