by misterioso » Mon Oct 15, 2018 5:00 am
Today I was using the BPM (Beats Per Minutes) Analyzer plug-in in Foobar2000 to evaluate and write BPM values to one of my Media Monkey playlists containing nearly 100 FLAC songs. To my surprise, when I viewed the properties of the songs in my playlists in MM, the BPM values were blank. However, when I viewed those same songs in their library file locations on my hard drive, the new values written to the ID3V2 BPM field by Foobar2K were visible.
From what I'm seeing, I've concluded the following.
1. In Media Monkey, any ID3V2 tag changes made to a song in it's library folder will be reflected when viewing that same song in a playlist.
2. Vice-versa, in Media Monkey, any ID3V2 tag changes made to a song in a playlist will be reflected in viewing that same song in it's library folder location.
3. However, any ID3V2 tag changes made to a song using a 3rd party app (such as MP3Tag, Foobar2K, etc.) WILL NOT BE visible when the song is viewed, but it WILL BE visible when the song is viewed in it's original library folder location.
Therefore, once you drag a song onto a playlist, the ID3V2 tag information remains static if changed by a 3rd party application. Apparently, Media Monkey keeps 2 sets of ID3V2 metadata - one for a song's original library folder and another for the song's playlist location.
Is this an accurate statement?
Is there a way to get my refresh my playlists to gain visibility of any ID3V2 tag changes made by 3rd party applications? Short of deleting songs out of my playlists and re-adding them in order to force a refresh, I don't know of any other way.
Is there a work around?
Thanks in advance for any help.
Today I was using the BPM (Beats Per Minutes) Analyzer plug-in in Foobar2000 to evaluate and write BPM values to one of my Media Monkey playlists containing nearly 100 FLAC songs. To my surprise, when I viewed the properties of the songs in my playlists in MM, the BPM values were blank. However, when I viewed those same songs in their library file locations on my hard drive, the new values written to the ID3V2 BPM field by Foobar2K were visible.
From what I'm seeing, I've concluded the following.
1. In Media Monkey, any ID3V2 tag changes made to a song in it's library folder will be reflected when viewing that same song in a playlist.
2. Vice-versa, in Media Monkey, any ID3V2 tag changes made to a song in a playlist will be reflected in viewing that same song in it's library folder location.
3. However, any ID3V2 tag changes made to a song using a 3rd party app (such as MP3Tag, Foobar2K, etc.) [b][u]WILL NOT BE[/u][/b] visible when the song is viewed, but it [u][b]WILL BE[/b][/u] visible when the song is viewed in it's original library folder location.
Therefore, once you drag a song onto a playlist, the ID3V2 tag information remains static if changed by a 3rd party application. Apparently, Media Monkey keeps 2 sets of ID3V2 metadata - one for a song's original library folder and another for the song's playlist location.
Is this an accurate statement?
Is there a way to get my refresh my playlists to gain visibility of any ID3V2 tag changes made by 3rd party applications? Short of deleting songs out of my playlists and re-adding them in order to force a refresh, I don't know of any other way.
Is there a work around?
Thanks in advance for any help.