More > Media Center 16 (Development Ended)
Is it possible to alter the replay gain values?
MrC:
Interesting! It does provide a curious "workaround", and so esoteric as to probably be fine left alone.
I took the gappie's cue here and tried it against [Number Plays], and discovered, sure enough, it worked.
I appreciate the necessity and nature of some non-editable fields. If you don't mind my asking, why is Number Plays read- / clear-only?
Matt:
--- Quote from: MrC on August 03, 2011, 05:03:19 pm ---I appreciate the necessity and nature of some non-editable fields. If you don't mind my asking, why is Number Plays read- / clear-only?
--- End quote ---
Things filled by the program like Replay Gain, Duration, Bitrate, Play stats, etc. aren't normally editable. The thinking is that there's a right answer, so why would you edit it? And if you edit it, does that mean the program should stop updating it?
gappie:
--- Quote from: Matt on August 03, 2011, 04:54:20 pm ---I would say it's a bug that it lets you edit a non-editable field with an expression, but I don't think people would like the fix.
Non-editable fields are normally non-editable for a reason. For example, there's a correct way to calculate Replay Gain so it's strange to modify it by hand.
It's not that we're trying to keep data locked up, but instead just trying to keep things understandable. Imagine "Hey, I converted my MP3s from 128 to 256 just by editing a column!"
--- End quote ---
it only works with 'clear only' type of fields, and have worked that way since i started using mc.. even made a contribution to the wiki a long time ago. so, i sure hope this will stay. especially with replay gain, most importantly with silent tracks messing up album gain. but also with number plays (ever tried to test a video file, it will mess up np and make the value unusable).
thanks
:)
gab
MrC:
--- Quote from: Matt on August 03, 2011, 05:09:14 pm ---Things filled by the program like Replay Gain, Duration, Bitrate, Play stats, etc. aren't normally editable. The thinking is that there's a right answer, so why would you edit it? And if you edit it, does that mean the program should stop updating it?
--- End quote ---
I can see that, and entirely get the reason for avoiding modifications to certain critical fields.
But not play stats... as we know what they say about stats.
The nuisance currently for me, albeit an extremely minor one, is that Number Plays increments prematurely in the case of DLNA. Its semantics becomes Number of Attempted Plays, and doesn't track play failures. Number plays is incremented immediately upon play attempt. I mentioned this in some other thread. So the values for track #1 are too high and incorrect. Play failures occur *every* time I playback a track, whenever my disc has gone into low power mode, and the combo of MC > Whitebear > SB time's out, and MC advances to the next track.
So I'd like to be able to correct the errors.
One additional reason. I use MC to manage all-things-music. But sometimes for convenience start playback to my Squeezebox devices from a browser via SB's web interface rather than via RDC > MC > Whitebear > SB. Likewise, I might playback on some other remote device. Thus, playback stats are incorrect, and I'd like to be able to quickly update them to account for this.
Alex B:
In my opinion, it is fine to adjust the measured Replay Gain values directly if that is preferred. Replay Gain is not exact science and personal tastes vary. However, there is one caveat. The already calculated album gain value does not update automatically when the track values are adjusted. Previously I have found that changing the album tag in one of the album tracks to some other value and then back again will do the trick.
Matt,
I'd like to repeat my old request: please adopt scthom's EQdb and integrate it into MC's UI. I guess he would not object this. (As he didn't object adopting the FLAC and Wavpack plugins.)
For example, iTunes can store volume adjustments and existing EQ presets to files (in iTunes: right-click a file or selected files > Get Info > Options...). With EQdb MC can do the same and and actually a bit more because it is not necessary to create a new EQ preset before the correction can be stored to the files and the adjustment can be easily fine-tuned during playback. If you want to adjust a complete album place the album files in Playing Now, start playback, make the preferred EQ adjustments and press the "Save To Playlist" button.
You could expose the EQ interface for this plugin and an additional standard EQ separately in the DSP chain so that both could be used simultaneously.
EQdb v.3.0.0 for MC14 is available here: http://sourceforge.net/projects/mcplugins/files/EQdb%20v3%20(for%20MC14)/. Scot didn't upload the source code for the latest version, but the older MC12/v.2.0.3 source is available here: http://sourceforge.net/projects/mcplugins/files/EQdb%20v2%20(for%20MC%2012)/EQdb%20v2.0.3/. According to Scot the only difference between the versions is in the registration process, which is not anymore correct in either of the versions.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version