[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
viavoice running smoothly (was Re: Error: Could not load libibmeci.so)
Lukas Loehrer <email@example.com> writes:
> first the easy stuff. If the beep tool from the beep package does no
> longer work, One way to restore the beep is to use the beep script
Thanks. The script did the trick.
Concerning the viavoice, it is now running very well. In probably what
amounts to 6 or 7 hours of use over the last day, I have had only one
crash and no echo problems. To test the issue of overlap after
something else accesses the sound device, I went to the sounds directory
and am suffering no ill effects.
> Anyway, what you have to do is choose a buffer size that is small, I
> would say at most 100ms. Mine is 4096 frames. Add some printfs to
> atcleci.cpp to see what sizes for buffer_size and chunk_size are used.
Since I do not know anything about c++, I took the trial and error
approach. I started with the value you mentioned above and initially
decremented it by 256. Things progressively got worse doing this, so I
started incrementing the value by 1024 until I got a value that worked
for me. I did the same for the period size and the period time. Here
are the values I was left with:
I left a bit of context for anyone reading this in the future. Note
that the value of period time is still 0. I am not sure what this
variable is for, but changing it did bad things.
Here is the output of aplay -l | head 1
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel
BTW, the aplay on my system does not give the card id in the first line
of output, and the head command requires a dash before the argument.
> Note that when testing different settings in the .asoundrc file, the
> changes only take effect after all processes have closed the sound
This was the case for me as well.
A question that might not be able to be answered is whether or not this
is an issue that can be solved in the atcleci.cpp file. While this
tweaking is not such a big deal for knowledgeable users, and only a
little bit of a problem for users like me who will plunge head-first
into the water without knowing how deep it is, there is a whole class of
users that will not take the time to mess around with the settings.
This issue will also be a problem with projects like Oralux where it
will be impossible to adjust the settings.
Just some thoughts. Thanks to everyone that helped see me through to
Robert D. Crawford firstname.lastname@example.org
To unsubscribe from the emacspeak list or change your address on the
emacspeak list send mail to "email@example.com" with a
subject of "unsubscribe" or "help"
Emacspeak Files |
Unsubscribe | Search