View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002481 | MMW v4 | Conversion/Leveling | public | 2006-05-05 15:16 | 2006-05-07 14:17 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.5.3 | ||||
| Summary | 0002481: VBR Encodes to the wrong rate | ||||
| Description | When using VBR encoding, MM encodes to a rate much higher than that selected by the user. This occurs whether Ripping a CD or using auto-conversion: Auto Conversion: VBR V5 (125) - Manual Settings enabled --> 205 VBR Medium Preset (160) - Manual Settings enabled --> 220 VBR Medium Preset (160) - Manual Settings disabled --> 220 Ripping from CD VBR V5 (160) - Manual Settings disabled --> 260 (used a different set of tracks) Converting with LAME Command line: Lame -V5 --vbr-new --> Average of 150! Note: CBR 128 encodes using MediaMonkey worked correctly | ||||
| Additional Information | reported at: http://www.mediamonkey.com/forum/viewtopic.php?t=9689 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 963 | ||||
|
|
Fixed in build 963 - Our MSVC build caused the problem. I was able to fix it, but only if speed was sacrificed (I'd say at least 20% difference). - We use ICL compiled Lame now. |
|
|
Tested this extensively in 2.5.3.957 and it seems to work well at all bitrates. The only reason I'm re-opening this is that the bitrates encoded with the lame command line did not match those encoded with MM. Is this expected? e.g. Lame xxxx -V5 --vbr-new --> 149kbps With MM, the same settings --> 152kbps This may not be a bug, I just wanted your feedback to be sure. |
|
|
Yes, it's a known issue of Lame, it doesn't give the same results when compiled by different compilers. It isn't a serious issue, the results should always be good, however it's a kind of bug, hopefully they'll fix it sometimes. |
|
|
Closing. |
