OpenAL fees are said to be small, NOT large as some suggested
Fees? There are no fees with OpenAL.
OpenAL Documentation said:Cost:
There is no charge for using OpenAL and free support is available on the mailing lists!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
OpenAL fees are said to be small, NOT large as some suggested
OpenAL Documentation said:Cost:
There is no charge for using OpenAL and free support is available on the mailing lists!
Fees? There are no fees with OpenAL.
Everybody I have talked to says for the most part audio has improved in Vista. Gaming not withstanding. The overall sound quality is said to be very good. You would think sound quality would be better in the new OS the audio routines are all brand new, the mixer is also brand spanking new. Improvements across the board it seems.
Well, Microsoft's audio team talk about hardware acceleration globally, which means both 2D and 3D components of DirectSound. If you were to say that removing hardware acceleration is only detrimental, in some aspects, to Creative card owners, you'd really be somewhat wrong -- thus my original point. The opinion that Microsoft was "targeting" Creative owners is quite absurd when we know that many other sound cards perform rudimentary hardware acceleration in XP. Maybe buffer acceleration was the main culprit in XP instability, and maybe it was other aspects, such as SRC, positioning, mixing or extensions that were the primary culprits. They really haven't said precisely what the issue was, which I take to mean that hardware acceleration in general was fubar.Obviously when we say "hardware acceleration" we mean DirectSound3D. It seems like what you wrote about was more or less semantics.
As these are the only Windows components. ASIO and OpenAL are really entirely separate things, as they have no real interaction with the stack in XP nor in Vista. If neither are installed on a given machine, then there are no hardware accelerated audio APIs in Windows Vista.No its not Only HW Acceleration of Direct Sound and DS3D is removed.
Well, Microsoft's audio team talk about hardware acceleration globally, which means both 2D and 3D components of DirectSound. If you were to say that removing hardware acceleration is only detrimental, in some aspects, to Creative card owners, you'd really be somewhat wrong -- thus my original point. The opinion that Microsoft was "targeting" Creative owners is quite absurd when we know that many other sound cards perform rudimentary hardware acceleration in XP. Maybe buffer acceleration was the main culprit in XP instability, and maybe it was other aspects, such as SRC, positioning, mixing or extensions that were the primary culprits. They really haven't said precisely what the issue was, which I take to mean that hardware acceleration in general was fubar.
As these are the only Windows components. ASIO and OpenAL are really entirely separate things, as they have no real interaction with the stack in XP nor in Vista. If neither are installed on a given machine, then there are no hardware accelerated audio APIs in Windows Vista.
The best Microsoft could do to prevent either of them working is to somehow lock down I/O, I guess.
From what I have heard so far it sounds pretty good. Directsound is still available for Audio player Plugins. I am mentioning that becasue I have had to help a few people thinking that these plugins won't work becasue Directsound HAL was removed. I like the new setup and properties available for each input and ouput. This is DirectX 10 so one would think the new sound routines would be fiarly good. I have more testing and playing to do. Alot of people have also been complaining and Crackling and popping under certain situations.
Well, that's one experience, anyway. I've had far more issues with Creative software and drivers than I've ever had with NVIDIA software or drivers. I've been quite truthful when I've said that I can't recall any specific issues I've had with ForceWare, nTune, NVIDIA firewall or other applications, but that isn't the issue here.I've used far worse drivers from nVidia for my Asus A8N SLI, sorry Phide but NV-RAID and the Firewall Crap-o-la is worse than ANY software Creative ever shipped IMHO!
I think it's much less about Creative's drivers than it is about drivers from other vendors and, yes, DRM. It seems like dropping the HAL was the main way to wrangle the protected paths, but it seems out of place that DRM could also function perfectly well when using other APIs, such as ASIO or OpenAL, as you've said. For that reason, I think it's a combination of drivers issues, HAL issues and DRM.I say again Magnetic, PLEASE re-open that WInXp X-Fi Driver question thread? Why?Then we could see how lame claims of Bad drivers really are.
I know of none that are anywhere nearly as functional in that area as Creative cards, but I also don't know if other chips, like C-Media's Oxygen HD 8788, lack all acceleration of DS3D functions. This kind of information is not printed on the sides of product boxes, nor is it something that could be realistically tested. Quite frankly, I have no fucking idea, and I wish I did. Coming across this kind of information is exceedingly difficult.Please link us to the cards with HW Accelerated DS3D?
That's the million-dollar question, isn't it? Any ballpark I could make would end up being based on absolutely zero evidence, as we don't know the true extent of what "hardware acceleration" entails across all chips.DRM is the real reason, not bad Audio drivers that affect how much of the Market?
The path of least resistance is generally the best path. Maybe it's lazy; maybe it was a compromise; maybe it was the only way. I'd like to think that Microsoft's competence is not always at the apex in the industry, so I'd definitely assume like the pure software path was an exercise in laziness.IMO Microsoft saw a problem (Windows crashing at an alarming rate due to HAL related issues) and took an extreme (and also probably the easiest) way of solving the problem. I don't blame them for trying to fix a problem, but they seemed to do without thinking of the consequences (or how it affected all the parties involved, even the end user).
Your experience is the opposite of my own, as it stands. It doesn't mean much. In fact, it means practically nothing. It's two individual experiences out of some random six or seven digit number. Drawing conclusions from two experiences or twenty is, statistically, quite stupid.
they took the solution that was easiest for them (instead of what was best for everyone).
Well, to be fair, Creative's won the market because EAX is fundamentally a good thing. Integration isn't complex, it's fast, and it works well. They didn't win by default because of EAX, but they did win because of EAX and because of robust hardware features.If some standard was designed with access to all, then we could test all the cards from creative,razer etc and truely see who has the best solution, not having creative win by default just because it has EAX 5.0
Creative ALchemy Project
al-che-my [al-kuh-mee] ~ any magical power or process of transmuting a common substance, usually of little value, into a substance of great value. - Dictionary.com
Welcome to the Creative ALchemy Project Beta Site
In Windows Vista, Microsoft has decided to remove the Hardware Abstraction Layer (HAL) for DirectSound and DirectSound3D. The HAL is the software layer that on previous Windows Operating Systems enabled an audio accelerator such as the SB X-Fi, to provide DirectSound3D applications with hardware accelerated audio. This enabled soundcards to perform tasks such as sample-rate conversion, mixing, 3D spatialization using HRTFs, filtering, and effects processing. Without the HAL, DirectSound on Windows Vista will be rendered in software with no advanced functionality such as EAX.
I say again Magnetic, PLEASE re-open that WInXp X-Fi Driver question thread? Why?Then we could see how lame claims of Bad drivers really are.
I think that he was refering to his "working" X-Fi thread not the alchemy thread.
if that's the case.. I will reopen it if the thread stays civilized. I gave forewarning and let that thread go too far before I closed it.
I think your always gonna have arguments in that thread becasue of the nature of the thread itself. Just because drivers work for some people on certain systems doesn't meant they unuversally work. This is just a fact of the PC. Can't really see what the point of the thread is anyway, My drivers work!, My drivers don't, My drivers work!, My drivers don't. It's not gonna solve anything or prove anything in the least you states this fact a few post ago. If you think it's gonna help or be informative great.....
if that's the case.. I will reopen it if the thread stays civilized. I gave forewarning and let that thread go too far before I closed it.
There is alot of people running this test @ Guru3D the Info didn't come from him. He is one of many testers.
Ouch, I guess that explains why Jesse hasn't posted much on ALchemy's site, no longer works for Creative. Looks like Dan is running the show for now.
Yeah, He no longer works for them. What is really funny is a few people asked him if by changing the Ini files you could get the ALchemy wrapper to work with the Audigy's and he repsonded NO. Kinda funny that's what alot of guys are doing and they are working just fine...
Using waveout yields the same results as DirectSound. I think because they both use the kmixer. The ASIO plug-in is too flaky for version .9 of Foobar; so I am stuck with Kernel Streaming. It's not a big deal, I just have to sacrifice a little audio quality for [44.1kHz] music till I figure out an alternative solution (I haven't put much time trying to get ALchemy working with other modes, so I am hoping I can work something out).
How much of the Creative THX or the other Consoles does Vista let you run?
None. I was under the impression they didn't work. I'm not sure how they would help me in this situation anyway.