beet mbsync setting bpm and replaygain values to 0?

[michael-ball]

I've recently upgraded from beets 2.6.2 to 2.10.0 and on running beet mbsync -M I've seen that now it's settin the "bpm" and replaygain tag values to 0.

Is this expected? it wasn't doing this in 2.6.2.

[snejus]

What's your overwrite_null configuration?

[michael-ball]

Here's the output of running beet mbsync -M -p:

0 - Entity - None
  bpm: 136 -> 0
  rg_album_gain: -7.4 -> 0.0
  rg_album_peak: 1.0 -> 0.0
  rg_track_gain: -7.2 -> 0.0
  rg_track_peak: 1.0 -> 0.0
0 - Entity - Reduced Beyond the Point of Renewal
  bpm: 89 -> 0
  rg_album_gain: -7.4 -> 0.0
  rg_album_peak: 1.0 -> 0.0
  rg_track_gain: -7.5 -> 0.0
  rg_track_peak: 1.0 -> 0.0
0 - Entity - Grasping the Outer Hull of the Tangible
  bpm: 112 -> 0
  rg_album_gain: -7.4 -> 0.0
  rg_album_peak: 1.0 -> 0.0
  rg_track_gain: -7.4 -> 0.0
  rg_track_peak: 1.0 -> 0.0
0 - Entity - (em)Pathetic
  bpm: 92 -> 0
  rg_album_gain: -7.4 -> 0.0
  rg_album_peak: 1.0 -> 0.0
  rg_track_gain: -6.9 -> 0.0
  rg_track_peak: 1.0 -> 0.0
0 - Entity - Conjoin the Vacuous
  bpm: 92 -> 0
  rg_album_gain: -7.4 -> 0.0
  rg_album_peak: 1.0 -> 0.0
  rg_track_gain: -7.5 -> 0.0
  rg_track_peak: 1.0 -> 0.0
0 - Entity - An Idiosyncratic Mirage
  bpm: 112 -> 0
  rg_album_gain: -7.4 -> 0.0
  rg_album_peak: 1.0 -> 0.0
  rg_track_gain: -7.7 -> 0.0
  rg_track_peak: 1.0 -> 0.0
0 - Null & Void - Null & Void
  bpm: 117 -> 0
  rg_album_gain: -10.9 -> 0.0
  rg_album_peak: 1.2 -> 0.0
  rg_track_gain: -10.9 -> 0.0
  rg_track_peak: 1.2 -> 0.0

[snejus]

What if you disable autobpm and replaygain?

[michael-ball]

If I disable autobpm and replaygain the result of beet mbsync -M -p is still the same as above.

[snejus]

Ah just noticed, you have import.from_scratch set to yes! This clears all fields when they don't get set by autotaggers.

[michael-ball]

Ah okay. From the documentation I understood this was only done at import, not when subsequently running plugins.

[snejus]

This configuration is taken into account whenever autotagging takes place, including syncing :) Will update the docs

[michael-ball]

Thank you, removing that from my config has resolved the problem. I appreciate the help!