With flash memory on a stick or SD becoming so inexpensive and massive it seems possible to carry a large music collection in a phone or on a key chain. I was wondering if I would get into some trouble down the line if modified the config and removed the drive letter for all paths that MusicBee needs. Not including any calls to other programs unless I put them in the Music Bee folder. (?)
Does MusicBee use its startup drive spec universally (with the external calls an understood exception) or should a start in be specified in a shortcut?
Allowing for the settings.ini to be mostly driveless. Which I have down without an issue
<ENV_OrigSetPath>\MusicBeePortable\AppData\</ENV_OrigSetPath>
<ENV_LibPath>\MusicBeePortable\Library\</ENV_LibPath>
<ENV_PromptLib>false</ENV_PromptLib>
<ENV_KnownLib>
Thanks
John
I am moving the "Portable" version off of an external expansion drive and back to the desktop after expanding the space available with a larger faster drive(s)
the move is from S:\MusicBeePortable to C:\Users\admin\Desktop\MusicBeePortable
Questioning my own answer - someone named DRJee simplified the question to relative paths
My question is if I had to change settings to what's shown below which made sense since I had moved it to the root of a drive.
but if I change <ENV_OrigSetPath> to C:\Users\admin\Desktop\MusicBeePortable\ or simply drop the S:
Won't the paths be normalized to C:\MusicBeePortable\~ ?
<ENV_OrigSetPath>S:\MusicBeePortable\AppData\</ENV_OrigSetPath>
<ENV_LibPath>\MusicBeePortable\Library\</ENV_LibPath>
<ENV_PromptLib>false</ENV_PromptLib>
<ENV_KnownLib>
<string>\MusicBeePortable\Library\</string>
<string>\MusicBeePortable\Purrfection\</string>
<string>\MusicBeePortable\Purrfection+\</string>
<string>\MusicBeePortable\temp\</string>
<string>\MusicBeePortable\Bliss\</string>
<string>\MusicBeePortable\Albums\</string>