Hi;
Alsa seems unable to find my audio analog chip set; put another way I
can't get any sound from analog cable tv with tvtime -- apparently
because alsa is not providing the sound. The TV video is great.
On the other hand, mplayer /dev/video1 gives me good sound but a
distorted picture.
If this sounds wishy-washy, it is because over the last several days I
have visited so many mailing lists (other that this one) and received so
much advice that even the few things I thought I knew about sound and
sound hardware has become very confused.
Succinctly, my problem is:
I have an integrated Audio Controller on a Gigabyte GA-G31M-ES2L
motherboard with PCIe bus:
product: 82801G (ICH7 Family) High Definition Audio Controller
[8086:27D8]
vendor: Intel Corporation [8086]
bus info: pci@0000:00:1b.0
version: 01
width: 64 bits
clock: 33MHz
capabilities:
Power Management,
Message Signalled Interrupts,
PCI Express,
bus mastering,
PCI capabilities listing
configuration:
driver: HDA Intel
latency: 0
resources:
irq: 16
memory: e5300000-e5303fff
]$ lsmod | grep hda
snd_hda_codec_realtek 265060 1
snd_hda_intel 29000 0
snd_hda_codec 65376 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 8600 1 snd_hda_codec
snd_pcm 79352 2 snd_hda_intel,snd_hda_codec
snd 65096 6
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_\
hwdep,snd_pcm,snd_timer
]$ lspci -vv
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 01)
Subsystem: Giga-byte Technology Device a002
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e5300000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
]$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xe5300000 irq 16
The TV tuner I am using is a:
Hauppauge_WinTV-HVR-1800
This card features:
* NXP/Philips TDA18271 (tuner for analog)
* Microtune MT2131 (tuner for digital)
* NXP/Philips TDA8295 (analog IF demodulator)
* Samsung S5H1409/Conexant CX24227 (digital demodulator)
* Conexant CX23417 (MPEG-2 encoder)
* Elpida (RAM)
• Conexant CX23887 (A/V Decoder & PCIe bridge)
/lib/firmware has
v4l-cx23885-avcore-01.fw
v4l-cx23885-enc.fw
The TV tuner and sound card do not seem to be communicating.
/etc/udev/rules.d/90-alsa.rules include
ACTION=="add", SUBSYSTEM=="sound", KERNEL=="controlC*", \
RUN+="/sbin/alsactl -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf
--initfile=/lib/alsa/init/00main restore /dev/$name"
ACTION=="remove", SUBSYSTEM=="sound", KERNEL=="controlC*", \
RUN+="/sbin/alsactl -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf
store /dev/$name"
The second line confuses me.
Even if I am just doing something stupid or overlooking the obvious,
please suggest a fix.
--
Regards Bill
Fedora 11, Gnome 2.26.3
Evo.2.26.3, Emacs 22.3.1
ZynAddSubFX is a truly amazing piece of work, an amazing little synth.
Sadly, when it comes to jack operation it's a case of flawed genius.
There's an experimental patch against the 2.4.0 release tarball at
<http://www.graggrag.com/?q=node/19>.
I've restructured the audio and midi drivers, and added Alsa audio. It
builds with multiple audio/midi options, nominate what to actually use
via command line parameters. The build options and default choices are
set as per normal in Makefile.inc.
If any mildly adventurous zyn enthusiast cared to try a build && run, I'd
appreciate 25 words or less on the experience. At the moment I'm mostly
interested in jack audio/midi performance.
The patch applies from the ZynAddSubFX-2.4.0/ directory, then off to src/
to edit Makefile.inc and build as usual.
cheers, Cal
Announcing the new public beta release of phasex! All phasex users
are encouraged to upgrade. Since the days of 0.11.1, all known bugs
and many annoying quirks have been worked out, making
PHASEX-0.12.0-beta3 is the most stable, best sounding, and most
studio friendly release yet:
* Fixed all currently known crash issues and build issues. Code has
been updated for newer versions of gcc, gtk, and glibc. Realtime
threading issues have been fine-tined, using realtime locks where
appropriate. The build system has been fixed up for newer
distributions and includes default optimizations for the entire x86
family (run './configure --enable-arch=foo', where foo is an
architecture supported by your version of gcc).
* Sound quality has been greatly refined by reshaping envelope
curves (eliminating pops and clicks), adding hermite interpolation
to the chorus (removing fuzziness from chorus), adding fine tuning
to oscillator frequencies and FM amounts, adding sampled oscillators
(currently with Juno-106 and vocal samples), fixing portamento
and key triggering logic, and more.
* The JACK code has been reworked to allow multiple instances with
persistent instance numbers and resilience to JACK crashes and
restarts.
* The GUI has been refined slightly, with a new color scheme, patch
folders in the file dialog shortcuts list, and a couple slight
optimizations to the knob code.
* There's more. See http://sysex.net/phasex/beta for details if
you're that curious.
Since 0.12.0-beta2, fixes have been implented for GTK >= 2.16
(fixing Fedora 11 builds), the max polyphony has been turned into a
runtime configurable setting, and the build system and default
architecture specific optimizations have been fixed up some more.
Source tarball and arch specific Fedora 11 RPMS are now available
for download:
http://sysex.net/phasex/beta/phasex-0.12.0beta3.tar.gzhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.src.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.i386.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.i586.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.i686.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.athlon.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.amd64.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.x86_64.rpmhttp://sysex.net/phasex/beta/phasex-0.12.0-0beta3.fc11.ia32e.rpm
Build reports and bug reports, and package build files for all
distributions are highly welcome. This is the final beta for
0.12.0. Any build and crash issues reported in the next two weeks
will be fixed for the 0.12.0 stable release. Please direct any
feedback to weston(a)sysex.net.
The latest version of phasex can always be found at:
http://sysex.net/phasex
For those of you who use git:
git clone http://sysex.net/git/phasex.git
Thank you all for your support, feedback, and contributions over the
years, helping to make PHASEX what it is today.
Happy music making!
--ww
It feels like my several year old PC will crap out soon for one reason
or another, so I need a replacement, better sooner than later.
This time it should be a laptop and I heard that formerly IBM and now
Lenovo thinkpads are of good build quality, even if they only come
with intel CPUs and cost an arm and a leg.
So, do you have any experience with those for audio work?
I'd be most interested in the T and R series and more recent models.
Also helpful would be some data that's impossible to find on websites:
- What chipsets are built in?
- do the usb buses and the like share interrupts with something nasty
like graphics?
Helpful commands to gather that data:
cat /proc/interrupts
lspci
lsusb
Thanks in advance for any help.
Regards,
Philipp
Hi everyone,
Atte's recent thread about sync got me to thinking about MIDI clock.
Is there a simple app out there that will generate MIDI clock at a
tempo can can be defined? If not, would one of you
scripting/programming wizards be willing (or able, if what I'm asking
is possible) to drum something up?
Thank you,
Josh
--
Josh Lawrence
http://www.hardbop200.com
Betreff: Re: [LAU] Kim did the switch to Linux
Gesendet: Mi, 05. Aug 2009
Von: Paul Davis<paul(a)linuxaudiosystems.com>
> On Wed, Aug 5, 2009 at 9:07 AM, Michael Bohle<opendaw(a)jacklab.org> wrote:
> > Nice article. But colored by ideology.
>
> Nice comments. But colored by workflow choices and a preference for
> simplicity over control.
Control what? The source code of an application? Or the kernel? I have very limited skills in programming languages - I'm just an old school music artist and multimedia designer. On OS X I have full control over my personal creative workflow. But Linux was controlling me in a way that I have to take care of lot admin tasks and bugs. Yes the bugs and workarounds on Linux controlling me and I'm to stupid to fix them all plus write my dream apps. I'm one of the guys, going into a music store and buy a guitar and not one of the guy who'd like to build a own. My handcraft is music, not wood.
But for code-developers Linux is a very good and productive playground, because they have full control.
>
> > -I'm more productive with a Mac environment
>
> The best reason you've cited, I think.
>
> >Sooperlooper is an good example: first made for Linux, then ported to OS X
> and now the "mainstream-Daws" Live and Logic have loopers as new features in
> their latest versions.
>
> Which once again reinforces the same sales/marketing approach that the
> entire audio tech industry offers beginners or relatively new users in
> every field: "we'll make it simpler for you". Its a noble sentiment,
> and would be a fine one if they actually lived up to the real desire
> of users: "make it simpler without taking away any power, control or
> options". In the real world, we know that this is not possible. And so
> people buy integrated control surfaces/computer audio interfaces
> ("because its simpler") and then later find that they love the control
> surface but need more channels/better quality/lower latency on the
> audio interface side and they can't trivially upgrade just one
> component without wasting money. Or they buy a DAW with its builtin
> live-looper ("because i don't have to be a computer geek to get it
> setup") but then discover that when they want to run the live looper
> standalone they can't (or something else isn't quite what they needed)
> and so they have to still get a standalone live looper anyway.
> Thankfully sooperlooper is available at no cost. Isn't that nice of
> Jesse?
Yes, thats very nice, thanks Jesse! I recognized SL with Linux as the best Looper i've ever seen and on OS X I used the AU plugin version until Live8. But the Live8 looper is much better integrated (drag n drop audioloops into the sequencer, more tight etc) and so the workflow is much easier for a stupid artist like me, so SL is not in use anymore... But I still recommend SL to everybody who like to "do the looper."
regards,
Michael
>
--- original Nachricht Ende ----
Sorry if someone responded and we missed it, but despite much googling and all of that, am still working on getting my own kernel(s) [2 machines] going with the following as had been suggested last week:
preempt_RCU
No_Hz
HZ_1000
and the other Rock-solid low-latency audio tweaks
99 ff migration
99 ff posixcputmr
98 ff IRQ-8 (real-time clock)
97 ff audio IRQ
80 rr Jack
Found the preempt_RCU and HZ_1000 spots in the debian/ubuntu kernel hack, still looking for the rest please.?
** Would really appreciate the assistance with figuring out where/how to put those.
Paul
my config:
Dell Studio
Ubuntu 9.04
rt kernel 2.6.29.4-rt15-rt
jackd version 0.116.1 tmpdir /dev/shm protocol 24
Ardour 2.7.1 (built from revision 4296)
USB iMic audio interface
KOrg nanoKontrol
cpufreq-set - both cpu's are set to 2.0GHz and userspace
I'm trying to get Jack and Ardour set up/optimized for my fall tour
I'm using the rt kernel as stated above
my Jack settings are 44.1kHz: frames 512: periods 5
latency is not a huge issue for me since I'm only playing back audio for
a live mix situation
and xruns in Jack seem to be tamed to 0 during playback
my Ardour session is 30 minutes in length, has 8 tracks of audio, and
the fader levels are assigned to the nanoKontrol
everything works fine for the session except at some random point after
playing for a while I get a single short burst of AM sideband noise,
like I'm multiplying the audio on the mix buss by another audio signal
it doesn't happen (so far) more than once per session and it doesn't
seem to be correlated to anything like mix buss levels or clipping on a
single channel etc
is there a setting in Jack that I'm overlooking or has anyone
experienced a similar intermittent burst of noise in playback with
similar Jack settings? or if this topic has already been discussed can
someone point me to a link in the archives? I wasn't able to find
anything on a cursory search
================
-- also, I started Ardour from command line when Jack wasn't running
and I got three panels in the open dialog box -- one of them being a
Audio Setup panel
-- is there a way to see this panel after starting Ardour with Jack
already running?
Greetings,
My editor at LJ asked an apparently simple question: In an ALSA-only
environment (no JACK), how can he record system sounds and a mic input
simultaneously when capturing his desktop with xvidcap ? He's working
with an hda-nvidia chipset that I also have on one of my machines, so I
can test any suggestions myself. So far I'm not having much luck
recording anything other than the mic input with xvidcap. So, any
suggestions ? Maybe some dmix or asoundrc wizardry ? Please advise if
more information is needed.
Of course, this was ridiculously easy with recordmydesktop and JACK. :)
Best,
dp
Hi Harry.
It's curious... you got the point I had in mind :)
My main idea is to extend the configuration dialog so that, same as
you can map wiimote keys/events to keyboard keys, you could map
wiimote keys/events to CCs helped by a select box with a list of
available CCs; first maybe a usefull and comprehensive subset and then
the whole set in later versions.
Maybe we can add the "advanced" section as well. But first I'm trying
to get information about the other topics on my list :)
Thanks Harry.
//On my mobile device. Sorry for top-posting and any mistakes
2009/8/2, Harry Van Haaren <harryhaaren(a)gmail.com>:
> Hey Carlos,
>
> Python & the wiimote is a nice combo, i've played with it and midi a little
> too..
> Not at all familiar with desktop applet coding, so ill leave that to the
> pro's!
>
> As far as the "what midi CC bindings" are useful, could you put in a
> "Drop-down-box" or "Entry-Box"
> for the CC's? Because there will always be some use for it. Perhaps have an
> "Advanced" section, in
> which one can manually type the CC Numbers, and have the "Simple" section
> up
> with a drop down of
> the most common CC's?
>
> Becuase I can really see the use of having a wiiMote around for debugging
> audio/midi progams with you applet.
> It would mean you could easily send any Midi CC's to a program using an
> "Easy-Access" unit. (IE: pick it up, use it,
> not like a keyboard where you'd spend time mapping a key to a different
> MIDI
> CC etc)
>
> Hope the project goes well for you, once im home ill check how much is done
> and where to get the Alpha release.. ;-)
> -Harry
>
>
>
>
> On Sun, Aug 2, 2009 at 3:32 PM, Carlos Sanchiavedraz
> <csanchezgs(a)gmail.com>wrote:
>
>> I have notice I forgot to send this mail to LAD as well. Sorry :)
>>
>> Here it is.
>> Of course, thanks in advance.
>>
>>
>> ---------- Forwarded message ----------
>> From: Carlos Sanchiavedraz <csanchezgs(a)gmail.com>
>> Date: Sat, 1 Aug 2009 19:18:17 +0200
>> Subject: Python and MIDI orientation for a project
>> To: linux-audio-user <Linux-audio-user(a)lists.linuxaudio.org>
>>
>> Hi folks.
>>
>> I'm cooperating with a friend and fellow to improve his project
>> related to wiimote.
>>
>> The project is Wiican[1]. In short, it is a tool (a system tray icon
>> actually) that makes it easier to connect the wiimote and configure
>> and create key mappings for use at your will. It's written in python
>> and uses bluez, hal with dbus, wminput and cwiid.
>>
>> My goal is to add some layer in such a way that you can map wiimote
>> events to MIDI. And maybe, to include it on the next improved release
>> of Musix.
>>
>> So, in adittion to my researches on the subject and what I already
>> know about MIDI CCs and so, I would like some advice and guidance
>> about how to:
>> - implement MIDI in python (which CCs are a must for you, create and
>> send MIDI messages, libs, bindings, reference projects),
>> - implement Jack and Alsa MIDI ports in python (libs, bindings,
>> reference projects),
>>
>> ... and every other interesting information or experiences on this.
>>
>> Thanks in advance.
>>
>> [1] https://launchpad.net/wiican
>>
>>
>> --
>> Carlos "Sanchiavedraz"
>> * Musix GNU+Linux
>> http://www.musix.es
>>
>>
>>
>> --
>> Carlos "Sanchiavedraz"
>> * Musix GNU+Linux
>> http://www.musix.es
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user(a)lists.linuxaudio.org
>> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
>>
>
--
Carlos "Sanchiavedraz"
* Musix GNU+Linux
http://www.musix.es
