On seg, 23 jul 2018, Doug wrote:
This may or may not be off topic,
I wouldn't call it completely off-topic, but it's definitely a thread
hijacking. It would have been better to start a new thread.
My friend has just gotten a Korean car--it's either a Hundai or a
Kia, I don't remember, but
On 07/22/2018 04:57 PM, Thomas Schmitt wrote:
Hi,
Bob Bernstein wrote:
The playback is jumpy, or skippy, anything but smooth and continuous.
https://www.cyberciti.biz/faq/linux-unix-mplayer-playing-audio-dvd-cd-using-bash-shell/
proposes option "-cache 5000":
mplayer -cdrom-device /d
Bob Bernstein (2018-07-22):
> mplayer [cdda|cddb]://track[-endtrack][:speed][/device] [options]
^
>
> I first tried 'mplayer cdda:///dev/cdrom'
^^
This is not a track.
> The playback is jumpy, or skippy, anything but smooth an
On Sun, 22 Jul 2018, Thomas Schmitt wrote:
https://www.cyberciti.biz/faq/linux-unix-mplayer-playing-audio-dvd-cd-using-bash-shell/
proposes option "-cache 5000":
mplayer -cdrom-device /dev/sr0 cdda:// -cache 5000
Joy reigns supreme in Mudville!
It has dawned on my somewhat dimmed (due to
Hi,
Bob Bernstein wrote:
> The playback is jumpy, or skippy, anything but smooth and continuous.
https://www.cyberciti.biz/faq/linux-unix-mplayer-playing-audio-dvd-cd-using-bash-shell/
proposes option "-cache 5000":
mplayer -cdrom-device /dev/sr0 cdda:// -cache 5000
I guess it's a real-tim
Firstly, *thank you* to all who chimed in with analysis and
suggestions! This list is the best. I will present an update on
my efforts and a bit more data.
Update: I think it was Nicholas last night who mentioned the
'cdda://' type of URL. Today I noticed on mplayer's man page
this line:
m
Thomas Schmitt wrote:
...
> The classic CD-DA ripper is cdda2wav.
i like jack, but it's broken at the moment in
unstable, unfortunately i don't know python well
enough to debug it yet.
so for my temporary hackish project i'm trying
to convert it all to python3 acceptable code, but
i'm not sur
Hi,
Nicolas George wrote:
> To be accurate, mount only directs the kernel into doing the reads and
> looking for filesystems.
Yes. But in hindsight my explanation was already more technical than
appropriate.
"mount(8) is not the right way to access an audio CD."
would have been better. But i
Thomas Schmitt (2018-07-22):
> Your reader program needs to use command READ CD or READ CD MSF.
> mount(8) or dd(1) won't do this. (Also mount(8) would find no filesystem.)
To be accurate, mount only directs the kernel into doing the reads and
looking for filesystems.
There was a kernel patch to
Hi,
Bob Bernstein wrote:
> bob@debian:~$ mount /dev/sr0
> mount: /dev/sr0 is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on /dev/sr0, missing
> codepage or helper program, or other error
> [...]
> bob@debian:~$ dmesg |tail
> [...]
> [ 1005.988702] Sense K
Bob Bernstein composed on 2018-07-22 01:37 (UTC-0400):
> /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0
> You can see where, on the last line, I tried monkeying
> with sr0's options. I've left the file now as it was
> installed by jessie, which flavor I am still running,
> albeit
I'll try to provide some useful signs/symptoms of the
particular difficulty. The principal message I get is:
--start snip--
bob@debian:~$ mount /dev/sr0
mount: /dev/sr0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on
/dev/sr0, missing codepage or helpe
12 matches
Mail list logo
