Greetings:
I have to write some documentation on DVD/VCD players for Linux. I own
a nice new DVD player (dmesg says it's a LITEON DVD-ROM LTD163D, ATAPI
CD/DVD-ROM drive) that works well on my machine, though I did have to
discover a few secrets for glitch-free viewing (e.g. my nVidia card
should have its double-buffering turned off). I'm writing not only about
viewing video discs but also recording and ripping them. Thus, a few
questions for anyone in the LAU community using a DVD player and/or
recorder.
1. What software do you use for viewing DVDs ?
2. Do you use that software for watching AVI, MPEG, or other video
formats ?
3. What software do you use for ripping/encoding DVDs ?
4. If you have a DVD recorder, please let me know how well it works
for you under Linux, what outstanding problems exist, what software you
use, etc.
5. Overall, how would you rate Linux DVD support, particularly
compared to Windows or the Mac ?
I don't own a DVD recorder and I'm curious about Linux users'
experiences with them.
I've been trying to rip DVDs using the dvd::rip software (based on
transcode) but keep receiving read errors. If anyone has any special
tips for DVD ripping I'm interested in them too.
My system includes an 800 MHz AMD CPU, two 15GB hard drives (tuned),
512 MB RAM, an SBLive soundcard, and an nVidia GForce2 (64 MB video
RAM). Kernel is 2.4.18 patched for low-latency. I've been using MPlayer
0.90 for viewing AVI and other video file formats. I was using MPlayer
for watching DVDs too but have recently switched to Ogle (a better DVD
player, IMO). Frame rate is normally between 24 and 29 fps (that's what
MPlayer reports, I don't really know if it's any different under Ogle).
I don't really know how to massage MPlayer's parameters, so any advice
for improving video file playback performance is most welcome. Ogle is
pretty straightforward, and the Ogle FAQ yielded some very useful tips
(particularly the pointer to the xvattr utility).
So, how's *your* DVD player performing under Linux ? :)
Best regards,
== Dave Phillips
The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm
The Linux Soundapps Site at http://linux-sound.org
hello all!
I usually wouldn't post the release of a minor version, but I updated
the main view and it looks a lot better than it did. I figured some of
you would want to see it / use it:
http://www.filter24.org/seq24/
cheers,
rob buse
Recently, after having tried every fix I could find on
the net for fixing the dropped samples that I get out
of my Delta44, it hit me to simply try 'nice'.
I got a profound increase in sound reliability by
preceding my play command with 'nice -n-20'. I was
finally able to get a couple of dropouts this way,
by simultaneously executing a recursive long directory
listing from the root (in other words thrashing the
hard drive), but I found that using nice, I am at least
to the point now that I can operate under normal
conditions with reasonable assurance that I am not
going to ruin a recording with drop outs.
This raises some questions. If negative 'nice' greatly
relieves my sound stablility problems, then what does this
say about the origin of the problem. Does it determine
which of the many causes (irq order, pci latency,
kernel preemption, disk throughput, etc..) should be
focused on to further alleviate the trouble?
Also, are there any suggestions as to how to conveniently
make sure that all processes that use the sound driver
run at the higher priority? If 'nice' is to be used,
what is the best way... Shall I run them as root using
nice, or is there another way to automatically cause them
to be -nice, perhaps even when run by normal users?
Thanks,
Tobiah
Paul Davis <paul(a)linuxaudiosystems.com> writes:
> >Then use --with-default-tmpdir=/mnt/ramfs to the JACK configure
> >line when you build it. No clients need to be recompiled.
>
> true, but no clients will be able to find the server.
No. That parameter is passed at *build* time. So, the new directory
gets built into both libjack and jackd.
> this is where the idea of a conf file starts to make sense. all
> clients (and jackd) would look at it to find out where to talk to each
> other.
That would be much cleaner.
--
Jack O'Quin
Austin, Texas, USA
For those of you who don't follow the jack list there was a recent
(semi) discovery htat greatly improves performance for journalled
filesystems.
The main problem is that jack writes data to a /tmp file. It has been
found that mounting /tmp as tmpfs (in RAM) solves the problems that many
people have experienced with lockups while using JACK.
Just put this in your /etc/fstab
none /tmp tmpfs defaults 0 0
I have added this info to the low latency howto also.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
Hi, this is my first posting to this list; I'm a professional musician
(organist) and avid Linux user from the Netherlands.
I want to make good quality recordings with lightweight equipment and to
further process the recordings on my Linux desktop PC.
Currently I own a DCC recorder, but there are no DCC tapes available
anymore. I have some tapes, but they are starting to show problems.
So I'm in the market for some new equipment. I researched quite a lot and
I think there are the following possiblities:
1. Minidisc recording.
consumer minidisc recorders are very compact which is good. But they
almost never have a digital out. Some have USB, but will not function as
an USB-Audio device under Linux (AFAIK, all use the proprietairy NetMD
protocol, which is partially reverse engineered, see:
http://www.marcus-brinkmann.de/freemd.en.html).
so to use most consumer market MD recorders it looks like I have to have a
good audio interface to record the sound from MD to my PC (and still have
it D->A and A->D converted in the process.)
A professional MD recorder which looks very good (the HHB PORTADISC
MDP500, see: http://www.hhb.co.uk/000/int.htm) has an USB interface that
if I understand correctly just manifests itself as an usb audio device
under Windows, and should thus also work with ALSA (?)
so with that recorder I could once record the sound and futher process it
fully digitally. The price is around EUR 1600,= which is quite a lot. My
main concern would be the availability of MD's.
2. Harddisk/flashcard/cd-rw recorders.
It seems these are very expensive now.
3. A laptop with a good (external?) audio interface (M-audio USB?)
Just Linux on it and arecord -f cd full_concert.wav :-)
My question is: What equipment do other people use? Would the HHB MDP500
be a good choice? Will MD stay for another decade? I think it is
important that open standards are used (I feel more confident with usb
audio than e.g. NetMD)
thanks in advance for sharing your thoughts :)
regards,
Wilbert Berendsen
--
Wilbert Berendsen (http://www.xs4all.nl/~wbsoft/)
"You must be the change you wish to see in the world."
-- Mahatma Gandi
On Thu, May 15, 2003 at 09:14:36 +0200, Robert Jonsson wrote:
> Hi Nick,
>
> > I can't imagine what else would cause problems with LADSPA plguins in
> > general on my system. It has to be Yet Another Operator Error somewhere.
> > If these plugins were this bad everyone would be complaining,
>
> I'm sorry I missed the beginning of this thread, are there any specific
> plugins that are acting up?
>
> I think Steve will agree with me if I claim that some of the plugs _are_
> buggy. But with so few bugreports it's difficult to fix. (unless there's some
> LADSPA/swh list I've missed?)
Hey, that's the truth ;) I have got some valuable bug reports from Nick,
but I've yet to fix the problems, thier deep and tedious to fix sadly.
I have been doing a fair bit of plugin hacking recently, I'l make a new
relaese when I've fixed the problem Nick found (flanger IIRC).
Theres done seem to be some SSE2/gcc3 wierdness going on too, I saw a
mention of some related sounding problems in an article somewhere, but I
forgot what the problem they'd found was.
I have been considering a mailing list so I can get consensus on bug
reports, if there are enough interested people I'l set one up.
Another idea (suggested by Dave Phillips) is setitng up a web page where
people can make comments agianst the docs or something, but that involves
me writing the web stuff, Its a great idea but frankly I'd rather put my
efforts into writing plugins. I will get round to it if there aren't
enough people for a list though.
- Steve
> I don't know how the multichannel cards works. I think that using
> OSS emulation you could make something like that:
> stereo channel 1 ---> input device: /dev/dsp
> stereo channel 2 ---> input device: /dev/dsp1
> stereo channel 3 ---> input device: /dev/dsp2
> stereo channel 4 ---> input device: /dev/dsp3
With Audacity (which also uses OSS emulation) you just choose /dev/dsp
and the number of recording channels you want, up to 16.
Unfortunately Audacity 1.1.3 doesn't seem to scale well beyond four
input channels on our machine.
Does tkeca have native ALSA support, or does it use OSS emulation
only?
Thanks
Daniel
Updated README with tip for better performance.
Removed fltk example client from package. This should fix any problems
with building the fltk client.
Taybin Rutkin
Version 2.1.2 of the cost free musical score editor NoteEdit is available:
http://rnvs.informatik.tu-chemnitz.de/~jan/noteedit/noteedit.html
New features:
- ritardando
- accelerando
o to create a audible ritardando (accelerando) simply
place the ritardando (accelerando) between two
different tempo signatures. NoteEdit assumes the ritardando (accelerando)
begins at left tempo signature and ends at right tempo signature
- piano pedal marks
o TiMidity++ users! NoteEdit uses the MIDI PEDAL COMMANDS to play
the pedal on/off signs. Unfortunately, TiMidity++ treats these
commands wrong. Therefore, if you are a TiMidity++ user, it is
recommended to avoid the MIDI PEDAL COMMANDS during replay
(see "configuration section"). Unfortunately, the
pedal on/off signs have no effect in this case :-(
--
J.Anders, Chemnitz, GERMANY (ja(a)informatik.tu-chemnitz.de)