Eugene Gavrilov

Hi : )

I would like to announce new release - 3542 - which supports E-mu E-DSP audio cards [0404, 1010, 1212, 1616, 1820, including 1616 CardBus].

The cards currently only work in 16/48 mode, that is, they are like 'audigy'
I'm planning to add additional support for 96kHz and 24-bit modes later.

Download http://download.kxproject.lugosoft.c...v3542-full.exe and install it.

Please report whether it worked for you or not. Please report the following information:
* device name as displayed in your 'Device Manager'
* device name as displayed by kX Mixer
* model name written on your PCI card [usually EMxxxx, e.g. EM8960]

Known issues:
* In order to make the card work after installation, you need to launch 'edspctrl.exe' application which will upload card's firmware. This utility is opensource, is distributed under GPL license and is included in the SDK
* kX Mixer will still display Audigy-like icons for inputs and outputs, I will change them in the future.
* E-DSP specific settings currenty have no user-friendly controls (such as +4dB, MIDI selection, clock selection, SPDIF mode etc.), this will be changed in the future. Meanwhile, if you are a hacker : ), feel free to review edspctrl source code - <b>kxctrl</b> can change any of the settings if you ask it to. (I added command line options to set/get FPGA registers].
* Inputs and outputs are mapped the following way:

[outputs: epilog]:
out0,1: main output on 0404/1212 card; DAC1 for AudioDock, also headphones on the 1616-CardBus and AudioDock
out2,3: on-board SPDIF output and dock SPDIF output [if present]
out4,5: DAC2
out6,7: DAC3
out8,9: DAC4 [for 1820 only]

ADAT gets data from out 2,3,4,5,6,7,8,9

[inputs: prolog]:
in0,1: Dock A, B
in2,3: ADC1
in4,5: ADC2
in6,7: ADC3
in8,9: SPDIF-In [on-board]
in10,11: for 0404/1212: main analog input
in 12,13 14,15: ADAT-In [only 4 channels]

These assignments can be changed by using kxctrl.exe ['-link' option, review edspctrl for details].

Almost forgot: you need to re-launch edspctrl each time you turn on your computer
and.. as always.. your feed back is welcome : )

And now I'm back to MacOSX version of the driver - I'm planning to release it this summer with some initial support for all audigy/live/audigy2/e-dsp cards...

E.

Max M.

[color=gray]cool! now we gonna be digged by " why does my E-mu resample to 16/48?" [/color]

__________________

Russ

Plugin compatibility appears to be the same as 3541.

Eugene Gavrilov

Russ: your plugin was also added : )

In the next build I'm planning some re-organization of the default DSP settings to make it more intuitive, will probably rename Wave devices to 1/2, 3/4, 5/6 etc. (instead of 0/1, 8/9), will rename ASIO channels, etc. etc.
--
There are some minor fixes compared to 3541, but haven't got a chance to copy-paste them here. Full list is in 'readme'...

E.

Russ

Is everyone meant to use the newer epilog (EpilogX)?

I am just curious because, although both seem to work fine (apart from skin issues with epilog_old), the default DSP config uses epilog_old.

AC3 passthru options no longer appear in kxmixer for my 10k1 card. I guess this is intentional (since it does not work with 10k1 models anyway)?

BTW: Regarding the plugin, you might want to add it to the LiveWare menu (possibly replacing CL Reverb).

woodendaze

Are there any news about the progress of x64 (Vista and/or XP x64) drivers?

Eugene Gavrilov

EpilogX should be default for 10k2-based cards only
Yep, I removed AC-3 passthru option for 10k1 cards since it does not work anyway
--
Yep, forgot to add it to the categories... Thanks for reminding!

Doug W

Thanks for still plugging along with all this. Maybe I'll get a 0404 now.

pkozerski

my up with a lot of plugins and DSP configs...

Russ

That is what I wanted to know, thanks for the info.

BTW: Is the name epilog_old going to be used for 10k1 cards in future versions? (Maybe it is just me, but) That name gives the impression that we are using the wrong plugin, and should be using something newer.

do500

* device name as displayed in your 'Device Manager' [COLOR=red]kX 10k2 Audio (3542) - Model E-1010[/COLOR]*
device name as displayed by kX Mixer [COLOR=red]E-1010 k2 [b000][/COLOR]
* model name written on your PCI card [COLOR=red]EM8810[/COLOR]

Here is problem:With all default setting,and playing sound can see peak plugine have singel,but no any sound from ADAT out.

Edit:after some DSP editting and routing,it ok...but sound always cilcking,and surrounder+ can't up-mixing stereo source.hope next release will fix them.

JMan65

Potentially stupid question but here goes:

Any value add or improvements for Audigy 2 ZS in this release?
(over the 3541 release)

i.e. Need I bother?

JGSF

omg... I just saw this... thank you, E.!!

JGSF

Working great, inputs/outputs, soundfonts too. Didn't test adat yet.

I couldn't get midi ports to work, though.

I have tested them with midi ox, dock's midi port light blinks when receives data, but no activity is shown in midi ox. 0202 midi port does not work either.
Are they functional in the e-mu cards?

[COLOR=Red] edit (not really sure about what I am doing, but...):
kxctrl -sfpga 0x0c 0 -> kX Uart receives no midi data when I plug the dock.
kxctrl -sfpga 0x0c 1 -> 0202 midi in to kX Uart.
kxctrl -sfpga 0x0c 2 -> audiodock midi in 1 to kX Uart.
kxctrl -sfpga 0x0c 3 -> audiodock midi in 2 to kX Uart.
[/COLOR]
Hardware manager reports: Model E-1010

DB Name:none
E-1010 k2 [bc00]
PCI Information:
Device: 41102 Subsys: 40011102 ChipRev: 3
Card is '10k2'
Card has MPU device
Card model is '5.1'
Card HAS NO AC97 codec
Port: bc00 Irq: 0x8(8)
Playback buffer: 20a0
Record buffer: 4000

ps: impressive asio performance!

DjGioD

The volume OSD is broken it hangs. how can i fix it?

Eugene Gavrilov

I renamed it back to 'epilog'. However, this creates a confusion with epilogx, which also should be called 'epilog', otherwise kX Mixer won't recognize it properly... (And both are displayed in 'kX DSP' 'add' menu under the same name 'epilog'...) I will need to re-design the way kX Mixer checks for plugin availability...

Eugene Gavrilov

nope : )
this is buggy release for E-DSP and kX enthusiasts only

Eugene Gavrilov

your method of changing MIDI function is almost correct, I will add a nice control panel for all these stuff a bit later...

so, do you have audiodock? or microdock? are all the inputs/outputs available and working?
do LEDs show '48000'?
what is your card's model name written on the PCI card (EMxxxx)?

after a cold reboot, please capture edspctrl.exe output and send it to me by e-mail (by running it this way: edspctrl.exe > output.txt)

ASIO performance is faster than CL drivers, because we are using hardware-accelerated 16-bit transfers, while 24-bit transfers require host CPU...

Eugene Gavrilov

Please capture edspctrl.exe output right after cold reboot.
Are you using microdock/audiodock? Or PCMCIA?
--
ADAT: is it clicky in 'spdif' mode as well?
kxctrl -sfpga 0xb 0x0 - this switches to 'SPDIF' mode
kxctrl -sfpga 0xb 0x3 - this switches back to ADAT mode

E.

JGSF

Cool! Do you know if it's possible to use all the 3 midi inputs at the same time (in terms of hardware)? Or at least 2 at the same time like in the audigy cards?

I have the audiodock (1820m), and all the analog inputs/outputs work. But are DAC1, Headphones out and card's analog out hardwired?

48000 led is on.

btw, I noticed that if you clear the dsp, micA and micB inputs will output in DAC1.

Ok, I'll do that when I get home.

I see... Thanks for clearing that up.

Russ

I understand, but could not epilogX code be updated to use the old code for k1 models and the new code for k2 models? As for epilog_old, changing the name is not so bad, it is just that "old" gives the impression that there is something newer, so something like epilogk1 would be better (although the skin will still have to be updated to use any new name). One other option might be to have the name used in the DSP and the name used in the menu different, such that epilogX appears as epilogX in the menu, but as epilog in the DSP. Anyway, just some thoughts...

Eugene Gavrilov

unfortunately, current way the epilog is generated cannot allow to use the same code for both cards without loosing some GPR registers [they need to be declared before epilog code is actually requested, and since the same code is loaded into kernel, I cannot use iKXPlugin-like stuff there... I can only use da_epilog stuff]
hmm... well.. I guess I found a solution while writing an answer : )
--
I tried changing display name and microcode name, but this confuses several parts of the driver which will need to be re-written..

I guess the best is to use the following:
create two da_.. files for two epilogs
use one epilog.cpp that would load these da_ files dynamically in request_microcode
use a special kernel hack that would choose between the two da_epilog files on load-time

E.

Eugene Gavrilov

what inputs do you mean? card's and dock's? or dock's and IO card's?
the chip has two MIDI input ports, one is onboard, another is either HANOA's (two-channel IO card - 1212) or DOCK's...

But are DAC1, Headphones out and card's analog out hardwired?

on your card, I guess, dac1 and phones can be used separately, but kX currently mixes them (see edspctrl.cpp for details).
if you have IO card, then you can get even more channels...

48000 led is on.

he-he
good!

E.

JGSF

Oh, sorry, I didn't mention this:

The audiodock has 2 midi ins / 2 midi outs, the microdock only has 1 midi in / 1 midi out (i didn't know that).

As I am using the 1010 card + the 0202 card + the audiodock (which I got later), which is not an officially supported configuration, I ended up with 3 midi inputs. But according to what you said, only 2 can be used at the same time. However, I still haven't found how to route inputs to Uart2.

What confuses me is this (and I am sure I am making a stupid question, but I assume myself as an ignorant regarding this matter):

#define EMU_HANA_MIDI_IN 0x0c /* 000000x 1 bit Control MIDI */ <- if it's "1 bit control" why did -gfpga returned a "e" value?
#define EMU_HANA_MIDI_IN_FROM_HAMOA 0x00 /* HAMOA MIDI in to Alice 2 MIDI B */ <-hamoa/hanoa? do they refer to the same?
#define EMU_HANA_MIDI_IN_FROM_DOCK 0x01 /* Audio Dock MIDI in to Alice 2 MIDI B */ <- isn't hamoa/hanoa the audio dock?

( these last two I had no luck messing around with. If you could explain why I was "almost correct", I would be appreciated I don't think I still understood how this works and I haven't found how to route midi in to Uart2 )

The analog inputs all work well independently (1010+0202+audiodock)

In linux, I can split 0202 out from DAC1, but I guess the resources are assigned differently too. Ok, I will see edspctrl.cpp, hopefully I will learn something more.

I will pm you the card's details + edspctrl dump.

Russ

I will take a stab at it (BTW: I do not have any E-DSP cards, so I am only using info from the header file).

From looking at emu.h, it seems you are setting the wrong register (unless it is a typo). You are setting register 0x0c instead of register 0x12 (and from your comment about reading a value of 'e' from reg 0x0c, I suspect that maybe you are mixing up these 2 registers somehow?).

Additionally, the different options of reg 0x12 are toggled by enabling/disabling bits, and are not numbered options (1,2,3, etc).

i.e.
From the above:

if bit 0 is 0, 0202 MIDI from Alice 2 = A
if bit 0 is 1, 0202 MIDI from Alice 2 = B

if bit 1 is 0, Audio Dock MIDI1 front, from Alice 2 = A
if bit 1 is 1, Audio Dock MIDI1 front, from Alice 2 = B

if bit 2 is 0, Audio Dock MIDI2 rear, from Alice 2 = A
if bit 2 is 1, Audio Dock MIDI2 rear, from Alice 2 = B

... etc.

So a value of 3 (00011 binary) has a 1 for both bits 0 and 1 and a zero for the rest, and thus would do ALL of the following (assuming each setting is not mutually exclusive):

0202 MIDI from Alice 2 = B
Audio Dock MIDI1 front, from Alice 2 = B
Audio Dock MIDI2 rear, from Alice 2 = A
Sync card = A
Normal


Does that make sense to you?

Eugene Gavrilov

Russ,
I guess, Johnny is talking about midi -input-, not -output-...

Johnny:
HANA = PCI card
HAMOA = IO card (comes with 1212) - hanoa is a misprint in the .h file

EMU_HANA_MIDI_IN: on my 1010 it returns either 0 or 1
can you get two separate MIDI ports under Creative drivers?
if yes, then install Creative drivers, configure your dock/card as you wish, after that unload E-mu patchmix and install kx drivers, do NOT reboot
after that, run edspctrl > output.txt
(it will not re-initialize the device, but will keep using Creative firmware - and you will get their default settings)
after that, shut-down, power-on, boot and re-run edspctrl > output2.txt
compare the files - and let me know the difference

E.

JGSF

Yes I was talking about the inputs, but thanks anyway, Russ. that made the bit part clear, I was thinking in numbering.

Sorry, I made a mistake, that "e" was read from somewhere else, not 0x0c, only later I realised that...
I can only use one midi port at a time with CL's drivers, but I'll check the differences anyway when I get home.

Thanks!

romanrex

Don't Download

__________________
Êóçíåöîâ Ðîìàí aka romanrex. fierytrance.ru/iXBT.com

JGSF

Hope it helps :

2shared - download kxdrv3542-full.zip

Russ

Oops, I knew that too, but somehow... I will blame it on the fact that I answered at midnight .