public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CD ripper that generates song titles?
Date: Tue, 8 Sep 2015 02:05:05 -0400	[thread overview]
Message-ID: <BLU436-SMTP223E10FF80D687D74F859BF8D530@phx.gbl> (raw)
In-Reply-To: <BLU436-SMTP95BA8CED376C3DE49FDD6E8D530@phx.gbl>

On Tuesday, September 08, 2015 1:59:35 AM Fernando Rodriguez wrote:
> On Tuesday, September 08, 2015 12:09:14 AM covici@ccs.covici.com wrote:
> > Fernando Rodriguez <frodriguez.developer@outlook.com> wrote:
> > 
> > > On Monday, September 07, 2015 7:45:47 PM covici@ccs.covici.com wrote:
> > > > Alex Corkwell <i.am.the.memory@gmail.com> wrote:
> > > > 
> > > > > On Wed, Aug 26, 2015 at 04:06:10PM -0400, Walter Dnes wrote:
> > > > > >   I went to the CNE (Canadian National Exhibition) yesterday and
> > > > > > indulged in a buying spree of 18 CD sets of my fave music 
(basically
> > > > > > anything pop/rock/country pre-Beatles).  I now have over 20 CDs 
that 
> I
> > > > > > want to rip to flac eventually.  I dread the gruntwork in renaming
> > > > > > tracks like track01.cdda.wav, etc.  What Gentoo ebuilds are there 
> for
> > > > > > stuff that'll get ahold of track titles?  Is it in the form of 
> metadata
> > > > > > on the CD?
> > > > > 
> > > > > I personally like using morituri [1] for ripping my CDs.
> > > > > It's a little bit slower than some, but very accurate (I believe it
> > > > > compares several reads, just to make sure there were no errors).
> > > > > It's not available in the main portage tree, but it's in the dev-
zero
> > > > > overlay as media-sound/morituri.
> > > > > 
> > > > > It can rip to flac (with optional cue files) and works from the
> > > > > terminal, if you prefer that.
> > > > > Additionally, it can adjust for drive read offsets when writing files,
> > > > > and is one of the few Linux things I've found which check the rips
> > > > > against AccurateRip.
> > > > > 
> > > > > What's particularly nice about it is that it uses what little 
metadata
> > > > > and such it can get from the CD to look it up in MusicBrainz and add 
> in
> > > > > the title, artist, etc.
> > > > > It also uses this to name the files according to album, artist, song
> > > > > title, etc.
> > > > > The template it uses to name the files and directories is relatively
> > > > > configurable, as well.
> > > > > 
> > > > > If you need more configurable tagging, cover art downloading, and 
such,
> > > > > then look into Picard [2], which is in the main portage tree as
> > > > > media-sound/picard.
> > > > > It uses MusicBrainz [3] to get a whole bunch of metadata, tags, 
cover
> > > > > art, and other stuff, and can rename files much more flexibly than
> > > > > morituri.
> > > > > 
> > > > > This is especially nice in combination with morituri, since morituri
> > > > > saves the MusicBrainz ID into the metadata of the ripped files.
> > > > > Normally, Picard looks files up by either the available metadata, or 
by
> > > > > the acoustic fingerprint.
> > > > > Since the MusicBrainz ID is already there, it immediately knows 
which
> > > > > album it is (although it may have the wrong release if you want to 
be
> > > > > that precise).
> > > > > 
> > > > > The only caveats with Picard that I know of are that it's GUI only, 
it
> > > > > can't embed full size cover art if the image is above some large
> > > > > resolution, and I think that submitting extra fingerprints requires 
you
> > > > > to register with AcoustID [4].
> > > > > Also, it's not an actual ripper.
> > > > > It just works on the metadata and tags of flac, mp3, and maybe a few
> > > > > other types.
> > > > > 
> > > > > I personally like to rip with morituri, then polish the tagging and 
> get
> > > > > the cover art with Picard.
> > > > > 
> > > > > [1] http://thomas.apestaart.org/morituri/trac/wiki
> > > > > [2] https://picard.musicbrainz.org/
> > > > > [3] https://musicbrainz.org/
> > > > > [4] https://acoustid.org/
> > > > 
> > > > In trying to emerge morituri from the overlay I get the folloing:
> > > > 
> > > > make[1]: Entering directory
> > > > '/var/tmp/portage/media-sound/morituri-0.2.3/work/morituri-0.2.3'
> > > > if test -e ./.git; then make REVISION; fi
> > > > make[1]: Leaving directory
> > > > '/var/tmp/portage/media-sound/morituri-0.2.3/work/morituri-0.2.3'
> > > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> > > > Progress:
> > > > 00:10
> > > >  (null)*(null) (null)ACCESS DENIED(null):  mkstemp:
> > > >  
> > > 
> 
/run/user/0/orcexec.XXXXXX-------------------------------------------------------------------------]
> > > >           Building documentation: morituri.common.checksum
> > > > 		(/var/tmp/portage/media-
> > > sound/morituri-0.2.3/work/morituri-0.2.3/morituri/common/checksum.py)
> > > > (gst-plugin-scanner:3783): GStreamer-CRITICAL **:
> > > > gst_structure_empty_new: assertion 'gst_structure_validate_name 
(name)'
> > > > failed
> > > > 
> > > > (gst-plugin-scanner:3783): Clutter-CRITICAL **: Unable to initialize
> > > > Clutter: Could not initialize Gdk
> > > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> > > > Warning: Unable to extract the base list for
> > > > twisted.trial.unittest.TestDecorator: Bad dotted name
> > > > Warning: Module gobject._gobject is shadowed by a variable with the 
same
> > > > name.
> > > > Warning: 18 markup errors were found while processing docstrings.  Use
> > > > the verbose switch (-v) to display markup errors.
> > > > >>> Source compiled.
> > > >  (null)*(null) --------------------------- ACCESS VIOLATION SUMMARY
> > > >  ---------------------------
> > > >  (null)*(null) LOG FILE: "/var/log/sandbox/sandbox-3700.log"
> > > >  (null)*(null)
> > > > VERSION 1.0
> > > > FORMAT: F - Function called
> > > > FORMAT: S - Access Status
> > > > FORMAT: P - Path as passed to function
> > > > FORMAT: A - Absolute Path (not canonical)
> > > > FORMAT: R - Canonical Path
> > > > FORMAT: C - Command Line
> > > > 
> > > > F: mkstemp
> > > > S: deny
> > > > P: /run/user/0/orcexec.XXXXXX
> > > > A: /run/user/0/orcexec.XXXXXX
> > > > R: /run/user/0/orcexec.XXXXXX
> > > > C: /usr/lib64/gstreamer-0.10/gst-plugin-scanner -l
> > > >  (null)*(null)
> > > >  
> > > 
> 
--------------------------------------------------------------------------------
> > > > 
> > > > >>> Failed to emerge media-sound/morituri-0.2.3, Log file:
> > > > 
> > > > >>>  '/var/log/portage/media-sound:morituri-0.2.3:20150907-233836.log'
> > > > 
> > > > 
> > > > So, how can I fix or is this a dead package i.e. no maintainance?
> > > > 
> > > > Thanks in advance for any ideas.
> > > > 
> > > > 
> > > > 
> > > 
> > > If you trust the ebuild you can try emerging it with FEATURES="-sandbox" 
> or 
> > > add an exception for the temp directory on the ebuild.
> > > 
> > > https://devmanual.gentoo.org/function-reference/sandbox-functions/
> > 
> > So, if I wanted to add addpredict /run where would I put it?  Somewhere
> > in the ebuild?  I still tink its pretty funky.
> > 
> > 
> 
> I installed the ebuild and it didn't throw any errors, but judging by your 
> output it's happening while building the documentation so it must be 
something 
> related to your epydoc installation. Disabling the doc use flag should get 
> around it.
> 
> 
...or maybe your have user-sandbox on your make.conf FEATURES...
-- 
Fernando Rodriguez


  reply	other threads:[~2015-09-08  6:06 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 20:06 [gentoo-user] CD ripper that generates song titles? Walter Dnes
2015-08-26 20:16 ` Daniel Frey
2015-08-26 20:38 ` covici
2015-08-26 20:49 ` Heiko Baums
2015-08-26 21:01   ` Marc Joliet
2015-08-27 11:28   ` Joerg Schilling
2015-08-27 23:48     ` wabenbau
2015-08-26 20:53 ` wabenbau
2015-08-26 20:58 ` Marc Joliet
2015-08-26 21:04   ` Emanuele Rusconi
2015-08-26 22:53   ` Walter Dnes
2015-08-27 11:37     ` Joerg Schilling
2015-08-27 19:42       ` Walter Dnes
2015-08-27 21:00         ` Neil Bothwick
2015-08-29  1:09           ` Walter Dnes
2015-08-29  9:38             ` Neil Bothwick
2015-08-30  0:20               ` Walter Dnes
2015-08-30 10:46                 ` Neil Bothwick
2015-08-30 17:39                   ` [gentoo-user] " James
2015-08-31 16:40                   ` [gentoo-user] " Stroller
2015-08-31 22:21                     ` Alan McKinnon
2015-09-01  3:22                     ` Walter Dnes
2015-08-26 21:04 ` Fernando Rodriguez
2015-08-27 11:30   ` Joerg Schilling
2015-08-26 21:12 ` [gentoo-user] " Grant Edwards
2015-08-26 21:40 ` [gentoo-user] " Neil Bothwick
2015-08-26 22:50 ` Alex Corkwell
2015-08-27  3:42   ` Daniel Frey
2015-09-07 23:45   ` covici
2015-09-08  0:49     ` Fernando Rodriguez
2015-09-08  2:51       ` covici
2015-09-08  3:17         ` Fernando Rodriguez
2015-09-08  4:09       ` covici
2015-09-08  5:02         ` Fernando Rodriguez
2015-09-08  7:09           ` covici
2015-09-08  5:59         ` Fernando Rodriguez
2015-09-08  6:05           ` Fernando Rodriguez [this message]
2015-08-27  4:14 ` Alan McKinnon
2015-08-27  9:53   ` Neil Bothwick
2015-08-27 14:43     ` Alan McKinnon
2015-08-27 17:29       ` Mick
2015-08-27 18:16         ` Alan Grimes
2015-08-28  1:03           ` [gentoo-user] " James
2015-08-27 18:56       ` [gentoo-user] " Neil Bothwick
2015-08-27 19:07         ` Todd Goodman
2015-08-28  5:03         ` Alan McKinnon
2015-08-28  8:04           ` Neil Bothwick
2015-08-27 11:24 ` Joerg Schilling
2015-08-28  6:15 ` Justin Findlay
  -- strict thread matches above, loose matches on Subject: below --
2015-08-27 20:06 Schilling, Jörg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BLU436-SMTP223E10FF80D687D74F859BF8D530@phx.gbl \
    --to=frodriguez.developer@outlook.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox