Messages

1

Questions / Don't Understand "Work" and "Composition" field

« on: August 03, 2020, 11:30:47 PM »

I am returning to MusicBee as my player and library manager.  I have been using MusiChi to create and manage my large (32,000+ tracks) library.  I have created a new library in MusicBee.  However, I do not understand why some of my files will have data in the "Work" field, while other files are blank.  When I look at the Tag Inspector, I see data in the Composition tag for both situations.

What is the relationship between the Tag Codes and the data displayed in MusicBee?

How do I get the Work tag to display the Composition data?

Thanks,

Art

2

Bug Reports / Re: Player Stuttering and Hanging Up - Version 7506

« on: May 02, 2019, 12:30:53 PM »

Hi Steven,

I understand.  When time permits, I will investigate further and report results for what it may be worth.

Best,

Art

3

Bug Reports / Re: Player Stuttering and Hanging Up - Version 7506

« on: April 30, 2019, 01:43:35 PM »

Hi Steven,

Thanks for your suggestion about possible security system interference.  I am using Windows Defender on all three computers and have been doing so for many months.  I am not aware of updates from Windows specifically related to Windows Defender, but who knows what mischief Microsoft has been making.

We are in the middle of a move from Johnson City TN to Raleigh NC.  Presently, one of my 3 PCs is in Raleigh, one is in Johnson City and one travels back and forth with me.

As you know, Windows implements rather frequent updates and over time, I have encountered other issues with flaky program performance (not just MusicBee) after a Windows update.

We will complete our move to Raleigh by the end of May.  As time permits, I will attempt to find additional clues related to the stuttering/stopping player problem and provide them.

Best,

Art

4

Bug Reports / Re: Player Stuttering and Hanging Up - Version 7506

« on: April 29, 2019, 12:31:16 PM »

Here is some additional info:

I have MusicBee installed on three different PCs - two older Toshiba machines and one new HP.  All machines are running Windows 10.  The HP and one of the Toshiba machines are running Windows 10 Home and the other Toshiba is running Windows 10 Pro.

The HP and the Toshiba running Windows 10 Pro are dedicated to music cataloging and playing - meaning that I have removed all unnecessary programs from both machines.  both machines can access the internet and both are connected to my WIFI networks.  Both machines have MusicBee and MusiCHI software installed.

I also have both MusicBee and MusiCHI installed on my Toshiba Business PC.

My purpose for posting the info was not to seek help.  I was simply providing information about my recent experience with MusicBee's Player.  I am encountering the stuttering and stopping playback issues on all three machines.  I have not encountered these issues on any of the three machines during the recent past, before the last couple of MusicBee upgrade releases.

I suspect that there is now a conflict of some kind between MusicBee and my updated versions of Windows 10.  If no one else is having difficulty, then there are no concerns beyond mine.

I do not need to troubleshoot this issue further.  I have switched from MusicBee to MusiCHI for playback and cataloging.  I will check back on this website for future upgrades to MusicBee and I will try them out.

Regards to all,

Art

5

Bug Reports / Player Stuttering and Hanging Up - Version 7506

« on: April 29, 2019, 03:41:46 AM »

Recently, my MusicBee player has begun to stutter and hang up.  I am running Windows 10 Pro on a dedicated Music PC.  This problem began several versions ago and has gotten worse as I have upgraded MusicBee versions.

The problem is now bad enough that I have switched from MusicBee to another player.

Regards,

Art Daniels

6

Questions / Re: No Sound From MusicBee in WASAPI Exclusive Mode on New HP PC

« on: March 02, 2019, 02:25:24 PM »

Quick Update:  I just resolved the problem.  I removed a program called HP Jump Start from the new PC.  Apparently this program was preventing MusicBee from running in the WASAPI Exclusive Mode.

Because I am using this PC as a dedicated music player, the first thing I did after initially booting up the PC was to uninstall all of the "Bloatware" programs which PC makers load onto new machines.  I did not initially uninstall Jump Start because it was not taking up much disc space and did not seem to be causing problems.  However, upon a recent reboot during this process, Jump Start intruded during the startup process, even though it was not in the Start Up folder.

So, I decided to remove Jump Start and, to my delight, removing this program also resolved the player conflict for the WASAPI Exclusive Mode.

Happy Again for the time being...

Art

7

Questions / No Sound From MusicBee in WASAPI Exclusive Mode on New HP PC

« on: March 02, 2019, 02:07:17 PM »

I am configuring a new HP PC to be used as my dedicated Music Player in my sound system.  All is well, except that I cannot get sound from MusicBee when I choose the WASAPI Exclusive mode.  All other modes, including WASAPI Shared mode work normally.

I have no problem with WASAPI Exclusive mode in my Toshiba PC (my current dedicated music player PC which is being replaced by the new HP machine).

Any thoughts or suggestions?

Thanks,

Art

8

Bug Reports / Re: Possible Problem With New 3.2 Release and Playback

« on: March 26, 2018, 09:00:30 PM »

Hi Steven,

Thanks for your suggestion.  Virtually all of my files are Lossless FLAC.  I do have a few MP3 files and a few WAV files, but this issue has been happening when I play FLAC files.

When I posted, I stated that this was a "possible problem with MusicBee".  I am also working with Fidelizer Pro.  I installed Fidelizer Pro and Version 3.2 of MusicBee at approximately the same time - so the problem could easily be a conflict between MusicBee and Fidelizer Pro.  I have been communicating with the developer of Fidelizer Pro about this same issue.

I have some troubleshooting options to implement to attempt to isolate the problem.  I also own a license for MusiChi Suite.  I plan to temporarily switch from MusicBee to MusiChi while retaining Fidelizer Pro.  That change may reveal the answer.

Prior to implementation of either MusicBee 3.2 or Fidelizer Pro, I would occasionally experience a stoppage of play while using MusicBee 3.2 Patch.  It happened randomly and infrequently, so it was just an occasional nuisance.

I have some other options I can try, including altering several of the Fidelizer Pro settings.

As I type, I have been listening now to a number of tracks after making one alteration to Fidelizer Pro.  So far, the 3.2 MusicBee Player has not stopped.  Perhaps I have already resolved the issue.

If I can establish a definite link between MusicBee, Fidelizer Pro and the player issue, I will post a report with the details in case other MusicBee users are also using Fidelizer Pro.

Best,

Art
 

9

Bug Reports / Possible Problem With New 3.2 Release and Playback

« on: March 26, 2018, 12:06:55 PM »

Since upgrading to released version 3.2, I have been experiencing an intermittent playback problem.  At times, the player will stop at the end of the track just completed and not go forward to the next track.  At other times, the player will go forward to the next track, but then immediately stop at the beginning of the track.  At still other times, the player will play normally.  The problem seems to occur randomly, but when it begins, it continues until I stop and restart MusicBee.  I am running in WASAPI mode.

Prior to upgrading to Released Version 3.2, I had been running the various 3.2 Patch versions without encountering this issue.

Regards,

Art

10

Questions / Re: Keeping Files and Tracks Correlated Between Data Sets

« on: March 07, 2018, 10:29:49 PM »

Hello boroda74  and redwing,

I did use a line-by line comparison for the very reason that boroda74 mentioned.  The issue was further complicated by data differences in both file sets.  The entire process, including correcting the data base problems as I found them, took less than one hour.

Based upon my experience, if I need to perform this analysis again, I would repeat the exact process I used.  I was in full control of the data comparison and I was very confident of the accuracy of my corrections.

Throughout the process, I kept the two data sets in sync on the spreadsheet by inserting blank cells and shifting the remaining cells down.  Keeping them in sync on the spreadsheet made it easy to scan fairly large blocks of data without having to look at each line independently.  When I found a difference, I quickly zeroed in on the actual difference, made the correction, inserted the appropriate number of data lines in the deficient column set, then moved on.

Hope this report upon how I proceeded helps to clarify the process I used and why I would use it again, if needed.

Regards,

Art

11

Questions / Re: Keeping Files and Tracks Correlated Between Data Sets

« on: March 06, 2018, 12:58:35 PM »

With MusicBee, it is important to be meticulous about the consistency of data in order to keep files properly listed.  In my case, it has turned out that I actually had track discrepancies between my two data sets.  I have successfully employed "redwing's" suggested approach, with one significant modification, to resolve all discrepancies between my two data sets.

The modification I made to his suggestion was to copy the URL data from each data set to a common Excel spreadsheet so the I could see the listings side by side.  From that point it was a simple task to scan down both sets of track listings and find the differences.  Once I found a discrepancy, I immediately made the actual corrections to the incorrect data set, then continued my analysis.

Thanks for the suggestions.  My two data sets are now in sync and I have a methodology for future analyses, should they be needed.

Art

12

Questions / Re: Keeping Files and Tracks Correlated Between Data Sets

« on: March 05, 2018, 05:55:08 PM »

Thanks for both replies.

I don't think that non-music files are responsible because the total number of files, as shown under Windows Properties, are the same for both data sets.

I will follow the approach suggested by Redwing to see if I can find the differences.

Art

13

Questions / Keeping Files and Tracks Correlated Between Data Sets

« on: March 05, 2018, 02:14:09 PM »

I have all of my music files stored on two different hard drives.  Each hard drive is associated with a different computer, so I have MusicBee loaded on to both computers.

When I do a "Properties" analysis on each File set, the total number of folders and files compare identically between the two data sets.

However, when I look at the total number of tracks using MusicBee, the total number of tracks are different between the two data sets.  I have performed a "Re-scan all Files" on both computers, but the total track count remains different between the two data sets.

I have two questions:

1.  How can there be a difference in MusicBee total tracks count between the two data sets, when the total files are identical between the two data sets?

2.  What methodology can I employ to find out where the track differences are?

Please note that I have over 26,000 tracks in my data set and the difference between the two sets is about 45 tracks.

Thanks,

Art

14

Bug Reports / Version 3.2.6626.33698 Possible Bug With Long File Names

« on: February 28, 2018, 10:16:33 PM »

Attempting to add new files to MusicBee.  Message returned is that files do not exist.  Fixing the problem has required that I shorten the total file length throughout the multiple folder path.  I have had this happen twice since implementing 3.2.6626.33698.

The rejected file names are not as long as previously-accepted file names.

Possible bug with this latest 3.2 version.

Regards,

Art

15

Beyond MusicBee / Re: Need Help Deleting an Empty Folder on My PC

« on: February 04, 2018, 09:12:06 PM »

One I have in my toolkit for just such occasions is LOCKHUNTER

Thanks - Lockhunter did the trick.  Pesky File gone!!!

Best,

Art