Home - BeBytes Info - Submit App - Your Account - Links - Contact Us

  EMUXKI Driver
Version 1.0
Contact Publisher
Homepage
Screenshots
Version History
Other Reviews
Send Updates
Talkback
  Submitted by: Wildman

Date Posted:
Aug-29-2016
Last Updated:
Aug-29-2016
License:
Free
Downloads:
2390
Page Views:
2506
User Rating:
awaiting votes..  

About EMUXKI Driver:

This is a hacked version of the emuxki drivers (for the SB Live and related cards).

I have modified the driver to support the external midi port, decrease the latency,
and improve its timing behaviour.

***YOU MUST ALREADY HAVE THE EMUXKI DRIVERS INSTALLED TO USE THIS!***

***SEE THE VERY IMPORTANT DISCLAIMERS BELOW!***



MIDI input and output are tested and work okay.
Latency is now 1.3 milliseconds (two buffers of 32 frames).
The Media Kit mixer appears to add a bit of latency itself so it isn't perfect, but
is a significant improvement over the default buffer size.

This is completely unofficial -- I have no connection to the original programmers
involved in writing the emuxki drivers or bringing them to BeOS.
I merely downloaded the source and hacked it for my own purposes.


!!!!!!!!!!!!!!!!!! NOTE !!!!!!!!!!!!!!!!!!!!!!!!

***You use these modified drivers ENTIRELY at your own risk!***

There's a strong possibility your system will lock up, or do something even
worse! It works for me, but it probably won't work for you; in fact it'll
probably kill you, so you've been warned.

***I HAVE COMPILED THESE DRIVERS USING BONE AND THE BETA MEDIA KIT.***

If you are using plain R5, there's an even smaller chance this will work
for you. If it doesn't work, try re-compiling the source. Install the BeOS
development tools, then double click the "Untitled.proj" file, and hit
command+m (for Project->Make). The new "emuxki" file is then created
in the root directory (with all the source).

Sorry to be so Linux-y, but this isn't a proper release; it's a hack.
If it was too easy to use, too many people would be severely injured by it.


Installation
======
You must have already installed a previous version of the emuxki drivers
and the multi audio addon. If you haven't done so, do it now.

Now, copy the "emuxki" binary file (in the "STOP! READ THE README..." directory)
into the following directory:

/boot/home/config/add-ons/kernel/drivers/bin/

(replace the existing version if present)

Then open the following two directories in Tracker:

/boot/home/config/add-ons/kernel/drivers/dev/audio/multi/
/boot/home/config/add-ons/kernel/drivers/dev/midi/

Now create a link from the "emuxki" file in the "bin" folder into
both of those folders.

(replace the existing version if present)


Reboot your machine.

There are four likely outcomes:

1. It'll work (unlikely)

2. Your system will boot, but you won't have any sound, or crashes randomly, etc.

3. Your system won't boot; locks up during booting, KDLs, etc.

4. http://www.twistedhardware.net/graphics/misc/mb0088.jpg


4 is pretty likely considering the modifications I've made, 3 is also *extremely* likely.

If you get (2) (think yourself lucky), then delete the files you installed in the installation
step, and re-install the proper emuxki drivers. Then reboot.

If you get (3), hit space during bootup (as the blue loading screen is fading in),
pick "select safe mode options" and select "disable user add-ons".

Then if your system boots up, do the same as (2), and reboot your machine normally.

If you still can't get your machine to boot, then it's beyond repair; you'll have to
buy another one, or take up knitting instead of computers. Please knit me some
socks to thank me for introducing you to your new passtime.



Recording doesn't work!!!
===============

Audio recording doesn't seem to work, at least using Soundrecorder. It might be
a problem in Soundrecorder, or it might be a problem with the hack; I'm not sure yet.
You can sometimes get away with hotswapping between the hacked (for low
latency and MIDI) and original (for recording) drivers, as long as you restart
media services.


The audio crackles or the CPU usage is extremely high. Why?
====================================

The latency is probably too low for your feeble excuse of a computer to handle;
you must get a better one. After all, you were obviously prepared to buy a new one
anyway, since you risked installing these hacked drivers.

Alternatively, you could increase the latency:

To change it, first install the BeOS development tools.
Now open "multi.h" and change the text:

#define BUFFER_FRAMES 32 // This is the minimum which works

to:

#define BUFFER_FRAMES 512 // Comparable latency to sending the buffers via snail-mail to Mars

Save the file, open Untitled.proj and hit command+m to compile it. Then copy the
newly generated emuxki file into the right places again, and reboot.

Might work, might not. Re-create the Linux experience on your own BeOS desktop!

You could also try other sizes, like 64, 128, or 256, must be a power of two.
Don't try anything smaller than 32; I tested this and it definitely doesn't work;
you get silence, then a kind of burning smell from the computer.



What did I change?
===========

The source files used for this were downloaded from the Haiku CVS around January 2006.


Latest Version

Details about this version:
(no information provided)

Intel (BeOS 5) + Source     (104.3K)
  





   
Most Popular
1. BeAIM - 3288
2. BePDF - 3125
3. Paladin - 3108
4. OpenTracker - 2989
5. AMD PCnet32 - 2988
6. nVidia Driver - 2892
7. nVidia 3D Driver - 2879
8. VMWare PCnet/PCI - 2858
9. SPICE - 2808
10. Firefox - 2758
11. ATI Radeon - 2742
12. Duke Nukem 3D - 2741
13. Sequitur - 2727
14. Basilisk II - 2726
15. Traker.Newfs - 2708
16. AbiWord - 2641

Account Status
  You are not logged in.
  Login