Does this ERD reflect good database planning?

I'm making a database to hold data for a media player that I'm working on. Originally, I thought to use one table with the fields:

{filePath,artist,title,album,track_number,length,date,artworkUrl}

Since I'm trying to use good DB design techniques, I've now created a DB with three tables. One for the audio file itself, one for the artists, and one for the albums:

I'd really appreciate it if some more knowledgeable people could evaluate my design and, give me some pointers. Thanks in advance!