Big AL

Here's a Youtube link - If you want a guide, here's a link - http://itproguru.com/expert/2016/06/installing-windows-server-2016-on-bare-metal/

Hi Phil, Yes, I tried other ports, both built-in and ports in an external USB 6-port hub, along with several spare keyboards and mice. No change. It's a doorstop when I boot to that SSD. ALL of the NON-music related roles and services (remote access, RDP, remote registry, remote desktop, HTTP, FTP, etc.) are disabled. Even the NIC is disabled. There isn't any way to remotely log into the system at all, given that it was configured for music playback ONLY and nothing else. Virtually every non-music related service and role is disabled. For all intents and purposes, it's a standalone, music player and nothing else. It's not even plugged into my LAN, since I don't really need Internet or LAN access from my studio computer, which is what it is. I have three other computers in my office I use for those and other non-music related tasks. It would appear that I am at the point where scrubbing the SSD and installing Windows Server 2016 is my only option. C'est la vie. Thanks for all the suggestions but, as I feared would be the case, it's time to upgrade that SSD to Server 2016. Not what I wanted to do this weekend, but obviously, it's time. AL

Hi Phil, Great idea, but how do I install/configure RDP on an OS without keyboard and mouse control of that OS? RDP is disabled, since I had no use for it when it was running normally (i.e. with keyboard and mouse control). As a reminder, I did NOTHING to this computer or the instance of Windows Server 2012 R2 or AO, either physically (no devices swapped in or out, no devices switched to other USB ports, etc.) or system configuration wise; no OS or BIOS tweaks or installs or uninstalls of any software. Nothing changed, either in hardware or software. One day I had keyboard and mouse control and the next day it did not. To respond to your original question about JPLAY and hibernation mode, I don't even have JPlay installed and I ALWAYS disable hibernation mode on ALL my computers (laptops included). I've never trusted it and it ALWAYS and eventually screws up a system. Is there a file within the AO installation or within Windows Server 2012 R2 that I can either edit or delete to either force it OUT of Core mode and back into GUI mode? AL

Hi Phil, I wasn't (or don't think I was) implying that it was an AO issue at all. I'm just wondering if there's something I can do, via one of the other OS's (GUI mode Server 2012 R2 or Windows 10) to reset or 'fix' the Core mode installation. Maybe some file I can edit or delete to get the OS (Core mode Server 2012 R2) OUT of Core mode so that Windows 'plug 'n play' can (maybe) get my mouse and keyboard working again? Like I said, I'm at a loss as to what to do when I can't do anything without a working keyboard and mouse. Just taking a stab in the dark here on this one. I guess my question should have been; is there some way to revert back to standard GUI mode externally, from another OS that has access to the Server 2012 R2 Core mode file system? That SSD just appears as another drive from within one of the other two OS's running on two other SSDs. AL

Phil --- or whoever might read this and know. I have no idea if this is a common or rare issue, but I have one. I'll explain... I have two instances of Windows Server 2012 R2, each running on it's own SSD. One runs in GUI mode, for studio recording work, and the other one in Core mode, for music playback only. Both instances boot right up, but when I boot into the Core mode instance, I've somehow lost both keyboard and mouse control, which, for all intents and purposes, turns my computer into a rather expensive door stop. I have to force a hard boot (press and hold the power button) to get out of that instance of Windows Server 2012 R2 / AO Core mode. My mouse and keyboard work just fine on the AO GUI mode SSD, as they do from a third OS on a third SSD running Windows 10 Pro 64-bit, which is used for everyday, goofing around stuff. It's ONLY the AO Core mode instance of Windows Server 2012 R2 that lacks keyboard and mouse control, which USED to work flawlessly. And NO; I did NOT change or swap out either the keyboard OR the mouse when this issue first appeared, OR switch them to different USB ports, OR change anything in the BIOS. Subsequent to the appearance of this issue, I have tried swapping them both out with spares. No difference; meaning neither works no matter which keyboard or mouse I plug in (I have several spares of each). Both (in fact ALL) of my keyboards and mice are USB, and they ALL work perfectly from any other OS and/or computer, of which I have four. I can access the file system on the SSD that runs Windows Server 2012 R2 and AO in Core mode from any other instance of an OS; either Windows 10 or Windows Server 2012 R2 running AO in GUI mode. I just can't do anything once I boot into the instance of Windows Server 2012 R2 running AO in Core mode. The keyboard doesn't work and the mouse doesn't work. It's kind of hard (make that impossible) to do ANYTHING from within ANY OS without keyboard and mouse control. This isn't really a show stopper for me, and although the non-responsive instance of Windows Server 2012 R2 running AO in Core mode is my PREFERRED music listening platform, I can still boot to either one of the other SSDs and listen to music. Also, I just purchased Windows Server 2016, and although I hadn't planned on upgrading to it any time soon, I may HAVE to at this point, just to get AO Core mode back. I DON'T want to have to reinstall Windows Server 2012 R2 again, as I spent a LOT of time optimizing and customizing the AO Core mode instance (both the OS and AO). If I HAVE to start from scratch, I'd much rather do that with Windows Server 2016, although I don't really want to do that just yet. Anyway, I'm pretty much at my whits (or lack thereof) end on this one and would greatly appreciate any and all suggestions. Thanks in advance to anyone who replies. Big AL

Johnseye --- Good points, one and all, but given that Phil isn't developing AO to run on Linux/UNIX, it's kind of a moot point. I WISH Phil would port his software/scripts to Linux! Compiling a kernel (ala the FREE Debian kit) that supports ONLY the hardware you actually have in your 'box' and includes ONLY the core elements of the OS that you really want or actually need for music playback and a file system/file server, etc., would obviously be the BEST way to fly! I've read good things about 'AP Linux' and am about to start building a new computer to test it on. Unfortunately, I seriously doubt that Phil is headed in that direction. That said, how cool would 'AO Linux' be!? VERY cool! As they say, hope springs eternal. Maybe some day. Thanks for posting!

There are a couple of dozen server roles and technologies, not to mention management capabilities and tools, that a desktop version of Windows will never have or require. It's just not in the nature of a desktop OS to provide anything more than desktop features. Turning off (disabling) services and scripts in Windows Server 2012 R2 is trivial. For the purposes of an 'audio file' server or player, core mode is where the REAL horsepower in 2012 R2 becomes obvious. The fewer service an OS runs, the better the audio playback quality becomes. Minimizing background processes minimizes the load on a CPU. The lighter the load, the quieter your system will run and the quieter it runs, the better your sound quality. You can only do so much with a desktop OS, while there's very little you CAN'T do with Server 2012 R2. Windows Server 2012 R2 Roles and Technologies Windows Server 2012 R2 Management and Tools Compare the above info, which is only a fraction of what can be done with Windows Server 2012 R2, to what a desktop OS (Win7, 8.1, 8, 10) provides, and it should become intuitive obvious that there is no comparison.

There is a BIOS setting called 'SpeedStep', for Intel CPUs. AMD calls it 'Cool n' Quiet'. If you force (set) that option to 'Enabled', your CPU should throttle down under idle loads. That said, I have no idea what AO might be doing to disable those features. You'll have to ask Phil that question.

Thanks for the reply. Unfortunately, I don't have room in my studio setup for another computer, nor do I really need or want another one in there. I read the same thing about Server 2012 R2 and the 'dual computer' setup, and while that's certainly an appealing option, I just don't have the space for it. Is it safe to assume that a single computer running 2016 core will sound better than a single computer running 2012 R2, or is that a setup you never made a sound quality comparison of?

This has turned into a really interesting post with lots of great info, suggestions and observations. This IS one of the best things about AO; our HUGE and active community of users who never tire of their quest for audio nirvana. ALL of you are one of the main reasons I started using AO and I hope you all know how much you add to the entire AO experience. Without YOU (and obviously, Phil), AO just wouldn't have the same appeal that it has WITH you! I have a question for those of you this pertains to, and for Phil as well. I have a somewhat involved setup so please bear with me when I start explaining how I use AO. My question is; From a sound quality perspective, how does Windows Server 2016 running in Core mode compare to Windows Server 2012 R2 running in Core mode? So far, I have two instances of Windows Server 2012 R2 running AO (last version of 1.4) and one instance of Windows 10 Pro 64-bit running AO 2.20 B4. Of the two Server 2012 R2 instances, one is running in Core mode and the other is running in GUI/desktop mode. The Core instance is for music playback only while the GUI/desktop instance is for music recording and playback (editing, mixing, mastering, etc.) using a variety of DAW software. The Windows 10 Pro instance is for recording and playback using Avid Pro Tools v12. Avid Pro Tools will not run on ANY version of Windows Server. It will install, but it won't run. It (Pro Tools) is THE best DAW software on the planet and is what I was using in my studio computer prior to installing Windows Server 2012 R2 and AO. I only installed Windows 10 so I could run Pro Tools again AND AO on the same computer. Each instance of Server 2012 R2 and Windows 10 runs from a separate SSD configured in Tri-Boot on my studio computer. In other words, I can boot directly into any one of the three operating systems whenever I want to. For those of your who are wondering how AO running on Windows 10 compares to Windows Server 2012 R2 in core mode, there simply is no comparison. Don't get me wrong here; running AO on Windows 10 sounds GREAT, but it does not compare to AO running on Server 2012 R2 in Core mode. The difference between the two is striking and immediately apparent, but I HAVE to run Windows 10 to be able to use Pro Tools. There just isn't any way around it. I worked with Phil on this one (over a year ago) and we tried every trick in the book to get Pro Tools running under Server 2012 R2, but to no avail. It took WEEKS to finally get Avid to admit that they're somehow preventing and/or blocking it from running under Windows Server, although they wouldn't tell me WHY. That's all ancient history at this point and I've since moved on. At any rate, I'm just wondering if anyone who is running AO under Windows Server 2016 was previously running it under Windows Server 2012 R2 and how they compared, sound-wise. Is there an obviously and immediately apparent (audio) advantage to switching to Server 2016 over 2012 R2, or is it too subtle of a difference to justify the additional expense?

Phil --- more importantly, is there any REASON to install the Windows 10 Creators Update? Or is it just more fluff with nothing actually useful to offer, in terms of audio?

I keep seeing you reference "not meant for production systems" (or words to that effect). I'm running AO on my studio computer, which I guess technically is a "production system", since I'm 'producing' (recording) music on it. That said, I'm running AO 2.2 Beta 4 and have yet to come across ANYTHING untoward. I've also been running it since it was available for download, although I'm not sure when that was. It's as rock solid as the previous 'full release' production version (or whatever it's called). And here's the important (to me) part; it actually sounds BETTER than the previous production/full release version. I guess my point is that I'm NOT producing anything earth shattering or of GREAT importance, either to the world OR to me. If I lose a track, no bit deal. It's simple enough to record another one, although that's never happened while running ANY version (beta or otherwise) of AO. My financial 'books' (data entry, record keeping, etc.) are all entered and kept on a separate (office) computer, NOT because I don't trust my studio computer or AO but because it's just simpler that way and it keeps my studio computer nice and clean. Clutter free is GOOD on a computer used for music production, whether it's just for listening, recording or for both. That's my studio computer; it does BOTH. I guess I'd never really thought about the stability of an AO beta version, since I've run quite a few of them. I guess if my studio computer was connected to a nuclear reactor, then sure .... I MIGHT hesitate to load AO onto it, although it's doubtful I'd be listening to 'Jazz at the Pawnshop' on a computer connected to a nuclear reactor. Sure, that's an extreme example, but I'm hesitant to even suggest that there might be something buggy or unstable about ANY version of AO (beta or otherwise) that might prevent me from loading it onto ANY computer. It's just VERY stable and 100% reliable. Good stuff!

I could not agree with you more, Franatic. I have only been running Audiophile Optimizer for about 1.5 years now but I have to say, as a developer myself, that I have NEVER come across a more thoroughly tested piece of software. And that includes the software I develop myself. I just don't have the patience for debugging at THAT level. Phil is meticulous beyond description and whether it's because he's Swiss or whether it's just a personality trait, I have no idea and I really don't care. All I know is the end result of his HARD work (a bug-free AO) and how much he truly cares about his customers. I couldn't begin to tell you how many questions and comments I've emailed to Phil, and every single one of them have been answered and/or addressed. I don't know how he does it but he ALWAYS takes time out of his busy schedule to answer my (probably dumb) questions, and he does it so quickly it's almost scary. We are VERY lucky to have Phil and I for one am extremely grateful for everything he does and especially for every line of code he writes!

That's great news! Thanks for the info, Phil. On the subject of 24-bit/192KHz sample rates, the author (Russell Smith) of the article you linked to stated --- "Although support for high sample rates is not common in consumer tech right now ..." Really? On who's planet?! My CONSUMER grade LG VG10 cell phone supports 24-bit/192KHz and my CONSUMER grade TEAC UD-503 supports up to 32-bit/384KHz and up to 11.2MHz DSD, all via USB. For that matter, I have at LEAST two other DACs and several sound cards, along with a Soundblaster Audigy 2 sitting in a box out in my garage, that ALL support 24-bit/192KHz. I purchased the SB Audigy 2 back in 2002/2003 time frame. The availability of source material encoded at 24-bit/192KHz was pretty scarce back then (maybe non-existent?), but the capability to decode it wasn't uncommon at all and has been VERY common for many years now. Am I missing something or just not interpreting his statement correctly? What do you suppose he REALLY means by 'consumer tech'? Big AL

I agree with your 'best bang for the buck' assessment of AO. Obviously, I've spent a lot more on many other products. Cables alone were a BIG expense, not to mention the DI/Mixer (Digital Interface), high-end DAC, studio monitors, microphones ... the list goes on and on. In terms of immediate and obvious results and instant gratification though, Audiophile Optimizer wins hands down, although (for me) JRiver Media Center is right up there too. I haven't tried HQPlayer yet, although my DAC (TEAC UD-503) is on the list of supported hardware. I'll check it out soon. Thanks for posting, clipper!