Lynx AES16e PCI Express card!

[TEMAS]

Originally Posted by nativeaudio

This already looks good, and will look even better when faster computers come out, because we then can stick to lower buffer settings more than we can do today, and even use 16 samples buffers.

Excellent; and thanks a lot for listing all that in such a logical way.

So with the new range of MacPros would it be unheard of for the 16 sample buffer scenario? Whats the best one could hope to acheive with an 8-Core system, with say 16 or 24 stereo tracks ok audio?

[ToddS]

Originally Posted by TEMAS

Excellent; and thanks a lot for listing all that in such a logical way.

So with the new range of MacPros would it be unheard of for the 16 sample buffer scenario? Whats the best one could hope to acheive with an 8-Core system, with say 16 or 24 stereo tracks ok audio?

Only Logic AFAIK can go as low as 32 samples currently. Cubase/Nuendo is 64. But I also remember hearing that PCs are inherently faster than Macs? Is ASIO faster than Core Audio? Will the AES16e be slower on the Mac?

It will be interesting to test if these specs hold up under real world sessions. Symphony has already proven itself in the real world. The AES16e is still vapor. On top of that, the tests were done without plugs, or high track counts (cant really do high track counts with a 16 channel card), so we will have to wait to know the answer.

[drmad69]

And there are many native concerns about the way the driver behaves;
For instance the rme driver clicked when it had dropouts; and always stayed phase accurate. lynx didn't fix that functionality for years.
There are also a couple other things in some of the benchmarks that came
out that require questions to be asked.
Those latency questions are assuming a perfect blank project, no disk, etc.
There is no reason that the second you add 1 or 2 channels it does start
dropping out. I found the lynx cards to be way more sensitive about
the hardware they were in; maybe pcie will fix that. Hopefully it would
fix the issues with multiple cards.
(They seemed to be much more of a pci hog than the rme cards were;
so maybe extra bandwidth will magically fix the cards problems.)
(Lynx knows they were there; they even added debugging tools to the
end user mixer.)

There are also things that have not been answered, and that have been
documented to operate quite differently between the leaders drivers on the benchmarks.

#1. Lynx says the driver is multi-cpu capable; so the question has been posed
but not answered if the stability of no dropouts would be based on a aggregate
of the total sum of all the cpu's or just what happens if core 0/1 is 50%.
(Comes down to how each manufacture threads their driver.)
(So assuming multi-core is off, and you're just using 1 cpu; you fill it
50%; lets say the driver begins to drop samples. If that same cpu hits
50% in multi-core mode, does it drop samples.)

#2. The behavior of lynx and their dropout situation has changed and is supposed to change again; sure one isn't supposed to get dropouts; but their
hw seems to be far more prone to it. (am example is the big samplitude issue, but many people experienced it with cubase, runaway dropouts under no load, etc)
#3. routing just got added, so you could have more than 4 monitoring sources;
since it's pcie, is the card going to finally support a routing matrix like rme,
anything to anywhere, etc, at it's highest sample rate?

If I was going to buy a pcie card; I'd kind of want to feel that all the arcticture
issues with the aes16 were solved with the aes16-pcie; and I'm under
the impression none of them will be.

You know, hard issues to solve or not a 1-2 year turn around isn't acceptable;
I don't know how many times I was told they were to busy with aurora.

It's obviously their new cash cow; doesn't have the riddled issues the old
interface did; nor the support issues; I for the life of me don't see
why they even bother releasing another card, based on the market.

And well, I guess it hasn't happened yet either.
But I'll say this; they bug fix process takes as long as their announcement to delivery.

[nativeaudio]

Originally Posted by TEMAS

Excellent; and thanks a lot for listing all that in such a logical way.

So with the new range of MacPros would it be unheard of for the 16 sample buffer scenario? Whats the best one could hope to acheive with an 8-Core system, with say 16 or 24 stereo tracks ok audio?

Maybe the new MacPros could have used the 16 buffer already, but it isn't an option yet. Using Apogee Symphony as a reference, their famous latency test was done on an old 2.66GHz Dual-Core Mac, and they ran 32 tracks playback/32 tracks recording using the 32 buffer (the sample rate was 96 kHz).

People have reported that the old 8-core was almost 50% faster than the old 4-core, so the new 8-core is definitely a lot faster than that Dual 2.66. Plus, if you don't record @ 96 kHz, but at 48, you should get twice as much power (in terms of possible tracks). Additionally, the new 3.2 gHz 8-core is 20% faster than the 3.0 gHz 8-core.

I've also heard that it was possible to get 200 stereo 16 bit/44.1 tracks on the old 8 core and Logic 8 (using higher buffer settings), and with all the power that old Dual 2.66 Mac test demonstrated with the 32 buffer, I can't see why the 16 sample buffer should not be usable on a 8-core 3.2 gHz Mac if only a DAW would allow us to enable it.

[deuc647]

Now i wanna know the specs of the XP PC they used, this card sounds too good to be true, but im not gonna doubt lynx. These cards sound good, but i wanna stay PC and want to know the specs of the PC they used........did i mention i wanna know the specs of the PC used, lol!

[broken head]

Originally Posted by deuc647

Now i wanna know the specs of the XP PC they used, this card sounds too good to be true, but im not gonna doubt lynx. These cards sound good, but i wanna stay PC and want to know the specs of the PC they used........did i mention i wanna know the specs of the PC used, lol!

The test computer was a std. Dell Dimension 9200, 2.4G DuoCore, 1GB RAM, Single SATA HDD, XP Home SP2. Basic OS Optimizations.

But again, this was with beta drivers and firmware. WHen we have release versions we will post "official" performance numbers.

[DRC]

Originally Posted by David Hoatson

Cards Per System: The driver can handle up to 8 cards per system - but of course your mileage may vary depending on how your system is configured and how many free slots you have. Starting with OSX 10.4 Apple gave us Aggregate device support which means you can combine the i/o on multiple cards and that is what we expect you to use with your software (except Digital Performer which always supported multiple cards). I'm just trying to make it clear that the driver has always supported multiple cards, but the OS X audio applications (except DP) could only talk to one card at a time. Starting with OSX 10.4 that limitation is gone.

Thats awesome! Guess I don't have to start looking at a Symphony or PT HD.

Originally Posted by broken head

The test computer was a std. Dell Dimension 9200, 2.4G DuoCore, 1GB RAM, Single SATA HDD, XP Home SP2. Basic OS Optimizations.

But again, this was with beta drivers and firmware. WHen we have release versions we will post "official" performance numbers.

I'm guessing those numbers will be posted for Mac users too? Please let us know the performance with the different DAW's as well (Logic, Cubase, etc.) And thanks for the update.

[deuc647]

Originally Posted by broken head

The test computer was a std. Dell Dimension 9200, 2.4G DuoCore, 1GB RAM, Single SATA HDD, XP Home SP2. Basic OS Optimizations.

But again, this was with beta drivers and firmware. WHen we have release versions we will post "official" performance numbers.

Thats fukin sweet! I guess the specs on a quad core will be great, i might just stay ITB after all.

[broken head]

Originally Posted by DRC

I'm guessing those numbers will be posted for Mac users too? Please let us know the performance with the different DAW's as well (Logic, Cubase, etc.)

Yessir. Will do...

[not_so_new]

Hi Paul / David

First off, I really like your products I hope you don't take the post below as a knock on you guys.



That said I am getting a little turned off by my current Lynx card, your honest answers to the questions below would go a long way to regaining my confidence in your products.

1) I am using Samplitude 8.3, I already have an AES16 and I do run into dropout problems often. If I unload the ASIO driver in Samp by switching to MME, saving and then switching back to ASIO that seems to fix it but it is a pretty annoying issue to deal with multiple times in the middle of a session. Is this fixed with the new AES16e card drivers?

2) I need to keep running my existing AES16 card with a new AES16e, I can do that right? I can get to and use I/O from both cards at the same time with Samp on Windows XP SP2?

3) I can do full 16 channel I/O hardware monitoring with the new AES16e card even if I am using the old AES16 card as well correct?

4) My dealer is telling me to stay away from the AES16e card because "there are going to be issues with it when it comes out." I think that is a little unfair based on the fact that the cards have not even shipped yet…. but it does point to some uncertainty in the marketplace on your hardware.

Have you tested the card with multiple DAW's and what can you do to ease the fears of your customers related to this subject? Honestly I have been thinking about dumping my Lynx AES card because of the delay in the AES16e and the multiple issues that never seem to go away using that card with Samp (I am not alone judging by the number of posts on the Samp forum related to this same subject).

Thanks guys. Again, not bashing a great company just want to know what I am getting into if I go with the AES16e.

[broken head]

Hey there,

Originally Posted by not_so_new

Hi Paul / David

First off, I really like your products I hope you don't take the post below as a knock on you guys.

No problem

Originally Posted by not_so_new

1) I am using Samplitude 8.3, I already have an AES16 and I do run into dropout problems often. If I unload the ASIO driver in Samp by switching to MME, saving and then switching back to ASIO that seems to fix it but it is a pretty annoying issue to deal with multiple times in the middle of a session. Is this fixed with the new AES16e card drivers?

Unfortunately, this is not nearly so simple. If there is a bug in the ASIO drivers, then one could expect some degree of consistency on its occurrence (i.e. do this, then this, then this, and then the app crashes).

Samplitude has been a rather unusual case. First off, I should say that we did not have a substantial number of users of V8 reporting problems. From our internal testing and input from users there was not an intrinsic compatibility issue between the two.

With version 9 we started getting feedback about a dizzying array of issues, from Lost ASIO buffers, dropouts and glitching, etc. Keeping in mind that the driver hadn't changed when these symptoms started to appear, but the ASIO engine in Samplitude had. Unfortunately, the users' experiences have been all over the map as have steps that seem to improve the situation (generally app specific changes like closing the editor, updating the dongle driver, disabling MIDI, etc.). Also, users were reporting that Lost ASIO Buffers were flagged, when there were no signs of any audio anomalies at the flagged position (a mechanism for LAB reporting is not part of the ASIO spec). Many users reported that the problems were app specific, not appearing in other ASIO apps that they tested.

We have provided Magix with hardware to attempt to replicate these problems which they have not had success replicating as yet.

Anyway, if your difficulties are with Version 8, it would be best if we could take some steps to make sure we know what we are looking at. I would recommend that you give me a call so we can do some diagnostics. We could even do a conference call with Magix support to try and get to the bottom of it. A symptom of dropouts occurring can have a variety of causes that we could look at.

Originally Posted by not_so_new

2) I need to keep running my existing AES16 card with a new AES16e, I can do that right? I can get to and use I/O from both cards at the same time with Samp on Windows XP SP2?

Yes, both cards will be unified under ASIO in Windows

Originally Posted by not_so_new

3) I can do full 16 channel I/O hardware monitoring with the new AES16e card even if I am using the old AES16 card as well correct?

Do you mean monitoring all 16 inputs through a pair of outputs? If so, this would be possible with both the AES16 and AES16e. You cannot do hardware monitoring of inputs from one card through outputs of another card.

Originally Posted by not_so_new

4) My dealer is telling me to stay away from the AES16e card because "there are going to be issues with it when it comes out." I think that is a little unfair based on the fact that the cards have not even shipped yet…. but it does point to some uncertainty in the marketplace on your hardware.

There are some users and dealers that have a blanket policy to avoid new products until they have been market tested for a period of time. This is an individual decision which everyone would have to make for themselves.

However, the ship date delay is precisely so that the product that ships is reliable for a realworld context. Also, although the bus is new, a 16-channel AES/EBU audio interface is not something new to us. The Aurora was a much wider leap from our existing line, and that has been very successful in the market for four years without any notable design changes.

Originally Posted by not_so_new

Have you tested the card with multiple DAW's and what can you do to ease the fears of your customers related to this subject?

Well, one of the benefits of a driver standard like ASIO, is that when an app implements it correctly, a properly written ASIO driver should work with it reliably. Not to say that driver development is easy, by no means the case, but that there generally is not a lot of app-specific alterations that need to occur.

That being said, the driver gets rigorously tested with all of the major DAW applications under OSX and Windows.

[not_so_new]

Hi Paul.

Originally Posted by broken head

Do you mean monitoring all 16 inputs through a pair of outputs? If so, this would be possible with both the AES16 and AES16e. You cannot do hardware monitoring of inputs from one card through outputs of another card.

Sorry, I didn't make myself as clear as I should have... my bad.



The AES16 will only do hardware monitoring to 4 outputs from what you told me before. As I understand it the AES16e will let me use hardware monitoring on all 16 channels right?

If that is the case and I have an AES16 and an AES16e in the same system can I use all 16 I/O channels on the AES16e for hardware monitoring? I am not taling about channels between the two cards, I just need to have hardware monitoring for more than 4 channels.

I hope that makes a little more sense this time.


Thanks again man.....

[broken head]

Hey there,

Originally Posted by not_so_new

The AES16 will only do hardware monitoring to 4 outputs from what you told me before. As I understand it the AES16e will let me use hardware monitoring on all 16 channels right?

Actually with the current firmware and driver, the AES16 can monitor up to 9 sources per output up to 96k using the Lynx Mixer, and up to 22 sources per output using ASIO Direct Monitoring (up to 48k). The AES16e will be similar initially, and then expand the monitor sources in the next version of the mixer. The AES16e has siginificantly more DSP resources, so will not ultimately have the same monitor source limitations as the AES16.

SO, the short answer is that you will be able to monitor 16 input channels through a pair of outputs at rates up to 96k. Feel free to call me with specifics of your situation and we can discuss.

[drmad69]

There are several dealers that got the wind of bad feedback on the AES16, so it
just isn't a new products thing. Nobody said to avoid the ICON that I know of.

Interestingly enough as well; as far as I know; no other audio card maker
had the several dozens of issues with samplitude that lynx did.

Unfortunately most vendors won't let you demo the cards; I'd suggest because of all the press lynx does some sort of manufacturer try before by gig. It's not like they'd loose alot over a demo pool of used cards. But; again; that could be bad
for them too; as I'd bet there's a few that would be looking at other options after
using it for a couple weeks.

And I would certainly suggest comparing it, with not only a comparable high end
product, but even it's driver compatibility with the $15 cards. Unfortunately; I saw bottom of the barrel cards have less overall issues then the AES16.

Originally Posted by not_so_new

Hi Paul / David

First off, I really like your products I hope you don't take the post below as a knock on you guys.



That said I am getting a little turned off by my current Lynx card, your honest answers to the questions below would go a long way to regaining my confidence in your products.

1) I am using Samplitude 8.3, I already have an AES16 and I do run into dropout problems often. If I unload the ASIO driver in Samp by switching to MME, saving and then switching back to ASIO that seems to fix it but it is a pretty annoying issue to deal with multiple times in the middle of a session. Is this fixed with the new AES16e card drivers?

2) I need to keep running my existing AES16 card with a new AES16e, I can do that right? I can get to and use I/O from both cards at the same time with Samp on Windows XP SP2?

3) I can do full 16 channel I/O hardware monitoring with the new AES16e card even if I am using the old AES16 card as well correct?

4) My dealer is telling me to stay away from the AES16e card because "there are going to be issues with it when it comes out." I think that is a little unfair based on the fact that the cards have not even shipped yet…. but it does point to some uncertainty in the marketplace on your hardware.

Have you tested the card with multiple DAW's and what can you do to ease the fears of your customers related to this subject? Honestly I have been thinking about dumping my Lynx AES card because of the delay in the AES16e and the multiple issues that never seem to go away using that card with Samp (I am not alone judging by the number of posts on the Samp forum related to this same subject).

Thanks guys. Again, not bashing a great company just want to know what I am getting into if I go with the AES16e.

[ImJohn]

Originally Posted by drmad69

Interestingly enough as well; as far as I know; no other audio card maker had the several dozens of issues with samplitude that lynx did.

And on the other side of the coin no other software DAW maker had the several dozens of issues with Lynx hardware that Magix has with Samplitude.

Just felt the need to balance the statement because as far as I know, no one has identified the exact source of all the issues and it could be one or the other or both . . .

[drmad69]

Well, that's not entirely true, for a long time there was issues with controlling the
asio direct stuff, with cubase; in fact seems to be issues with just lynx every time steinberg revs their product; which required a driver change and many iterations of testing.
And no other daw has had widely known problems with any other card, including
magix, which really; points at the lynx driver. The fact that after years users still
report their V1 driver to be more stable than V2; and have card order control;
is just an example on how their haven't solved their core issues or moved forward.
The fact that the problem couldn't be identified, or was not good publicity to release; doesn't make me feel any better about the issue being put to rest either.

Remember, I have multiple installs of the AES16, since they were released.
After 3 years of bugs and issues on more than 4-5 machines; I gave up.
At some point I was posting what a big PITA they were and somebody said;
Then shutup and buy a different one...And I figured, I was sick of betaing their
product and haven't had a lick of problems since I switched.

[not_so_new]

Originally Posted by drmad69

Well, that's not entirely true, for a long time there was issues with controlling the
asio direct stuff, with cubase; in fact seems to be issues with just lynx every time steinberg revs their product; which required a driver change and many iterations of testing.
And no other daw has had widely known problems with any other card, including
magix, which really; points at the lynx driver. The fact that after years users still
report their V1 driver to be more stable than V2; and have card order control;
is just an example on how their haven't solved their core issues or moved forward.
The fact that the problem couldn't be identified, or was not good publicity to release; doesn't make me feel any better about the issue being put to rest either.

Remember, I have multiple installs of the AES16, since they were released.
After 3 years of bugs and issues on more than 4-5 machines; I gave up.
At some point I was posting what a big PITA they were and somebody said;
Then shutup and buy a different one...And I figured, I was sick of betaing their
product and haven't had a lick of problems since I switched.

Which is my main worry.

I already have a lot invested in Lynx, I have an AES16, the drivers are already installed (I hate swapping out drivers on a production machine), I have special cables made for my AD-16x and DA-16x converters and the cables are burred in my rack.

I have been SERIOUSLY considering making the jump to RME cards but that would cost me a chunk of change. First my AES16 card is not going to be worth as much now that the AES16e card is out, then I need 2 RME cards and all new cables plus I would have to get everything up and running in my system.

It sucks, I just wish the Lynx cards were more stable. If I get better stability and it sounds the same it might just be worth the pain now to make the jump.....

That is the fence I am on.


Anyway, is the AES16e available now? Anyone have a chance to use it yet?

[broken head]

drmad69 makes a number of assertions, including:

"with just lynx every time steinberg revs their product; which required a driver change and many iterations of testing."

"The fact that after years users still
report their V1 driver to be more stable than V2;"

"is just an example on how their haven't solved their core issues or moved forward."

I would encourage anyone reading these assertions to visit the Lynx forum and examine these issues themselves. If there was in fact, a firestorm of protest over these issues, that should be pretty easy to trace on a public forum.

Also, a visitor might see if the overall level of satisfaction with support that Lynx customers express, seems supported by the tone and statements of the poster. No single product can satisfy every user, especially a computer product. In my 4 years with Lynx there have been exactly 2 customers whom I thought for their situation is would be best for them to use a different product. This poster is one of those two - for the record....

In regards to the Magix problem, the fact is that when the ASIO engine was changed with Version9 that problems showed up, some of which are LAB reporting errors. By definition, I think that precludes this being only a driver issue. Still we are work with Magix to find a solution.

[not_so_new]

Originally Posted by broken head

drmad69 makes a number of assertions, including:

"with just lynx every time steinberg revs their product; which required a driver change and many iterations of testing."

"The fact that after years users still
report their V1 driver to be more stable than V2;"

"is just an example on how their haven't solved their core issues or moved forward."

I would encourage anyone reading these assertions to visit the Lynx forum and examine these issues themselves. If there was in fact, a firestorm of protest over these issues, that should be pretty easy to trace on a public forum.

Also, a visitor might see if the overall level of satisfaction with support that Lynx customers express, seems supported by the tone and statements of the poster. No single product can satisfy every user, especially a computer product. In my 4 years with Lynx there have been exactly 2 customers whom I thought for their situation is would be best for them to use a different product. This poster is one of those two - for the record....

In regards to the Magix problem, the fact is that when the ASIO engine was changed with Version9 that problems showed up, some of which are LAB reporting errors. By definition, I think that precludes this being only a driver issue. Still we are work with Magix to find a solution.

All very good points Paul.



I would just say one thing related to all of that.... my Samp issues are with 8.3, have always been there and have never really gotten much better. Also, there were plenty of users who exerpicend issues with ASIO dropouts with Samp 8, many of these (I would say "all" but I am not sure about that, I just know it was more than average) were AES16 users.

Not bashing Lynx, you guys make a great product. It just happens to be that my projects are tracked with Samp, I am kind of stuck using that DAW as of now and for better or worse my AES16 card is not always that happy with it.

[drmad69]

Exactly, This the exact reason it took me so long to jump when people said,
just use a different card, etc.
I also had two LS-ADAT's So that was another loss I'd take directly.
Had I been smart; I would have originally spent $500 for another rme card
and the spdif port I needed for the avocet; Rather than $2200+ on the several year hassle. But I bought into the hype that surrounds that product and got screwed. I kept hoping they'd work right.

You know; I never said support wasn't nice; Paul spent years working with me!
Between him and david they solved several problems. just not a few key showstoppoers; 2 of which were firmware changes that took over a year.
(Hey, great!, but heavens!!! This is a pro-audio product; not a DIY for audo
professionals that's projects take years to complete.

And in fact he had stated more than once;
I was one of the few using the cards fullest capabilities; and not just using it
for simple recording/playback. I tried those cards in over 6 different setups
before I gave up; and it was never considered a hardware problem with the cards.

And I would look in the forums; although I specifically got asked by paul/david not to post all my open problems on their forum for all the see.
I have about a dozen bugs in their private bugbase; most all confirmed; only some solved.

Most of these are not assertions; but more fact; Repeated by more than one person on the forum; and here.

Unfortunately; finding those common problems is about as easy as searching the duc or calling evey bbs in the country in the 80's to compare notes.

But; just search for something like (clicking, dropouts, bad driver, v1, v2, cubase 3 / 4 prodblems, external fx, sample drift)


I suppose there is comfort in paul's statement; That I was one of those two users.. So what I needed to do was:

Play 32 channels phase coherantly to a summer/analog mixer. (Not fixed for years)

At Other Times user 16 of the channels over ADAT;

Use 16+ Of the channels to do external FX. (Which drifted for years.)

Preferably play 1 pair of in/outs with some media player/mp3/etc. (Gave up on it.)
(although there's a slew of threads/etc, the multi client driver is flaky and changed consistantly.)

And I can't think of the rest anymore; Having the card order in V2 show up the

same way/configurable, like say PT.


I'm just saying be cautioned when buying these cards (remember the 4 source monitoring limitation that hosed who knows how many folks, stated on forum..)

But more than that; it's those flakey issues accross the platforms that
you may not see/put your finger on the card driver, etc for a month or two..
Right after you can't return it, have made cables, etc..


I have absolutely no interest is fibbing or blowing things out of proportion;

*EXCEPT* to keep people from all the hassles I did; and possibly eventually

raising the bar in the market place so it doesn't happen to me or others again.

(and maybe keeping people like nathan A, pimping the product for a year or so

claiming it's the best in the world and the dumping for PT HD and say his lynx

never worked right, etc, in the next post, etc)

Originally Posted by not_so_new

Which is my main worry.

I already have a lot invested in Lynx, I have an AES16, the drivers are already installed (I hate swapping out drivers on a production machine), I have special cables made for my AD-16x and DA-16x converters and the cables are burred in my rack.

I have been SERIOUSLY considering making the jump to RME cards but that would cost me a chunk of change. First my AES16 card is not going to be worth as much now that the AES16e card is out, then I need 2 RME cards and all new cables plus I would have to get everything up and running in my system.

It sucks, I just wish the Lynx cards were more stable. If I get better stability and it sounds the same it might just be worth the pain now to make the jump.....

That is the fence I am on.


Anyway, is the AES16e available now? Anyone have a chance to use it yet?

[laser]

Originally Posted by drmad69

But I bought into the hype that surrounds that product and got screwed. I kept hoping they'd work right.

I was one of the few using the cards fullest capabilities; and not just using it
for simple recording/playback.

Play 32 channels phase coherantly to a summer/analog mixer. (Not fixed for years)

This is exactly what I plan to use two AES16e cards for at 88.2 kHz. Can I safely assume that two Lynx AES16e cards will do this without issues?

I'd like to get a confirmation from Paul from Lynx that their product will be deliver 32 channels of audio (88.2 KHz) without problems.

Laser

[DRC]

Originally Posted by laser

This is exactly what I plan to use two AES16e cards for at 88.2 kHz. Can I safely assume that two Lynx AES16e cards will do this without issues?

I'd like to get a confirmation from Paul from Lynx that their product will be deliver 32 channels of audio (88.2 KHz) without problems.

Laser

Same here. I really, really just want something stable that can do 32 in and 32 out without a problem. I hate the idea of having to buy HD cards off of eBay.

[jeangodard]

Just a wild stab at it but, I'd guess that when the product comes onto the market we'll get an idea of how stable it is.

[mmcfarlane]

Any news on the latest ship date for either Lynx or RME's AES(16) PCIe card?

I've pre-ordered the Lynx card and am antsy that my new Aurora16 has never been turned on...