Peter, I think that was an old entry because:

also from the Pyramix website:
http://www.merging.com/download/V5_0/ASIO_Driver.pdf

I've got the drivers, but Vegas seems to crash a lot when I am trying to use it with Vegas. Nuendo seems to work pretty well. Both are using the ASIO 2.0 drivers.

Also, the word clock only seems to allow me to use 44, while my studio is set to 48.

Any ideas?

--Cory

(the specs of the mykerinos card are GREAT 24 in and out, and I'm out of PCI slots on the comp.... anyone got any ideas?)

Nope, no ideas.

What are you doing when it crashes? Be very specific.

Have you contacted Pyramix? What did they tell you? (I know, "it works with Cubase/Nuendo.")

Did they test their drivers with our (any other) software?

Vegas demos are fully available and they could easily test their stuff with ours in a few minutes.

Regardless, there is not much we can do as we don't have this hardware.

It is very unlikely that

- They would send us hardware to test
- We would purchase such hardware to test


I will ping them, but I would not expect a response.


Peter

I have contacted Pyramix and, you guessed it, "It works with Cubase"
is pretty much the answer I got.

As for the crashes, there are too many right now to be completely specific about. The biggest problem I am having is being unable to set the word clock to what I would like to set it to...

I am willing to send you my Mykerinos hardware by FedEx if that helps at all...

Thanks for the continuing support!

Wow, that's an offer Sony shouldn't refuse. A shame they can't wokr it into their own budget and business plan to test hardware.

I just talked to a guy in kansas who's used the Mykerinos card with SONAR and got it to work.... but he said he hasn't been able to get it to play well with sound forge... does that help at all? Do soundforge and vegas handle asio drivers the same way?

Here is a copy of one of the many errors I have gotten when trying to use the ASIO drivers..

Sony Vegas 7.0
Version 7.0d (Build 192)
Exception 0xC0000005 (access violation) WRITE:0x1 IP:0x78147138
In Module 'MSVCR80.dll' at Address 0x78130000 + 0x17138
Thread: GUI ID=0xAFC Stack=0x12F000-0x130000
Registers:
EAX=00000000 CS=001b EIP=78147138 EFLGS=00210246
EBX=0239bcb8 SS=0023 ESP=0012faf0 EBP=0012fb00
ECX=0000000f DS=0023 ESI=00003c00 FS=003b
EDX=00000000 ES=0023 EDI=00000001 GS=0000
Bytes at CS:EIP:
78147138: F3 AA 8B 45 F0 8B 4D 08 ...E..M.
78147140: 8B 55 10 03 C8 2B D0 52 .U...+.R
Stack Dump:
0012FAF0: 0000000F
0012FAF4: 00000000
0012FAF8: 398C37BF 396A0000 + 2237BF (vegas70k.dll)
0012FAFC: 0239B78E 02380000 + 1B78E
0012FB00: 00000000
0012FB04: 35279CB7 35260000 + 19CB7 (sfasio.dll)
0012FB08: 00000001
0012FB0C: 00000000
0012FB10: 00003C00
0012FB14: 0239BCB8 02380000 + 1BCB8
0012FB18: 0239BCB0 02380000 + 1BCB0
0012FB1C: 0239B0A8 02380000 + 1B0A8
0012FB20: 0239BCBC 02380000 + 1BCBC
0012FB24: 3526498F 35260000 + 498F (sfasio.dll)
0012FB28: 0239B78E 02380000 + 1B78E
0012FB2C: 00000001
> 0012FB44: 352A15EC 35260000 + 415EC (sfasio.dll)
> 0012FB48: 398C35A0 396A0000 + 2235A0 (vegas70k.dll)
> 0012FB68: 398B5EC7 396A0000 + 215EC7 (vegas70k.dll)
> 0012FB84: 7C839AA8 7C800000 + 39AA8 (kernel32.dll)
> 0012FB88: 7C8025F8 7C800000 + 25F8 (kernel32.dll)
> 0012FB90: 7C8025F0 7C800000 + 25F0 (kernel32.dll)
> 0012FB94: 7C802532 7C800000 + 2532 (kernel32.dll)
> 0012FB9C: 7C90D57D 7C900000 + D57D (ntdll.dll)
> 0012FBB4: 398B62DB 396A0000 + 2162DB (vegas70k.dll)
> 0012FBB8: 398B62F8 396A0000 + 2162F8 (vegas70k.dll)
> 0012FBD8: 0073F943 00400000 + 33F943 (vegas70.exe)
0012FBDC: 00239FE0 00140000 + F9FE0
0012FBE0: A0000000
0012FBE4: 0E01482B 0DFA0000 + 7482B
0012FBE8: 00000000
> 0012FC0C: 77D4885A 77D40000 + 885A (USER32.dll)
> 0012FC38: 004CF95C 00400000 + CF95C (vegas70.exe)
0012FC3C: A0000000
0012FC40: 0E01482B 0DFA0000 + 7482B
0012FC44: 00000000
0012FC48: A2F7AD78
> 0012FCB0: 00473B72 00400000 + 73B72 (vegas70.exe)
0012FCB4: 00000000
0012FCB8: 00000000
0012FCBC: 00390001 00390000 + 1
0012FCC0: 0D8E0070 0D7A0000 + 140070
> 0012FCD8: 7C16E0C7 7C140000 + 2E0C7 (MFC71.DLL)
> 0012FCDC: 00474E37 00400000 + 74E37 (vegas70.exe)
0012FCE0: 00000000
0012FCE4: 00000100
0012FCE8: 00000020
0012FCEC: 00390001 00390000 + 1
> 0012FD20: 77D48B26 77D40000 + 8B26 (USER32.dll)
> 0012FD34: 004239D0 00400000 + 239D0 (vegas70.exe)
> 0012FD3C: 77D488D1 77D40000 + 88D1 (USER32.dll)
> 0012FD48: 77D488DA 77D40000 + 88DA (USER32.dll)
> 0012FD54: 00475702 00400000 + 75702 (vegas70.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 009302DB 00400000 + 5302DB (vegas70.exe)
0012FFFC: 00000000

We do work it into our budget and business plan. We purchase a ton of hardware - mainstream and some not so mainstream.


The Mykerinos cards are VERY non-mainstream. It is not designed to be a general purpose ASIO audio solution, but a propretary audio solution for their specific software platform.

We have to balance the cost to benfit of any purchase. My bet is that 1 user of all of our products - cchoy - uses this card. If not, we would have heard about it before - we have not.

Regardless, Merging has contacted us and told us they have problems with their ASIO drivers and other hosts - including Stienberg's. They are preparing an update. I have arranged for licenses for them for all of our products that support ASIO. They have my contact information (and phone #) if they believe they have discovered something we are doing wrong.

I believe it is their drivers otherwise every other ASIO driver would crash in the exact same way. However, if they can point out what we are doing wrong, then we will fix it.

Peter

I contacted and was contacted by Merging Technologies.

They are preparing an update to their ASIO drivers because there are compatability issues with many hosts.

I have arranged full licenses of our products for them so they can test and veryify their drivers before they are released. (They could have always tested against the demo versions, but it is obvious they did not.)

I believe it is their drivers otherwise every other ASIO driver would crash in the exact same way. However, if they can point out what we are doing wrong, then we will fix it. (Do a Google on "Mykerinos ASIO" and you will read many stories of incompatabilities. A number of "colorful' words are used to describe the ASIO drivers.)

Anyway, if it is at all possible, and Merging follows through with me, we will get this fixed one way or another. I have no reason to expect Merging not to work with us to resolve this problem.

Thanks for the offer, but no, I cannot do this. It is up to Merging to deal with this issue and work with us. It is to there benifit as well as ours for them to fix their ASIO drivers or tell us what we are doing wrong. If it is important, then we can arrange with Merging to provide us hardware if need be.


Peter

>>The biggest problem I am having is being unable to set the word clock to what I would like to set it to...

With out having the hardware, I cannot know what it is you are trying to do and the resultant problems you are having.

Can you be specific and elaborate on what is not working - remembering that I don't have the hardware.

Peter

I am very excited about Sony and Merging talking together to make the products work. I love Vegas' interface and useabilty, and want to do everything I can to make sure that the studio here implements it as a viable mixing tool as an alternative to ProTools!

thanks for the continuing support!

=================

What I am trying to do is use the Mykerinos ASIO drivers (with 24 ins and outs) as the I/O for Vegas. When I have the Mykerinos card selected Vegas takes an unusually long time to boot. I cannot use a project other than 44.1 or the program crashes. Switching to the Mykerinos cards under audio devices sometimes crashes the program. After the mykerinos card has been selected, it takes about 2 minutes to get to the timeline. Every once in a while I can get sound to play. More often then not, though, the program unexpectedly quits. This is with Vegas 7.d

However, I just tried a few things with Vegas 5, and it seemed to work a little bit longer. I was able to play sound through the drivers for about 15 minutes before the program crashed...

I will write more detailed notes soon.

>>When I have the Mykerinos card selected Vegas takes an unusually long time to boot.
<<

Q: Did you read the ASIO pdf you pointed me to?

From the ASIO pdf manual for this card:

"Routing and Other Changes Take a long Time

This is due to the hardware design and limitations of the ASIO drivers. Due to the design of the ASIO driver the only way of informing the application of new settings is by forcing a reset of the driver. The driver has to be reloaded and this takes a considerable amount of time."

If it takes that long to rest the driver on routing changes, then it will take a long period for the driver to be enumerated when Vegas starts up as Vegas interogates the driver as startup for validity and availablity.

Nothing we can do about this.

Note also that Vegas does not support the control of clock sources or Direct Input Monitoring. If the driver does not correctly report clock source changes - as well as sample rate changes - then any number of problems - crashing specifically - could occur. The driver must tell us about external changes otherwise we are unable to deal with them.

I am waiting to see what Merging discovers with their new drivers and the licenses I sent them of Vegas and ACID. In the mean time, there is nothing that can be done about any of this.

Peter

Peter, you could offer to write them a decent driver, in your spare time ! ;-)

geoff

<bg>

I am sure that their pending update will solve the problems. They were very interested and responsive to solve this problem. They were aware of a number of issues with other host applications.

It is refreshing to have a hardware vendor interested in working with us.

Peter

I did read that PDF...

I hope that their update comes soon.

On a different note, I know that the mykerinos daughter card that I have also has video support. Would vegas be able to use this as a video source? or is that another can of worms completely?

>>Would vegas be able to use this as a video source?

Don't know. Ask in the video forum.

Better yet, ask Merging as they should know how their hardware works and what it works with.

Peter

Peter,
Keep up the good work, This gives us hope that somebody at SMS is noticing and interested audio related issues and problems.
Rick