Excellent! I assumed I was the only one "challenged" in this arena....
When I drop a flac on the SpecWeb Play icon it does open a tab in MS Edge, but then I get a message almost immediately that the file "finished processing" and Edge asks if I want to close my tab. Whether I choose yes or no it closes the tab. Now playing of the file or adjusting of knobs is allowed.
This is an HDTrack 24/96
-pmicrosoft-edge:http://localhost:7681
When I drop a flac on the SpecWeb Play icon it does open a tab in MS Edge, but then I get a message almost immediately that the file "finished processing" and Edge asks if I want to close my tab. Whether I choose yes or no it closes the tab. Now playing of the file or adjusting of knobs is allowed.
This is an HDTrack 24/96
I had a similar "swishy" sort of sound from cymbals in the rear channels when using a "24x192" HDtracks album ("Candy-O" by The Cars, the first song "Let's Go"). Honestly, I really don't even know what 24x192 means, but is there something I can do to prevent this? Do I need to "downsample" the tracks? I'm a dummy, so simple, step by step instructions are best!
I think I'm going write a small app to help with resampling up and converting to 24bit, surround conversion using SpecWeb, retagging (add '(upmix)' to the tagged album title), rename the files without 'MCH', copy to a new folder and resample down to either 96 or 88.2kHz, whatever is the best based on original sample rate. A one click, but long wait, solution.
When I drop a flac on the SpecWeb Play icon it does open a tab in MS Edge, but then I get a message almost immediately that the file "finished processing" and Edge asks if I want to close my tab. Whether I choose yes or no it closes the tab. Now playing of the file or adjusting of knobs is allowed.
This is an HDTrack 24/96
Thanks for trying to help... I've found that every 24x192 track that I run through SpecWeb sounds bad. The 24x96 files sound great, though...Can you be more specific about how to "change the fft size in the ini file" ( I don't know what any of these terms mean or how to accomplish your recommendation... Just an average music fan... But if your suggestion will make these files sound good, I'd love to try it!) Do I have to make changes every time depending on the type of source file?See my post above regarding setting the fft size setting in the ini file
Thanks for trying to help... I've found that every 24x192 track that I run through SpecWeb sounds bad. The 24x96 files sound great, though...Can you be more specific about how to "change the fft size in the ini file" ( I don't know what any of these terms mean or how to accomplish your recommendation... Just an average music fan... But if your suggestion will make these files sound good, I'd love to try it!) Do I have to make changes every time depending on the type of source file?
Edit: OK, I think this might be what I do: should I type "-N32768" in the command line before I start processing?
Edit the SpecWeb.ini file in your Specweb folder. Find the [fft] line. Just below that is Size - change that value to 32768.
Thank you! I tried it by manually entering in the command line before processing, and the output file sounded great! If I edit the SpecWeb.ini file, will this change the default fft setting so I no longer have to change it each time?
Re: the helper; setting the output back to the original sample rate isn't working for me. I end up with file at 176400 sample rate. Is there a log file somewhere that would show errors?
By the way, 2x upsample should be plenty. 44.1 to 88.2, 48 to 96, etc. Going higher might not yield the best results, especially given the FFT size and overlap limitations in SpecWeb.
Also, you might consider Eac3to as a resampler, in order to get the Ssrc re-sampling lib. It's supposed to be the "best". If you have AudioMuxer installed you already have Eac3to in your AudioMuxer Roaming Profile.
Enter your email address to join: