Announcement

Collapse
No announcement yet.

CD ripper not identifying CDs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • pclinux1
    replied
    Thank you Tomcoppa I switched from vortexbox to daphile and today switched back. Missed cdripping which is faster on vortexbox than on Daphile. Also missed Plex.

    Back on vortexbox now and cd ripping works, DVD ripping works [on 2.4], and my plex is back!

    Leave a comment:


  • TopCat
    replied
    The config mod worked for me - Thanks. I hadn't ripped a CD for a few weeks and just came back here on the off chance this morning. Much appreciated. VortexBox lives on for another day. Just like my old SONOS, I'm keeping it limping along. Come to think of it I'm just about limping along too, (I broke my ankle recently). Best wishes to all and stay healthy.

    Leave a comment:


  • Fifer
    replied
    Originally posted by tomcoppa View Post
    I am a long time user of the VortexBox software and this is a first post. I hope it is helpful.
    I am pleased my VortexBox is back in business.

    Helpful? That's fantastic - tried it, it works and my Vortexbox is also back ripping as it should. Thanks - I doubt there's ever been a better first post!

    Leave a comment:


  • tomcoppa
    replied
    The information about gnudb.org was very helpful. Investigating further has enabled me to find the changes necessary to return the CDDB lookup functionality to my VortexBox by configuring gnudb.org as the CDDBHOST in the file /etc/ripit/config. I am running VortexBox 2.5 and made the following edits to /etc/ripit/config.

    In the CDDB Options section -

    mb=0
    CDDBHOST=gnudb.org
    mirror=gnudb
    transfer=http
    proxy=proxy.gnudb.org:3128

    I am not 100% sure if the proxy entry is necessary, but once it started working did not go back to further diagnose if the proxy is needed.
    I don't think I have any other significant customization or have made any edits to other supporting files on my VortexBox.
    Maybe a rewrite of the aforementioned perl files will not be necessary at this time.

    I am a long time user of the VortexBox software and this is a first post. I hope it is helpful.
    I am pleased my VortexBox is back in business.


    Last edited by tomcoppa; 07-18-2020, 06:15 AM.

    Leave a comment:


  • durks
    replied
    Originally posted by bart View Post
    gnudb,org ?!
    Hmmm interesting!
    It's indeed helpful to know that gnudb.gnudb.org has taken over responsibility for this public service. At least that gives us a chance here.

    Originally posted by bart View Post
    I had a quick look, but lack the time for the moment to dig deeper and test...
    it seems we have to change the cddb host, the adress has to be altered.
    inside usr/bin/cddb.pl I've found it is pointing to freedb.freedb.org
    the gnudb.org website states to use gnudb.gnudb.org
    Vortexbox does its ripping via the /usr/bin/ripit Perl script, which calls out to the /usr/share/perl5/vendor_perl/CDDB_get.pm module to get the metadata. So it's the latter code which needs looking at. Unfortunately it's definitely not just a case of swapping out freedb.freedb.org for gnudb.gnudb.org - the CDDB_get.pm code will need a fair bit of attention to get this back working. If I manage to make progress I'll post back; equally I hope others might also take a look.

    This codebase looks ancient to me though. A complete rewrite might be the way to go.

    Leave a comment:


  • bart
    replied
    gnudb,org ?!
    Hmmm interesting!


    I had a quick look, but lack the time for the moment to dig deeper and test...

    it seems we have to change the cddb host, the adress has to be altered.
    inside usr/bin/cddb.pl I've found it is pointing to freedb.freedb.org
    the gnudb.org website states to use gnudb.gnudb.org

    Maybe someone else can investigate further ...

    cheers,
    bart/

    Leave a comment:


  • Vroderick
    replied
    Hello,
    i have a question ; how to change from freedb.org (service is down) to gnudb.org?

    until than,
    thx
    vrodi

    Leave a comment:


  • garym
    replied
    Originally posted by pulinap View Post
    Thanks all....it might be the case....
    garym with regards to dbpoweramp - do you use normal PC?

    Cheers
    yes, on either my laptop or desktop, both windows machines.

    Leave a comment:


  • pulinap
    replied
    Thanks all....it might be the case....
    garym with regards to dbpoweramp - do you use normal PC?

    Cheers

    Leave a comment:


  • garym
    replied
    Aha. I'm sure that's it. I've never used VB for ripping (always used dbpoweramp and then moved files over to the VB.

    Leave a comment:


  • bart
    replied
    as noted in another thread: https://www.vortexbox.org/forum/supp...sing-any-disks

    Originally posted by Mr. Bill View Post
    I did contact Andrew and he replied back that the ripping has not been working well on the Vortexbox as the free metadata service is not working well (his words) but offered no solution.

    I did check the 'Freedb' site which I believe is (was) used to get the metadata and found the following information:
    Wikipedia Quote: 'freedb.org and its services was scheduled to be shut down on March 31 of 2020. As of May 28, 2020 the site was still operational. On the 13th of June 2020 it was observed that the URL used for lookups, freedb.freedb.org, no longer resolved to a host name and as a result the service no longer appears to operate.'

    ........

    Mr. Bill


    Leave a comment:


  • garym
    replied
    has the VB lost its connection to the internet or having DNS problems? first thing I would do is turn off VB, remove power to router and modem. Then restart modem, let fully start, restart router, let fully start, then power up VB. May not solve problem, but can't hurt.

    Leave a comment:


  • pulinap
    started a topic CD ripper not identifying CDs

    CD ripper not identifying CDs

    Hello Fellow Travellers,

    Hope you all are safe and well.

    I have an old Vortexbox CD ripper with 2TB internal HDD and suddenly it stopped identifying the CDs being ripped - this actually happened so suddenly that I was ripping CDs one night perfectly and the next morning it stopped recognising the CDs that are being ripped.

    The version I have is:

    VortexBox SW Version: 2.4

    Linux OS Version: Fedora release 23 (Twenty Three)

    Any thoughts....?

    Cheers
Working...
X