It's an old thread but there has been some changes with asio vs wasapi. With an ASUS essence stx, if use ASIO, it's louder than wasapi but not as much as before the Creator update from windows 10. Wasapi has a better sound now which can be hard to dicern when we don't have the right hardware to listen to it. ASIO is still the best but Wasapi is VERY close behind. Also because of the " creator update" those who own a DAC can see that windows can play now 24/192 at the USB output. IT might be 32/196 but anyway, I've red that it has been changed since the creator update. Cheers !
Okay... Check your "drivers" if one of those methods is louder than the other... As for better sound that's subjective. Do you even know what you're talking about by the way?
I've been using WASAPI since I found out about it's existence with a Windows 7 era machine I no longer have. I've been through almost every update of Windows 10 (Initial, November Update of 2015, Anniversary, Creators) and I've not notice any change to how WASAPI functions at all other than my mom's Windows 7 era laptop failing to stop playback after you pull out the headphones but that was going on with the initial update and is pretty much just a compatibility problem with either the hardware or drivers and not a change in how WASAPI functions.
It bothers me for a month. Windows will automatically update itself to keep up the latest version, but after Windows update, I can't open 'properties' for my files in fb2k. Click properties, then fb2k crashes. After reboot fb2k, listening [to them] is still available, but as for now I can't edit all those information to my files. Keep clicking properties, fb2k will keep crashing............
I've submitted several crashed reports. No replies. My Windows is the latest, haha. And so is my fb2k - version 1.3.16 Really need your help, thanks!
Great plugin and I love the customizability! Here's my version of the controls. It's a minimalist set-up that gets rid of all the media control buttons except play/pause (it's now the album art). It's also intended to work with the default Windows 10 taskbar height (~46 pixels). Enjoy
Well, I gave those away, I didn't like them at all. You can try cheap ones but you still have to try great grands. One of my favorite brands is Audio-Technica, they have quite cheap ones, also of course another great brand is Sennheiser but look into Sony, Philips, JVC, Koss for cheaper ones.
Did you check that link I sent you? They have good headphones for all prices.
As I still haven't found a clear winner, I've decided I'll try a very cheap model which should also be decent and, if I'm not satisfied with that, I'll switch to a pricier one. The model I've chosen is the Xiaomi Piston 3 (which I've found available on AliExpress from Xiaomi's official store for about 8$, shipping included). I've read that it doesn't provide a very good isolation: maybe that can be improved by replacing the provided tips? (If that's true, what kind of tips would you recommend to me?).
@Rollin: well, OK... I can leave with that, still good to know that it is something that possibly can be fixed if I dig deeper. EDIT: I see that there are no waveforms from 3gp files recorded only with Sony Ericsson E15i (Android based), also known as Xperia X8 if I am not mistaken. Files recorded with other phones (some Nokia, Sony Ericsson - various models non-Android based, some camera) work fine and indeed display waveforms... LOL...
@Zao : if problem with Westbam Mvid is that file itself is malformed and incorrectly reports its length / ffmpeg can not read it properly and pass it to foobar - OK, I have no pretensions that it can not be fixed - totally bad input = bad output But for other supposedly broken files from the package I only ask for not discarding data that were calculated for initial blocks and displayed before error occurred. Their length is reported properly so base condition for waveform seekbar component exist. I intentionally added there 1 file or 2 files, that display full wavefom, despite they also throw decoding/playback error at the very end. Also I noticed that incomplete downloads still allow to display not disappearing waveform, despite they are also malformed at the time when they still download and playback decoders throw errors on them.
Of course I don't expect anything to be fixed immediately. Just when next release will be planned for whatever reason, you can consider also not clearing seekbar when certain errors occur, but leaving empty space in it instead - as for incomplete downloads happens now.
What kind of noise or distortion does a marginal USB cable make?
I don't think that any of the common audiophile descriptions fit.
'course not. Audiophools, not audiophiles, make it look like it behaves as some sort of analogic media, when it is obviously does not.
Being digital, all those zeros and ones will either get to the other side or not, or, in more realistic terms and as Saratoga's pointed out, the device will be recogzined or not. So no "noise" is supposed to be generated from that.