Why don't you guys open pipes to ASIO for pulsar. Cubase works
fine, it's a shame that we can not use Vegas with Pulsar properly,
since both products are very cool.


Alex



Peter Haller wrote:
>>The Pulsar is _very_ resource intensive. To the point that
Creamware
>>recommends 256 meg of memory if you are going to do any programming
>>of the Pulsar.
>>
>>What I have seen is that the Pulsar control program is very graphic
>>intensive as well as memory intensive when loading programs.
>>Switching between Vegas and the Pulsar program can cause major
>>activity on both the video card and in memory. Jolts like this can
>>cause i/o operation to suspend long enough as to cause Vegas to
>>starve and therebye introduce gaps in its audio processing. If you
>>have multi busses routed to multiple Pulsar devices, and one of
these
>>busses is starved, Vegas will loose sync.
>>
>>We are working on a way to solve this for cards like the Pulsar. We
>>have found that the adding memory to a Pulsar system will improve
the
>>problem, but not completely resolve it.
>>
>>Peter
>>
>>
>>Thomas Kay wrote:
>>>>These two seem to have difficulties working together. They
>>>>work but I am very limited with what I can do in Pulsar as
>>>>it creates jitter and audio tracks in Vegas to be thrown
>>>>off. I have to go back into Vegas to restart song. But
>>>>sometimes when I'm in Vegas, audio has a hard time staying
>>>>together.
>>>>
>>>>Whose fault is this, Creamware or Sonic Foundry? I think
>>>>both products have alot to offer. But since software needs
>>>>soundcards, the two companies should work it out?
>>>>

When I used Cubase with Pulsar, my drivers could be thrown by looking
at it the wrong way. Never again.

Aleksandar Jovanov wrote:
>>
>>Why don't you guys open pipes to ASIO for pulsar. Cubase works
>>fine, it's a shame that we can not use Vegas with Pulsar properly,
>>since both products are very cool.
>>
>>
>>Alex
>>
>>
>>
>>Peter Haller wrote:
>>>>The Pulsar is _very_ resource intensive. To the point that
>>Creamware
>>>>recommends 256 meg of memory if you are going to do any
programming
>>>>of the Pulsar.
>>>>
>>>>What I have seen is that the Pulsar control program is very
graphic
>>>>intensive as well as memory intensive when loading programs.
>>>>Switching between Vegas and the Pulsar program can cause major
>>>>activity on both the video card and in memory. Jolts like this
can
>>>>cause i/o operation to suspend long enough as to cause Vegas to
>>>>starve and therebye introduce gaps in its audio processing. If
you
>>>>have multi busses routed to multiple Pulsar devices, and one of
>>these
>>>>busses is starved, Vegas will loose sync.
>>>>
>>>>We are working on a way to solve this for cards like the Pulsar.
We
>>>>have found that the adding memory to a Pulsar system will improve
>>the
>>>>problem, but not completely resolve it.
>>>>
>>>>Peter
>>>>
>>>>
>>>>Thomas Kay wrote:
>>>>>>These two seem to have difficulties working together. They
>>>>>>work but I am very limited with what I can do in Pulsar as
>>>>>>it creates jitter and audio tracks in Vegas to be thrown
>>>>>>off. I have to go back into Vegas to restart song. But
>>>>>>sometimes when I'm in Vegas, audio has a hard time staying
>>>>>>together.
>>>>>>
>>>>>>Whose fault is this, Creamware or Sonic Foundry? I think
>>>>>>both products have alot to offer. But since software needs
>>>>>>soundcards, the two companies should work it out?
>>>>>>

Peter, thanks for the reply. It would be great for Sonic Foundry to
pay serious R&D to this project as I really like this program.
Software companies have to, at least, find compatible partners for
their product to sell. I sell your stuff everyday and it would be
nice to know that if I sell a Delta 1010 to go with Vegas, it's going
to work. If you have any info about 100% compatible cards, let me
know. Please fix this multi I/O problem.

Thanks


Peter Haller wrote:
>>The Pulsar is _very_ resource intensive. To the point that
Creamware
>>recommends 256 meg of memory if you are going to do any programming
>>of the Pulsar.
>>
>>What I have seen is that the Pulsar control program is very graphic
>>intensive as well as memory intensive when loading programs.
>>Switching between Vegas and the Pulsar program can cause major
>>activity on both the video card and in memory. Jolts like this can
>>cause i/o operation to suspend long enough as to cause Vegas to
>>starve and therebye introduce gaps in its audio processing. If you
>>have multi busses routed to multiple Pulsar devices, and one of
these
>>busses is starved, Vegas will loose sync.
>>
>>We are working on a way to solve this for cards like the Pulsar. We
>>have found that the adding memory to a Pulsar system will improve
the
>>problem, but not completely resolve it.
>>
>>Peter
>>
>>
>>Thomas Kay wrote:
>>>>These two seem to have difficulties working together. They
>>>>work but I am very limited with what I can do in Pulsar as
>>>>it creates jitter and audio tracks in Vegas to be thrown
>>>>off. I have to go back into Vegas to restart song. But
>>>>sometimes when I'm in Vegas, audio has a hard time staying
>>>>together.
>>>>
>>>>Whose fault is this, Creamware or Sonic Foundry? I think
>>>>both products have alot to offer. But since software needs
>>>>soundcards, the two companies should work it out?
>>>>

Tom:

I hear what you are saying. We are working toward publishing a list
of compatable cards and a general FAQ.

I work just about everyday with different hardware vendors concerning
compatability. It is a daunting task to say the least.

Thanks
Peter


Thomas Kay wrote:
>>Peter, thanks for the reply. It would be great for Sonic Foundry to
>>pay serious R&D to this project as I really like this program.
>>Software companies have to, at least, find compatible partners for
>>their product to sell. I sell your stuff everyday and it would be
>>nice to know that if I sell a Delta 1010 to go with Vegas, it's
going
>>to work. If you have any info about 100% compatible cards, let me
>>know. Please fix this multi I/O problem.
>>
>>Thanks
>>
>>
>>Peter Haller wrote:
>>>>The Pulsar is _very_ resource intensive. To the point that
>>Creamware
>>>>recommends 256 meg of memory if you are going to do any
programming
>>>>of the Pulsar.
>>>>
>>>>What I have seen is that the Pulsar control program is very
graphic
>>>>intensive as well as memory intensive when loading programs.
>>>>Switching between Vegas and the Pulsar program can cause major
>>>>activity on both the video card and in memory. Jolts like this
can
>>>>cause i/o operation to suspend long enough as to cause Vegas to
>>>>starve and therebye introduce gaps in its audio processing. If
you
>>>>have multi busses routed to multiple Pulsar devices, and one of
>>these
>>>>busses is starved, Vegas will loose sync.
>>>>
>>>>We are working on a way to solve this for cards like the Pulsar.
We
>>>>have found that the adding memory to a Pulsar system will improve
>>the
>>>>problem, but not completely resolve it.
>>>>
>>>>Peter
>>>>
>>>>
>>>>Thomas Kay wrote:
>>>>>>These two seem to have difficulties working together. They
>>>>>>work but I am very limited with what I can do in Pulsar as
>>>>>>it creates jitter and audio tracks in Vegas to be thrown
>>>>>>off. I have to go back into Vegas to restart song. But
>>>>>>sometimes when I'm in Vegas, audio has a hard time staying
>>>>>>together.
>>>>>>
>>>>>>Whose fault is this, Creamware or Sonic Foundry? I think
>>>>>>both products have alot to offer. But since software needs
>>>>>>soundcards, the two companies should work it out?
>>>>>>

ASIO is not an open standard. It is controlled by a company that is,
well, our competitor. We cannot assume that we would have any voice
in how the spec would progress. This would leave us at the mercy of
Stienberg. This is not good for our end users.

We have found that properly implemented Wave drivers are what is
needed. When a driver is written correctly, none of our applications
have issues with audio i/o. I am not saying that we are never at
fault, but audio problems can be traced back to the drivers 90% of
the time.

We work very hard with all hardware vendors that are interested. We
have never turned away from helping to solve driver related issues,
whether they are the driver's or a problem with our software.

As far as the Puslar goes specifically, I am working on solutions to
the problems that users have been experiancing.

This also comes down to priortiy issue.

While the Pulsar is a very powerful card, it is not a widely used
card. When a problem comes in from users we have to weigh it by the
installed base as far as what gets fixed first. If there is a problem
reported with say an Event/Echo card, this must take priority as
there are many more users that have these cards than the Pulsar.
(Note, there are little if any problems with our applications and the
Echo cards.)

This does not mean we ignore the Pulsar problems, but that the larger
installed base must be addressed first. I know that this may not be
what a particular card user wants to hear, but this is the way it has
to be.

Having said this, we never let an issue go unresolved. If we can fix
it, we will. If it means spending time with the hardware vendor, we
do that. What ever it takes.

Peter



Aleksandar Jovanov wrote:
>>
>>Why don't you guys open pipes to ASIO for pulsar. Cubase works
>>fine, it's a shame that we can not use Vegas with Pulsar properly,
>>since both products are very cool.
>>
>>
>>Alex
>>
>>
>>
>>Peter Haller wrote:
>>>>The Pulsar is _very_ resource intensive. To the point that
>>Creamware
>>>>recommends 256 meg of memory if you are going to do any
programming
>>>>of the Pulsar.
>>>>
>>>>What I have seen is that the Pulsar control program is very
graphic
>>>>intensive as well as memory intensive when loading programs.
>>>>Switching between Vegas and the Pulsar program can cause major
>>>>activity on both the video card and in memory. Jolts like this
can
>>>>cause i/o operation to suspend long enough as to cause Vegas to
>>>>starve and therebye introduce gaps in its audio processing. If
you
>>>>have multi busses routed to multiple Pulsar devices, and one of
>>these
>>>>busses is starved, Vegas will loose sync.
>>>>
>>>>We are working on a way to solve this for cards like the Pulsar.
We
>>>>have found that the adding memory to a Pulsar system will improve
>>the
>>>>problem, but not completely resolve it.
>>>>
>>>>Peter
>>>>
>>>>
>>>>Thomas Kay wrote:
>>>>>>These two seem to have difficulties working together. They
>>>>>>work but I am very limited with what I can do in Pulsar as
>>>>>>it creates jitter and audio tracks in Vegas to be thrown
>>>>>>off. I have to go back into Vegas to restart song. But
>>>>>>sometimes when I'm in Vegas, audio has a hard time staying
>>>>>>together.
>>>>>>
>>>>>>Whose fault is this, Creamware or Sonic Foundry? I think
>>>>>>both products have alot to offer. But since software needs
>>>>>>soundcards, the two companies should work it out?
>>>>>>

Peter,

The way you have decided to handle solving your problems with
soundcards is completely reasonable. But if I may ask: Do you have
even the MOST tentative estimate as to when (assuming if) we can see
this problem resolved?

James

3Q 2000 as a guess, since I don't even know what the problem is you
are concerned with????

Peter



wrote:
>>Peter,
>>
>>The way you have decided to handle solving your problems with
>>soundcards is completely reasonable. But if I may ask: Do you
have
>>even the MOST tentative estimate as to when (assuming if) we can
see
>>this problem resolved?
>>
>>James

Ahh. Sorry. I am asking about the Pulsar/ 'devices coming out of
sync' problem.

James

Peter Haller wrote:
>>3Q 2000 as a guess, since I don't even know what the problem is you
>>are concerned with????
>>
>>Peter