I have proposal for adding new variable that would be used for title formatting - for example on window title or status bar. It is related to current ReplayGain mode (something like %replaygain_current_gain_mode%). It is essential especially when ReplayGain's "Source mode" is set to "by playback order". Sometimes volume effects are so strange to me, that I am not sure what RG mode foobar is applying at the moment. It would be also useful for those who set album/tack or none values, but they tend to change them occasionally or have keyboard shortcuts for various RG modes.
That small thingy, together with possibility to enable in status bar information about how many tracks is selected on playlist ("Show number of selected tracks", similarly to the currently present option "Show total time of selection") are for me 2 most sought after features in foobar. The rest of app is almost perfect
Additionally - I couldn't find clear information - what is exact mapping of RG modes to certain playback orders when RG mode is set to "by playback order"? Was this mentioned anywhere?
Probably it is only mine situation - but I suppose it is better to mention this in case someone will accidentally start having the same situation. I encountered so many nonsense problems in Windows 10, that I have never heard of when I used even Windows 8/8.1 so I am very cautious about Win 10 and I totally disbelief in its robustness. That's just my experience...
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.Do you remember what you didn't like about them?
I'll surely try bigger brands too if I'm not satisfied with the Xiaomi I've just bought (waiting for arrival) or if I find a (better) conclusive model in the meantime.
I'm quite inexperienced regarding in-ear, slightly more experienced about on-ear headphones as I've tried/used various brands like: AKG, Sennheiser, Koss.
Did you check that link I sent you? They have good headphones for all prices.Sure, looks like theheadphonelist provides an updated and searchable list of the same kind. I've briefly visited Head-Fi and Reddit too (for opinions).
It's been a while since I've used Audacity but I tried out what happens when I normalize the whole album to -1.0dB to give some headroom (only normalize ticked, dither off), export it in original quality and then use SoX to downsample.
It seems to have eliminated any clipping, plus the volume difference I get when I use the guard option. Is this a recommended way to avoid clipping after resampling?
Does "sox INFO gain: 0.534dB not reclaimed" mean that you lose half a dB and potentially go from 16 bits resolution to 15.9 bits resolution? Not sure if I would bother ;-)
I went back to check the clipping part in that track and it seems that a nasty vinyl click clipped, but I can't hear the clipping itself.
Do you think it's better to ignore the reported clipping if I listen to it and can't hear it? That would save me the hassle of normalizing in Audacity, or letting SoX turn down the volume of a single track by half dB, potentially interrupting the flow of the album volume-wise, but I don't know if ignoring it can cause me more trouble in the future, for example when I want to convert to mp3 for portable use.
That is not a generic problem, EpicForever. There are plenty of people with Office who have absolutely no problems. For example I have two such machines and foobar2000 doesn't crash.
OK, that makes sense, thanks!
This component has never ran on XP. Older versions with support for IE7/IE8 still required Vista or above.
The component it was based on (WSH panel mod) still runs on XP because it hasn't been updated since 2012...
@citriodorus : don't be surprised if after fixing your issue with "MacType" under Windows 10 you will encounter another problem - if you use MS Office 2013/2016. My parallel Win 10 installation provided me with foobar's crash after I was opening window to pick destination for saving files from Converter component. What was causing that? Office's "grooveex.dll" file. located in :
C:\Program Files\Microsoft Office\root\VFS\ProgramFilesX86\Microsoft Office\Office16\ (on my 64bit OS, with my Office 2016).
To fix this I had to rename / delete this dll, to avoid it being loaded by either foobar or Explorer. But after every Office update file was recreated . And crashes occurred again. Now I'm on Win 7 and don't plan to run Win 10 for longer time...
Windows 10 and its updates at their best...
Any chance of a non SSE2 build?
I thought maybe version 1.1.0 might work, but sadly, the author has removed all binaries on Github earlier than version 1.2.4.
Edit - I'm trying to run this on a XP machine. Saw in the changelog that 1.3.0 drops IE8/IE7/WINE support. So I tried 1.2.4 and got the same error. It's SSE2 related. Wish I knew how to compile it so I could try to do so with SSE2 requirement disabled.