Skip to main content
Topic: MP3 repacker (Read 482267 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

MP3 repacker

Reply #425
Cool, thanks.
BTW: Did you ever check out the problem I reported with 256 and 320kbps CBR files? It seems to be the same problem LAME had when not using the ISO compliance flag. The windows system decoder does not decode such files.

MP3 repacker

Reply #426
Cool, thanks.
BTW: Did you ever check out the problem I reported with 256 and 320kbps CBR files? It seems to be the same problem LAME had when not using the ISO compliance flag. The windows system decoder does not decode such files.

Sorry for the delay on that one. It looks like I just skipped it.

Try to use the "-r" option and see if that helps. That attempts to minimize the bit reservoir all the time. The only reason it's not on by default is that it requires more memory and slightly more processing time.

[edit]That is a really annoying limitation. It would take a whole lot of work to actually get this implemented. The MDB limit is based on the frame bitrate, which in mp3packer isn't decided on until the end, which looks like it would become a horrible mess. Therefore I must warn you: if the "-r" switch doesn't work then I doubt I'll come up with a fix for it...
"We demand rigidly defined areas of doubt and uncertainty!" - Vroomfondel, H2G2

MP3 repacker

Reply #427
Arrgh!

I used the lastest version of this program along with Winmp3repacker to convert my collection to CBR......for some reason the files are still VBR according to Winamp and my CDJ. However, winmp3repacker still views them as CBR. I've even tried forcing them back to VBR and they're still viewed as CBR by Win Mp3 packer.

Any ideas of what to do next? Maybe use the program sans win mp3 repacker?

Btw, I used the "Auto Minimum bitrate" when converting.

EDIT: I've also tried to use "force" mode as well, and did manage to make one into VBR...but since it was VBR already, the only difference is that the program recognized it as VBR(as opposed tp thinking all CBR are VBR for some reason).

MP3 repacker

Reply #428
It is quite possible that mp3 repacker cannot change much the bitrate of those files, and ends up with an almost equal file, but adding the  vbr header.
Of couse, passing it back to cbr should have removed that, although i believe that if the file doesn't change, it keeps the original file, so that would explain the strange result.

MP3 repacker

Reply #429
Any ideas of what to do next? Maybe use the program sans win mp3 repacker?


Yes, use the command line program with the command "mp3packer -i <file.mp3>" Look for the minimum bitrate necessary for CBR, then use mp3packer with this bitrate: "mp3packer -b <bitrate> -R <file.mp3>"

Re-run mp3packer with the -i switch: "mp3packer -i <file-vbr.mp3>". Check it for being VBR or CBR, look for the bitrate distribution if you still get VBR.

If it is still VBR you need to start to experiment with the -b <bitrate> switch. Try "-b 320" first, (should always be CBR) then 256, 224, 192, 160, 128.... Always check it with an mp3packer run with the -i switch set.

Sometimes one gets crazy bitrate distributions like this one with 99.99% 128kbps and 0,01% 320kbps (which means that it is now a VBR mp3 file with almost exactly 128kbps). That usually points to at least one faulty and re-synced MP3 frame somewhere in the bitstream and means that your file was broken...

After that you should get a proper feeling what was happening (or was wrong), etc....

MP3 repacker

Reply #430
Me being on windows vista wouldn't have anything to do with......

I tried some more files using Mp3 repacker.....same result....*sigh*...my poor CDJ.....

I don't get why I'm the only one having these problems....


Any ideas of what to do next? Maybe use the program sans win mp3 repacker?


Yes, use the command line program with the command "mp3packer -i <file.mp3>" Look for the minimum bitrate necessary for CBR, then use mp3packer with this bitrate: "mp3packer -b <bitrate> -R <file.mp3>"

Re-run mp3packer with the -i switch: "mp3packer -i <file-vbr.mp3>". Check it for being VBR or CBR, look for the bitrate distribution if you still get VBR.

If it is still VBR you need to start to experiment with the -b <bitrate> switch. Try "-b 320" first, (should always be CBR) then 256, 224, 192, 160, 128.... Always check it with an mp3packer run with the -i switch set.

Sometimes one gets crazy bitrate distributions like this one with 99.99% 128kbps and 0,01% 320kbps (which means that it is now a VBR mp3 file with almost exactly 128kbps). That usually points to at least one faulty and re-synced MP3 frame somewhere in the bitstream and means that your file was broken...

After that you should get a proper feeling what was happening (or was wrong), etc....



Thanks, only one problem?

How does one do these commands?

I've gotten mp3packer to run but I cant seem to get it to do anything to mp3s without it saying "syntax is wrong" or "error, no directory" etc.

*sigh* I'm considered just using ex-cd da to re-code the files, but I'd really love to get it working withou a loss in file quality.

MP3 repacker

Reply #431
FIXED!

Had to set the minimum bitrate to 32, but they now play on the cdj-200!

MP3 repacker

Reply #432
FIXED!

Had to set the minimum bitrate to 32, but they now play on the cdj-200!


Sorry to hear you had trouble with WinMP3Packer... development on it has stagnated as I've been busy with work :/.

I'd recommend using the "3. Convert to CBR in place (force)" settings preset if you want *really* make sure the MP3s that it outputs are CBR (in other words, untick 'Auto' and select 'All' in the input types section)

 

MP3 repacker

Reply #433
Hey, here's a unixy binary of 1.20, compiled on osx 10.4.11 (intel)
I'll whip up a gui and post that in a bit.
http://alexyule.com/softwares/mp3packer.gz

EDIT: Gui is now up, use it via drag-n-drop (multiple files supported). Each file will be processed, and the resulting output will go to the same folder with -vbr added to the song name.
i.e. 22 Acacia Ave.mp3 --> 22 Acacia Ave-vbr.mp3

Self-contained GUI is here: http://alexyule.com/softwares/mp3packerX_v1.20.zip

Automator action to rename the vbr files (overwriting the originals) via drag-n-drop (you can just drag all the files and it will only rename the -vbr ones) is here: http://alexyule.com/softwares/mp3packer_renamer.zip

MP3 repacker

Reply #434
Just found out about your tool  So sexy!

MP3 repacker

Reply #435
Hi everyone

I just registered to share that I built a native PPC mac OSX version of mp3packer.
I had to install ocaml from source to get it to work - both fink and macports builds failed to work as did the binary ocaml install.

I'm not sure of the dependencies on the binary so I included the entire source tree as it built for me, you can download my results here:

http://www.woopwoopwoop.com/mp3packer-bin-osx-ppc.zip

Let me know if it doesn't work for you and I will try to help you get it working.

Cheers,
Tom

MP3 repacker

Reply #436

97 MP3s, in: 437.67 MiB, out: 275.56 MiB, 37.0 % decrease in size!

The original files were all spoken word (Assimil language course MP3 CD) joint stereo 320 kbit/s CBR.  Stripped using MP3packer v1.20 along with WinMP3Packer v1.0.18, settings: -s -t -z.  Yielding equally great sounding VBR files of 201 kbit/s on average.

Great job, Omion and Psyllium!

MP3 repacker

Reply #437
Anyone know if it's possible to run MP3 Repacker via foobar2000's converter dialog?
If so can someone let me know what the correct settings are.

Thanks in advance.

C.


EDIT: Peter's just said this is not possible so please ignore.
Thanks.
PC = TAK + LossyWAV  ::  Portable = Opus (130)

MP3 repacker

Reply #438
is this only for CBR files?


i have lame V2 -vbr new files...and i have vista and when i open the command thing is dissapears too..is this only xp?

MP3 repacker

Reply #439
is this only for CBR files?


i have lame V2 -vbr new files...and i have vista and when i open the command thing is dissapears too..is this only xp?


No, it will work with any MP3 out there, though there is no idea to use it with (LAME packed) VBR files because of the efficiency of (especially LAME) VBR model.

It's not only for XP. Open "Command prompt".

MP3 repacker

Reply #440
[EDIT] - My problem seems to be a corrupted mp3 file, completely unrelated to MP3 repacker.

Oh, and I almost forgot... thank you for the outstanding program. 

MP3 repacker

Reply #441
So, I take back my previous statement - of course, I don't mean the thankyou , but the one about a corrupted file. After testing some other tracks, I've discovered what appears to be an inconsistency in foobar2000's identification of the Codec Profile (Context Menu>Properties>Properties Tab) for LAME MP3s compressed by MP3 repacker. For example, both a 320kbps album repacked to ~300kbps VBR and a 192kbps album repacked to ~191 are identified by fbk2 as MP3 VBR V4, while another 320kbps album is identified as MP3 VBR V2.

Any thoughts?

MP3 repacker

Reply #442
MP3Packer seems to change the encoder name in the tag to Xing.
I had a bunch of files encoded with FHG (CBR) [which was reflected in the tags], and after I used MP3Packer on them the encoder shows as Xing (VBR).
I wonder whether that is a feature or a bug?

MP3 repacker

Reply #443
MP3Packer seems to change the encoder name in the tag to Xing.
I had a bunch of files encoded with FHG (CBR) [which was reflected in the tags], and after I used MP3Packer on them the encoder shows as Xing (VBR).
I wonder whether that is a feature or a bug?
Features:
* Writes valid LAME/XING header for proper VBR seeking

MP3 repacker

Reply #444
thank you

MP3 repacker

Reply #445
I'm still alive! 

I just had somebody send me a file which causes mp3packer to go really slowly. (not sure if he has an alias, and I don't want to drop people's real names on the internet) In response, 1.21 is out.

Anyway, I made some of the algorithms a bit more efficient and less likely to take forever. The files should be exactly the same size and the frames should be in exactly the same places. The only difference between the files from 1.20 and 1.21 is the frame padding (which contains the version number).
"We demand rigidly defined areas of doubt and uncertainty!" - Vroomfondel, H2G2

MP3 repacker

Reply #446
Thank you, Omion. Nice to know that mp3packer is still actively being developed.
lame3995o -Q1.7
opus --bitrate 140

MP3 repacker

Reply #447
It would be great if the new output files would have the same modification date and time as the originals: I like to see when I got the files/downloaded/ripped them.

MP3 repacker

Reply #448
In response, 1.21 is out.


Hi.  I've been successfully using mp3packer for a couple years, and am currently on version 1.20.  It's been a very handy program for repairing damaged files and stripping non-audio data.  Hoping to see an improvement in speed for the -z option, I downloaded version 1.21.  However, when I attempt to run the .exe, it simply says,

(Sys) This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
"L:\Mp3Packer\mp3packer.exe"

I tried various command lines that have always worked in previous versions, as well as mp3packer with no parameters. All result in the same error on two different systems - one a Win XP sp3 system, and the other a Win 2000 system.  Any suggestions for getting this latest version to run?
--
FoxWolfie


 
SimplePortal 1.0.0 RC1 © 2008-2019