Hello Foundry fellows,
I must comment you on one of the most wonderful pieces of
Audio software to ever arrive for the PC. Your windows
standard - non proprietary - simple - and efficient Vegas is
outstanding.
I downloaded the demo a long time ago, but have yet to
purchase the software due to the fact that it is not
compatible with my hardware.
I am a Samplitude owner, and your software packages are very
similar in many ways. Samplitude has you beat for wealth of
features, but you have them hands down on ease of use and
efficiency.
The problem is that BOTH Samplitude and Vegas access the
window's MME in a similar way, and lead to the same problem
in Pulsar. When using multiple outputs (wave devices) the
wave drivers will lose sync with one another. This happens
when audio glitches for any reason. For example. Route your
kick track to Bus A (Pulsar wave driver one) and your snare
to Bus B (Pulsar wave driver 2). Then start to drag a
window and hold (or perform any other GUI sort of thing) the
audio will glitch for a second. This is bad enough, but the
really horrible thing is when it comes back you will have
the snare track playing apriciably later than it should be.
This can make the best drummer sound pretty bad. You
should try auditioning reverb patches this way too... makes
the predelay WAY too long ;)
I believe that this problem is caused by a combination of
things:
1. The way you and SEK'D talk to hardware.
2. Shitty (excuse me) Creamware Wave devices.
Although I am fairly sure that #1 plays a role (as all other
programs that use windows MME don't do this), it is my
belief that the real blame rests on Creamware.
Why am I coming to complain to you then?
Well, I want to use (buy) your software. I cannot justify
owning TWO expensive software packages that have the same
problem with my hardware, and I cannot currently afford a
new card. Also, the Pulsar is conceptually quite a cool
system, and if it worked with Vegas and Samplitude I'd be
glad to use it.
You have emntioned in the past on this board that you will
not support ASIO because it is not entirely open. What
about EASI?
EASI is open. And from what I understand it is not terribly
hard to implement. EASI drivers are imminent for the
Pulsar, and would perform with even lower latency than MME
with all the cards that will support it. The venerable
STUDI/O already does.
So... Here is the essence of my tirade:
A. Is there any chance (from your perspective) that the
problem affecting Pulsar will be fixed? In MME I mean.
B. Even if the answer to that question is "Thats
Creamware's problem" Will you implement EASI into Vegas?
I certainly hope that one of the answers is Yes. ;)
regards,
James Johnson
I must comment you on one of the most wonderful pieces of
Audio software to ever arrive for the PC. Your windows
standard - non proprietary - simple - and efficient Vegas is
outstanding.
I downloaded the demo a long time ago, but have yet to
purchase the software due to the fact that it is not
compatible with my hardware.
I am a Samplitude owner, and your software packages are very
similar in many ways. Samplitude has you beat for wealth of
features, but you have them hands down on ease of use and
efficiency.
The problem is that BOTH Samplitude and Vegas access the
window's MME in a similar way, and lead to the same problem
in Pulsar. When using multiple outputs (wave devices) the
wave drivers will lose sync with one another. This happens
when audio glitches for any reason. For example. Route your
kick track to Bus A (Pulsar wave driver one) and your snare
to Bus B (Pulsar wave driver 2). Then start to drag a
window and hold (or perform any other GUI sort of thing) the
audio will glitch for a second. This is bad enough, but the
really horrible thing is when it comes back you will have
the snare track playing apriciably later than it should be.
This can make the best drummer sound pretty bad. You
should try auditioning reverb patches this way too... makes
the predelay WAY too long ;)
I believe that this problem is caused by a combination of
things:
1. The way you and SEK'D talk to hardware.
2. Shitty (excuse me) Creamware Wave devices.
Although I am fairly sure that #1 plays a role (as all other
programs that use windows MME don't do this), it is my
belief that the real blame rests on Creamware.
Why am I coming to complain to you then?
Well, I want to use (buy) your software. I cannot justify
owning TWO expensive software packages that have the same
problem with my hardware, and I cannot currently afford a
new card. Also, the Pulsar is conceptually quite a cool
system, and if it worked with Vegas and Samplitude I'd be
glad to use it.
You have emntioned in the past on this board that you will
not support ASIO because it is not entirely open. What
about EASI?
EASI is open. And from what I understand it is not terribly
hard to implement. EASI drivers are imminent for the
Pulsar, and would perform with even lower latency than MME
with all the cards that will support it. The venerable
STUDI/O already does.
So... Here is the essence of my tirade:
A. Is there any chance (from your perspective) that the
problem affecting Pulsar will be fixed? In MME I mean.
B. Even if the answer to that question is "Thats
Creamware's problem" Will you implement EASI into Vegas?
I certainly hope that one of the answers is Yes. ;)
regards,
James Johnson