Hello community, here is the log from the commit of package vbrfix for openSUSE:Factory checked in at 2017-10-11 23:02:56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/vbrfix (Old) and /work/SRC/openSUSE:Factory/.vbrfix.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "vbrfix" Wed Oct 11 23:02:56 2017 rev:2 rq:533169 version:0.24 Changes: -------- --- /work/SRC/openSUSE:Factory/vbrfix/vbrfix.changes 2017-08-28 15:13:22.760645610 +0200 +++ /work/SRC/openSUSE:Factory/.vbrfix.new/vbrfix.changes 2017-10-11 23:02:57.532681834 +0200 @@ -1,0 +2,5 @@ +Sat Aug 26 14:13:48 UTC 2017 - [email protected] + +- Compact very long description. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ vbrfix.spec ++++++ --- /var/tmp/diff_new_pack.Wgg5fB/_old 2017-10-11 23:02:58.260649940 +0200 +++ /var/tmp/diff_new_pack.Wgg5fB/_new 2017-10-11 23:02:58.264649764 +0200 @@ -20,7 +20,7 @@ Name: vbrfix Version: 0.24 Release: 0 -Summary: Corrects MP3 files that have incorrect VBR information +Summary: Repair MP3 files that have incorrect VBR information License: GPL-2.0+ Group: Productivity/Multimedia/Sound/Editors and Convertors Url: http://www.willwap.co.uk/Programs/vbrfix.php @@ -34,35 +34,21 @@ Provides: vbrfixc = %{version}-%{release} %description -In an average song there are points that require high quality and points -that require low quality (i.e. silence). - -Instead of having the whole file at, say, 160kbps CBR (Constant Bit Rate), -we can use VBR (Variable Bit Rate). This allows us to have use low bitrates -at points that does not require high quality (were a higher bitrate would -not affect the sound heard) and high bitrates when needed. The result is -usually a smaller MP3 file, with higher quality. - -Unfortunately, the many MP3 decoders estimate the time of a MP3 file based -on the first bitrate they find and the filesize. This means that the -"prediction" used by such decoders is wildly wrong with VBR encoded files -and, as a result, you can get fairly random times for such songs. - -As most songs start with silence you usually get the song length being -shown as much longer than it should be. Also when you jump through a -file encoded in VBR, 50% through the file is usually not 50% through the -song. - -A VBR null frame is placed at the beginning of the file to tell the MP3 -player information about the song length and indexing through the song. - -The problem arises because some poor encoders don't produce this null -frame or do so incorrectly and this is what vbrfix attempts to fix. - -Vbrfix can also fix other problems with MP3s as it deletes all non-MP3 -content (you can keep tags that you state, though). It can also help -when merging two VBR MP3s together with a merging tool and then needing -a newly calculated VBR null frame. +Many MP3 decoders estimate the time length of an MP3 file based on +the filesize divided by the first data packet's bitrate. As songs may +start with silence and hence a low bitrate packet, this length +prediction can produce quite nonsensical values, and when jumping +through a VBR file, 50%% through the file is usually not 50%% through +the song. + +vbrfix places a VBR null frame at the beginning of the file to tell +the MP3 player information about the song length and indexing through +the song. + +vbrfix can also fix other problems with MP3s, as all non-MP3 content +is deleted (you can keep tags that you state, though). It can also +help when merging two VBR MP3s together with a merging tool and then +needing a newly-calculated VBR null frame. %prep %setup -q -n "vbrfixc-%{version}"
