use relative paths for controller presets in mixxx.cfg

[mixxxbot]

Reported by: rryan
Date: 2016-05-27T23:57:08Z
Status: Confirmed
Importance: Low
Launchpad Issue: lp1586561
Tags: controllers

---

We store absolute paths to presets in mixxx.cfg:

[ControllerPreset]
Numark_V7 /Users/rjryan/Library/Application Support/Mixxx/controllers/Numark_V7.midi.xml
SCS.3d /Users/rjryan/Library/Application Support/Mixxx/controllers/SCS.3d.midi.xml

If I move my profile directory (e.g. to a thumb drive) these will break! Instead, we should make the paths relative to the profile:

[ControllerPreset]
Numark_V7 controllers/Numark_V7.midi.xml
SCS.3d controllers/SCS.3d.midi.xml

[mixxxbot]

Commented by: Holzhaus
Date: 2020-05-10T20:49:00Z

---

How can we distinguish built-in mappings from user mappings then? This won't work with relative paths.

[mixxxbot]

Commented by: Be-ing
Date: 2020-05-10T21:02:08Z

---

I thought about that, but it would be possible to indicate whether a mapping is from the system folder or user folder explicitly without using the absolute file path. Someday I would like Mixxx to be able to run from a USB drive and using absolute paths in the config file like this would be an obstacle.

[mxmilkiib]

I was going to create a new issue, but this one, AFAIU, relates directly to the bug.

I've moved from a home dir Mixxx config with NAS music storage to a FAT32 USB with some music on the stick and a .bat (for FAT32 execution) that has a config and a music dir on the stick.

When I click "Open User Mapping Folder" in the prefs with the stick config, it opens "/home/milk/mixxxdb/controllers/" which doesn't exist.

[mxmilkiib]

Aah, my bad, I was using mixxx --settingsPath ./mixxxdb when I should have been using mixxx --settingsPath $(dirname $0)/mixxxdb, and had changed to running the script with an absolute path whilst in my home dir, so ignore the above post.