> I just sold mine on Ebay this morning. (At least I think it wasn't
> shared memory. Hardly remember anymore. Anyway, it's gone...)
It's not that easy to get anything to Russia :)
>
>> Is it possible to do 8in/8out and 64-sample buffers with RME Multiface
>> CardBus on a laptop with shared video memory?
>
> Depends on the laptop but possibly. Why so stringent about 64/2? Do
> you _really_ require sub-3mS?
>
Processing live inputs better be done with lowest latency.
Since 64/2 is only a part of total latency, increasing this value is
noticable. Especially when playing guitar.
>
> Possibly, but even shared memory probably won't kill you if you're
> just running Ardour, etc.
>
I hope it will not kill me for running some live processing stuff -
SooperLooper, Jack-rack, etc.
Hey Terrance, The fact that you don't see anything in /proc/asound
suggests to me that there are no alsa modules loaded in your kernel.
What output do you get from lsmod? Maybe you could also attach the
kernel config that was used to build your currently running kernel. If
you are using the kernel that came with your distro this should be
/boot/config... If you built your own kernel this should be
/usr/src/linux/.config. Here is the alsa card matrix for cirrus logic (I
believe that this is the manufacturer of Crystal Soundfusion chips).
There are a few different cards here. You may be able to find your
particular varity by checking out the output from lspci or by checking
the manufacturer of your laptops web site. I suspect that your screen
reader is using oss and that the alsaconf utility modified /dev/dsp and
this is why it's not working now. I think that the first thing to do is
confirm that alsa is not loaded by checking out lsmod. The second thing
to do is setup alsa drivers if they are not setup. The driver, lib, &
util can be downloaded from alsa-project.org. If you can't determine the
exact model of chip you can just compile all of the chips listed on the
below link. There are installation instructions on that page if you
follow the chipset links. Also, If you have the oss drivers for that
chip loaded they will need to be unloaded with rmmod. Let me know if any
of this is confusing. Also, if anyone else on the list thinks I am
leading Terrence down the wrong path please speak up. -Garett
http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Cirrus_Logic
Terrence van Ettinger wrote:
>Hi, Garrett,
> The screen reader boots up just fine, without any errors. The
>sound card is a Crystal Soundfusion; I'm not sure what the version is or
>anything. Doing ls /proc/asound? only tells me there's no such
>file or directory, and there isn't an /etc/asound.conf file.
>
>Thanks,
>Terrence
>the sound card, I don't know what variety it is, unfo
>
>
Both optical sensors and contact mic's are often used for this by the
professional calibration tools.
I would probably plan on using a contact mic inside the clock case to minimize
outside noise interference. It is important to perform final adjustments with
the works inside the case and the case carefully leveled in order to get the
final accuracy needed, although with large case clocks this isn't always
possible without some kind of portable device.
One problem with an optical sensor is that it cannot help much with the first
step and that is telling the difference between the 'tick' and the 'tock' sound.
A clock that is not level or that has the internal linkage to the pendulum
off-center will not perform as designed and be very hard to accurately set.
Although a simple and inexpensive solution to this is to just use a cheap
amplifier available from Radio Shack and use the ear as the calibration tool.
> thats not a very fair comparison. USB2.0 is the "new USB", FW800 is the
> "new FW" :) but FW is also a better protocol, which means its easier to
> get close the theoretical maximum than it is with USB.
>
Fair enough, given USB2.0 and FW400 in most of laptops. And UA-101 is a
USB2 device (though, has no driver support yet)
Anyway, I'm interested in practical applications, not a theoretical ones.
> if you were in the US, i could offer you the best prices on RME gear
> (i'm a dealer), but with a european location, thats not likely.
>
Thank you, Paul. I also know where the linux drivers come from ;)
Dmitry.
On Wed, 2005-09-28 at 17:32 +0400, Dmitry Baikov wrote:
>
> yes, its much better: vastly higher bandwidth, much faster bus
> clock.
>
> Theoretical(!) numbers are: FW-400 = 400MBits/s, USB2.0 = 480 MBits/s
thats not a very fair comparison. USB2.0 is the "new USB", FW800 is the
"new FW" :) but FW is also a better protocol, which means its easier to
get close the theoretical maximum than it is with USB.
> >From reading RME mailing lists, I know there were many problems with
> Ricoh controllers (on PCI bursts). And everybody recommends TI. But
> most notebooks to choose from have Ricoh controllers. Do you know if
i have ENE controllers in my two HP laptops, as do a couple of other
people on LAD. there *were* problems with these in the 2.4 kernel
series, but they were fixable from user-space *and* are gone in 2.6
(AFAICT).
if you were in the US, i could offer you the best prices on RME gear
(i'm a dealer), but with a european location, thats not likely.
--p
On 9/28/05, *Paul Davis* <paul(a)linuxaudiosystems.com
<mailto:paul@linuxaudiosystems.com>> wrote:
> Is it possible in practice? And for what number of channels? Also,
is FW
> much better than USB2 and why?
yes, its much better: vastly higher bandwidth, much faster bus clock.
Theoretical(!) numbers are: FW-400 = 400MBits/s, USB2.0 = 480 MBits/s
> As for RME Multiface
i'm not sure that its that hard anymore. kernel 2.6 seemed to have fixes
...
--p
As I see, you insist on RME :) Reasonable choice. More expensive, but
bullet-proof.
From reading RME mailing lists, I know there were many problems with
Ricoh controllers (on PCI bursts). And everybody recommends TI. But most
notebooks to choose from have Ricoh controllers. Do you know if these
problems were solved? According to the list everybody went for Fireface
now, so there's no feedback on modern cardbus setups.
And even less on linux setups.
Questions about FA-101 still remain :)
More opinions / experiences are welcome :)
Thank you.
Dmitry.
Hi all!
I've just recently installed the latest release of linuxsampler (0.3.3?) and
I've got a problem. I only use telnet to access LS. If I want to shut the
sampler down (really quit the server), it tells me something like:
Stopping diskthread...
There it just hangs eternally. I have to kill it. It doesn't stop my work
and playing, but it is nasty and I suppose not the way it is expected to be.
Anyone the same problem, fixes?
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net - the Linux TextBased Studio guide
Slat Sounds Like A Theremin
Slat 0.4b is up now. It no longer requires ClanLib and the images get
installed properly with make install.
The "b for beta" is there because I've had to leave out the extra
cursor - the one that shows the rotating point.
I'm pretty new to X/imlib programming, and I've run into problems
using imlib_paste_image.
More detail is at
http://blog.dis-dot-dat.net/2005/09/slat-without-clanlib-kde-without.html
There's a commented line that kind of puts the cursor back, but it
behaves strangely.
Everything works without it, so Slat should be perfectly usable.
If anyone has a clue about this, or can spare a few minutes to see if
the same thing happens to them with the extra line in place, I'd be
grateful.
James
--
"I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb. Thank you."
(By Vance Petree, Virginia Power)
Anyone have a good suggestion for a tutorial for making accurate
high-resolution high-priority clocks in C? I found some tutorials but
they were kinda old, so wondered if they might be out of date as to how
far real-time scheduling has come on linux. I want to be able to wake up
a pthread very accurately.
Thanks
Iain
I would like to build an application to assist in setting the "Beat" of
a pendulum type clock. This is a tool used by a clock repair person to
set a clock to keep accurate time. It is basically a low frequency
oscilloscope with some specialized functionality.
A microphone is placed inside the clock case and attached to the mic
input of the sound card. I want to have a display of the resulting tick
and tock waveforms. There are two primary functions that are needed to
accurately set a clock's beat.
One is to be able to compare the tick waveform to the tock waveform. A
clock that is off balance and hence off beat will have a difference in
the sound of the tick and the tock. Tick being the pendulum swinging in
one direction vs the tock being the opposite direction swing.
The other function is to measure the time between the tick and the next
tick or full cycle of the pendulum swing. For instance, a lot of
pendulum clocks are set to have a pendulum cycle time of exactly one
second. Measuring this to say, hundredths of a second allows for
accurate adjustment of the clock.
I am looking for pointers to libraries and sample code that might help
me get started with this project. Once completed, it would be released
as an Open-Source project for use by any clock repairer that wants it.
I have not seen any open-source projects of this type and the commercial
units that perform this function cost several hundred dollars.