I don't think you'll have a problem, but it depends on the audio chipset and the operating system (and driver set) you are using.
If you use Windows for Doom 3, then it should be fine. If you use Linux for Doom 3, it's up in the air. I don't know how capable the 3D audio portion of the Doom 3 code will be on Linux. There have been some interesting advances in OpenAL on Linux within the last few months, so we may see some neat tricks after all.
Let me rephrase myself... I mean "one that is actually used and has proper drivers that work with most hardware".
It is true that some hardware accellerated OpenAL libraries for Creartive Labs cards (using the ALSA drivers) exist, and that there may be such functionality added into the Aureal Vortex drivers for HRTF (A3D) support, but there is not a system available today (with the hardware and software support) that is comparable to EAX.
Yeah. I don't think that there is anything else that id could have done. We all know what happens when Creative sues the shit out of another company (simply to bankrupt them with lawsuits). Look at Aureal for a prime example.
This is what really annoys me about this system and companies like Creative Labs (who haven't made an innovative product since the mid-90s). They simply buy up all sorts of technology (Aureal, Sensaura, EMU, Ensoniq, etc.) and slack off with their own products. Creative hasn't done anything substantial with their soundcards since the Live series was released (even then it was sub-par in terms of quality), and has simply re-released the same DSP with some pumped-up driver hacks and better codecs. It's no wonder that companies like M-Audio and Turtle Beach have produced sonically superior products for the average consumer.
Unfortunately, other areas of audio have suffered. There is no "OpenGL" of 3D audio because Creative owns all of the patents from its acquisition of companies like Aureal and Sensaura. They will always have the one-up on 3D audio performance over their customers, and any improvements will be at their own pace. PC audio has been so stale over the last few years. It's sad to see that it's come down to this, but literally; PC audio has gone virtually nowhere because of patent issues like this. This issue with their (stealing) patenting of Carmack's Reverse really shows why we are probably set-back several years in terms of a truly awesome 3D audio experience.
MOV is a container. It "contains" the metadata for the codecs (in addition to other information) and also contains the audio and video streams. It's possible to have a MOV file with only audio. Ogg is also a container. The audio in the Ogg file is called Vorbis. OGG containers can include video as well, which will most commonly be Theora based (off of the VP3 format) in addition to the Vorbis audio. OGM files are also containers, that typically have Divx video and Vorbis for audio (instead of the norm of MP3 for the audio portion).
WAV should not be classified as the same sort of thing. It is not a container. it is not compressed. It's essentially a (slightly modified) raw PCM bitstream.
Sure. But try running much of that code for DOS, Win 3.11, or even Windows 95/98 on your XP box.
A large number of programs will not run properly, even in "compatibility mode". I can specifically recall having problems with 4 or 5 programs, mostly older games, that have problems on newer NT machines.
I agree. It can't be matched for speed and price. It's an amazing card, and I'm glad I picked one up a few months ago. It really seems to be the "Radeon 9500 PRO" of the new generation of "value cards".
And, of course it should run Doom 3 just fine. You can't beat it for $170.
It is strange that people working for free, I am talking open source here, do not produce something that is useful for home users. All the OSS firewalls I have looked out require you to have a good to expert knowledge (depending on firewall) of networking in order to effectivly use them. They all seem to be just creating replacements for professional products rather than somehting that is useable by the average Joe.
You mean, like Firestarter?
http://firestarter.sourceforge.net/
It doesn't require any knowledge to configure the firewall.
My understanding is that the normal Linux DLLs (like those from the MPlayer site) are slightly hacked, and will not work with Windows. I'm not certain though. I know that stuff like the Quicktime codecs use Winelib to do part of the dirty work, since they are so Windows dependent in their design.
I've never tried to use "official" codecs, from Microsoft's site, before. It might be worth experimenting with them.
a. LindowsOS version 4.0 and LindowsOS version 4.5 (now renamed Linspire 4.5) include the following copyrighted files owned by Microsoft: wma9dmod.dll, wmadmod.dll, wmspdmod.dll, wmv9dmod.dll, wmvdmod.dll (collectively, the "Windows Media Files"). Within ninety (90) days of the Effective Date of this Settlement Agreement, Lindows shall cease any further use or distribution of the Windows Media Files in any product or by any method of distribution. Lindows, its successors in interest, and present and future subsidiaries agree to make no further use of the Windows Media Files in any product at any time.
b. Within ninety (90) days of the Effective Date of this Settlement Agreement, Lindows shall offer to its Distributors a modified version of its renamed Linspire operating system product that does not include the Windows Media Files.
c. Within ninety (90) days of the Effective Date of this Settlement Agreement, Lindows shall inform its Distributors to discontinue all further use of any versions of Lindows products that contain the Windows Media Files and that any authorization or license from Lindows to distribute versions of Lindows products that contain the Windows Media Files is withdrawn and replaced with Lindows' authorization or license to use the modified version that does not contain the Windows Media Files.
d. To the extent Lindows does not have the contractual authority to require Distributors to discontinue the use of versions of Lindows which contain the Windows Media Files, Lindows shall within ninety (90) days inform its Distributors that it has entered into a settlement agreement with Microsoft providing that it will cease distribution of the Windows Media Files, that Microsoft alleges that unauthorized distribution of the Windows Media Files infringes its copyrights, and that Lindows will not provide Distributors with indemnity against claims brought by Microsoft arising out of unauthorized use of the Windows Media Files.
e. Within ninety (90) days of the Effective Date of this Settlement Agreement Lindows shall review the following products distributed by Lindows to assure that the Windows Media Files are not included with such products: Lindows DVD Player, MPlayer, and Xine Lindows. Lindows, and successors in interest, agree not to post on its website any links or directions to other locations from which users may download unauthorized copies of the Windows Media Files from other sources.
6. Payment by Microsoft
Within thirty (30) days of the Effective Date of this Settlement Agreement Microsoft agrees to pay to Lindows the sum of Fifteen Million Dollars U.S. ($15,000,000) by wire transfer pursuant to instructions to be provided by Lindows. Within seven (7) days of the execution and confirmation by Lindows of the Domain Name Assignment described in Section 1(f) herein, Microsoft shall make an additional payment to Lindows in the amount of Five Million Dollars U.S. ($5,000,000) by wire transfer pursuant to instructions to be provided by Lindows.
7. Windows Media Format Components License
Microsoft shall enter into a Windows Media Format Components License with Lindows, consisting of a Windows Media Format Components Source Development Agreement and Windows Media Format Components Distribution License, as set forth in the forms attached hereto as Exhibits D and E, respectively.
It mentions that Linspire has ninety days to remove some specific Windows DLLs (looks like they are for video playback), but may enter an agreement to license these instead.
Hmmm. Or, it could be that many of us just like reliable, opensource software - alternatives to often buggy, proprietary, and costly commercial software.
Agreed. And anyone that says that audio on Linux is a joke needs to have their head checked. Not only is the latency lower than Windows, but the ALSA/Jack subsystem is becoming more functional than DirectX in many respects.
If people would stop buying crappy integrated chips, they'd realize that Linux audio is certainly not a joke. It may not be perfect yet, but in a few years it will be THE system for audio. The framework is already there. We simply need more support from hardware manufacturers.
I seriously doubt this. I've never seen any evidence that Patrick is a "GPL zealot" in such an extreme that he would refuse to include OO.o.
In fact, he was including XF86 4.4 for a while, in current, until people the majority of users opted for X.org instead, so he changed it. He also has frequently included Netscape, which is not GPL compatible, and does not have the same license as Mozilla. Even Java is included, and it definitely is not GPL compatible.
I suspect that Pat doesn't include OO.o for other reasons - like the fact that there are already some fantastic word processors that come with Gnome and KDE. It wasn't until recently that Slackware started using two CDs. Pat's always been about making Slackware as thin as possible, but flexible and powerful as well.
When you learn on RedHat, you learn to use "RedHat".
When you learn on Slackware, you learn to use "Linux" (and even UNIX).
Most RedHat users (you are a minority in this case) have extreme difficulty moving to a distribution that doesn't have their unique tools. Same goes for Suse/Mandrake users. Slackware users, on the other hand, can almost always work on another distribution without too many difficulties.
I keep my sources for most of my programs. If I want to remove the program, I simply go to the source directory, switch to root, and type:
"make uninstall"
Viola.
The majority of programs that use a Makefile for installation will have no problems uninstalling a program with "make uninstall". I've been doing this since I started using Slackware 7, and have never had a problem.
A more conventional way is to simply make a Slackware package with "makepkg". It only takes a few seconds more. "Checkinstall" is another option, but it doesn't come with Slackware by default.
This is one of my favorite parts about Slackware. Everyone complains about "dependency problems" on most distributions, but I've been using Slackware for years and have yet to experience but an occasional missing library. 9 times out of 10, that library is some obscure game library for some opensource game... A library that no other programs will ever use. "Battle of Wesnoth" comes to mind, since it requires about a million obscure libraries. Most of the time, Slackware has no problems compiling most programs since it has the most important libraries.
ATI's drivers DO support the 9800 series on Linux. Sure, the drivers are far from perfect, but they work (I didn't have any problems with most games). I used them for some time before selling my Radeon and buying a GeForce card.
WD-40 is made mostly of solvents (at least 50%, from what I've read) that are designed to loosen parts, not protect and lubricate. It only has a small amount of mineral oil for lubrication. Is certainly "works on everything", but isn't ideal for lubricating bicycle chains.
Well, it's possible that they did it so it wouldn't equate to "SFW", often an acronym "So Fucking What". Of course, it could mean also "Safe For Work", for those of us that browse FARK articles on company time. That wouldn't work though, because we know that Windows is not "SFW".
Some parts of the Dreamcast PowerVR graphics system and the Hitachi SH4 utilize an 128 bit wide bus. But yes, it's not a true 128 bit CPU core. That never stopped it from spanking the hell out of the PS2 though (from a technical standpoint, considering it was "dated hardware").
Slashdot Mirror
I don't think you'll have a problem, but it depends on the audio chipset and the operating system (and driver set) you are using.
If you use Windows for Doom 3, then it should be fine. If you use Linux for Doom 3, it's up in the air. I don't know how capable the 3D audio portion of the Doom 3 code will be on Linux. There have been some interesting advances in OpenAL on Linux within the last few months, so we may see some neat tricks after all.
Let me rephrase myself... I mean "one that is actually used and has proper drivers that work with most hardware".
It is true that some hardware accellerated OpenAL libraries for Creartive Labs cards (using the ALSA drivers) exist, and that there may be such functionality added into the Aureal Vortex drivers for HRTF (A3D) support, but there is not a system available today (with the hardware and software support) that is comparable to EAX.
Yeah. I don't think that there is anything else that id could have done. We all know what happens when Creative sues the shit out of another company (simply to bankrupt them with lawsuits). Look at Aureal for a prime example.
This is what really annoys me about this system and companies like Creative Labs (who haven't made an innovative product since the mid-90s). They simply buy up all sorts of technology (Aureal, Sensaura, EMU, Ensoniq, etc.) and slack off with their own products. Creative hasn't done anything substantial with their soundcards since the Live series was released (even then it was sub-par in terms of quality), and has simply re-released the same DSP with some pumped-up driver hacks and better codecs. It's no wonder that companies like M-Audio and Turtle Beach have produced sonically superior products for the average consumer.
Unfortunately, other areas of audio have suffered. There is no "OpenGL" of 3D audio because Creative owns all of the patents from its acquisition of companies like Aureal and Sensaura. They will always have the one-up on 3D audio performance over their customers, and any improvements will be at their own pace. PC audio has been so stale over the last few years. It's sad to see that it's come down to this, but literally; PC audio has gone virtually nowhere because of patent issues like this. This issue with their (stealing) patenting of Carmack's Reverse really shows why we are probably set-back several years in terms of a truly awesome 3D audio experience.
MOV is a container. It "contains" the metadata for the codecs (in addition to other information) and also contains the audio and video streams. It's possible to have a MOV file with only audio. Ogg is also a container. The audio in the Ogg file is called Vorbis. OGG containers can include video as well, which will most commonly be Theora based (off of the VP3 format) in addition to the Vorbis audio. OGM files are also containers, that typically have Divx video and Vorbis for audio (instead of the norm of MP3 for the audio portion).
WAV should not be classified as the same sort of thing. It is not a container. it is not compressed. It's essentially a (slightly modified) raw PCM bitstream.
Sure. But try running much of that code for DOS, Win 3.11, or even Windows 95/98 on your XP box.
A large number of programs will not run properly, even in "compatibility mode". I can specifically recall having problems with 4 or 5 programs, mostly older games, that have problems on newer NT machines.
I agree. It can't be matched for speed and price. It's an amazing card, and I'm glad I picked one up a few months ago. It really seems to be the "Radeon 9500 PRO" of the new generation of "value cards".
And, of course it should run Doom 3 just fine. You can't beat it for $170.
I don't have the "false hit problems" because I checked the box in the options that said "ignore hits meant for other machines".
Have you tried that?
You mean, like Firestarter?
http://firestarter.sourceforge.net/
It doesn't require any knowledge to configure the firewall.
"Duel"? You mean that the processors fight? Wow!
The nVidia drivers aren't compiled on your machine. The installer compiles a wrapper to glue the binary-only driver to your kernel.
A lot of people seem to think that it compiles *the driver*, but this is not the case.
And you don't "get the code" either. You get the wrapper code. That's it.
Yeah... And a Mobile Celeron at that.
My understanding is that the normal Linux DLLs (like those from the MPlayer site) are slightly hacked, and will not work with Windows. I'm not certain though. I know that stuff like the Quicktime codecs use Winelib to do part of the dirty work, since they are so Windows dependent in their design.
I've never tried to use "official" codecs, from Microsoft's site, before. It might be worth experimenting with them.
It mentions that Linspire has ninety days to remove some specific Windows DLLs (looks like they are for video playback), but may enter an agreement to license these instead.
Hmmm. Or, it could be that many of us just like reliable, opensource software - alternatives to often buggy, proprietary, and costly commercial software.
It's just a thought.
Agreed. And anyone that says that audio on Linux is a joke needs to have their head checked. Not only is the latency lower than Windows, but the ALSA/Jack subsystem is becoming more functional than DirectX in many respects.
If people would stop buying crappy integrated chips, they'd realize that Linux audio is certainly not a joke. It may not be perfect yet, but in a few years it will be THE system for audio. The framework is already there. We simply need more support from hardware manufacturers.
Sound works out of the box on Slackware 10 (through ALSA). You will simply need to turn the volume levels up with the mixer.
I seriously doubt this. I've never seen any evidence that Patrick is a "GPL zealot" in such an extreme that he would refuse to include OO.o.
In fact, he was including XF86 4.4 for a while, in current, until people the majority of users opted for X.org instead, so he changed it. He also has frequently included Netscape, which is not GPL compatible, and does not have the same license as Mozilla. Even Java is included, and it definitely is not GPL compatible.
I suspect that Pat doesn't include OO.o for other reasons - like the fact that there are already some fantastic word processors that come with Gnome and KDE. It wasn't until recently that Slackware started using two CDs. Pat's always been about making Slackware as thin as possible, but flexible and powerful as well.
When you learn on RedHat, you learn to use "RedHat".
When you learn on Slackware, you learn to use "Linux" (and even UNIX).
Most RedHat users (you are a minority in this case) have extreme difficulty moving to a distribution that doesn't have their unique tools. Same goes for Suse/Mandrake users. Slackware users, on the other hand, can almost always work on another distribution without too many difficulties.
I hope that answers your question.
I keep my sources for most of my programs. If I want to remove the program, I simply go to the source directory, switch to root, and type:
"make uninstall"
Viola.
The majority of programs that use a Makefile for installation will have no problems uninstalling a program with "make uninstall". I've been doing this since I started using Slackware 7, and have never had a problem.
A more conventional way is to simply make a Slackware package with "makepkg". It only takes a few seconds more. "Checkinstall" is another option, but it doesn't come with Slackware by default.
This is one of my favorite parts about Slackware. Everyone complains about "dependency problems" on most distributions, but I've been using Slackware for years and have yet to experience but an occasional missing library. 9 times out of 10, that library is some obscure game library for some opensource game... A library that no other programs will ever use. "Battle of Wesnoth" comes to mind, since it requires about a million obscure libraries. Most of the time, Slackware has no problems compiling most programs since it has the most important libraries.
ATI's drivers DO support the 9800 series on Linux. Sure, the drivers are far from perfect, but they work (I didn't have any problems with most games). I used them for some time before selling my Radeon and buying a GeForce card.
WD-40 is made mostly of solvents (at least 50%, from what I've read) that are designed to loosen parts, not protect and lubricate. It only has a small amount of mineral oil for lubrication. Is certainly "works on everything", but isn't ideal for lubricating bicycle chains.
Well, it's possible that they did it so it wouldn't equate to "SFW", often an acronym "So Fucking What". Of course, it could mean also "Safe For Work", for those of us that browse FARK articles on company time. That wouldn't work though, because we know that Windows is not "SFW".
Some parts of the Dreamcast PowerVR graphics system and the Hitachi SH4 utilize an 128 bit wide bus. But yes, it's not a true 128 bit CPU core. That never stopped it from spanking the hell out of the PS2 though (from a technical standpoint, considering it was "dated hardware").