meta data for this page

Importing music into dlna/daap database

The description shows the steps to import a audio file into the database of the dlna and daap service. Both services create their directories by reading the META data (id3 tags) stored in the music files.

1.Step: Open remote desktop on jupiter

From any Linux PC open a remote desktop session (xrdp) to jupiter with the vinagre GUI. Username is guest.

2.Step: Mounting source and target dirs to jupiter

  • Source: First decide how audio files arrive at jupiter. Either via USB memory stick, local or remote filesystem. Please note that picard is not supporting virtual file systems. Also bear in mind, that audio files after import will be deleted automatically on source dir by picard.
  • Target: Next prepare the target directory. The dlna server is runnning on rosetta and a nfs share of the music directory can be enabled by the openmediavault NFS service plugin. Because picard is not supporting virtual filesystems, it is necessary to go the hard way of mtab mounting instead of user space mounting the target dlna directory from rosetta onto jupiter. Go to dir /home/guest, create directory nfs_mnt.

Mount the remote directory via sshfs from rosetta to nfs_mnt:

guest@jupiter:~$ sshfs guest@rosetta:/media/e2fc7414-8810-44a2-9de9-9d0bb3855db8/music ./nfs_mnt/ 

The rosetta dlna target directory is now mounted to /home/guest/nfs_mount .

3.Step: Using Musicbrainz Picard for moving and tagging audio files

The Musicbrainz Picard application is used for automatically id3 tagging and moving the audio files from the source to the target directory. It is important, that the settings of the target directory in Picard is /home/guest/nfs_mount . Also renaming of files should be set according to this:

$if(%compilation%, %artist% -,) %title% 

For import add the directory containing the source audio files. On the left tab then you can see a list of all found audio files. There are several ways of gaining the META information for each audio file.

  1. By means of the existing tags in META data using the Musicbrainz service.
  2. By analysing the acoustic fingerprint compared with existing ones in Musicbrainz service.

The successfully analysed audio files appear on the right tab. Until now, changes are made neither in the source nor in the target filesystems. After saving the elements on the right tab, the files will be

  • moved from source to target directory (means deleted on source!!)
  • renamed according settings in Picard
  • rearranged in a new subdirectory structure according settings in Picard
  • saved with the acquired META tags

With this information, the dlna/daap services could offer a most convenient music database.