Hi,
because audio on linux is still a complicated thing for normal
users, and people like to watch videos with a glass of beer
in their hand, I thouht it would make sense to make some
tutorial videos.
I put the first one here:
http://sysexxer.sf.net/files/LinuxAudioBasics.avi
On Mac or Win you should use VLC to play the video; media
player or quicktime do not play the video by default.
I have read the thread about the free music page, the same
problem with the videos: if there were some of them, it needs
webspace and bandwidth, so I do not know if I can make it a
successful project.
What I'm interested in is:
* is the video technically correct, or did I teach somethnig
completely wrong (I'm still a newbie to linux audio)?
* is it helpful for non-experienced users?
* do you think something like this should be done, or is it a
useless waste of time?
I can think of a lot further videos concerning linux audio as
well as other aspects of a linux system.
Any comments are really welcome, mainly the negative
ones ;-) .
Have fun,
ce
>>>qjackctl connections window shows alsa_pcm->capture_1
>>>and capture_2, which are connected to things in Ardour,
>>>but not qaRecord.
>>
>>
>> Well... you're not going to capture anything with qaRecord unless you
>> patch the alsa capture intputs to it.
>>
>> In Ardour, do you have the tracks to capture you input armed? Hitting
>> the record button doesn't do anything if none of the tracks are armed.
>>
>
>Thanks for the reply.
>
>If I connect alsa_pcm:capture_1 or _2 to qaRecord:in_0 or in_1, then
>something shows up in the level monitor in qaRecord, but hovers down at
>-80dB and doesn't change regardless of the input.
>
>In Ardour: I start a new project, add an new track "Audio 1", click the
>button "INPUT" which gives me "in 1" or "in 2", so I choose "in 1".
>Then, press track's RECORD button and it turns pink. Then press record
>button, press play and send sound into mic and line-in. This does not
>seem to produce anything.
The -80dB is probably the noise floor. Either that or you have things turned down so low it is barely getting a faint signal. Run alsamixer and make sure the channels you are recording from are turned up and/or unmuted.
Beyond that I can't help you much. SB cards are an absolute nightmare. Perhaps somebody else on this list who has a SB card can offer more help. The Alsa Wiki can sometimes help.
-Reuben
BEAST/BSE version 0.6.4, BSE-ALSA version 0.6.4 and BSE-PortAudio
version 0.6.4 are available for download at:
ftp://beast.gtk.org/pub/beast/v0.6/
or
http://beast.gtk.org/beast-ftp/v0.6/
This is a development version of BEAST/BSE, the BEdevilled Audio SysTem
and the Bedevilled Sound Engine. BEAST is a powerful music composition
and modular synthesis application released as free software under the
GNU GPL and GNU LGPL, that runs under unix. BSE-ALSA is an ALSA driver
and BSE-PortAudio is an experimental PortAudio driver for BSE.
The project is hosted at:
http://beast.gtk.org
A mailing list is available at:
http://mail.gnome.org/mailman/listinfo/beast/
GUI skins, example sounds and instrumets for BEAST/BSE as well as
screenshots can be found at:
http://beast.gtk.org/browse-bse-files.htmlhttp://beast.gtk.org/screenshots/index.html
This new development series of BEAST comes with a lot of the internals
redone, many new GUI features and a sound generation back-end separated
from all GUI activities.
Outstanding new features include support for skins, many sample
file formats, MIDI file import abilities, an improved piano roll
widget, the track editor which allows for easy selection of
synthesisers or samples as track sources, loop support in songs,
mixer support, unlimited Undo/Redo capabilities and MIDI automation.
Overview of Changes in BEAST/BSE 0.6.4:
* Fixed storage logic that caused data loss when overwriting BSE files
* Added -N and -n=<nicelevel> options to drop nice level priorities
* Removed libbsw from package, glue code is inlined now
* GCC-3.4 build fixes
* Fixed high CPU consumption on scope updates
* Added spectrogram view for module outputs
* Minor GUI fixups and miscellaneous other buglet fixes
* Updated Canadian English translation [Adam Weinberger]
* Updated British English translation [David Lodge]
* Updated Czech translation [Miloslav Trmac]
* Updated Dutch translation [Tino Meinen]
* Updated Spanish translation [Jorge Gonzalez]
Overview of Changes in BSE-ALSA 0.6.4:
* Build fixes.
Initial Release of BSE-PortAudio 0.6.4:
* Provide a PortAudioV19 PCM driver for BSE
--
-* Stefan Westerfeld, stefan(a)space.twc.de (PGP!), Hamburg/Germany
KDE Developer, project infos at http://space.twc.de/~stefan/kde *-
>Great. Btw: does anyone know exactly what framerate non drop 30 fps
>MTC has? Should i really send with 29.97 fps?
For NTSC, yes. The frame rate has to do with the frequency used by the AC power grid. In the US, the frequency is a little under 60HZ (59.94HZ). TVs were designed so that each scan would coincide with the AC cycle. Since the TV signal is interlaced, it scans twice for each frame. That's how we get the frame rate of 29.97. In Europe, the power grid configuration is so much better, the power output is more consistant and the frequency drifts less. It also runs at 50HZ, hence the PAL framerate of 25fps.
Just a bit of useless trivia for you. :)
-Reuben
On Friday 17 December 2004 23:19, linux-audio-user-request(a)music.columbia.edu
wrote:
> > >This is being offered gratis till the end of december by Mackie. This
> > > one
> >
> > might just be coaxed into running under Wine which would be quite an
> > achievement.
> >
> > >Kudos: 1. The program, though free, needs be registered to a "machine
> >
> > number". Did this under Windows, did not get that far using Wine. Might
> > need a second copy just for the Linux runs.
>
> was able to do all this with only the latest version of wine - no
> windows partition involved.
If the dialogs work, registration should work. My concern is being able to use
one copy alternatively in Windows AND in Linux once that works. I will
request a second key once I have the dialogs up.
>
> > >2. The program searches for all its own VST dlls and any on the VST
> >
> > directory. Might have problems doing this in Wine. Some VST demos bring
> > up an error box saying please register, limited trial, etc. Such things
> > may be disruptive in Wine. (Other VST hosts let you manually find them
> > when you want them, avoiding this problem in most cases)
> >
> > >Anyway, the thing appeared to hang up but I was able to get out. No
> > > crash, no
> >
> > bebug offer. Clean.
>
> it scanned all the vst plugins in my vst directory (which is in my fake
> windows drive) except for one steinberg grm tools one, which crashed it,
> but on next boot, it said it had disabled it due to a problem :) all
> the vst's that it successfully scanned are available from within an open
> project - and all their gui's display correctly in tracktion ...
Yes, it does. When I ran from the windows directory, it scanned them but hung
on those with the warnings. They were disabled the next run which is normal
Tracktion functionality I suppose.
>
> > The main problem is that any UI pop-up, i.e. to choose files, etc., does
> > not come up visibly. This is the apparent hangup. Alt-F4 dismisses the
> > invisible dialog box.
>
> this is not a problem for me - all dialogue boxes work as expected. in
> fact,
Now .. what do you do which is different? I have a dual boot system with Win98
and Linux partitions. I am running Debian, Wine from Sid.
> > It audio output device is listed as "direct sound" (under Windows, the
> > card's ASIO drivers would be listed).
> >
> > But .. one would not get anywhere near this far with Sonar.
>
> everything seems to work EXACTLY as required, except for a working sound
> device ... i too get "directsound" listed in the audio setup, but no
> sound devices are listed ... i might try messing with the sound settings
> in winecfg to see if i can get a wine audio device listed ...
I have only had audio play with the OSS selected in Wine's config. Plays
through ALSA's OSS compatibility layer, I suppose. Selection ALSA or Jack has
not worked for me.
>
> when i was using windows, i used tracktion quite a bit, and was really
> impressed by its interface and usability - plus it's got an interesting
> approach to layout/structure ..
Yes, this program looks interesting. Interface is eccentric. Does it do
mix-automation--I like Sonar's graphical controur control fo this since
moused mixer panels just do not cut it.
>
> anyone else want to test this as well, see if they can get it going?
Keep us all posted :-)
Hi
I did a test to get some actual numbers on my latency controlling csound
from midi in real time: I hooked up a mic to capture the sound of the
key hitting the buttom of the keyboard. I then made a simple csound
patch with instant attack. Recorded both on my computer one on the left
one on the right channel. Then I opened a soundeditor and measured the
time between the two.
I was able to go down to 0.014 s. It feels pretty snappy, but it *looks*
like a lot. What can you guys achieve with a similar test? And what
would be typpical of commercial hardware synths?
My setup is:
*p4 2.4G laptop
*debian/unstable
*stock kernel 2.6.9
*edirol ua-1a usb soundcard
*evolution MK-249C keyboard
--
peace, love & harmony
Atte
http://www.atte.dk
Hi,
i have written a small MTC generator that sends MTC via alsa_seq. It is
based on the RTC running at a frequency of 8192hz (this introduces
systematic jitter) and currently only sends 30 FPS (nodrop? i think :)
It seems to perform fine on my 2.6.x RP kernel (with the RTC irq at
highest prio above soundcard irq (jackd with ardour running at prio 60)).
Here's the webpage (with tarball):
http://www.affenbande.org/~tapas/wiki/index.php?rtc_mtc_gen
Maybe someone finds it useful. Let me know what you think.
Is there any software other than ardour on which i can try it? I don't
have any hardware here that speaks MTC either..
Flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
On Fri, 17 Dec 2004 16:06:42 -0800 (PST), Hiji <hijinio(a)yahoo.com> wrote:
> On a side note, it's good to see more and more audio
> people trying out Wine!! :)
>
> Hijinio
Someone ripped me a new one 2 years ago when I suggested using Wine.
Now many of us do. It really adds value - when it works... ;-)
Cheers,
Mark
This is being offered gratis till the end of december by Mackie. This one
might just be coaxed into running under Wine which would be quite an
achievement.
Kudos: 1. The program, though free, needs be registered to a "machine number".
Did this under Windows, did not get that far using Wine. Might need a second
copy just for the Linux runs.
2. The program searches for all its own VST dlls and any on the VST directory.
Might have problems doing this in Wine. Some VST demos bring up an error box
saying please register, limited trial, etc. Such things may be disruptive in
Wine. (Other VST hosts let you manually find them when you want them,
avoiding this problem in most cases)
Anyway, the thing appeared to hang up but I was able to get out. No crash, no
bebug offer. Clean.