Finally I decoded QS recordings with Adobe Audition

QuadraphonicQuad

Help Support QuadraphonicQuad:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Lucanu said:
Now that I can make a comparison btw pc and sansui I still actually prefer pc.
But that's my modest opinion. ;)

Wow! :eek:
 
Lucanu said:
You must have a C:\qs folder where to put the sample you have then save it to front.wav and rear.wav.
The script must be into the AA1.5 script folder.

This is the script I want to share with you.

I downloaded your .zip file, saved the file as front.wav and rear.wav at c:\.. When I try to run the script it says something like 'script only works on entire loaded waveform' then 'script stopped', when I tried opening front.wav and then running the script it just says 'script stopped'. I don't know much about these things, if you spot any errors I have made please let me know. Thanks for your effort on this script, I picked up a couple of QS classical titles at a garage sale recently - just something to play with.
 
Thanks Lucanu. I don't even want to tell you what I did wrong... I had the files in c:\sq instead of c:\qs d'oh!!
 
I did some tests with my QS encoded Grass Roots LP last night and came up with some VERY good results. I only have a Lafayette SQ-W and it gave a good "feel" in the QS setting but was hardly discrete.

Ran the song Temptation Eyes thru the QS script and it was so clean, it was almost as discrete as the Q8 version!! Very well done!! Even more impressed than the SQ decoder! Good job! (y) (y) :phones
 
I just ran side one of the Four Tops "Main Street People" through your decoding script, and it's pretty good!

I think you would get much better sound if you were to bump up the resolution (FFT size) quite a bit in the Center Channel Extractor. 8192 FFT just isn't enough to avoid watery sounds.

I typically use 16384 as a FFT size (with a higher number of Overlays.) This requires much more processing power, but I think it really improves the sound in a big way.
 
Yes you can do it. And for my personal experimentation I forgot to better the settings.
I did my experimentation without a good sample, so I did not get much difference.
If you wish to create your own settings for this script you can edit the file and change the 8192 value to 16384 in the script,
or (this is in case you don't feel safe in editing) select the confirmation message during the script.

Thanks again, I really appreciate your feedback.
 
I am very intrigued by this whole subject and look forward to hearing some of the results.

Have any of you techy types ever considered doing a similar thing for CD-4?

Even considering how bad many American pressings were, I feel certain that some form of software decoding -- including selective filtering of distortion-prone frequencies -- should be able to significantly improve on a 35-year old mass-produced consumer unit.
 
I have been playing with the plug-in a bit in the past few days. I find the seperation to be excellent. However, I find the sound quality to be watery, I don't think we're quite there yet. I'd like to tweak the settings and get rid of the watery sound. The thing is, I can't seem to find which settings it is that effect the sound. Does anyone else here that has been experimenting with this know what settings effect what in what way and what in particular will effect how watery things sound? Any detailed info people have found playing with these settings will greatly help me tweak these setting to perfection.
 
ArmyOfQuad said:
I have been playing with the plug-in a bit in the past few days. I find the seperation to be excellent. However, I find the sound quality to be watery, I don't think we're quite there yet. I'd like to tweak the settings and get rid of the watery sound. The thing is, I can't seem to find which settings it is that effect the sound. Does anyone else here that has been experimenting with this know what settings effect what in what way and what in particular will effect how watery things sound? Any detailed info people have found playing with these settings will greatly help me tweak these setting to perfection.
The watery sound can be attributed to the FFT size in the center channel extractor. If you increase that number it should sound better.

If Lucanu doesn't mind, I could update his script with different values that might make it sound better.
 
Here is a script that does more or less what Lucanu's does. It's optimized with different default settings that should make it sound better. It also runs quicker, as I decided not to run the filter as many times as Lucanu's script calls for.

Rename the .txt file to a .scp and let Audition do the rest.

Remember to have the files located in the c:\QS\ directory and to have them named "Front.wav" and "Rear.wav"!

EDIT: Use the Script I have posted below
 
Last edited:
HearToTemptYou said:
Here is a script that does more or less what Lucanu's does. It's optimized with different default settings that should make it sound better. It also runs quicker, as I decided not to run the filter as many times as Lucanu's script calls for.

Rename the .txt file to a .scp and let Audition do the rest.

Remember to have the files located in the c:\QS\ directory and to have them named "Front.wav" and "Rear.wav"!

When I run the script, it seems to highlight the first 20 minutes or so. The it highlights other parts. Is this normal? Does the highlighted part actually matter or is the whole file being decoded? My full file length is about 40 minutes.
 
What does the "selected" line do? Also, in Dylan's script it says SR 48000. I assume that that means 48k as in 48k, 44.1k, 96k. My files were originally in 96k. I can't really tell if there is a problem or not for sure.
 
Bob Romano said:
When I run the script, it seems to highlight the first 20 minutes or so. The it highlights other parts. Is this normal? Does the highlighted part actually matter or is the whole file being decoded? My full file length is about 40 minutes.
I thought I had set it to "Select all" when I did the script. I probably didn't need to do that. That might have caused the problem.

I'll see if I can correct it.

The file(s) I built the script with were at a 48K sample rate, but it shouldn't make a difference with whatever files you choose to use, so long as they are named "Front" and "Rear" and in the right place.

I'll see if I can correct the script for the other bug though.
 
I believe I corrected the bug.

Here's a second try. Like before, rename the file to .scp.

EDIT: Use the script I posted below.
 
Last edited:
Back
Top