Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - kidjedi

Pages: 12
1
It's more a gut feeling than a specific raise for concern, but there could be some self-referencing going on.
E.g. if you let MusicBee scan your Music folder, it will also scan 'itself'.

Not if you set MusicBee to skip that folder (I have it set to skip the whole "_UTILITY" folder in my case).


2
This is probably a long and crooked shot, and likely has nothing to do with your issue, but I noticed you have your MB installation in a folder that resides in the folder that contains your music files?

Is that a good idea?

I'm running portable (so it can live on the server), so I'm not sure why it would be an problem.  I haven't read anything to indicate that it would cause problems, but I'm I'd love to know about any potential issues!

3
are you happy to run a debug version?

Yeah, I can do that.

4
I posted on this last year, but the thread kind of fizzled.  I just upgraded to 3.3.767 P and I'm still experiencing the same issue, so I'm gonna try again.  I will be as specific and articulate as possible.

I have MusicBee portable installed on a network drive, so I can run it from various computers, and other than this particular issue with playlists, it works flawlessly.  It took me a while to get all the preferences set up so making changes from any computer (any running instance of MusicBee) correctly updates the database in such a way that nothing breaks (i.e. MusicBee still runs correctly no matter which computer I run it from).  All the media paths start from the network source (\\NETWORK\music) and function identically no matter which computer I run MusicBee from.

For the explanation of the issue, I'm going to start with my file structure...

All my music is within a folder on the NAS called "music".

Within the "music" directory I have a directory called "_UTILITY".

Within "_UTILITY" is a directory called "MusicBee".

Within the "MusicBee" folder is a directory called "PORTABLE".  This is where MusicBee portable lives on my NAS (and where I run any MusicBee Portable update executables), and where I always run MusicBee from, no matter which computer I'm using.

I also have a directory called "PLAYLISTS" set up to hold all my playlists in "\\NETWORK\music\PLAYLISTS".


I have my media catalog set up for ease of syncing with various devices (and also ease of shuffling within certain categories), thus I have various PLAYLIST FOLDERS set up within MusicBee: Single Artists, Single Albums, Lounge Music, Classical, Jazz, etc.

When you create a playlist within MusicBee, you can only create a NEW playlist at the top of the Playlist Folder hierarchy.  In other words, when you select a bunch of songs and then right-click and select "Add To Playlist," you are given the option to add to the sub-folders and the playlists within those sub-folders, but <New Playlist> is not an option within the sub-folders.  Thus, any new list, no matter which Playlist Folder it's going to end up in, must be created in the "top" Playlist Folder.

When you create the playlist, the file structure of all the songs is correct.

However, when you drag and drop the folder into its appropriate Playlist Folder (i.e. Single Album), the media file path changes to include "Playlist" in the file path.

So, when the playlist is created, MusicBee access the media file via:
 "\\NETWORK\music\Beck\Mellow Gold\08 Beercan.flac"

But when I drag that playlist into the Playlist Folder called Single Albums, the file path of the media in the playlist changes to:
"\\NETWORK\music\PLAYLISTS\Beck\Mellow Gold\08 Beercan.flac"

Obviously that's not where the media lives, and I don't know why PLAYLISTS is being added to the file path.

This happens regardless of whether or not "use relative file paths" is ticked in Preferences>Library>Playlists.


This has been a nuisance for more than a year.  The work around is to simply use the Tools>Locate Missing Files location once I move the Playlist to it's appropriate Playlist folder, but obviously that's a real pain in the keester to have to re-associate all the media files every time you create a playlist.

After some time, I realized I could create a new (empty) playlist in a sub-folder(right-click a Playlist Subfolder, select "New>New Playlist"), then send songs from the library there (into an already created sub-folder playlist), but this is still a work around and requires settings up the empty playlist manually before placing songs in it vs. being able to just create a new playlist on the fly from selected songs in the library.

Hopefully I have been clear in relaying this issue, and hopefully there is a solution to be found, because other than this, MusicBee Portable has been a great solution to being able to play music from a Network Source via any computer I'm using (and MusicBee Portable is the only player I've been able to successfully configure in this way --and I've tried quite a few!).

Thanks in advance for any help you might be able to offer.

...

5
it sounds to me like you are looking at exported playlists. MusicBee library playlists are .mbp files which are binary and not easily edited

Interesting.  So are playlists automatically exported when created within MusicBee?  When I look in the library preferences tab of MusicBee, at the bottom in the "playlist" section there are two places to designate a playlist path (library playlists and exported playlists).  In my prefs, they are set as the same (\\N5550\music\PLAYLISTS).

Doing a search in my music directory (which includes my "PLAYLISTS" directory) and also in the MusicBee sub-directory, there are *no* files with an MBP extension except for "nowplaying."

All of my playlists utilize the m3u extension, and I've never manually exported a playlist.

6
I'm supposed to unpack the executable and manually place folders and files in the appropriate locations to run v3.3 as "portable"?).
This.

See my sig.

Cool.  Thanks.  I'll give it a shot and report back with the results.

7
...try updating to v3.3 from the first forum topic

In looking at that thread, I'm kind of assuming the install file is only for the "regular" version of MusicBee, but I'm running *portable* since I've got it installed in a network location.  Lemme know if I'm mistaken and I'll go ahead and update to v3.3 if it works as portable (perhaps I'm supposed to unpack the executable and manually place folders and files in the appropriate locations to run v3.3 as "portable"?).

8
Thats not something i can reproduce, nor heard ever reported before. Additionally i dont see any code that changes the file paths in a playlist due to moving the playlist to a new folder.
So I wont be able to help with this

edit:
in v3.2 i do recall there was a bug with the remap file paths function for playlist files, so for that issue try updating to v3.3 from the first forum topic

Using a file editor and looking at the text for the individual playlists... it would seem that the file path of a playlist created in the main playlist directory (top of the directory) begins with "..\" while a playlist in a sub-folder begins with "..\..\" so it would appear that it's actually a matter of the file path NOT changing when you move a playlist to a playlist subfolder within MusicBee, as I had previously thought and suggested.

I'm not sure how this would best be handled, but it seems like a link should still resolve if the playlist is moved, especially if it is moved from *within* the MusicBee interface.  In other words, moving the playlist from the top directory to a subdirectory should update playlist file paths to the next level (from ..\ to ..\..\) and so on, depending upon how many levels down the subfolder exists.

All that said, I will try updating to v3.3 to see if that resolves the issue.

9
I use MusicBee portable from a network location.  My music media is in the same network location.  I have MusicBee portable set up in a subfolder ("Utility") of my music media directory.  Playlists are setup in a folder called "PLAYLISTS" in the main music directory.

When I create a playlist with MusicBee, the file path to the media is correct.  If I use MusicBee to move the playlist to a subfolder in the Playlists folder (i.e. drag the playlist "The Flaming Lips" to a subfolder called "Single Artists" in my MusicBee Playlists), the file path for each *song* is automatically changed to the file path of the Playlist.

In other words, the original playlist contains files utilizing the path: \\N5550\Music\The Flaming Lips\The Soft Bulletin\Race for the Prize.flac

But when I drag the playlist to a subfolder (within MusicBee), the path becomes: \\N5550\Music\PLAYLISTS\The Flaming Lips\The Soft Bulletin\Race for the Prize.flac

My Library preferences show that library playlists are located in the PLAYLISTS folder utilizing the path \\N5550\Music\PLAYLISTS, but this should in no way affect the file path of each *song.*

"Relative file paths" is not checked in preferences, but as I understand it from numerous forum posts, this should be irrelevant, as "relative file paths" are *only* significant to *exported* playlists.


I was having this issue with v3.1... but I updated to current (3.2.6902) to verify the problem still exists before posting.

edit:  Additionally, when I correct the file path from within MusicBee using Tools>Locate missing files..., the path is corrected for the active session, but after MusicBee is shutdown and re-opened, the file path returns to the incorrect file path (utilizing the PLAYLISTS sub directory).

10
Questions / Re: Move Library
« on: February 28, 2018, 10:46:59 PM »
It's a confusing interface.  Those are directories that have already been individually remapped.  They're the same left and right, correct?

Nope.  Hundreds of directories on the left. All blank on the right.

So I have NO idea what just happened, but suddenly, "remap" is now bringing up only one path on the left and one path on the right.  I was able to correct the file paths and everything is working now (after months of frustration).

It should be noted that I did move my MB file from one place to another and back, so perhaps this updated/changed something automatically in a file structure somewhere.

I do find it incredibly frustrating that MB portable will automatically change lots of filepaths/structures if you move the program itself (instead of leaving the structures as you had them set, or at least allowing for a setting within MB that allows you to set the root).

11
Questions / Re: Move Library
« on: February 28, 2018, 10:33:11 PM »
It's a confusing interface.  Those are directories that have already been individually remapped.  They're the same left and right, correct?

Nope.  Hundreds of directories on the left. All blank on the right.

12
Questions / Re: Move Library
« on: February 28, 2018, 09:23:57 PM »
How are you bringing it up?  You should definitely be able to just remap the root folder.

When I open MB, if I go straight to File > Library > Remap Music Folders the a dialog box pops up and lists every single folder in my root music folder (apparently requesting me to remap every single artist folder).


13
Questions / Re: Move Library
« on: February 28, 2018, 08:32:37 PM »
Wow, this was incredibly easy. My hdd died, and I restored the backup library to a hdd with a different root letter.

File->Library->Remap Music Folders

Couldn't have worked any smoother. Thanks!

When I do this, MusicBee brings up a window with every. single. artist. folder. and asks me to fill in the new path (for every single one). There are hundreds of artist folders, so usually this eventually just goes into hang trying to populate the pop up window.

Am I seriously supposed to "remap" every single folder?  Why can't I just remap the root location?


14
Bug Reports / Re: unable to open file (error=BASS_ERROR_INIT)
« on: February 21, 2017, 03:52:07 PM »
For me this happens when I try to burn a disc ("Burn failed with the following error: Unable to open file (error=BASS_ERROR_FILEOPEN")

I am unable to burn discs with MusicBee (v. 3.0.6132).

15
Questions / Re: Duplicates & .asx files
« on: January 25, 2017, 06:54:01 PM »
i am going to make 2 changes for this functionality
- enforce title as part of the duplicate matching criteria
- prompt with the number of files that will be deleted on the confirmation dialog

Cool.  I was going to suggest a delete confirmation, but was only thinking about having to do that for each and every file (obviously not feasible when working with a lot of files).  Great idea to simply have the user confirm number of files being deleted.

Pages: 12