why src asio plgin doesnt show 3/4 inputs?

mrvomit · Sep 25, 2004, 04:33 PM

at my first experience with logic.
anyway it is related with asio.
The asio src plugin doesn't show input 3 and 4,after input 2 there is asio-input 5..is it normal?
or is a bug on the src?

or maybe ,is related to the "mistaking asio maps" of the sb060,described around by dj?

mrvomit · Sep 25, 2004, 04:44 PM

sorry about the title,i know th. "asio" plugin is not the "src" plugin,but title can't be edited after you post.
anyway its related to "asio"plugin

**dj_stick** · Sep 25, 2004, 05:19 PM

on certain 10k1 boards these registers don't work, its a fix designed for the sb0060/sb010x models i tihnk

mrvomit · Sep 25, 2004, 06:01 PM

Ok i understood (argh its always a travel )
On epilog ,
asio 4/5 ------mapped in logic input 7/8
(so 4 IS WORKING,but mapped strangly)

LEMURY RENAMED "estetically" asio 4 & 5 =to 5 & 6
so in logic is like that:

On sb060 cards -with "ASIO profx plugin":

asio input 5/6 = mapped in logic input 7/8
(as logic strats counting asio from "1",not from "0" , like Kx)

man ,sure is always confusing with numbers

mrvomit · Sep 25, 2004, 06:04 PM

but this, mean th sb060 cards have less asio input than the others?

there are bad mapped (and is possible a sofware- adjustment)

,or are simply hardware-not-working,and in this case is not fully asio compliant?

**dj_stick** · Sep 25, 2004, 07:25 PM

i actually did a test on an SB010x model card with 3538a
each asio input in the asio profx module matched exactly with those in logic (taking into account the 0/1 count difference)

mrvomit · Sep 25, 2004, 08:49 PM

oh so is very promising,Cool!

Lex Nahumury · Sep 28, 2004, 10:33 PM

Hmm,..well it's a complicated story.

1.There is an issue with certain cards regarding the ASIO mapping.
So yes, those cards will have less ASIO "Inputs".
The rumours about this beeing fixed in 3538a are not officialy confirmed,
so I wouldn't rely on it to much.

2. The numbering of things in computer world is always a mess.
Programmers count from 0, most users from 1.
One Asio Sequencer counts from 0, another from 1.
So I decided to stick with the way most kX DSP-plugins are numbered.
In case of those 'troublesome' cards, numbering gets messed up even more
because of the shifting.
Not much you can do about that other then finding your correct mapping,
and write it down.

3. The 'Asio' plugin from the ProFX menu still needs to be re-written/improved
to detect those troublesome cards better.
Although I'm surprised it seem to function very well as it is, judging from user posts.

/LeMury

PS:
Im not sure which driver version mrvomit is using (I think 3537),
but in general I think it's a bad idea to promote newbies to use
the developer releases. This will only lead to false bug reports
and confusion.

**dj_stick** · Sep 28, 2004, 10:55 PM

Quote:

Originally Posted by LeMury

Hmm,..well it's a complicated story.

1.There is an issue with certain cards regarding the ASIO mapping.
So yes, those cards will have less ASIO "Inputs".
The rumours about this beeing fixed in 3538a are not officialy confirmed,
so I wouldn't rely on it to much.

i actually confirmed this myself on an SB0102 card (live 5.1), one of the affected models

Lex Nahumury · Sep 28, 2004, 11:15 PM

Quote:

Originally Posted by dj_stick

i actually confirmed this myself on an SB0102 card (live 5.1), one of the affected models

No offense dj, but I hardly call that 'official'.

Please correct me if I'm wrong but;
AFAIK Eugene has not confirmed this (actualy,he was suprised by those post),
nor was it mentioned in the 3538a changelog.

Moreover; I also tested one of the affected models,
after reading those reports, and it wasn't solved in my case.

Nevertheless I hope these reports may lead to a permanent fix.
Untill then it remains unofficial to me.

/LeMury

mrvomit · Dec 14, 2004, 06:52 AM

somebody knows if that is got/being fixed with the latest releses ,i got no clues browsing the Eugene posts about in "general " section.

Lex Nahumury · Dec 14, 2004, 10:12 AM

I seriously doubt that. (but who knows)
Point is, KX_OUT(0x11) and KX_OUT(0x12) are 'shared' with
Analog Center and Analog LFE on these issue cards.
So actualy you could get ASIO_IN to work on those ports,
however, those signals would also reach Center/lfe outputs.
That's why we don't 'connect' these ASIO_Inputs in microcode.

So my best guess about these 'reports' is that somehow/someway/sometime Epilog/kxlt
failed to detect an issue card therefore 'enabeling' those asio pins
and some people got asio input (not aware of faulty Center/lfe output).

But like I said; Who knows.....

/LeMury

**Eugene Gavrilov** · Dec 14, 2004, 09:56 PM

no, I cannot confirm the issue was fixed. at least, I really doubt that some of the changes I made could ever fix the issue

>> somehow/someway/sometime Epilog/kxlt
>> failed to detect an issue card

this is possible, since, for instance, the new sb22x boards have 5.1-capable ac97 codec, but DSP assignment is quite different compared to 'generic' 5.1- Lives. anyway, 3538g should detect sb22x, thus disabling asio inputs (although this is not necessarily correct).

E.