So today I dared installing Ubuntu + Steam for Linux...(Warning: tears)


Recommended Posts

Cool! The new Steam for Linux is out and what do I see? THEY GIVE A FREE TF2 HAT!?!?! I MUST HAS IT!!

So I downloaded Wubi and started installing...

Nice. It completed. Let's have it reboot and expect it to finish the install...

WRONG!

It doesn't boot because it says that Windows is hibernated. Windows 8 hibernates the kernel to speed up startups yet Wubi didn't tell me anything about that. Let's turn the hybrid boot off and expect it to work...

WRONG!

It still doesn't boot with the same reason. Let's go back to windows and turn hibernation off with powercfg -h off.

WRONG!

Again, it doesn't work. Same reason. Let's reboot windows and delete the whole hibernation file and reboot again.

RIGHT!

So the install starts. It starts copying stuff around for a while. Let's wait until it continues... it will certainly end.

WRONG!

It hangs at about 75%. After a while the log starts showing warnings that the copy process has freezed. After about 20 minutes I issue a "sudo reboot" command from console, of course it doesn't work and I have to do an hardware reboot. I try a couple more times then give up and download the whole Ubuntu ISO. Then, let's install the latest 64bit from the ISO like the wiki page suggests for Win 8/UEFI users (no, my machine doesn't have UEFI but since Wubi doesn't work the only alternative is the whole Ubuntu disc hoping it doesn't screw up my bootloader)...

FINALLY!

It finally installed, so let's open Steam website and download the Steam client. Let's run that nice .deb package and expect it to work.

WRONG!

The package available on the website is 32bit only. Apparently I need to use the Ubuntu software center for that. Let's open it, let's register (what's this damn obsession of having to register for free software?) and install Steam 64bit hoping it works.

WRONG!

The Ubuntu software center crashes with no reasons at all. Let's open it again, maybe it was just bad luck!

WRONG!

It crashes again. Let's try using the command line to install it then. It will certainly work.

WRONG!

WROOOOOOOOOOOONG!

WROOOOOOOOOOOOOOOOOOOONG!!!!!!!!!!!!!!!!


Package dependencies cannot be resolved
This error could be caused by required additional software packages
which are missing or not installable. Furthermore there could
be a conflict between software packages which are not allowed to be
installed at the same time.
The following packages have unmet dependencies:
steam64: Depends: steam (= 1.0.0.27ubuntu1) but it is a virtual package
[/CODE]

Apparently Valve didn't even make sure Steam for Linux worked with the latest 64bit version of Ubuntu.

Now I'm going to curl up in a corner and cry, my TF2 hat collection will never be the same without that hat. Thanks, Gabe and Mark :cry:

  • Like 2

Firstly... install it properly, on a real partition.

Secondly... it sounds as if pretty much all of those problems are to do with Windows 8 and not Linux itself. Microsoft never design their OSes to boot well with a Linux dualboot. Steam on Linux does work properly on Ubuntu 64 bit, you need to purge and uninstall the 32 bit client and install the 64 bit client from the software centre.

Thirdly... Don't expect Dot Matrix to give you any objective advice regarding Linux.

Can't comment on Steam and Linux, had zero interest in trying it, but Canonical hid the Wubi installer for a reason as it's been depreciated. It either works fairly well (but is stupidly easy to break), has known problems with Windows 8's hybrid boot, but more often than not it'll make you want to bash your forehead into a brick wall repeatedly when something goes wrong. Personally you're much better off just creating a partition for it and doing a "proper" dual boot... faster and a lot more reliable. Sucks about the x64 not being tested very well though, they should look at their own stats page.. 32 bit installs are going the way of the dodo. Looks like an easy fix though.

So, from what I got from that.. half the issue was because you had 8.. so if you had 7 it wouldn't have mattered.. then you had issues with ubuntu 64bit and steam. So.. instead of looking up how to fix it (which is to simply download the 32bit libraries) you called it quits.

Also, Steam for Linux works on other distros than just Ubuntu, could have used arch, mint, fedora, etc but you didn't. While I agree it seems like it was a pain to go through, it could have been easily avoided by just googling information on how to do it all.

First link searching for: "how to install steam for linux on ubuntu 64bit"

http://steamcommunity.com/app/221410/discussions/0/864959809718405749/

Just sayin'

  • Like 3

Secondly... it sounds as if pretty much all of those problems are to do with Windows 8 and not Linux itself. Microsoft never design their OSes to boot well with a Linux dualboot.

Funny, I've had no issues with Windows 8 and dual booting Linux.

Funny, I've had no issues with Windows 8 and dual booting Linux.

Natively it is very difficult to get Windows anything and linux to co-exist. Most times you have to run some extra grub scans or use easybcd or manually edit the windows boot config.

Funny, I've had no issues with Windows 8 and dual booting Linux.

If you install Linux first you'll be screwed. Windows will just hose the Linux bootloader and install it's own. If you install Windows first it's usually OK, as Linux actually seems to recognise that interoperability is important.

  • Like 2

I think it says about 400 times on the Ubuntu page that the Windows installer doesn't work on Windows 8.

Wubi has always been garbage. I don't understand why anyone they released it in the first place, or why anyone with a reasonable idea of how computers work would think they could install one OS inside another one (that's not a virtual machine).

Lol I once tried Ubuntu, managed to break the OS in an hour, tried installing a theme that required things to be typed into the Terminal... :/

post-350302-0-61427100-1361113799.jpg

How long ago was this?

When I install themes it's as easy as: extract .tar.gz folder, copy it to th ~./themes directory, open the de's settings tool and select it. I do it via CL but could be done with a tool.


tar -xgvf ./MyTheme.tar.gz
mv ./MyTheme/ ~./Themes/
[/CODE]

Right click on the panel in the bottom hit settings, hit the Themes button, and it shows up

Cool! The new Steam for Linux is out and what do I see? THEY GIVE A FREE TF2 HAT!?!?! I MUST HAS IT!!

So I downloaded Wubi and started installing...

Nice. It completed. Let's have it reboot and expect it to finish the install...

WRONG!

It doesn't boot because it says that Windows is hibernated. Windows 8 hibernates the kernel to speed up startups yet Wubi didn't tell me anything about that. Let's turn the hybrid boot off and expect it to work...

WRONG!

It still doesn't boot with the same reason. Let's go back to windows and turn hibernation off with powercfg -h off.

WRONG!

Again, it doesn't work. Same reason. Let's reboot windows and delete the whole hibernation file and reboot again.

RIGHT!

So the install starts. It starts copying stuff around for a while. Let's wait until it continues... it will certainly end.

WRONG!

It hangs at about 75%. After a while the log starts showing warnings that the copy process has freezed. After about 20 minutes I issue a "sudo reboot" command from console, of course it doesn't work and I have to do an hardware reboot. I try a couple more times then give up and download the whole Ubuntu ISO. Then, let's install the latest 64bit from the ISO like the wiki page suggests for Win 8/UEFI users (no, my machine doesn't have UEFI but since Wubi doesn't work the only alternative is the whole Ubuntu disc hoping it doesn't screw up my bootloader)...

FINALLY!

It finally installed, so let's open Steam website and download the Steam client. Let's run that nice .deb package and expect it to work.

WRONG!

The package available on the website is 32bit only. Apparently I need to use the Ubuntu software center for that. Let's open it, let's register (what's this damn obsession of having to register for free software?) and install Steam 64bit hoping it works.

WRONG!

The Ubuntu software center crashes with no reasons at all. Let's open it again, maybe it was just bad luck!

WRONG!

It crashes again. Let's try using the command line to install it then. It will certainly work.

WRONG!

WROOOOOOOOOOOONG!

WROOOOOOOOOOOOOOOOOOOONG!!!!!!!!!!!!!!!!


Package dependencies cannot be resolved
This error could be caused by required additional software packages
which are missing or not installable. Furthermore there could
be a conflict between software packages which are not allowed to be
installed at the same time.
The following packages have unmet dependencies:
steam64: Depends: steam (= 1.0.0.27ubuntu1) but it is a virtual package
[/CODE]

Apparently Valve didn't even make sure Steam for Linux worked with the latest 64bit version of Ubuntu.

Now I'm going to curl up in a corner and cry, my TF2 hat collection will never be the same without that hat. Thanks, Gabe and Mark :cry:

1/2/3. This is not really ubuntu's fault. How is it supposed to automagically know/fix weird stuff another operating stuff is doing? Also I would always recommend against using wubi.

4. Yeah, valve did indeed totally screw up the official steam for linux release. they did not test it AT ALL with new ubuntu 12.04.2 so the dependencies are all ****ed up. I really hope they fix that soon, gives a really bad impression (on 12.04.2 even if you don't have thge 32 bit library problem and it installs sucessfully the steam installer downgrades all of the 12.04.2 quantal backported xorg packages to the old 12.04.1 ones, which is both not optimal for gaming and can cause problems because its downgrading a bunch of system packages)

Firstly... install it properly, on a real partition.

Secondly... it sounds as if pretty much all of those problems are to do with Windows 8 and not Linux itself.

Nobody put that in doubt that Windows 8 was the factor, but they should have at least tested Wubi with Windows 8 and figured out basic issues like this since the hybrid boot is enabled by default on every Windows 8 install (though the issue in the end was also with the hibernation file itself, maybe the hibernation detection was bugged?). Windows 8 has been out for more than 3 months, why didn't they fix the issues or at least put the appropriate warnings?

Microsoft never design their OSes to boot well with a Linux dualboot. Steam on Linux does work properly on Ubuntu 64 bit, you need to purge and uninstall the 32 bit client and install the 64 bit client from the software centre.

That's exactly what I did. I went in the software center, I found Steam for 64bit and tried to install it. And that was the result (see the Steam link where they acknowledged the issue). You install Ubuntu, you install that nice Steam 64bit put in plain sight in the store and it fails despite Steam for Linux having been tested for a while and having been launched officially just a few days ago. WTF?

So, from what I got from that.. half the issue was because you had 8.. so if you had 7 it wouldn't have mattered..

So Canonical shouldn't be expected to test their windows installer on a version of Windows that has been out for months? Even a simple warning would have been enough but the download page only warns UEFI users and people who buy a Windows 8 LOGO system (UEFI) but my issue had nothing to do with UEFI (that I don't use nor my motherboard supports).

then you had issues with ubuntu 64bit and steam. So.. instead of looking up how to fix it (which is to simply download the 32bit libraries) you called it quits.

That's a Valve problem, that they indeed acknowledged, and I'm waiting them to fix it rather than using workarounds to get it working. After wasting a lot of time (Wubi downloading the files and installing several times, downloading the standalone ISO and updating the whole distro aren't quick tasks, they took hours) to get software that should have worked but hasn't I'm pretty sure anybody else would have quit trying and wait for some official fix.

Also, Steam for Linux works on other distros than just Ubuntu, could have used arch, mint, fedora, etc but you didn't.

Why should I have done that? Valve advertises Ubuntu for Steam so that's what I used.

While I agree it seems like it was a pain to go through, it could have been easily avoided by just googling information on how to do it all.

First link searching for: "how to install steam for linux on ubuntu 64bit"

http://steamcommunity.com/app/221410/discussions/0/864959809718405749/

Just sayin'

Installing all the 32bit libraries from terminal is just a workaround (the workarounds are also written in the Steam page I linked). At this point I'd rather wait for an official fix since it's a pretty huge issue but still... I was just expecting to install Ubuntu and Steam on it and that it should have simply worked like it was supposed to. Screw me, right?

I think it says about 400 times on the Ubuntu page that the Windows installer doesn't work on Windows 8.

The warning is for Windows 8 logo systems (because they are mandatorily UEFI) and other UEFI systems, if you click the warning indeed it leads you to the UEFI Ubuntu wiki page. The warning also said to use x64 Ubuntu instead so it's 100% UEFI related (x64 is required for UEFI). My motherboard uses a plain old BIOS (not even an UEFI-wrapped BIOS, a real BIOS BIOS) so if it really doesn't work with Windows 8 they should change the text in the download page because it's unrelated to the real issue: if they only write UEFI or Windows 8 Logo systems (computers sold with Win8 preinstalled so still UEFI) if you don't have neither of the two you expect it to work. Anyway in the end Wubi was actually working, it was the Ubuntu installer that kept getting stuck, I managed to get it to shutdown the third time and it looked like it had some issues initializing the ext4 partition.

Funny fact: the Wubi wikipedia page shows Wubi installing on Windows 8. This is clearly a conspiracy!

1/2/3. This is not really ubuntu's fault. How is it supposed to automagically know/fix weird stuff another operating stuff is doing? Also I would always recommend against using wubi.

Whose fault is it then? It's a Windows installer, not just anyone's but an Ubuntu specific one, shouldn't it be expected to work on Windows?

4. Yeah, valve did indeed totally screw up the official steam for linux release. they did not test it AT ALL with new ubuntu 12.04.2 so the dependencies are all ****ed up. I really hope they fix that soon, gives a really bad impression (on 12.04.2 even if you don't have thge 32 bit library problem and it installs sucessfully the steam installer downgrades all of the 12.04.2 quantal backported xorg packages to the old 12.04.1 ones, which is both not optimal for gaming and can cause problems because its downgrading a bunch of system packages)

Good thing I didn't follow the instructions then. I was somewhat expecting all sorts of havoc too, instructions that said to install the whole x86 subsystem on a 64bit platform didn't sound much right.

Nobody put that in doubt that Windows 8 was the factor, but they should have at least tested Wubi with Windows 8 and figured out basic issues like this since the hybrid boot is enabled by default on every Windows 8 install (though the issue in the end was also with the hibernation file itself, maybe the hibernation detection was bugged?). Windows 8 has been out for more than 3 months, why didn't they fix the issues or at least put the appropriate warnings?

So Canonical shouldn't be expected to test their windows installer on a version of Windows that has been out for months? Even a simple warning would have been enough but the download page only warns UEFI users and people who buy a Windows 8 LOGO system (UEFI) but my issue had nothing to do with UEFI (that I don't use nor my motherboard supports).

You do realise that Ubuntu 12.10 was released BEFORE windows 8, right?

You do realise that Ubuntu 12.10 was released BEFORE windows 8, right?

You do realize Windows 8 had developer previews, consumer previews, release previews and the RTM was already when Ubuntu was launched? Still this is an unrelated issue: Wubi is a separate download, it could have been updated in the meanwhile. Or they could have simply put the proper warnings rather than telling to install x64 standalone because of UEFI.

Ubuntu only release revised installers for LTE releases, they don't do it for .10 releases. The simple fact is, you're blaming them because you didn't do your homework properly. Linux developers actually work pretty hard on interoperability but like everything it takes time. Microsoft however don't work on it at all, in fact one could just reverse your argument and say it's Microsoft's fault for never bothering to make their bootloaders interface nicely with non Microsoft operating systems.

Next time do your research.

  • Like 2

Ubuntu only release revised installers for LTE releases, they don't do it for .10 releases. The simple fact is, you're blaming them because you didn't do your homework properly. Linux developers actually work pretty hard on interoperability but like everything it takes time. Microsoft however don't work on it at all, in fact one could just reverse your argument and say it's Microsoft's fault for never bothering to make their bootloaders interface nicely with non Microsoft operating systems.

Next time do your research.

Yes, it's certainly the user's fault if Canonical didn't bother either updating the software adding at least a messagebox saying "Your operating system is not supported" (how much would that be, 3 lines of code? 1 minute of recompiling?) or at least add a proper damn warning on the download page rather than a confusing one regarding a completely unrelated UEFI issue.

Their release schedules are not a valid excuse, they could have certainly done something about that but they didn't. It's their fault. Stop with the double standards. And no, nobody said Microsoft is better: google "Games for Windows Live Windows 8", fun for everybody!

Whose fault is it then? It's a Windows installer, not just anyone's but an Ubuntu specific one, shouldn't it be expected to work on Windows?

Good thing I didn't follow the instructions then. I was somewhat expecting all sorts of havoc too, instructions that said to install the whole x86 subsystem on a 64bit platform didn't sound much right.

Installing the 32 bit libs is actually right, because for some reason valve made steam 32 bit only on linux. Ubuntu does support multilib (running 32 bit programs on 64 bit like you can in windows) out of the box, you just need to grab the appropriate 32 bit libraries first, which the installer/software center usually does automagically, not sure why so many people seem to be getting the 32 bit libs error. Did you make sure to install all ubuntu updates before installing steam?

The package downgrading issue is another problem all together and is a problem with valve's steam installer having totally outdated package dependencies. I wouldn't recommend anyone install steam on ubuntu 12.04.2 until valve sorts that out. afiak it should work fine on 12.10 though, it installed fine when I used the beta on 12.10. I've only had problems when installing it on 12.04 LTS. I'm not sure what version you are running.

Yes, it's certainly the user's fault if Canonical didn't bother either updating the software adding at least a messagebox saying "Your operating system is not supported" (how much would that be, 3 lines of code? 1 minute of recompiling?) or at least add a proper damn warning on the download page rather than a confusing one regarding a completely unrelated UEFI issue.

Their release schedules are not a valid excuse, they could have certainly done something about that but they didn't. It's their fault. Stop with the double standards. And no, nobody said Microsoft is better: google "Games for Windows Live Windows 8", fun for everybody!

Unfortunately that's how distros work. There was a problem with Fedora 15 or 16 I think where the release .iso version couldn't be put onto a USB stick and was discovered a day or so after release. Even though it was a simple fix (rebuild with a newer version of something), they didn't update the .iso. Instead you had to follow directions to build your own .iso with the updated package, and then it would work.

It might have been much more than 3 lines of code to fix it though, so it might have taken more time (and needed through testing), or just hold off on the fixes until 13.04.

Website note though should have been done.

Thread summary: It's everyone's fault and Steam on Ubuntu 64 doesn't work without workarounds.

Everyone could've done a bit more testing, but I think the blame here rests more on Valve's shoulders for not setting dependencies right.

As for Ubuntu and Windows not getting along, unfortunately there's no real standard on bootloaders, and Microsoft doesn't want to bother with official support when trying to integrate into GRUB. I can't blame them either, as GRUB is, commercially, a very small minority.

Gaming on Linux still has a ways to go. Someday!

Unfortunately that's how distros work. There was a problem with Fedora 15 or 16 I think where the release .iso version couldn't be put onto a USB stick and was discovered a day or so after release. Even though it was a simple fix (rebuild with a newer version of something), they didn't update the .iso. Instead you had to follow directions to build your own .iso with the updated package, and then it would work.

It might have been much more than 3 lines of code to fix it though, so it might have taken more time (and needed through testing), or just hold off on the fixes until 13.04.

Website note though should have been done.

Depends on the distros, some distros would probably release a new iso for that type of issue.

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!