features you disabled in Windows 7 and why?


Recommended Posts

Did you know that Windows Media Player runs just fine with just the executable (and no other files present) in the dir? Although the visualizer is part of another dll file - mpvis.dll - you should keep that if you want the cruddy anims when playing music. I also wouldn't remove the wmplayer.exe.mui, mui files are important as long as the file they are referring to exists.

:)

Do you even have the slightest idea how many applications depend on Internet Explorer? Winamp, for example, uses it, as well as countless other applications. Internet Explorer isn't just an application, it's also framework. It might not be such a big deal in Windows 7, but disabling it before sometimes (more times than not) resulted in severe issues with programs that contacted the internet, as well as Windows Explorer.

When I had used XP, I tried to completely remove it. The thing is Source games like CS:S use it for rendering the server page. With a total removal of Internet Explorer, it will ask you what to do with htm/html files - as there is no IE Core to render them. It will annoy you to no extent, it is better to just kill the browser but not the engine. Also Windows Explorer should work fine without IE and as far as I can tell it has nothing to do with networking abilities - internet will work fine, but all applications that use the IE render will suffer.

Did you know that Windows Media Player runs just fine with just the executable (and no other files present) in the dir? Although the visualizer is part of another dll file - mpvis.dll - you should keep that if you want the cruddy anims when playing music. I also wouldn't remove the wmplayer.exe.mui, mui files are important as long as the file they are referring to exists.

:)

No, I don't buy the statement that WMP runs just fine with only the exe present. You may think it does, but something in the functionality will stop working when you get rid of it, you just haven't found it yet. I tried it in my vBox 7 that I use as a sandbox, and I've completely lost the ability to stream music, the language pack is totally effed up (all box characters), and some icons are missing. So no, I wouldn't say "it runs just fine". Thankfully, I restored the files and it now functions perfectly again.

It's quite retarded that you call that "tweaking". What exactly are you trying to tweak? You're removing functionality, and you do realize that the entire WMP12 Program Files folder (also checked the appdata folder) is roughly 6 and a half megabytes. Congrats. You shaved off 6 megabytes from your precious, oh, what's the standard HD sizes nowadays? 250 GB at least? Yeah, awesome.

No offense, but you really do sound like you know what you're doing, but you and the rest of your "tweaking" crowd seem to be suffering from a placebo affect. You can cry "it's my software, I'll do with it what I want", but at the end of the day, Windows 7 has worked on every single computer I've tried it on, both old and new, laptop and desktop, and I have yet to encounter any problem that required "tweaking". I think the issue is that the nostalgia from all the so called "tweaking" and "optimizing" from XP has driven you guys to assume that each Windows OS needs to be totally modified otherwise it will perform poorly.

I'm waiting for the day where people realize that Windows 7 has got to be the most hassle-free OS to use out of all the Windows OSes, and that it doesn't require much disabling except UAC and search indexing, if you don't use those.

No, I don't buy the statement that WMP runs just fine with only the exe present. You may think it does, but something in the functionality will stop working when you get rid of it, you just haven't found it yet. I tried it in my vBox 7 that I use as a sandbox, and I've completely lost the ability to stream music, the language pack is totally effed up (all box characters), and some icons are missing. So no, I wouldn't say "it runs just fine". Thankfully, I restored the files and it now functions perfectly again.

It's quite retarded that you call that "tweaking". What exactly are you trying to tweak? You're removing functionality, and you do realize that the entire WMP12 Program Files folder (also checked the appdata folder) is roughly 6 and a half megabytes. Congrats. You shaved off 6 megabytes from your precious, oh, what's the standard HD sizes nowadays? 250 GB at least? Yeah, awesome.

No offense, but you really do sound like you know what you're doing, but you and the rest of your "tweaking" crowd seem to be suffering from a placebo affect. You can cry "it's my software, I'll do with it what I want", but at the end of the day, Windows 7 has worked on every single computer I've tried it on, both old and new, laptop and desktop, and I have yet to encounter any problem that required "tweaking". I think the issue is that the nostalgia from all the so called "tweaking" and "optimizing" from XP has driven you guys to assume that each Windows OS needs to be totally modified otherwise it will perform poorly.

I'm waiting for the day where people realize that Windows 7 has got to be the most hassle-free OS to use out of all the Windows OSes, and that it doesn't require much disabling except UAC and search indexing, if you don't use those.

Does it still play MP3s? Yes.

Does it still play MP4s? Yes.

Therefore, to me there is no functionality that is lost.

This is not tweaking, this is pure removal of unnecessary functionality. :)

Actually it does work. A normal Windows XP install boots in about half a min on a 2004 my emachines, while a nlited install boots in about half that time. I haven't yet tried a lited 7, but the results should be the same. The results of tweaking can actually be seen at boot by just booting the 12 or so (12 if you remove some dependencies, more like 15) services needed for basic functionality and internet VS. booting at all 50 or so.

Does it still play MP3s? Yes.

Does it still play MP4s? Yes.

Therefore, to me there is no functionality that is lost.

This is not tweaking, this is pure removal of unnecessary functionality. :)

No, unneeded function as defined by you. The rest of us who use WMP to manage our libraries and stream them to our Xboxes, we call that needed functionality. And no, it doesn't make a damn bit of difference whether or not you delete them. I've timed the startup times after removing it and it does nothing for speed. You can gladly say "it's my OS, I'll do it the way I want" but the point is that it's not assisting your machine in any way, and any improvement you may think you see from deleting said files is purely placebo.

Actually it does work. A normal Windows XP install boots in about half a min on a 2004 my emachines, while a nlited install boots in about half that time. I haven't yet tried a lited 7, but the results should be the same.

No idea where XP's boot time has anything to do with deleting the majority of a 6 MB folder's contents.

No idea where XP's boot time has anything to do with deleting the majority of a 6 MB folder's contents.

No, that was a comparison between the normal 2GB install of XP and an lite XP that can be installed on a 512MB Partition. :)

No, that was a comparison between the normal 2GB install of XP and an lite XP that can be installed on a 512MB Partition. :)

And why pray tell would you want to install XP on a 512 MB partition? Don't you realize that programs, by default, install to the C:/ (or whatever the install drive is) drive?

If you're still living with ancient hardware, that's not called tweaking and "optimizing", that's called being too cheap to get decent hardware (which is no longer expensive, if all you're trying to run is XP).

And why pray tell would you want to install XP on a 512 MB partition? Don't you realize that programs, by default, install to the C:/ (or whatever the install drive is) drive?

If you're still living with ancient hardware, that's not called tweaking and "optimizing", that's called being too cheap to get decent hardware (which is no longer expensive, if all you're trying to run is XP).

You missed the point.

You missed the point.

If you say so. meanwhile, I'll still have a fully functioning operating system that does everything Microsoft intended it to, and when I have support issues, I won't have to keep a list saying "this is what I disabled, I wonder if this will cause an issue". Oh, and my Windows 7 runs plenty fast. Defragment regularly, don't install crapware, and you won't ever have to reinstall.

Have fun.

As I said earlier the only ones qualified to tweak/optimise windows is Microsoft, as they know what every part of their operating system does.

Microsoft have done a pretty good job of optimising Windows 7 to get it running on new and old hardware. So there is no need to tweak windows on any machine.

with hard drives being so cheap these days i don't really care about space....

You should. Fast Flash based, server grade and the Raptor harddrives from Western digital are expensive and relatively small. Bigger files also means longer time to load, and more fragmentation issues.

If you say so. meanwhile, I'll still have a fully functioning operating system that does everything Microsoft intended it to, and when I have support issues, I won't have to keep a list saying "this is what I disabled, I wonder if this will cause an issue". Oh, and my Windows 7 runs plenty fast. Defragment regularly, don't install crapware, and you won't ever have to reinstall.

I guess you are not very fast, on a general basis :p I find programs to launch much slower then on XP, and its strange that my Raptor WD1500 HD sounds much less busy in Vista and 7, than XP. Seems like Microsoft decided to insert a few millions NOOP instructions per HD I/O. NVIDIA Control panel takes several seconds to open vs. almost instantly on XP. Perfectdisk analyzing a HD is also much slower XP vs. vista and 7.

The user interface is also much more sluggish then XP. Each folder takes about half a second to open in Vista and 7, vs. instantly on XP.

Here is a video that shows how much CPU usage 7 uses vs. XP. GDI+ have several operations that can be hardware accelerated with proper graphics cards in XP, but it is not in Vista and 7. Latest WDDM 1.1 adds some, but still feels just as sluggish (could be my gtx 285 and WDDM 1.1 drivers). Vista and 7 the desktop composition is running in hardware, but they didn't migrate the GDI+ over.

Check out the link for more information on GDI+ and hardware acceleration.

Mac OSX they have migrated and now everything runs on the GPU, the CPU only have to issue relatively small drawing calls. On Vista and 7 however, we have GDI+, Windows DEsktop Compostition, WPF and now lately Direct2D.

If you look at the three Quartz implementation diagrams in sequence, you can see how the video card portion of the diagram has slowly expanded over the course of four years to encompass more and more of the display layer. The reason is clear when you look at the bandwidth numbers: 30GB/s between the GPU and VRAM, and that number is climbing rapidly—much more rapidly than the bandwidth between the CPU and RAM.

http://arstechnica.com/apple/reviews/2005/...osx-10-4.ars/14

In programmer circles, Microsoft is the very model of modern bloated software. As a quick example, just check out your Windows Live Contacts database. Each contact gets a default 32MB database file.

I'm all for new features, but I think Windows Vista and 7 could run on much slower hardware if Microsoft wasn't such a bloat machine. It's not very environmentally friendly to produce computers (just check all the chemicals they use to make CPU's) and power efficiency is important in these days of possible human made climate change (the experts does't agree yet). You don't need a super CPU just for the web and there is no excuse not to hardware accelerate video playback.

As I said earlier the only ones qualified to tweak/optimise windows is Microsoft, as they know what every part of their operating system does.

Microsoft have done a pretty good job of optimising Windows 7 to get it running on new and old hardware. So there is no need to tweak windows on any machine.

Well, let's define "tweaking", shall we? If you mean disabling services or uninstalling system files / folders because you want to reduce the footprint of the OS, then I agree completely. But tweaking can also mean modifying the interface so it better suits your comfort level, enabling or disabling items in the startup menu (ie, run, search, recent docs, etc), removing icon arrow overlays, disabling some visual effects, moving the pagefile to where you want it, and so on. I see absolutely nothing wrong with doing any of these things.That's all part of "making the OS your own".

Here is a video that shows how much CPU usage 7 uses vs. XP. GDI+ have several operations that can be hardware accelerated with proper graphics cards in XP, but it is not in Vista and 7. Latest WDDM 1.1 adds some, but still feels just as sluggish (could be my gtx 285 and WDDM 1.1 drivers). Vista and 7 the desktop composition is running in hardware, but they didn't migrate the GDI+ over.

GDI+ is never hardware accelerated on any version of Windows. GDI+ is a software library with various utility functions and classes that make dealing with graphics easier. It does everything in software, and calls GDI when it's time to actually show something on screen (so that part can be accelerated, but nothing else.) Pedantry maybe, but worth knowing. The performance penalty for using GDI+ instead of GDI can be extreme, especially on slower systems.

Check out the link for more information on GDI+ and hardware acceleration.

Firstly I'm going to say that 7 does perform worse than XP. That isn't in dispute. However, the example you're using to "prove" this is extremely flawed. You cannot use Explorer to make some point about a graphics API, and you can't use it to compare different versions of Windows.

Explorer in XP and 7 is not the same program. It has changed massively, even on the graphics side. In XP it uses standard windowing and common controls, whereas in 7 it is based on Microsoft's internal windowless GUI framework. This might introduce additional overhead compared with XP, overhead that is entirely in the software framework itself and not with any Windows API.

In addition, scrolling up and down in Explorer is not necessarily just a benchmark of the graphics side. All the data that is being drawn has to come from somewhere. Changes might have been made in the way Explorer handles the extensions that create thumbnails of your files, for instance. Maybe they now run out-of-process for reliability reasons, something that adds more overhead. Maybe the code that creates the thumbnails has changed as well. Maybe it takes more processing power to read and draw icons and images that have higher quality. Maybe changes have been made to the artificial delays in various parts of the user interface (Windows has lots of these), and so on. The list goes on.

If you just want to make a point about graphics performance, then you have to run synthetic benchmarks that just do graphics, under controlled conditions. There wouldn't be much point though, because everyone recognizes that it is so. It is a necessary step towards the future. Maybe GDI is slightly slower, but at the same time the experience you get while running several Direct3D programs at the same time is much more pleasant than it was with XP and D3D <= 9.

What it feels like in real world use is more important than synthetic benchmarks, and Explorer honestly doesn't feel slow to me, and in some ways it even performs better. I have a folder with close to 7000 images, for instance, and 7 seems to handle this much better. Same with the image viewer.

Mac OSX they have migrated and now everything runs on the GPU, the CPU only have to issue relatively small drawing calls. On Vista and 7 however, we have GDI+, Windows DEsktop Compostition, WPF and now lately Direct2D.

Well, they had an easier job with OS X. Its APIs are fairly new, and they have little concern about breaking applications. Windows APIs like GDI and windowing (user), on the other hand, were designed in the 1980s and are very fragile, with thousands of applications relying on internal implementation details. The only real option I see is to create new frameworks that live side-by-side with the old. Microsoft has done that with Direct2D, but sadly there is no UI framework to go with it. The reason, in my opinion, is because Microsoft got so lost in their .NET vision.

there is no excuse not to hardware accelerate video playback.

What are you referring to here? Windows does have hardware acceleration of video. In fact, depending on the hardware you have, virtually the entire process can be handled by your graphics card's video decoder.

As I said earlier the only ones qualified to tweak/optimise windows is Microsoft, as they know what every part of their operating system does.

Microsoft have done a pretty good job of optimising Windows 7 to get it running on new and old hardware. So there is no need to tweak windows on any machine.

another person who is up microsoft's arse. Microsoft will set the defaults that are most suited to the mainstream user, typically someone who isnt particurly savvy. However it is never ever possible to have a configuration that is optimal for 100% of userbase.

I have enabled superfetch on my machine again now and will concede that superfetch is significantly better than it was under vista, it still runs when the machine isnt idle but not very frequently so is fine. However I would leave it off if I didnt have much ram. Windows search is still turned off tho.

The worst thing a software developer can do is not allow their software to be configurable, eg. microsoft have alienated some people by dumbing down windows 7 gui, its less configurable than previous versions of windows. A developer may have a vision of how a product such work but its a garuantuee not everyone will agree with him, and if he tries to force the issue by not allowing tweaks etc. then he will restrict takeup of software.

I like windows 7 but I feel sick when I read things such as "its perfect" "it does nothing wrong" "no need to change anything" "if it doesnt work then it must be a end user problem".

NVIDIA Control panel takes several seconds to open vs. almost instantly on XP.

I have the same problem, it is a mystery, here is what I have discovered.

1 - The 182.50 wddm 1.0 nvidia driver the panel loads signifcantly faster than newer driver versions, but still way slower than XP, in XP I was using a way older driver, so could be driver related.

2 - The nvidia panel opens alot faster on my amd box than on my intel, the weird thing about this is that on paper my amd spec is weaker.

3 - on XP I know the configuration of IE affected how fast the nvidia panel opened, eg. when I used spybot to fill up the restricted site zone with rogue sites it made nvidia panel open very slowly. So it is possible some part of IE has affected how fast the panel opens in windows 7.

I too don't like the way the GUI functions. What is the logic in not offloading scrolling to the GPU? (Windows Explorer)

For those who completely want to get rid of Internet Explorer in C:\Program Files\Internet Explorer ,

---> Do not remove ieproxy.dll

---> It is responsible for opening folders in the same window.

---> The rest doesn't seem used, so the rest can go

:)

I too don't like the way the GUI functions. What is the logic in not offloading scrolling to the GPU? (Windows Explorer)

For those who completely want to get rid of Internet Explorer in C:\Program Files\Internet Explorer ,

---> Do not remove ieproxy.dll

---> It is responsible for opening folders in the same window.

---> The rest doesn't seem used, so the rest can go

:)

WHY in the world would you even do something like this?

I guess you are not very fast, on a general basis :p I find programs to launch much slower then on XP, and its strange that my Raptor WD1500 HD sounds much less busy in Vista and 7, than XP. Seems like Microsoft decided to insert a few millions NOOP instructions per HD I/O. NVIDIA Control panel takes several seconds to open vs. almost instantly on XP. Perfectdisk analyzing a HD is also much slower XP vs. vista and 7.

The user interface is also much more sluggish then XP. Each folder takes about half a second to open in Vista and 7, vs. instantly on XP.

Here is a video that shows how much CPU usage 7 uses vs. XP. GDI+ have several operations that can be hardware accelerated with proper graphics cards in XP, but it is not in Vista and 7. Latest WDDM 1.1 adds some, but still feels just as sluggish (could be my gtx 285 and WDDM 1.1 drivers). Vista and 7 the desktop composition is running in hardware, but they didn't migrate the GDI+ over.

Check out the link for more information on GDI+ and hardware acceleration.

Mac OSX they have migrated and now everything runs on the GPU, the CPU only have to issue relatively small drawing calls. On Vista and 7 however, we have GDI+, Windows DEsktop Compostition, WPF and now lately Direct2D.

If you look at the three Quartz implementation diagrams in sequence, you can see how the video card portion of the diagram has slowly expanded over the course of four years to encompass more and more of the display layer. The reason is clear when you look at the bandwidth numbers: 30GB/s between the GPU and VRAM, and that number is climbing rapidly?much more rapidly than the bandwidth between the CPU and RAM.

http://arstechnica.com/apple/reviews/2005/...osx-10-4.ars/14

In programmer circles, Microsoft is the very model of modern bloated software. As a quick example, just check out your Windows Live Contacts database. Each contact gets a default 32MB database file.

I'm all for new features, but I think Windows Vista and 7 could run on much slower hardware if Microsoft wasn't such a bloat machine. It's not very environmentally friendly to produce computers (just check all the chemicals they use to make CPU's) and power efficiency is important in these days of possible human made climate change (the experts does't agree yet). You don't need a super CPU just for the web and there is no excuse not to hardware accelerate video playback.

You really don't know the original meaning of software bloat, do you?

Well offloading as much as possible from the CPU seems logical. Especially when it comes to drawing 2D stuff.

It may seem logical, but it is extremely difficult to completely rewrite the implementation of an API designed in the 1980s (and designed around old hardware) to work on a completely different architecture. Even if you managed to do it and emulate the publicly defined API perfectly, you would most likely still end up with thousands of programs that would cease to function because they dependend on some internal implementation detail or quirk that you have now changed.

Chances are it is never going to be done, and that we will instead see a new UI framework that exists side-by-side with the legacy APIs (GDI/User) that new applications will be written to use.

It may seem logical, but it is extremely difficult to completely rewrite the implementation of an API designed in the 1980s (and designed around old hardware) to work on a completely different architecture. Even if you managed to do it and emulate the publicly defined API perfectly, you would most likely still end up with thousands of programs that would cease to function because they dependend on some internal implementation detail or quirk that you have now changed.

Chances are it is never going to be done, and that we will instead see a new UI framework that exists side-by-side with the legacy APIs (GDI/User) that new applications will be written to use.

:(

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Creative Sound Blaster AE-X PCIe review: your headphones will love it by Steven Parker If you have been reading Neowin for any length of time, you may remember that I reviewed the Sound Blaster Audigy FX Pro back in April. I found it to be an excellent budget sound card, even though it lacked support for formats such as DTS over the included SPDIF port. Anyway, Creative reached out to me again asking if I was interested in reviewing the Sound Blaster AE-X. It is a card mainly targeted at headphone wearers, which I'll get into a bit later. Before we get underway, here is a disclaimer: Creative Labs provided a free sample without any review pre-approval. Here are the full specs of it: Creative Sound Blaster AE-X Dimensions: 179 x 126 x 18 mm Weight: 263g / 9.28 oz Platform: PCI-e DAC: ESS ES9039Q2M Connectivity Options Side: Rear: 1 x HD Audio Front Panel Connector, 1 x ⅛“ Headphone port, 1 x RCA Line-out (Left) port, 1 x RCA Line-out (Right) port, 1 x Coaxial SPDIF-out port, 1 x ⅛“ Mic in/Line-in port, 1 x TOSLINK SPDIF-in port Surround: No DNR / SNR: THD+N: 0.0001% Dynamic Range 130 dB Recording Resolution: PCM up to 32-bit / 192kHz (Stereo) Direct Mode: Line Out (Stereo): PCM up to 32-bit  384 kHz Coaxial SPDIF Out: PCM up to 24-bit 192.0 kHz Headphone Amp: PCM up to 32-bit / 384kHz (Stereo) Native DSD: DSD64, DSD128, DSD256 Output Impedance: 1Ω, Supported Headphone Impedance: 8–600Ω, IEM: 0.5Vrms, Low: 1.5Vrms, Mid: 3Vrms, High: 6Vrms, Maximum output power: 350mW @ 32Ω (High), Maximum output voltage: 6Vrms (High) Front Panel Headphone Amp: PCM up to 32-bit / 192kHz (Stereo) Native DSD: DSD64, DSD128 Output Impedance: 10Ω, Supported Headphone Impedance: 32–300Ω, Maximum output power: 40mW @ 32Ω, Maximum output voltage: 1.9Vrms ASIO: ASIO 2.3 Total Harmonic Distortion: THD+N: 0.0006% Dynamic Range: 114 dB Scout Mode: Yes EMI shielding: No (but it passed all the FCC emission tests) Operating temperature: 0–45°C Input Power: 12V⎓0.5A Warranty: 1 Year (MSRP) Price: $179.99 / £169.99 The Sound Blaster AE-X was announced at the end of May, and it becomes clear that it is mainly for headphone wearers. I should also note that the card does not support DDL/DTS encoding technology, but it is said to support decoding through the coaxial SPDIF port. I was able to test this working with the classic Windows Sound properties, but I could not get a DTS (decode) signal through my Logitech Z906, it defaulted to 3D sound whenever I played DTS content through Plex or Emby. In addition, this card only supports two channels (stereo) over the speakers. The surround support is limited to the Headphone Amp, so before I get underway, what we have here is a card mostly intended for headphone use, especially with its SPDIF In (Toslink) port where you could connect another device like a console. So what about the highlights of this card? The AE-X is powered by the ESS SABRE DAC (ES9039Q2M), which is capable of a 130 dB dynamic range. In addition, it supports 32-bit/384 kHz playback for deeper detail and clarity. The headphone amplifier delivers up to 350 mW @ 32Ω, which admittedly far surpasses standard onboard audio, offering support for studio-grade headphones. DSD256 and ASIO 2.3 are also supported. What doesn't it have? No support for What-U-Hear, Super X-Fi, or the SmartComms Kit No EMI shielding, but it passed all the FCC emission tests (from the FAQ) I also want to make it clear that I am no audiophile. For me, it's purely subjective and it should just "work" out of the box. First impressions As I said in the introduction, I was a bit sad to see that the AE-X only supports stereo output, meaning it would not be on par with my ALC1220 over my speakers, as I mentioned it seems like this card is marketed toward headphone users. Since I am not an avid gamer that would rule me out as a potential customer, but I can still test its capabilities! The card arrived in a nice-looking box, as shown above. It's quite a bit larger than the Audify FX Pro that I reviewed back in April, and at first I thought the covering meant that it was EMI shielded, but it isn't as mentioned above in the highlights section. What's in the box: 1 x Sound Blaster AE-X PCIe card 1 x 3.5 mm CTIA TRRS to Dual TRS Headset Splitter Cable 1 x Quick Start Guide Aside from the Quick Start Guide, which someone at my age (I guess) needs a magnifying glass to read thanks to the tiny fonts, Creative Labs also has the manual online, which first requires you to prove that you're human in order to access it (so I can't direct link it). Anyway, the box is mostly made up of cardboard, and the only plastic in it is the anti-static bag for the card itself. Design Top Bottom The card itself looks pretty cool and actually wouldn't look out of place in an all-white build. There's only one connector, and for some reason it is awkwardly placed on the side (front-facing) that is for the front panel audio connector, which will let you use the headphones through the front PC audio jack. Since the front panel Headphone Amp has fewer capabilities than the rear headphone port, I decided not to use it. Rear of card PCI-e interface The rear of the card is completely open and is normally where you would find the front panel connector. The PCIe interface side is completely covered, which initially made me think it was EMI shielded. I/O panel Side (front-facing) with Front panel connector On the outer rear bracket side we have the TOSLINK SPDIF in, Coaxial SPDIF out, RCA line out (Right), RCA line out (Left), Headphone out, and Mic/Line in ports. On the front facing portion of the card itself is the F-panel connector. Usage Test System Our test system consists of the following: AMD Ryzen 9 9950X3D Gigabyte X870E AORUS MASTER (BIOS F12) Corsair RM1000x (2024) Thermal Grizzly Kyronaut (33x33x0,2mm) 2x 32GB Kingston Fury Beast RGB DDR5 6000MT/s CL36-38-38-80 T-Force Z540 2TB (PCIe Gen5) NVIDIA GeForce RTX 5090 Founders Edition (NVIDIA) Creative Sound Blaster AE-X Windows 11 25H2 Pro I installed the card into the Gigabyte X870E AORUS MASTER which includes the RealTek ALC1220 onboard audio. For our subjective listening tests, I used the Coaxial SPDIF port to my Logitech Z906 speakers. For headphone tests I used the OneOdio Studio Max 2 Wireless DJ Headphones that I reviewed last month. After installing the audio driver, I installed Creative Nexus, which is a relatively new app designed for the latest Sound Blaster cards. Then I discovered the AE-X needed both a driver update from 1.00.15.0001 to 1.01.09.000 and a firmware update from 1.00.06.0000 to 1.00.06.0002, then I was set to go. It should be noted that the card did not work without the driver (not Plug and Play). As you can see above, you can manage the firmware, driver, and inputs via Advanced Settings on the Device tab. By default Nexus enabled "Direct Mode". Upon clicking on Acoustic Engine, the Equalizer can be enabled and set to four different presets, which are: Gaming Music Movies Footsteps Enhancer There's also a dedicated Scout Mode for gamers. I mainly used Tidal and Spotify in the past week to listen to some of my Liked Songs (which now total over 700) in Shuffle mode; there were no pops or interference that I could hear. I also found a 5.1 Surround Music playlist on Tidal that sounded really great over Studio Max 2 headphones. When I reviewed the Audigy FX Pro, I went out and purchased a Logitech Z906 set second-hand for €100 specifically to use with the card, but in this instance all I could get on the AE-X was the 3D output of surround sound through Coaxial SPDIF and although it still sounded great, it isn't quite as good as DTS Interactive via my onboard Realtek ALC1220. Conclusion So what have I learned? The AE-X lacks multi-channel support for 5.1/7.1 setups and drops support for modern surround technologies like Dolby or DTS, functioning strictly as a stereo output device. So to really benefit, you will need Studio-grade headphones to "hear" the benefits of this card. With that being said, I can imagine it will appeal to gamers who are switching between console and PC. By utilizing the SPDIF in port, you could just plug your headphones into the AE-X (front or rear port) and then switch between PC and Console without having to move the headphones to a different port. As I said in the Sound Blaster Audigy review, the EQ in the Creative Nexus app offers safe presets, which allows a user to further tweak the lows, mids, and highs for a personal listening experience. Of course it all depends on the headphones you hook up to it. Speaking of headphones, I kind of wish I had higher-quality Studio-grade headphones to really test this card with; I'm not usually wearing headphones in my day to day duties. The only time I will wear them is if I want to listen to music very late at night and I don't want to disturb my neighbors, so my rating (verdict) is based on this fact. Someone with a PC/Console setup and wears headphone religiously to game, and consume media will benefit much more than I from the high-quality Headphone Amps that are included in the AE-X. Once again, I do feel like Creative could have gone the extra mile to support the S/PDIF port a bit more. Why include it if you're not supporting the main popular digital formats? It seems like the decision was more of a legacy-based one, offering uncompressed 2-channel PCM audio, for users with high-fidelity audio systems and external DACs. Maybe I will be lucky enough to review a card that truly includes all these features in the future. I am sure readers with far more knowledge on audio systems than me will correct me in the comments below. I'll just say I am happy to learn what I don't know! Where to buy The Sound Blaster AE-X is available to purchase now in preorder for $179.99 on the U.S. Creative website, or for £169.99 on the Creative UK website and will start shipping to customers from June 25.
    • $80 or 90%, anything else would be financial suicide one way or another.
    • Or... just use Bitwarden. Free, and has on-prem option as well. Works both on desktop and mobile, wherever you are. The age of local password files is over.
    • Thanks
    • I actually got to use one of those so called "backup codes" once. It was for a customer, I choose the backup code option, and by the grace of god, they actually hade them printed out. Imagine my surprise, when after using the backup code, Google then told use we had to enter a code they just sent to the gmail address we currently did not have access to. I was not amused, Google backup codes should be the end all get out of jail free card, because you had to have access to the account to even get them.
  • Recent Achievements

    • Week One Done
      Supreme Spray LV earned a badge
      Week One Done
    • One Month Later
      Genuinetonerink- Dubai earned a badge
      One Month Later
    • Week One Done
      Genuinetonerink- Dubai earned a badge
      Week One Done
    • One Year In
      hhgygy earned a badge
      One Year In
    • Week One Done
      AMV earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      +Edouard
      164
    3. 3
      PsYcHoKiLLa
      88
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      73
  • Tell a friend

    Love Neowin? Tell a friend!