[Musix-usuarios] Sin imprimir de nuevo en 0.40 (buscar en google)
Marcos Guglielmetti Gmail
marcospcmusica en gmail.com
Lun Jun 5 20:07:32 CEST 2006
El Lunes, 5 de Junio de 2006 22:16, Rodolfo Lopez escribió:
> Instalé musix 0,40.
> Rápido, excelente como siempre, en general.
>
> Pensé que acabaría el problema de impresión.
>
> Como dije lo resuelvo solamente instalando como knoppix. Pero surgen otros
> problemas: el módem serial se bloquea.
Ni idea, ¿más datos sobre el modem? ¿has buscado en google información sobre
ese modelo del modem y problemas en sistemas de tipo knoppix, debian, etc.?
> Me gusta siempre instalar tipo debian, porque mi modem no se bloquea y con
> el programa Ext2IFS_1_10b.exe desde windows puedo ver y modificar archivos
> de texto, incluyendo grub, si formateo a ext3.
>
> El problema como ya lo comenté con instalación debian cups no corre.
Podríamos ver qué sucede con cups en ese caso.
> El
> modem serial que uso para internet no tiene problemas.
> Actualicé todo, incluyendo cupsys.
>
> ¿Como puedo correr cups desde la instalación debian? : x
¿Qué error da CUPS si lo corres en consola?
cupsd
(luego busca en Google a ver si ese error le ocurre a otra persona, y reporta
si lograste algo...)
> ¡No quiero ir a windows para imprimir o navegar!
Yo tampoco!
> Otra cosa: respuesta a lo del system timer de rosegarden:
> http://www.rosegardenmusic.com/resources/faq/#toc31
Gracias...
Rosegarden
Home – Tour – Resources – Support – Get Rosegarden
Resources: Tutorial – Documents – Links – Authors – FAQ
14th February, 2006
Release 1.2.3 of Rosegarden-4 is now available!
1st September, 2005
The new release of Fervent Software's Studio to Go!, the easiest way to get
Rosegarden, is available now!
1st July, 2005
The Rosegarden Companion, a book by adjunct developer D. Michael McIntyre, is
released in English.
Supported by
Rosegarden FAQ
1. General questions
1.1. Do I have to be using a particular desktop environment (KDE or
whatever)?
1.2. What are the hardware requirements like?
1.3. Does it support my soundcard?
1.4. Is it available in my language?
1.5. Rosegarden apparently saves in a binary format, where can I find the
format definition ?
2. Compilation or installation problems
2.1. Rosegarden is crashing at startup
2.2. How to get a stack trace for a crash
2.3. Crash at startup with LADSPA plugins enabled
2.4. I'm using RedHat/Fedora version (whatever), what packages do I need to
build this?
3. The Composition View
3.1. How do I set a loop?
3.2. How do I view the track labels?
3.3. How do I change the instrument for a track?
3.4. How do I rename a segment?
3.5. How do I rename a track?
3.6. How do I stop segments from snapping to the nearest beat when I move or
resize them?
3.7. How do I make a composition more than 100 bars long!?
4. Notation and Matrix editing
4.1. Can I get more than one staff at once in the notation editor?
4.2. How do I do something like a two-staff piano part?
4.3. Can I edit all the segments at once in the matrix editor?
4.4. Notation rendering is rather slow
5. Playback and recording
5.1. ALSA? JACK? Huh?
5.2. My soundcard has no built-in MIDI synth and I have no external MIDI
devices. How can I get sound?
5.3. How do I use an ALSA soft synth, such as fluidsynth or Timidity?
5.4. How do I select an Instrument?
5.5. I've selected a synth Instrument but I don't hear any sound
5.6. What does "System timer resolution is too low" mean?
5.7. Only notes at the very start of the composition are played at all
5.8. How do I get audio to work?
5.9. I'm not seeing the right program names for my MIDI device (or any at
all)
5.10. I've followed all your instructions but I still don't hear any sound
6. Improving Performance
6.1. I get drop outs or xruns with JACK. How do I improve performance?
1. General questions
1.1. Do I have to be using a particular desktop environment (KDE or
whatever)?
No. Rosegarden uses the KDE libraries for various common controls, but you can
run it under any window manager or graphical environment you like with no
change in functionality.
1.2. What are the hardware requirements like?
Reasonably demanding, because of the mixture of graphical and interactive GUI
stuff with precisely timed audio stuff. See
http://www.rosegardenmusic.com/getting/requirements) for more details.
1.3. Does it support my soundcard?
Rosegarden uses the ALSA (Advanced Linux Sound Architecture) soundcard
drivers. To find out whether your card is supported by ALSA, see the ALSA
project's soundcard matrix (http://www.alsa-project.org/alsa-doc).
1.4. Is it available in my language?
Translations are included for Russian, German, Spanish, French, Italian,
Estonian, Welsh, Swedish, Dutch, Japanese, simplified Chinese, Czech, and
Catalan.
These translations are provided and maintained by volunteer contributors, and
so they may not always be up to date with the current state of the GUI.
If you can help out with translating musical or technical documentation (no
programming required, but it's quite hard work), please let us know!
See also docs/howtos/i18n.txt in CVS if you are interested in the technical
aspects of translation.
1.5. Rosegarden apparently saves in a binary format, where can I find the
format definition ?
Actually it's just gzipped XML.
gzip has a bit of trouble with gzipped files that don't end in .gz, so the
easy way to have a look is to use
gunzip -c somefile.rg > somefile.xml
2. Compilation or installation problems
2.1. Rosegarden is crashing at startup
Try running up the sequencer by itself first to see if it's a problem with
that or the main part of the program. Run:
$ rosegardensequencer
And you should get a few lines of output finishing with:
RosegardenSequencer - started OK
If the sequencer starts up OK, try to start the main application with the
command line switch "--nosequencer". If that fails, see next question on how
to obtain a stack trace, which you should provide as part of any bug report
you submit.
2.2. How to get a stack trace for a crash
First export the environment variable KDE_DEBUG as follows (in bash):
$ export KDE_DEBUG=1
Start rosegarden from the command line, and reproduce the crash. You should
now have a core file in your current directory. The core file is either
named "core" or "core.<number>". Run gdb :
$ gdb rosegarden <core_file>
Then once you get the gdb prompt, use the command 'where' to get the stack
trace, and mail to the authors or to the Rosegarden development mailing list,
or include in a bug report.
2.3. Crash at startup with LADSPA plugins enabled
If you find that Rosegarden segfaults immediately upon startup, and if when
you run rosegardensequencer by itself as mentioned earlier in this FAQ you
get the following output:
rosegardensequencer: created plugin manager
MappedAudioPluginManager::discoverPlugins - discovering plugins
Segmentation fault
and if you have the Steve W. Harris LADSPA plugins (swh-plugins) installed,
and have Rosegarden compiled with JACK and LADSPA support, then you may have
hit Weird Plugin Startup Crash Bug That We Don't Understand #421.
Check to see if you have the sfftw2 package for your distro installed. The
versions of swh-plugins provided by some distros appear to require sfftw2
instead of fftw2 for some reason, but do not specify it as a dependency,
resulting in a broken set of plugins. If you find that installing sfftw2
fixes the problem, you might also want to submit a bug report to the
maintainer of your distro's swh-plugins package.
2.4. I'm using RedHat/Fedora version (whatever), what packages do I need to
build this?
This is most often asked by someone who's also using GNOME and hasn't built a
KDE application before, in which case the answer is that you need the
kdelibs, kdemultimedia and arts packages (yes, you currently need the arts
package for trivial reasons even if you aren't building aRts support), plus
the -dev versions of all of those.
Note that RedHat 9 didn't ship a recent enough version of ALSA, so if you want
to build on a RedHat 9 system with ALSA support you have to upgrade rather
than using the ALSA packages they supply.
3. The Composition View
3.1. How do I set a loop?
While holding down Shift and and the left mouse button sweep out a loop region
in the ruler at the top or bottom of the main composition window. The loop
icon in the transport will become enabled and playback will always occur
within this loop until you disable it. You can disable the loop by clicking
on the loop icon or shift+left clicking in either loop ruler.
3.2. How do I view the track labels?
On the main window go to Settings->View Track Labels
3.3. How do I change the instrument for a track?
Either click with the right mouse button, or click and hold with the left
mouse button, on the track/instrument label. A pop-up will appear from which
you can choose a new instrument for the track.
3.4. How do I rename a segment?
Click the "..." button next to the segment's name shown in the Segment
Parameters box.
3.5. How do I rename a track?
Double-click on the track label.
3.6. How do I stop segments from snapping to the nearest beat when I move or
resize them?
Hold down the Shift key while you move or resize the segment. (Shift is also
used to enable multiple selection, so sometimes you may have to press Shift
only after you start dragging.)
3.7. How do I make a composition more than 100 bars long!?
A composition has a nominal duration that you can change. Go to Composition ->
Change Composition Duration... and enter the number of bars you'd like.
4. Notation and Matrix editing
4.1. Can I get more than one staff at once in the notation editor?
The Open in Notation Editor option on the main view's Segments menu will open
all the currently-selected segments together in a single editor. So to open
them all, first use the Edit menu's Select All Segments option, then this
one. (You can also edit a subset of segments by selecting them with
shift-click on the main view, then using Open in Notation Editor.)
4.2. How do I do something like a two-staff piano part?
There are various angles to this question, and there's not (yet) any one
perfect answer.
One thing you can't do is make the notation view use more than one staff for a
single segment based on the pitches or other properties of the notes (it's a
possibility under consideration, but not likely in the near future). So you
have to split the segment onto multiple tracks, and then open a multi-segment
notation editor (see the question above this one).
Versions 0.9 and later include a split-by-pitch function (finally!) which you
can use to divide a segment into two parts.
You can also select events within a certain pitch range in the Matrix view:
you can shift-click on a key in the piano keyboard to select all the notes of
that pitch, and you can shift-click and drag to select a range of pitches.
The notes are added to any existing selection, so if you want a clean new
selection, clear any old one first (by clicking in space with the select tool
on the matrix or just hitting Esc).
4.3. Can I edit all the segments at once in the matrix editor?
No. A matrix editor shows a single segment only.
4.4. Notation rendering is rather slow
Yes, it can be. Unlike most other notation applications (including Rosegarden
2.1), we render the full length of each segment to a canvas when the notation
editor starts, instead of rendering sections at a time when it scrolls. This
means scrolling should be smooth and quick but the initial rendering phase
relatively slow. This can be a problem for long segments, although for other
practical reasons you're probably better off dividing long pieces into more
manageable segments anyway.
5. Playback and recording
5.1. ALSA? JACK? Huh?
Rosegarden likes to use the ALSA Linux sound drivers for MIDI communication,
and the JACK low-latency audio server for audio. The build system should
detect which of these you have available.
If you have (or build with) ALSA but not JACK, you will be able to send and
receive MIDI to or from outboard MIDI hardware and other MIDI applications
such as soft synths, but you will not be able to use synth plugins in
Rosegarden, nor to record or play back audio segments or apply effects
plugins.
5.2. My soundcard has no built-in MIDI synth and I have no external MIDI
devices. How can I get sound?
You need a soft synth! See the next question.
5.3. How do I use an ALSA soft synth, such as fluidsynth or Timidity?
Well first, here's how to get fluidsynth working with a soundfont. First get
fluidsynth -- see http://www.fluidsynth.org/. Then find a soundfont: one
reasonable GM example is Musica Theoria 2, available as mustheory2.sf2 from
the Collections area of http://www.hammersound.net/, although it's large and
it's packed using some stupid Windows-only format (common problem -- a few of
the soundfonts on there are only zipped, though, so have a look around).
Then run up fluidsynth with
$ fluidsynth -m alsa_seq ./mustheory2.sf2
or equivalent for whichever soundfont you want to use. Alternatively get hold
of qsynth (URL:http://qsynth.sourceforge.net/> which provides a nice GUI for
fluidsynth.
If you're relatively short on CPU power, also give it "-R no" to turn off
reverb and you'll get a bit more polyphony before it breaks up. (If you're
very short on CPU power, forget it.) You may find you have to run it as root
or else the pitch goes awry, particularly on laptops with variable-speed
CPUs.
Anyway, when fluidsynth is running you should be able to assign tracks to it
in Rosegarden. To set a track to one of the soft-synth instruments,
right-click on the track label at the left of the track until the instrument
menu appears and select the instrument on there. (If you have no other MIDI
devices at all, then the soft-synth should be the default device.)
You can also use Timidity as an ALSA soft-synth with soundfonts. Run it in
ALSA input mode:
$ timidity -iA
You can also use Timidity to play to JACK with reasonably low latency, with
some magic incantation like:
$ timidity -iA -Oj -B2,8
In my experience it takes rather more CPU power than fluidsynth for rather
lower-quality output, though I'm sure these things vary a lot depending on
how the soundfont is made.
5.4. How do I select an Instrument?
You can check which Instrument is selected for your Track by making sure that
Settings->Show Track Labels is unchecked. You can change Instrument for a
Track by right-clicking or clicking and holding on the Track/Instrument
label. A pop up menu will appear from which you can select a different output
Instrument. Rosegarden automatically assigns the first available synth device
on your soundcard for its default output Instrument when importing MIDI
files.
5.5. I've selected a synth Instrument but I don't hear any sound
If you're hearing silence with a Synth device (say "Emuk10k1 Port 0" or "OPL
3") then make sure you've loaded a soundfont for your soundcard. To load
soundfonts use the "sfxload" utility. For example the Creative SBLive!
soundcard comes with a set of standard soundfonts (2gmgsmt.sf2, 4gmgsmt.sf2,
8mbgmsfx.sf2) and you can load the 8MB soundfont as follows:
$ sfxload 8mbgmsfx.sf2
For more fun with soundfonts including how to create them for yourself have a
look at the Smurf/Swami project: http://swami.sourceforge.net/.
The other classic problem for new users of ALSA is that the mixer settings are
either zero or muted. Run alsamixer and check that your levels are okay and
unmuted. (Muting is displayed and changed separately from the levels
themselves: you can be on 100% but still muted.)
5.6. What does "System timer resolution is too low" mean?
If you see this message in an error dialog when Rosegarden starts up, then you
are probably using a Linux kernel that doesn't offer sufficiently
high-resolution system timers for MIDI use.
Rosegarden uses ALSA sequencer queue scheduling (inside the Linux kernel) for
its MIDI output. The sequencer queue can use a variety of timing sources, of
which the default is the kernel system timer. The kernel system timer was
1000Hz in Linux 2.6 kernels up to 2.6.12, but as of 2.6.13 it's now 250Hz in
mainline kernels. This is not good enough for good MIDI timing.
Your options are:
1. Switch the sequencer to use a different timing source (Settings ->
Configure Rosegarden... -> Sequencer -> Synchronisation). The best one in
theory is the RTC timer, which is only available if you have snd-rtctimer
loaded, but unfortunately that has a habit of totally locking systems running
real-time kernels. Meanwhile, the PCM timers only work if the JACK audio
server is running, and suffer jitter corresponding to the JACK buffer size.
2. Recompile your kernel with HZ set to 1000. Sadly there's no way to
change this without a recompile. It's the best solution though.
3. Switch to a different Linux distribution that provides a kernel more
appropriate for multimedia use.
4. Put up with the poorer timing of a 250Hz timer (if you want to get rid
of the warning while continuing to use this timer, set the timer source
to "system timer" rather than "(auto)").
Hopefully future versions of Rosegarden and/or the Linux kernel will provide
better ways to solve this problem.
5.7. Only notes at the very start of the composition are played at all
If Rosegarden plays notes at time zero but then gets stuck and doesn't play
anything else afterwards, you might have a non-running sequencer timer
selected.
Try going to Settings -> Configure Rosegarden... -> Sequencer ->
Synchronisation and changing the "Sequencer timer" setting.
5.8. How do I get audio to work?
If you're using ALSA, then you need to obtain and install JACK
(http://jackit.sourceforge.net/) and run jackd before starting the Rosegarden
sequencer. If you give jackd the -v option, it will report when Rosegarden
succeeds in connecting to it.
Unfortunately getting the right combination of magic incantations to make JACK
work is not always easy. Good values for an SBLive and indeed on the built-in
via868 on my Acer laptop as follows:
$ jackd -d alsa -d hw -r 44100 -p 2048 -n 2
This will usually ensure that I don't get any xruns (JACK being unable to
process audio in time) and provide reasonable latency. The '-r 44100' option
sets the sample rate for the JACK server which will in turn define the rate
at which WAV audio files will be recorded. This is important if you want to
transfer any of the WAVs directly to CD - 44100Hz (44.1KHz) is the sample
rate that audio CDs work at.
5.9. I'm not seeing the right program names for my MIDI device (or any at
all)
Rosegarden has an internal Studio to map your MIDI Program Change information
into meaningful instrument labels. You need to set this up do this mapping in
the MIDI device manager (Studio->Manage MIDI Devices->Banks or Import). Once
you've made changes in your current Rosegarden file you can save it as a
default studio (replacing your autoload.rg file) so that all your subsequent
sessions in Rosegarden utilise your specialised Studio settings.
5.10. I've followed all your instructions but I still don't hear any sound
If you've done everything we've suggested above then you can check what
devices the sequencer is seeing by running the Rosegarden sequencer up by
itself. Try:
$ rosegardensequencer
and examine the output of the screen. The output for JACK and ALSA for an
SBLive! should look something like this:
rosegardensequencer: created plugin manager
MappedAudioPluginManager::discoverPlugins - discovering plugins
Rosegarden 4-0.9 - AlsaDriver - alsa-lib version 0.9.3
AlsaDriver::jackSampleRate - sample rate changed to 44100
AlsaDriver::createJackInputPorts - adding input port 1
AlsaDriver::createJackInputPorts - adding input port 2
AlsaDriver::createJackInputPorts - getting ports
AlsaDriver::createJackInputPorts - found 2 JACK physical inputs
AlsaDriver::createJackInputPorts - connecting from "alsa_pcm:capture_1"
to "rosegarden:in_1"
AlsaDriver::createJackInputPorts - connecting from "alsa_pcm:capture_2"
to "rosegarden:in_2"
AlsaDriver::initialiseAudio - JACK sample rate = 44100Hz
AlsaDriver::initialiseAudio - added output port 1 (left)
AlsaDriver::initialiseAudio - added output port 2 (right)
AlsaDriver::initialiseAudio - found 2 JACK physical outputs
AlsaDriver::initialiseAudio - connecting from "rosegarden:out_1"
to "alsa_pcm:playback_1"
AlsaDriver::initialiseAudio - connecting from "rosegarden:out_1"
to "alsa_pcm:playback_2"
AlsaDriver::initialiseAudio - JACK playback latency 0.092879R
AlsaDriver::initialiseAudio - JACK record latency 0.046439R
AlsaDriver::initialiseAudio - initialised JACK audio subsystem
ALSA Client information:
64,0 - (Rawmidi 0 - EMU10K1 MPU-401 (UART), EMU10K1 MPU-401 (UART))
(DUPLEX) ctype 2, ptype 2, cap 127
65,0 - (Emu10k1 WaveTable, Emu10k1 Port 0) (WRITE ONLY) ctype 2,
ptype 2078, cap 66
65,1 - (Emu10k1 WaveTable, Emu10k1 Port 1) (WRITE ONLY) ctype 2,
ptype 2078, cap 66
65,2 - (Emu10k1 WaveTable, Emu10k1 Port 2) (WRITE ONLY) ctype 2,
ptype 2078, cap 66
65,3 - (Emu10k1 WaveTable, Emu10k1 Port 3) (WRITE ONLY) ctype 2,
ptype 2078, cap 66
Creating device 0 in Play mode for connection 65:0 Emu10k1 Port 0 (write)
Default device name for this device is MIDI soundcard synth
Creating device 1 in Play mode for connection 65:1 Emu10k1 Port 1 (write)
Default device name for this device is MIDI soundcard synth 2
Creating device 2 in Play mode for connection 65:2 Emu10k1 Port 2 (write)
Default device name for this device is MIDI soundcard synth 3
Creating device 3 in Play mode for connection 65:3 Emu10k1 Port 3 (write)
Default device name for this device is MIDI soundcard synth 4
Creating device 4 in Play mode for connection 64:0 Rawmidi 0 - EMU10K1
MPU-401 (UART) (duplex)
Default device name for this device is MIDI external device
Creating device 5 in Record mode for connection 64:0 Rawmidi 0 - EMU10K1
MPU-401 (UART) (duplex)
Default device name for this device is MIDI hardware input device
Record client set to (64, 0)
AlsaDriver::initialiseMidi - initialised MIDI subsystem
rosegardensequencer: RosegardenSequencer - started OK
Note the ALSA device list shows the external MIDI port and the wavetable
on-board synth devices. If you're using a soft synth, you should see it here
too. All of these will be available in the drop-down Instrument list inside
Rosegarden.
If you're using a recent version of Rosegarden-4 (0.9 or greater) then you can
also access this sequencer status information by using the application
itself. Go to:
Settings->Configure Rosegarden->Sequencer->General->Show detailed status
6. Improving Performance
6.1. I get drop outs or xruns with JACK. How do I improve performance?
The short answer to this is with care and with some luck. There are various
recipes for improving JACK performance. Some are more labour intensive than
others. Ask on the rosegarden-user and rosegarden-devel lists for the latest
advice and also keep an eye on jackit-devel for more JACK tips.
--
Marcos Guglielmetti
* Director del desarrollo de Musix GNU+Linux, 100% Software Libre
* Descarga el CD de Musix: (www.musix.org.ar) (www.pc-musica.com.ar/musix)
* Videos, programas y otras cosas en: ftp://musix.ourproject.org/pub/musix/
* Reporte de errores a:
https://www.musix.org.ar/wiki/index.php?title=Problemas-Bugs
Más información sobre la lista de distribución Musix-usuarios