Jump to content
Computer Audiophile

Search the Community

Showing results for tags 'windows 10'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Reviews
  • CA Academy
  • Audio Shows
  • Bits and Bytes
  • Digital Vinyl
  • The Music In Me

Blogs

There are no results to display.

There are no results to display.

Categories

  • Downloads
  • CA Sample Club's Files

Forums

  • Equipment
    • General Forum
    • Music Servers
    • DAC - Digital to Analog Conversion
    • Disk Storage / Music Library Storage
    • Networking, Networked Audio, and Streaming
    • Headphones & Speakers
    • Software
    • DSP, Room Correction, and Multi Channel Audio
    • iTunes and Everything Apple
    • Article Comments
  • Music
    • Music Downloads & Streaming
    • Music in General
    • Music Analysis - Objective & Subjective
    • In Memoriam
  • Sponsored Forums
    • Sonore (Sponsored)
    • HDtracks (Sponsored)
    • UpTone Audio (Sponsored)
    • Highend-AudioPC (Sponsored)
    • Abbingdon Music Research / iFi audio (Sponsored)
    • Ciamara (Sponsored)
    • Vinnie Rossi (Sponsored)
    • Klipsch (Sponsored)
  • CA All Access
    • Buy & Sell Audio and Computer Components
  • Allo's Allo Topics
  • CA Sample Club's Topics
  • CA Sample Club's Q & A

Found 11 results

  1. Hello all Has anyone got any advice ion getting the windows 10 driver for the Perreaux Audiant 80i http://www.perreaux.com/support/usb-audio-driver-installation to actually work. The company's only proposal is to send in the unit to New Zealand (at my expense), but the unit works absolutely fine on iOS? Any ideas welcome. thanks gg
  2. Hi All: I have a Lenovo TS140(Xeon) with 16GB RAM. I currently use it to run Hyper-V with one VM which does Roon Core and I run Plex on the main server. I am thinking of porting Plex into Azure and repurpose this TS140 to run as Roon Core machine. This is a headless machine, which will be stuck in a media closet area, that I had developed at home and will be hardwired to the network. I am thinking of putting Windows 10 on this machine. Good or bad idea and anything else that I should think of. This machine does not have any SSD but two seagate HD. I was thinking of keeping my QNAP as the source of music instead of the HD. I would appreciate any input. Ahmed
  3. Hello What USB to SPDIF/AES-EBU interface today supports Windows 10 Creators Edition USB driver (i.e. no installation required on Windows) -? thanks,
  4. Something I've noticed while streaming Tidal on my Windows 10 PC is clipping and distortion. I'm currently using Peter's Equalizer APO (Peace). With a flat EQ or with EQ turned off, I get clipping. I decided to test Spotify and levels never reach clipping. Current setup: Windows 10 vol 100% => Tidal app vol 100% => Schiit Jotunheim w/DAC module => Headphones Taking the software vol control in Tidal down a bit does stop the clipping, but I figured that should be maxed out given my setup. Spotify has it's vol control maxed with no issues. Any thoughts?
  5. Please excuse me if this is the not the right area to post this question, this is my first post. I have been using my Cary 303T SACD as a DAC to listen to digital music stored on my computer running WIndows Vista. This worked fine till my laptop died, and I ended up with a new Windows 10 laptop. The Cary USB drivers seem to install correctly: install completes without errors, and the Cary Audio USB Driver is listed under control panel - installed programs. But when I plug the laptop to the Cary with the USB: The Cary does not recognize the PC, the display shows: PC/USB D-IN: NONE Windows 10 beeps (so it recognized something was attached) but does not recognize the device, Device Manager displays: Unknown Device, and when I check the driver details for the unknown device it says that No driver files are required or have been loaded for this device. The drivers are the latest ones available from the Cary web site. I tried re-installing this multiple times, with different combinations of installing in Compatibility mode for Windows 7 or Vista, as administrator, etc. I tried the Windows compatibility troubleshooter. I tried disabling driver signature enforcement following this video. I tried disabling USB selective suspend setting following this advice, and forbid WIndows to turn off the device to save power based on this site. The cable is OK (it is the same one I was using previously), but I also tried another one just in case, and tried all the laptop's USB connectors just in case. No luck. Has anyone else run into this ? Any suggestions to solve the issue ? Thanks in advance, Christiaan
  6. Following is a procedure for setting up a PC to run Windows 10 diskless (i.e. with no local storage). This procedure should also work for setting up diskless Windows Server 2012/ Windows Server 2012 R2, though I have not tried it. This is a Windows-only procedure with no Linux involvement, so no Linux expertise is required. "Server" refers to the PC running Windows Server 2012 with iSCSI target service acting as remote disk server. "Client" refers to the diskless PC booting OS remotely over Ethernet. It is up to the individual user to decide which of their audio PCs to run diskless. In a dual PC setup it should be possible for both control PC and audio PC (using AO terminology) to run diskless, though a 3rd PC or NAS will be needed to fulfill the role of iSCSI target. The procedure below only covers setting up a PC with Windows Server 2012 R2 to act as iSCSI target. As there are many alternatives possible, please consider this procedure as a guide, as it represents just one solution. A Linux-based iSCSI target is much more cost-effective than a WS2012-based iSCSI target. ************************* Diskless Windows 10 Setup Jan 17, 2015 Sam Chau Client PC Requirements - Gigabit Ethernet NIC with PXE boot support Server PC Requirements - Gigabit Ethernet NIC, with driver for Windows Server 2012 R2 (note: some consumer class NICs lack driver for Windows Server 2012 R2 and cannot be used) Ethernet Switch - Gigabit Ethernet switch - Connection to home wireless/wired router as DHCP server - Alternative: use static IPs on the same subnet for both server and client Contents of iscsi.ipxe (text) file: #!ipxe echo iscsi.ipxe script running... ifopen net0 dhcp set net0/gateway 0.0.0.0 echo IP: ${net0/ip}, Gateway: ${net0/gateway} set keep-san 1 echo keep-san: ${keep-san} sanboot iscsi:<server IP>::::iqn.1991-05.com.microsoft:<server name>-win10-target boot Note: - replace <server IP> with server static IP address: e.g. 192.168.0.100 - replace <server name> with server name, e.g. audioserver. This name must match what the client sees within iSCSI Initiator - setting gateway address to 0.0.0.0 is a workaround to avoid Windows 10 suffering an "INACCESSIBLE BOOT DEVICE" blue screen crash during boot Setup Procedure Hardware setup: 1. Connect client PC to server PC via their NICs 2. Options for client PC IP address assignment A. Connect client PC to home wireless/wired router - use router DHCP server B. Configure DHCP server on Windows Server 2012 R2 to assign IP address to client C. Set static IP address on same subnet for client For options B & C, internet connection for client is optional 3. Enable PXE boot option in client PC BIOS setup Server: 1S. Install Windows Server 2012 R2 (Standard, Essentials, etc.) 2S. Assign static IP address to NIC 3S. Enable Remote Desktop feature ("Allow remote connections to this computer") for allow client to remote manage server running "headless" 4S. Using Server Manager, install iSCSI target feature 5S. Create a disk folder to carry VHDX files, e.g. C:\iSCSIVirtualDisks 6S. Share C:\iSCSIVirtualDisks folder with rear/write permission for client username 7S. Create C:\TFTProot folder 8S. Put ipxe-undionly.kpxe and iscsi.ipxe files in C:\TFTProot 9S. Download and set up Tiny PXE Server (Tiny PXE Server - reboot.pro) - Update config.ini: - root=C:\TFTProot - filename=ipxe.undionly.kpxe - altfilename=iscsi.ipxe - proxydhcp=1 - poolsize=0 - Click "Online" to launch pxesrv 10S. At Control Panel\System and Security\Windows Firewall\Allowed apps - Enable iSCSI Service - Add entry for pxesrv.exe Client: 1C. Connect client PC to home network via gigabit Ethernet NIC and cable 2C. Attach local storage (HDD/SSD) 3C. Install Windows 10 OS into hard disk - Copy OS install files into FAT32 formatted USB flash drive to use for OS installation 4C. Install NIC driver and other device drivers (graphics, audio, etc.) as needed 5C. Ensure client can properly browse on Internet 6C. Launch iSCSI Initiator - Type "iscsicpl" <Enter> at the Command Prompt window and answer Yes to the prompt - This will configure Win10 to auto launch the iSCSI initiator service at OS startup 7C. Launch Registry Editor (regedit.exe) to set boot flag for LAN driver - Locate the LAN driver service name under HKLM\SYSTEM\CurrentControlSet\Services - Example: for motherboards featuring Intel I217V/LM, I218V/LM, I219V/LM LAN the driver service name is: e1dexpress - Click on the driver service name, locate the Start key (REG_DWORD), double-click it and change its value to 0 - Repeat this Start key value change to 0 in HKLM\SYSTEM\ControlSet001\Services and HKLM\SYSTEM\ControlSet002\Services - Close Registry Editor 8C. Download and run Disk2VHD.exe (from Microsoft Sysinternals: https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx) - Ensure "Use Vhdx" and "Use Volume Shadow Copy" checkboxes are checked - In "VHD File Name" box, enter "\\<Server IP>\<share name>\Win10.VHDX (e.g. \\192.168.0.100\c\Win10.VHDX) - Run Disk2VHD to create VHDX file on server Server: 11S. Set up iSCSI target LUN - Use "existing VHDX" option to select Win10.VHDX - Add MAC address of client to iSCSI initiator list Client: 9C. Launch "iSCSI Initiator" - On "Discovery" tab, click "Discover Portal" and enter IP address or DNS name of server - on "Targets" tab, ensure a target appears on "Discovered targets" list - target name should look like: iqn.1991-05.com.microsoft:<server name>-Win10-target 10C. Shut down Windows and detach hard disk from client 11C. Power up client and it should proceed to PXE boot - PXE boots to iPXE from server, then chains to iSCSI target LUN to start Windows 10 boot Notes: A. This procedure sets up a fixed size VHDX on the server. An alternative is to create a new dynamic VHDX (of desired max size) on the server, mount it locally (using iSCSI Initiator running on the server), connect the client disk to the server via USB-to-SATA adapter, then partition copy the client disk to the mounted VHDX. This preserves the dynamic nature of the VHDX file and helps conserve disk space on the server. -end-
  7. Hi maybe most of view are mac users , I read a lot about mac is far better for music then pc by the way i have a pc and a laptop about pc , i tried on different machines with a built in realteak ausus motherboard and and other with soundblaster audio card on these machine same drivers i started to listenen music with headphone and with densen amply i used foobar2000 and aimp to play music and (i haven't tried windows 8.1 ) but again same hardware same ,audio settings, same audio card settings ,music under w10 sounds better then windows 7 i wanted to use the WSAPI on foobar last version and aimp 4 too (by the way i haven't understood the different between foobar (Wsapi event vs push) but it's not relevant seeings i used aimp too i tried asio too the audio -> flac but seems that w10 again sounds always better is wrong ? ps hope it's the right section thanks best regards
  8. I'm at the end of my rope: I have ~3000 wav songs accumulated over the past 25 years with no metadata, and I've spent untold hours trying to set up a music player on my Windows computers (7 & 10) to listen to them. Sequentially in folders, and gaplessly; a simple folder/tree-based menu. I've installed a dozen reputed players and futzed with them for hours, but wind up with nothing to show but an ugly screen and an endless random string of totally unorganized songs - and that's a positive outcome. My only player for the past 10 years is through a media USB input on a Samsung DVD player, which structures my folders perfectly. It doesn't offer much flexibility (through my hi-fi only) and, drat, it isn't gapless. I'd be grateful for anyone who has knowledge of a music player solution, or where next to seek one. Or if I'm stuck with the Samsung player.
  9. All, Warning Microsoft damaged the USB drivers in Windows 10 Anniversary edition and everyone is complaining about BAD SOUND. We have contacted the Windows Sound group and they are aware of the problem. Thanks and you can go back to your regularly scheduled programming! Gordon
  10. Hello Folks The beta of AudiophileOptimizer for Windows 10 is making progress. It's still a lot to do, still many things not perfectly or only partially working, but the results are still pretty good so far, both for functionality as well as for sound quality. The first phase of the beta is going to end now, so from now on not only "chosen" ones can test the beta, every existing AO customer who is interested in testing the new beta is warmly welcome to do so. So this is the beginning of phase 2, the partially public beta. Quality To help us improve the quality and performance of the AudiophileOptimizer during the beta phase, please only use a fresh installation of Windows 10. Do NOT use any foreign scripts or other audio enhancement tools/software, etc. because your results would be useless for us. Just Windows 10, the AudiophileOptimizer and the mediaplayer of your choice. Who is the beta for? Please let me outline for who the beta is and for who it probably isn't yet. Consider yourself a possible beta tester if you: - Have a valid AO 1.30/1.40 license in place - Are a very experienced user of the AudiophileOptimizer and very computer savvy as well - Are able to provide a clean and fresh installation of (any) Windows 10 version to test the beta - Don't mind if you need to format and reinstall your system (maybe even multiple times) - Do fully understand what a software in early beta stadium is - Have no problems reporting issues or features that do not yet work as expected - Are able to clearly focus your testing on the features that are mentioned in the change log - Are able to provide feedback about technical issues via email to windows10@highend-audiopc.com - Are able to read, understand and follow our instructions carefully If you don't feel comfortable with the points mentioned above then testing the beta is probably not for you. You should wait for the final release of AO 2.00. But if you think you are the right person, have fun in testing things, are able to provide us valuable feedback and be an active part of this second beta phase, please feel free to give us a message to windows10@highend-audiopc.com and let us know about your interest and especially why you are the right person for this part of the beta phase. Change Log of AO Version 2.00, beta 4 ============================================ AudiophileOptimizer 2.00 - Several adjustments for Windows 10 - Enables MinimServer in core mode (Server 2012 R2) - Improvements on Kernel-Streaming and MediaPlayer support (Server 2012 R2) - Possibility to disables Windows Defender (Windows 10) - Possibility to disable OneDrive (Windows 10) ServiceTool 2.00 - Several adjustments for Windows 10 - Shell replacement for JRiver Media Center 21 - Shell replacement for MinimServer - Possibility to strip down Windows 10 (remove all apps, optional features, etc.) Setup 2.00 - Several adjustments for Windows 10 ...so let the fun begin! :-) Enjoy, Phil
  11. Windows 10

    I've been thinking of trying out Win 10 for my next Audio PC. A google search brings up the Preview version which I am assuming is not what others are using on here. Could someone share what one needs to do to get a full version of Win 10? At least a version that is functional for Audio. Thanks for any help in advance.
×