Hello LA land!
I got a Startech USB audio device based on the C-Media CM6206 purely in the
hope of being able to use its S/PDIF input under JACK. It runs JACK just
fine, I just don't know how I might access the SPDIF input (or even the
line-in, just out of interest) from under JACK?
When I run alsamixer and switch to viewing the capture ports of the cm6206
there are 4 capture channels - PCM, Line, Mic and S/PDIF In but under JACK
I only get 2 capture ports which are the L and R analogue mic input
channels. I can also see the light emitting from the S/PDIF out port so I
am confident the S/PDIF should work and hopefully under JACK.
I'm running AV Linux 6
arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 2: Device [USB Sound Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
cat /proc/asound/devices
1: : sequencer
2: [ 0- 3]: digital audio playback
3: [ 0- 0]: digital audio playback
4: [ 0- 0]: digital audio capture
5: [ 0] : control
6: [ 1- 1]: digital audio playback
7: [ 1- 1]: digital audio capture
8: [ 1- 0]: digital audio playback
9: [ 1- 0]: digital audio capture
10: [ 1] : control
11: [ 2- 0]: digital audio playback
12: [ 2- 0]: digital audio capture
13: [ 2] : control
33: : timer
Thanks!
Dan
All,
Latest beta 2 version squashes a highly sporadic bug in l2ork version of
cwiid library, improvements to the K12 module, and perhaps most notably
introduction of a completely rewritten tidy (clean-up) functionality,
usability improvements (e.g. when connecting objects that are so far apart
that they are not visible on the same screen the canvas focus follows cursor
and connection cord; consistent positioning of iemgui objects; autopatching
improvements; etc.), as well as improved automated compiler from source (see
pure-data/l2ork_addons/tar_em_up.sh in the dev tarball). For a detailed list
of improvements, please consult pd-l2ork's git project page.
This is also the first release of the .deb format. It is currently generated
in a way that clashes with other forms of pd so please be aware of that (in
other words installing pd-l2ork requires uninstalling of
pure-data/pd-extended due to some shared files). Also, everything has been
compiled on Ubuntu 12.04 which has caused some grief to those who run Debian
systems that do not ship (yet) with glibc 2.15. Even if you are running
Debian, I would still appreciate it if you would test the .deb to see if it
dpkg will detect the lack of glibc 2.15 prior to trying to install it, as
well as to check if all the supporting libraries are also appropriately
installed. That said, *PLEASE BE CAREFUL WITH THE DEB* since this is the
first one I ever made of pd-l2ork and as such I am not sure how it will
behave and/or whether it will work at all. So, if you are interested in
experimenting with .deb files I would advise doing so on a non-production
system. All that said, the deb worked fine on my end (Ubuntu 12.04).
As usual, regular binary builds are also available.
I'd appreciate feedback on the said builds. Please include as much info as
possible, including distro/version/32 vs 64bit/problem and how it manifests
itself, etc.
You can get pd-l2ork from the usual place:
http://l2ork.music.vt.edu/main/?page_id=56
Thanks!
Ivica Ico Bukvic, D.M.A.
Composition, Music Technology
Director, DISIS Interactive Sound & Intermedia Studio
Director, L2Ork Linux Laptop Orchestra
Head, ICAT IMPACT Studio
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-6139
(540) 231-5034 (fax)
ico(a)vt.edu
http://www.music.vt.edu/faculty/bukvic/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
linuxaudio.org will be down this Sunday, November 18, from 11:00 to
12:00 EST because our hosting provider is maintaining the storage system.
sorry for the inconvenience,
robin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQorDIAAoJEKCQvOAs9X8EzXwP/RWzKQdCIrOnn0P1G68PmjZK
NEkICVmYnuu/ul3C9gtsu/vXkeBrF2+kPo6KQRr2jhT2491UVCHZhnABRPBTbKU3
Yy4wRvk9AM1tHUdhEsOTWu3tyBvN03Crn6RAotpDw+1LBfHHQcjabRxQsYEBAglB
YMpSzxHvGrHU7b8yYQlpSQ4Ysro1lYHxzebY02qjpaU4nX49LtdkxSltL4AxXYSi
pO9RTrUVGfuwRCoMASmdDtcJxc2XepYs2UayDGst+aqikjYNm0VGL8m84HkBIbgs
ulhQOL8/XZyqTgsryr5uZ5pWQ+1ZBiOpkITXd0LaS3G8kcIvLTncuJsLxaPiWeZn
6eo5dIPIh+ttZOBYqWMJhY7YpgPEqakKHD+Ahkfzzo7oTreylt0Xk4HQZ+Wj+vtF
We3G/skhgcugtqHpF+o4AILCsmiSwYv51LRyq+y5gaOVYkjTFRx1p4v7sGQAzVVX
Bgn7tufO8FREGYctuCsXxaqLGwXV/aY2fXEDebk0lZxBBCut8aYcvgsQ79BU8udT
+H/CeSbmeS3QsbptdFsLrFSpPcD+x4Tumq/tfWEBOmw7uXhsp2weC2K6o/wOKmFg
W5mZ1nppGjp0qJtkHwP8Fo9iux0YLDCgL40FItrFSD1pOnACq292taylTpf3veCI
xWcGTyNEySpTHk3h1Djf
=Bydq
-----END PGP SIGNATURE-----
Hello list,
For the first time in my life I need to work with huge recordings, I
would like to understand how much memory and computing power is
required to handle it on a linux box with Ardour.
The recording, retrieved from an Alesis hd24, will be about 1 hour and
a half long, 24 channels, 44.1KHz, 16bit,
What are the minimal requirements to work with it?
If I choose sample rate and bit depth to be 48kHz/24bit, will it
require much more resources (other than disk space)?
Thank you!
--
Asa Marco <marcoasa90(a)gmail.com> 朝
On 12/11/12 21:19, Fons Adriaensen wrote [in a different thread]:
> On Mon, Nov 12, 2012 at 02:17:03PM -0500, Paul Davis wrote:
>
>> with no plugins, it would be hard to buy a computer today that could *not*
>> handle editing that session.
> True. I've been doing 30-track editing on a P4 system with 512 MB
> memory, no problem at all, Ardour handled that very well. That was
> just editing, mixing with a lot of plugins etc. could be another
> matter.
>
> The *only* case when I've seen it fail was strangely enough when
> recording just a single stereo track on a dual quad-core machine
> with 4GB of memory. Input was coming from firefox playing a Youtube
> video, routed via ALSA's Jack plugin, and recording failed repeatedly
> with 'your hard disk was not fast enough' messages.
Most probably it was flash draining all CPU or something.
For this use case I'd recommend using something, such as youtybe-dl
(which also provides a nice --extract-audio flag), to download the audio
contents and then just import that into Ardour.
Lorenzo.
Hello everyone!
I had put this off for such a long time. so here is "A Year starting Now".
If memory doesn't betray me, you may have heard all of these songs already,
but here they are in one piece and with the general idea, gently holding them
together. You can't really call it a concept.
http://juliencoder.de/nama/a_year_starting_now/
You will find short explanations for each piece and downloads in OGG and mp3
format. I hope, that seeing them organised and explained together makes a
little more sense.
More shall follow soon.
Warm regards
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
On November 11, 2012 07:34:03 AM you wrote:
> I am just wondering to myself how easy/hard it would be to have the GUI of
> mudita on a different machine to which it is running. The reason being I
> was thinking of using netjack and the box with the audio interface would
> end up not having a monitor. It would still be nice to be able to use the
> metering to set inputs as the HW metering shows the peaks as the 24bit
> input sees them but the application shows things after it has been
> 32bit-ized. I have found things look fine in ardour but the input is
> peaking.
>
> I am guessing I could do that now just with x, or a text interface would
> work too. I am not asking you to do a bunch of coding unless the idea
> catches your fancy. Just asking how easy it looks to split the GUI from
> the control part of the app. I suppose it may be just as easy to build a
> text version from scratch or on top of alsamixer. Just that you know the
> code and I don't (and my coding skills are not production level by any
> means :)
>
> I am seeing that new mother boards are getting harder to deal with audio
> cards. I am thinking that when I replace my old one (already 10 years old)
> I may not be able to use my audio card and for that matter find an
> inexpensive replacement. I may end up using this MB as an ethernet sound
> card. I may even package it into a mini-distro...
How about MIDI controller assignment to each Mudita slider and checkbox?
A reasonable path, it's already using ALSA.
Or maybe OSC?
Tim.
Radium is an open source music editor with a novel interface.
It's inspired by trackers, but has fewer limitations and uses graphics
to show musical data.
Screenshot:
===========
http://dl.dropbox.com/u/4814054/radium-1.9.1.png
Source code:
============
http://dl.dropbox.com/u/4814054/radium-1.9.1.tar.gz
64 bit binary:
===============
http://dl.dropbox.com/u/4814054/radium-1.9.1_linux64.tar.gz
(Requires GNU libc 2.14 or newer. It should work with Ubuntu 12,
Fedora 17 or Mint 13)
Homepage:
=========
http://users.notam02.no/~kjetism/radium/
(It's not quite updated, I can't seem to login to the web server right
now.)
Source code repository:
=======================
https://github.com/kmatheussen/radium
Most important changes 0.67.1 -> 1.9.1:
=======================================
* Audio.
* A quick-to-use modular mixer. Jack ports can be inserted anywhere.
* VST plugins and instruments (native, not via wine)
* LADSPA
* Fluidsynth instrument
* 20 STK instruments. (Physical modelling)
* Sampler instrument (soundfiles, xi instruments, soundfonts)
* Multiband compressor
(http://users.notam02.no/~kjetism/radium/pictures/screenshot-multiband.png)
* Built-in filters and equalizers.
* Simple arpeggiator
* Drunk input velocity
* Various GUI improvements
* Pitch expand made available in the menues.
* Tapiir plugin
* Zita reverb plugin
* Demo song
* Reconfigured keybindings
* Various bug fixes
Acknowledgment:
===============
Full list: http://users.notam02.no/~kjetism/radium/development.php
Especially thanks to Yann Orlarey for Faust, Julius O. Smith III for
the Faust filter and compressor code and more, Romain Michon for the
Faust
STK instruments, Fons Adriaensen for the amazing Zita reverb sound
(and Julius O. Smith III for the Faust implemention of it),
and Rui Nuno Capela for QTractor. (Plugin GUI code are based on code
taken from QTractor.)
Hi,
it's possible to have more then the normal stereo output by zynAddSubFX?
I like to record different sounds with different midi channels at once,
for example with ardour.
thanks
chris
Good point about the driver
Unfortunately i couldnt find any info at all about this device (probably
because its cheap, new and built by a rather unknown company) and exactly
for this reason i would liks to share what i have found out
Grtz
Thijs
On 8 Nov 2012 12:43, "Paul Davis" <paul(a)linuxaudiosystems.com> wrote:
On Thu, Nov 8, 2012 at 1:54 AM, Thijs van severen <thijsvanseveren(a)gmail.com>
wrote:
>
> Hi all
>
> ...
there is a reason why MIDI is a standard protocol.
the only way that a MIDI device is not Linux compatible is if it doesn't
actually send MIDI, but instead uses some proprietary protocol which is
then converted by a device driver into MIDI that can be seen by apps on the
computer.
there are very few such devices. the question to ask is whether it has its
own device driver - if it does not, then its about 99.78% certain that it
will work on Linux or with any other MIDI capable platform/device.