PPM - trouble installing MP3 stuff

[Bushbuck]

Attempting to install MP3 tag editors recently, I've had a "No space on device, exiting" type of error.

Being an ex-programmer (and guess what of, dear readers... but one has to eat), I tried changing the place it downloaded to from root (where there was lavish space anyway) to /mnt/sdb1

That didn't work. Saying "only download the stuff", and then clicking on the resulting file, seemed to work, but it didn't result in a good install.

My configuration should be properly described in my sig, but it is the latest Xenial plus an Intel PC with plenty of resources.

None of this is of any priority, anyway, as it is all workable around. I did wonder if PPM had some semaphore file that could get messed up.

PS, there has also been a bit of "PPM already loaded, aborting", since I started with this, which seemed to be fixed by rebooting.

[bigpup]

it is the latest Xenial

Need the specific Puppy version.
Is this Xenialpup 7.5 or Xenialpup64 7.5 or Xenialdog64 or Xenialpup 7.0.6 or etc.......
How is it installed?
Full or frugal?
If frugal:
Using a save file or save folder?
If save file, how big is it?

In PPM did you update the database before doing any downloads?
PPM>Configure>Update database

[bigpup]

What mp3 stuff you trying to get?

The players already in Puppy can play mp3.

[Bushbuck]

I'm trying to install EasyTag, to adjust ID3 tags.
( --> http://murga-linux.com/puppy/viewtopic. ... 94#1002094 )

Configuration is
Distro: xenialpup64 7.5
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
Bash: 4.3.42
Geany: 1.27
Gtkdialog: 0.8.4
Perl: 5.22.1
Python: 2.7.12
Yad: 0.27.0
--
busybox: 1.23.1
dhcpcd: 6.6.2
Glibc: 2.23
OpenSSL: 1.0.2g 1 Mar 2016, built on: reproducible build, date unspecified
wpa_supplicant: 2.4

It is a frugal install, using a save folder on /sda2, which has got 24G available:

Filesystem Size Used Avail Use% Mounted on
/dev/sda2 32G 6.7G 24G 23% /mnt/sda2

I just tried updating the PPM database, got the "PPM already running, exiting" message, then tried running PPM again, and successfully updated the database.

Tried to install easytag_2.4.2-1, and still got the "No space left on device. Exiting" message.

[perdido]

Interesting bit of info could be the cause of the error.
http://45.33.15.200/puppy/viewtopic.php ... 965#825642

.

[festus]

@Bushbuck

Try this version of easytag on xenialpup64-7.5, it works wonderfully for me:

easytag-2.2.6-x86_64.pet 248 kb
MD5: a383d5e0a862ff2d2f0d59be1badf096

The deps are: id3lib, taglib, wavpack available from ppm if necessary, but they are already in xenial64-7.5, so were not needed.

[norgo]

Hello @festus

thank you very much for easytag pet.
Unfortunately easytag has massively problems to embed covers into mp3 files. Existing tags becomes modified without interaction of user.

Nevertheless thank you once again for your work.

I think easytag is a little bit antiquated.
Here a screenshot for comparison after cover embedding into a mp3 file.

[Bushbuck]

@Bushbuck

Try this version of easytag on xenialpup64-7.5, it works wonderfully for me:

easytag-2.2.6-x86_64.pet 248 kb
MD5: a383d5e0a862ff2d2f0d59be1badf096

The deps are: id3lib, taglib, wavpack available from ppm if necessary, but they are already in xenial64-7.5, so were not needed.

That looks like a good install -- nice work, Festus.

I'm heading in the direction of 40,000 mp3s, so anything that will corrall the herd in any way is good,

Looks like that might scan the entire directory, so I baled out of pointing it at the dreaded WavConv (944GB). Looks excellent, though, so thanks.

[r__hughes]

I wonder if this might help?

I'm using frugal slacko570 npae puppy which has a slackware-14.0 version of lame-3.99.5 pre-installed
(check using the Puppy Package Manager).

Lame is a very poweful mp3 utility. open a terminal and type 'lame --help' (without quotes) to see
all the options for creating and re-tagging mp3 audio files.

LAME 32bits version 3.99.5 (http://lame.sf.net)

usage: lame [options] <infile> [outfile]

<infile> and/or <outfile> can be "-", which means stdin/stdout.

RECOMMENDED:
lame -V2 input.wav output.mp3

OPTIONS:
-b bitrate set the bitrate, default 128 kbps
-h higher quality, but a little slower. Recommended.
-f fast mode (lower quality)
-V n quality setting for VBR. default n=40=high quality,bigger files. 9=smaller files
--preset type type must be "medium", "standard", "extreme", "insane" or a value for an average desired bitrate and depending on the value specified, appropriate quality settings will be used. "--preset help" gives more info on these

--help id3 ID3 tagging related options

--longhelp full list of options

--license print License information

[Bushbuck]

Thanks for that, r__hughes.

It didn't occur to me that Lame might also do the ID3s. Duh. The version pre-installed here in Xenial Puppy 64 is "LAME 64bits version 3.99.5"

I already use lame to cook my WAVs into mp3, from a Python script, so I should be able to integrate the tagging directly into the conversion process.

(...)

Just tweaked the script, and it worked. Thanks again!

The building of the lame command-line is now

Code: Select all

strCmd = "lame -V4 " + strWav + " " + strMp3 +
" --id3v2-only --ta '000 Radio Stuff' --tl '000 Radio Stuff' --ty 2018" 

where strWav and strMp3 are the fully qualified paths.

If anyone else does this sort of workflow, I'd be happy to post the full Python script, such as it is.

If any of the target files already exist, it's a nuisance working out which one(s), so most of the script is about checking that, and flagging up the errors.

There's also a dummy version which does no conversions, and just flags up any duplicates.