From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Dividing Daisy Audiobooks.
Date: Sat, 22 Dec 2018 10:58:59 +0200 (SAST) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1812221051450.24331@willempc.meraka.csir.co.za> (raw)
In-Reply-To: <CAO2sX33zg3gfdcN4g8RT2GTDpZKFRd40CE+yutXAkJ7OwBBqYQ@mail.gmail.com>
Willem here.
You would first need to get rid of the encryption before any of the tools
would be usable.
Exactly how you would go about making a daisy book with only some of the
content of the original one, depends on if you have daisy3 or daisy 2.2
books.
It boils down to unzipping the book and removing some entries from the
.opf and nav.xml files and then removing the relevant files from the
directory structure. This is for daisy3, for daysi2.2, it is the same
idea, but different files to be edited.
HTH, Willem
On Fri, 21 Dec 2018, Linux for blind general discussion wrote:
> Good Morning,
>
> I have a few Gigabytes worth of Daisy audiobooks, mostly magazines I
> either copied from cartridges sent by NLS or downloaded from the BARD
> website.
>
> My digital media player(a Blaze ET) is authorized to play Daisy
> audiobooks Encrypted with BARD's DRM, but it takes a really long time
> to load ones with longer play times, and navigating within a long
> Daisy program is a bit annoying.
>
> Does anyone know a way of splitting a Daisy audiobook into a separate
> audiobook for each top-level heading with little to no loss of audio
> quality and retaining all lower level headings? Ideally, I'd like to
> separate each Magazine into a separate Daisy folder for each article
> and to be able to split any future novels I add to my Daisy collection
> into one Daisy book per chapter, just as I merge my rips of CD audio
> books into one flac file per chapter.
>
> If the process can use the input Daisy book to automatically give the
> separated parts a meaningful title/filename, all the better.
>
> --
> Sincerely,
>
> Jeffery Wright
> Bachelor of Computer Science
> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
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=alpine.DEB.2.21.1.1812221051450.24331@willempc.meraka.csir.co.za \
--to=blinux-list@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).