EzAudDac Alpha release: Cheap DACing!

[carmangary]

The aim would be to intergrate as much hardware with as much (homebrew) software as possible with the least amount of effort. Maybe one way to go would be to interface homebrew software (laseroids, spagetti, etc.) with the mamba layer because many hardware drivers already exist that the mamba layer can talk to. It would require an API to the mamba layer though, is that available?

Yes, the Mamba driver API is openly published. Like I said, I already created a template when making a Moncha Mamba driver. So, none of that is new. I guess what you are asking for already exists in a way. But, unless all hardware companies and software companies write their drivers and software to interface with that standard API it doesn't do a lot of good. And, as I said before, it doesn't help with custom configuration that is unique to each of the DACs.

But, anyway, there are already MLD mamba drivers for a lot of different DACs so just change your software to talk to the MLD drivers and I think you have what you want.

[Zoof]

Yes, the Mamba driver API is openly published. Like I said, I already created a template when making a Moncha Mamba driver. So, none of that is new. I guess what you are asking for already exists in a way. But, unless all hardware companies and software companies write their drivers and software to interface with that standard API it doesn't do a lot of good. And, as I said before, it doesn't help with custom configuration that is unique to each of the DACs.

But, anyway, there are already MLD mamba drivers for a lot of different DACs so just change your software to talk to the MLD drivers and I think you have what you want.

I think that will do the trick in terms of hardware and software. But probably some legal issues are there. Can anyone use the mamba drivers without having bought a copy of / license for Mamba? Medialas has probably developed those....

If not it may still pay to define something like that but completely open. Actually, my original idea was that if the soundcard driver source was in the public domain similar drivers could then easily be made by different people so easlylase compatible progs/games will work with their hardware.

If that idea takes off, and the easylase API is generic enough, the easylase API could become the standard one.

Do you have a pointer to the mamba API? would like to read up on it.

[carmangary]

The Mamba API is probably not good anyway. I think it only does 12bits.

Just create your own and create wrappers for all the hardware. That's basically what I did inside my software. I only have 4 methods on my interface:

Initialize
SendFrame
SendBlank
Close

You could create your own interface that does the same and wrap all the drivers. I can help you do that if you are interested since I have already done it for Moncha, EasyLase, Lumax, Riya, and sound card. I guess you would want to do it in C or whatever. Mine is in C#.

[OldGrumpy]

The Mamba API is probably not good anyway. I think it only does 12bits.

That's how rumors emerge. And BTW it's wrong.

I only have 4 methods on my interface:

Initialize
SendFrame
SendBlank
Close

How would you use different scanspeeds?

[carmangary]

Grumpy, I must have been thinking about something else. If Mamba does 16 bits that's cool. Here is the MLD API btw:

WORD WINAPI MLRegisterDriver(char* buffer);
BOOL WINAPI MLDevicePresent();
BOOL WINAPI MLGetName(char* buffer);
BOOL WINAPI MLInitDevice(WORD h);
BOOL WINAPI MLInitShow(WORD h, WORD c);
BOOL WINAPI MLDraw(WORD h, WORD c, Point* d, short n);
BOOL WINAPI MLHaltShow(WORD h, WORD c);
BOOL WINAPI MLHalt();
BOOL WINAPI MLParams(WORD h, WORD c, Params* d);
WORD WINAPI MLNumDevices(WORD h);

After looking at it again and refreshing my memory, I really don't have any complainsts about it.

I send scan speed as a parameter in my SendFrame method.

[Zoof]

Hi Grumpy,

how would medialas feel about the free software community using the mamba API in order to use the existing hardware drivers?

How would medislas feel about a small software company doing the same and charging for the software?

Where can I get a copy of the mamba API docs?

cheers.

[drlava]

If you all want to try to standardize an api, have a look at the Riya DAC api. It uses double-buffering calls that I think reduces the overhead in buffer feeding from the player and results in a pretty smooth and fast display even on slower computers.

[carmangary]

Riya, Lumax, and EasyLase APIs are all pretty much the same. They all use double buffering. So does Moncha but there is no "public" api for it.

But, for a common API, I don't think the end user should need to worry about handling double buffering. They would just want to send a frame and let the driver worry about making sure it gets to the hardware correctly.

Mamba has it right. They have simple methods for discoverying the card and it's description with generic methods for sending frames. Within the custom MLD files the dirty work is done. I can't remember if the scan speed has to be set up front with the mamba API. If so, I don't like that because not all software uses the same scan speed for every frame. That might be might only complaint.

[drlava]

They use double buffering internally, yes but for example the easylase has to be polled to make sure its buffer isn't full, where what could be done is have the driver call a hook in the program whenever it is ready for a new frame, so polling wouldn't be necessary and the program fills the alternate buffers directly.

[drlava]

Posted a major update (V0.14) see 2nd post for download.