Hi Juan
>Hi, I basically write this because i'm pretty frustrated
>Today I wanted to learn how to use a typical sequencer
>(I mantain my own midi sequencer, but it's not very typical)
>I simply wanted a sequencer that supports a track editor
>and a pianoroll.
>
>So I went and checked some. Tried to see if I could
>get stuff done with any of them, so In order of what I tried,
>I'll list them here in the order I used them:
>
..snip..
>
>MUSE:
>
>This one looked pretty good at the begining, but
>some things I dont like. First of all, it didnt detect
>the midi devices properly, as i had to go and reset
>them in the midi ports menu.
>
I guess you are talking about external midi devices?
>MIDI input worked
>some times, and some others it didnt, and the
>overall interface is pretty UNintuitive. Many
>essential parts of the program lack proper shortcuts,
>and the ability to customize them (like rosegarden).
>I spent the most time with MUSE, trying to figure
>out how to do things. In most cases it took me a while
>but it wasnt bad, just strangely organized (like the track
>menu, the way you add tracks, the master tempo).
>The pianoroll looks good, but it lacks a lot of keyboard
>support, and also Painting events doesnt seem to be
>working, as i cant paint no matter how much I try.
>Documentation is too basic to learn how to use the
>program efficiently. It also crashes a lot, but
>on more specific situations.
>
MusE has always been the platform I've favoured, and with the current
status of things I don't think this will change anytime soon.
Considering your critisism I realise that you are probably right about
alot of usability issues, I've used it too long, I no longer think about
the quirks it has ;).
I understand though that it can be a major obstacles for new users
(together with lacking documentation).
I'd be very happy for any suggestions you might have about usability
enhancement (or anything else for that matter). You mentioned for
instance keyboard shortcuts and customizability which is duly noted (and
master tempo which is a long standing usability problem). You mentioned
trouble to do certain things, do you remember if there where other
"things" than those mentioned?
If you have more, please send it along.
Of course that goes for others also!
Regards,
Robert
> Something we've noticed is that aconnect is seeing
> ports 0 -> 8. Of course that would appear to be nine
> i/o ports. Is that correct?
I think one port is for SMPTE, so it seems
to be correct.
Regards,
J.Backhaus
>
> --- Clemens Ladisch <clemens(a)ladisch.de> wrote:
> > R Parker wrote:
> > > Do you see any advantage to using a pci card or
> > usb;
> > > is interupt overhead lower in one or the other,
> > etc,
> > > etc,?
> >
> > USB has a latency of 1ms due to the frame-based
> > communications, the
> > latency on the PCI bus is certainly lower.
> >
> >
> > HTH
> > Clemens
> >
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
hi, i'm a recent linux user, coming from mac universe. i started by
putting YDL on one of my old macs last summer, but now i'm gonna get
serious.
so my question is: what parts would you recommend for making a Linux
box to run audio on? i realize this is a big field, but any clues are
helpful.
also, i'm probably going to use redhat, given that my ydl exprerience
is based on redhat. any precautionary measures?
thanks all
--
_________________________________________________________________
Jonathan Segel -- MAGNETIC -- PO Box 460816 S.F. CA. 94146-0816
4014 Brookdale Ave. Oakland, CA 94619
jsegel(a)magneticmotorworks.com <-----> magsatellite(a)yahoo.com
http://www.MagneticMotorworks.com
tel (510) 534 7825 cell (510) 484 7415 fax (425) 955 4495
Patrick Shirkey wrote:
Sorry I missed the refernce to lockup in the previous note. It should be
replaced with "xruns".
> So this is the revised version. Antti - could you add this to the jack
> FAQ and I will link to it in the low latency howto.
>
>
>
> To reduce the audio buffer overruns while using JACK under certain
> conditions. It has been found that mounting /tmp/jack as tmpfs (in RAM)
> solves the problems that many people have experienced with LOCKUPS << here
> while using JACK.The solutions mentioned above (and below) help when
> your /tmp directory is mounted on a journalled filesystem.
>
> Just put this in your /etc/fstab
>
> none /tmp/jack tmpfs defaults 0 0
>
> There is also a compile option to enable JACK to place its FIFOs on a
> ram-based filesystem follows:
> ---------------------------------------------------------------
> # mkdir /mnt/ramfs
>
> [edit /etc/fstab and add the following line]
> none /mnt/ramfs tmpfs defaults 0 0
>
> Then use --with-default-tmpdir=/mnt/ramfs to the JACK configure
> line when you build it. No clients need to be recompiled.
> ----------------------------------------------------------------
>
>
--
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 to all,
I was just checking the Macintosh USB iMic using ALSA-USB-driver. The device
gets recognized but I don't get sound from it.
Does anyone have experience with it and knows where the trouble could be ?
Gracias
-- A l e x
Hi, I basically write this because i'm pretty frustrated :)
Today I wanted to learn how to use a typical sequencer
(I mantain my own midi sequencer, but it's not very typical)
I simply wanted a sequencer that supports a track editor
and a pianoroll.
So I went and checked some. Tried to see if I could
get stuff done with any of them, so In order of what I tried,
I'll list them here in the order I used them:
Rosegardern (KDE version):
This program looks very, very nice and professional, It
makes a lot of sense to me when I use it, and the keyboard
support is fantastic and intuitive. It detected my midi devices
and got them ready to work automatically, but
unfortunatedly, but some things I dont understand
very well, and the documentation isnt very detailed
Also, the pianoroll doesnt seem to be nearly as
worked on as the staff sheet editor. What
turned me out of this program is mainly
that it's very, VERY unstable. A lot of things
I try to do get it to crash almost instantly.
I suppose i'll wait a while until it becomes more usable.
MUSE:
This one looked pretty good at the begining, but
some things I dont like. First of all, it didnt detect
the midi devices properly, as i had to go and reset
them in the midi ports menu. MIDI input worked
some times, and some others it didnt, and the
overall interface is pretty UNintuitive. Many
essential parts of the program lack proper shortcuts,
and the ability to customize them (like rosegarden).
I spent the most time with MUSE, trying to figure
out how to do things. In most cases it took me a while
but it wasnt bad, just strangely organized (like the track
menu, the way you add tracks, the master tempo).
The pianoroll looks good, but it lacks a lot of keyboard
support, and also Painting events doesnt seem to be
working, as i cant paint no matter how much I try.
Documentation is too basic to learn how to use the
program efficiently. It also crashes a lot, but
on more specific situations.
Brahms:
Totally wicked interface, and I _hate_ the fact that relies on ARTS,
It seems pretty basic, so I didnt give this much of a chance,
didnt detect a simple thing (midi/audio).
JAZZ++
Saw some screenshots, looked-like-motiff. Didnt even want to try it.
In short, I didnt find anything I could use and be efficient with.
Since the last time I evaluated this software, probably a year
ago, I saw several improvements on each, and the addition
of a lot of new features. Feature-wise, I can easily say
that rosegarden and muse are way ahead of programs
such as cubase or cakewalk from not more than 2 or 3 years ago,
but I think their main problem is consistency and lack of documentation
on "how to use this" and "how to use this efficiently".
So I propose something, i dont know if anyone
writes professional music with these.
Does anyone use such programs at all
Could you post project files for these,
and would you like to explain in brief
how do you use them efficiently?
Thanks and my apoligies if i said something being
misinformed.
Cheers!
Juan Linietsky
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