Problem was noticed for sure after several hours of using foobar. It v 1.3.17 there was no problem even right after starting the app.
And now some confusion (mainly for me) - I updated back to 1.4 b11 and for example right now I can rename whatever I want - there is no problem with hooks, Unlocker doesn't show anything strange. I can't explain that. Components... well, there is a lot of them here...
I will keep my eyes open and report back if this occur again and/or if I find the reason.
To this point I have been analyzing each file manually in Audacity and downsampling it to 22050 if there is not a significant amount of information above 11KHz. However, as I have become more ambitious I have begun working with more and more files. My current project has a little under 60, my next one is likely to have hundreds.
Given that I am really not looking forward to manually analyzing hundreds of files, I'm wondering if there is a tool that will do this automatically. Even something that could compare two spectrum analyses and discard one of them would do it (since I could downsample everything and then ask it to decide if the new file sounds the same as the old one). Any thoughts?
Agreed, if more than one listening seat is involved.It has nothing to do with seats and everything to do with mono (one sub) having zero chance of reproducing inter-aural spatial effects/lateralisation etc, as has been covered many times here, including many AES links by your truly. Einstein rules of insanity applies.By what metric(s)?All. Nearfield = zero modal problems at seat. Nothing to "correct" (and/or "incorrect" elsewhere).
Only issue might be phase due to propagation delay vs the mains, but the lower you cross, the less that matters as the low pass filter of the sub will automatically introduce a delay...and it will all appear in the frequency domain at given crossover, so easily measured (though not necessarily heard, depending on Q of any notch).
Please read, there are links to over 40 studies compiled https://secure.aes.org/forum/pubs/conferences/?elib=17270
We can consider two questions: whether one sub in a system is better than none, or whether multiple subs are better than one. An auxiliary issue would be, are the main speakers 'full range' or not?
The 2006 Wilson/Meridian review that you cite considers the literature of multiple subwoofers versus one (and to a degree, full range mains versus limited mains). It doesn't really consider none vs one, which was something I addressed above. The OP thinks 1 sub in a stereo setup 'sounds wrong' but I would say it's likely better than no sub, given that it offers more flexibility in locating the LF source (that said, the OP's personal situation appears to preclude most locations, and it could be that his limited placement options 'sound wrong', but many factors could be in play ) . I don't question that multiple are able to offer better sound than one.
The paper reviewed what we knew in 2006 about how to provide uniform bass across a listening area (i.e., taming modal issues) and how to provide low-frequency spatial information ('stereo bass' -- i.e, a system where subs are receiving different signals). I don't see in it a recommendation for nearfield subwoofer placement. It does favor multiple subs for addressing both issue -- at least two to allow 'presentation of spatial information' . If anything , the review appears to find the most promise in a system with 5 full-range loudspeakers + DSP.
It is however unclear to me from that review whether 'stereo bass' matters in typical-sized consumer rooms. It's not something that gets cited a lot as a 'must have', even now 12 years later. (For decades during the analog era, bass was 'summed to mono' in commercial releases anyway. ) If it *is* a goal, then we need at least two LF sources and they need to have some left-right side-to-side separation. I certainly don't dispute that. But I'm honestly not sure I have ever really experienced 'stereo bass' in a home setup. I'm curious to do so.
I haven't read all the cited references, except for the Welti/Harman-originated ones I'm familiar with from years ago.
Is the M: drive some special network share? I have only tested with local NTFS volumes.
I don't understand why there should be a compilation error, particularly as the amazon-audiobooks-com.boo script doesn't have PageEncoding anywhere in it.Thanks. I now had a look an the script and there was PageEcoding in it.
During install of 1.,03 I had not checked this script and there must been an older script with PageEcoding that remained in the folder.
After checking the scripts to install all is fine.