On Thu, Apr 06, 2006 at 05:09:27PM -0400, linux-audio-user-request(a)music.columbia.edu wrote:
> Date: Thu, 6 Apr 2006 23:07:39 +0200
> From: Wolfgang Woehl <tito(a)rumford.de>
>
> Chris McCormick <chris(a)mccormick.cx>:
> > <http://www.sciencegirlrecords.com/chr15m/music/CD004/searc
> >h_and_rescue.mp3>
>
> a master at that. What will you do now?
Optimise, explore, iterate.
Thank you very much for listening!
Best,
Chris.
-------------------
chris(a)mccormick.cx
http://mccormick.cx
Hello,
I've been trying to work with a very large MIDI file (over 420 bars and
50 tracks) and I found some problems with both Muse and Rosegarden (both
in their latest released versions).
First, Muse seems to go faster in tempo than what is set in the midi
file. To test this, I imported the same file in both programs and set
both to sync with jack and started playback. After some time Muse was
ahead of Rosegarden. Why is this happening? Both are set to the same
tempo (I have Rosegarden set to sync to the system timer). Beside this,
I found, in Muse, that some notes in one instrument were imported with
longer duration.
Second, Rosegarden crashes when I scroll horizontally through this large
file. It doesn't matter if I do it fast or slow, I just have to keep
scrolling for some seconds and then it will crash and make the X server
to restart. If I manage to get beyond bar 320, I find that the display
gets corrupted and the segment boxes disappear but the midi notes are
still being drawn (it looks like the notes keep going outside the
boundaries of the segment container). I found the same problem in
previous versions of Rosegarden and it's present using two different
distro versions (I tested in Ubuntu Breezy and Dapper).
So, these problems made both programs unusable for this particular
project... I wonder if anyone suffered of the same or have any idea how
to solve this problems. Any help will be very appreciated!
Thanks!
Hector.
Hello!
I'm planning to get RME Multiface (II) and have a question to it's owners.
Can you, please, post its latency in audio loop, measured with jaaa in
2x64 buffer setup.
Thank you.
Regards,
Dmitry.
This is a serious request.
I've goofed up my Linux (currently AGnuLa/DeMuDi) flavor, and will
have to reinstall. I have Debian Sarge and Mandrake 9.1 as well.
I am asking our German constituent what flavor of Linux they prefer.
I'm on dialup and it takes around 2 days to download 1 ISO CD from
the Internet.
I'll be using KDE and Muse; other music applications as I become
familiar with them.
Germany, what distro do you use?
Thank you,
Stephen.
On 4/5/06, Loki Davison <loki.davison(a)gmail.com> wrote:
> On 4/4/06, Dave Griffiths <dave(a)pawfal.org> wrote:
> > > G'day All,
> > >
> > > The first release of Khagan is now out!
> > >
> > > Khagan is a live user interface builder for controlling parameters via
> > > OSC. It's mainly aimed at the Om modular synth but anything OSC can be
> > > controlled. You can create gui's using the phat widgets. The pad
> > > widget is xinput ready and if used with a graphics tablet allows 5-d
> > > control.
Khagan 0.1.1 out now. Some how one of the glade entries had renamed
itself making pad editing no longer work. Fixed now. Few minor feature
additions too.
Loki
Greetings all;
Has anyone a url where I might be able to purchase the expansion
interface gizmo for an Audigy 2 value card?
Thanks.
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Well after some thought I decided to give my website a tidy up. Also
investigating ogg, mp3 etc. players and converters I realised there is
more out there than I thought. With that in mind I have begun the
oggification of my music, and just put a link to information for my
friends who use a 'different' OS - not that anyone here will need it!
In the process I've made a few tweaks (I can never resist the urge to
fiddle) and there are some new tracks as well. Some are just musical
'toys' others, such as 'Dreamer' more serious - if that's the right
word. There *shouldn't* be any problems with the site. If there are
please let me know.
As usual the website is http://www.folderol.ukfsn.org
Enjoy.
--
F
ftp://andrei.myip.org/midisport/
The binary packages were built on Fedora Core 5. The src.rpm packages
should rebuild cleanly on most RPM-based systems, I suppose.
The spec files used to generate them were slightly hacked from the
original ones.
Works For Me (TM) on Fedora 5 with M-Audio Midisport 4x4
--
Florin Andrei
http://florin.myip.org/
I open up CD master, choose audio > edit > insert file
but when I browse to add a wav file I get no response. The menu shows the
files and allows me to choose the file but the screen does not progress
beyond the insert file. I just have to cancel out of it.
Is this a bug or am I doing something wrong?
--
View this message in context: http://www.nabble.com/Problem-creating-an-audio-CD-with-Gnome-CD-Master-t14…
Sent from the linux-audio-user forum at Nabble.com.
( LAU folk: this is an initial outline of an email I want to dispatch to
the desktop-architects list in the very near future. Your comments
are eagerly sought. Note that this section specifically seeks to
avoid any discussion of implementations or specific approachs. I
would like to fully flesh out the list of tasks ASAP )
Making Sound Just Work
------------------------
One of the "second tier" of requirements mentioned several times at
the OSDL Portland Linux Desktop Architects workshop was "making audio
on Linux just work". Many people find it easy to leave this
requirement lying around in various lists of goals and requirements,
but before we can make any progress on defining a plan to implement
the goal, we first need to define it rather more precisely.
DEFINING THE GOAL
=================
The list below is a set of tasks that a user could reasonably expect
to perform on a computer running Linux that has access to zero, one
or more audio interfaces.
The desired task should either work, or produce a sensible and
comprehensible error message explaining why it failed. For example,
attempting to control input gain on a device that has no hardware
mixer should explain that the device has no controls for input gain.
PLAYBACK
- play a compressed audio file
* user driven (e.g. play(1))
* app driven (e.g. {kde,gnome_play}_audiofile())
- play a PCM encoded audio file (specifics as above)
- hear system sounds
- VOIP
- game audio
- music composition
- music editing
- video post production
RECORDING
- record from hardware inputs
* use default audio interface
* use other audio interface
* specify which h/w input to use
* control input gain
- record from other application(s)
- record from live (network-delivered) compressed audio
streams
MIXING
- control h/w mixer device (if any)
* allow use of a generic app for this
* NOTE to non-audio-focused readers: the h/w mixer
is part of the audio interface that is used
to control signal levels, input selection
for recording, and other h/w specific features.
Some pro-audio interfaces do not have a h/w mixer,
most consumer ones do. It has almost nothing
to do with "hardware mixing" which describes
the ability of the h/w to mix together multiple
software-delivered audio data streams.
- multiple applications using soundcard simultaneously
- control application volumes independently
- provide necessary apps for controlling specialized
hardware (e.g. RME HDSP, ice1712, ice1724, liveFX)
ROUTING
- route audio to specific h/w among several installed devices
- route audio between applications
- route audio across network
MULTIUSER
- which of the above should work in a multi-user scenario?
MISC
- use multiple soundcards as a single logical device