Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)

In message Brad Knowles writes: : However, that's precisely the kind of additional work that needs : to get folded into 4.0, so that 4.1 or 4.2 *is* ready for general use : in a production environment. What, specifically, is broken in 4.0 that would

Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)

At 10:07 AM 3/21/00 -0700, John Reynolds~ wrote: >I would have to agree with Jordan here. Of course with the plethora of PC >hardware combinations out there (with some of the marginally designed >components people pick up) it is impossible for the developers to make sure >100% of everything "works

Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)

don't worry guys I am stepping in however not today I have work related priorities dictating my time . Fortunately, I am coming out of my crunch. For years, I have supported you guys so please keep the flames down for starters thats not really who we are -- Remember we are friendly and cool 8)

Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)

Cameron Grant: |Randall Hopper: |> - Have we identified exactly what functionality is missing in the new |>sound driver but supported by Voxware? | |to my knowledge, midi is the only functionality missing. also, multiple |opens of /dev/dsp are not yet implemented. both will be soon.