0013411: Replay Gain: Add option to Calculate Replay Gain on RIP - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0013411	MMW 5	Burning / Disc Handling	public	2016-07-12 22:30	2022-09-14 14:33

Reporter	peke	Assigned To
Priority	high	Severity	tweak	Reproducibility	N/A
Status	feedback	Resolution	open
Target Version	5.2

Summary	0013411: Replay Gain: Add option to Calculate Replay Gain on RIP
Description	We already have Level Track on RIP, some users ask why there is no option to calculate Gain Index on RIP. We should add that to avoid additional steps user needs to do in order to preserve source file ripped bit to bit.
Additional Information	https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=100625
Tags	No tags attached.

Fixed in build

peke 2016-07-29 11:36 developer ~0045256 Last edited: 2016-07-29 11:38	Reminder sent to: rusty NOTE: On more analyze I think it is more reasonable to Analyze volume rather than level as it will speed up RIP and also it is more useful than leveling in case User then sync those files to MMA and he can also later decide Leveling Type (Track/Album) and should be Enabled by default due its non destructive nature

Ludek 2016-07-29 15:15 developer ~0045265 Last edited: 2016-07-29 15:16	In Options > Volume Leveling we already have checkbox: [ ] Automatically analyze volume of unanalyzed files: [Audio^] I guess enabling this checkbox would cover this issue? So the question is whether to not enable it by default?

peke 2016-07-29 20:13 developer ~0045272 Last edited: 2016-07-29 20:40	That is not a solution as with many users like me it would trigger 80k+ Volume analyze. This option is for new RIPs

rusty 2016-07-31 17:23 administrator ~0045273	I agree with Ludek on this. To my way of thinking users would either want tracks to be analyzed or not. If yes, the same setting should apply to newly ripped tracks. As to the objection that this would cause entire collections to be analyzed, true, but why would a user want to analyze just a specific CD rip, but not their other tracks? I also tend to agree with Ludek that it probably makes more sense to change the default so that MM automatically analyzes unanalyzed files--provided that the implementation works smoothly and without interfering with MM usage (my recollection is that we originally disabled this option because it was causing some problems).

peke 2016-08-01 02:53 developer ~0045275 Last edited: 2016-08-01 02:54	I would normally agree, good points on your side and for MM5 I would make it default enabled along with Analyze Volume on track playback for new installations but not for users that already have 10k+ files in library. My main concern is CPU/Memory usage when this is enabled by default and user scans 10k of tracks. It would hog the system and HDD/LAN and is very time consuming. Still I would add that option to RIP Dialog as it is low risk regression, no new strings for UI and translation even replacing Level Track volume would be more than enough. Especially as we should lower regression risk in MMW 4.x due teh focusing on MM5 One of the problems is that if analyze is taking all CPU Cores MMW lag and even be unresponsive at times, along with risk of crash in case corrupted files is analyzed. Using batches of few hundred at time when listening music is preferred.

Ludek 2016-08-01 16:12 developer ~0045284 Last edited: 2016-08-01 16:14	Yes, I agree that once we decide to change the default to [x] Automatically analyze volume of unanalyzed files: [Audio^] then also Performance > Volume Analysis default should be lowered from [All] to just [1] CPU core. Rusty also suggested that it should be part of the first-run wizard (which I guess currently is missing entirely in MM5 pre-alfa -- TODO)

rusty 2016-08-03 21:41 administrator ~0045307	I've added the changes re. initial configuration of automated volume analysis to 0013444. However, I'm thinking that Peke is also right--if a user doesn't want to enable automatic volume analysis globally, it probably would make sense that they should be able to configure how the track is ripped (and similarly how a track is converted). With that in mind, the following change could be implemented for the rip/conversion dialogs: Volume leveling: _[Analyze Volume, Level Track Volume, None]^_. This has the added benefit of providing a resolution to the problem in the even that 0013444 isn't resolved. Note: all strings already exist. I would also propose that this should only be implemented in MM5. Finally it's not a high-priority issue as CD Ripping isn't the highest priority feature.