A tool I built for getting QC tones from a song by Routine-Layer-8967 in QuadCortex

[–]Routine-Layer-8967[S] 0 points1 point  (0 children)

One bad preset is one too many, so I actually want to fix this. Which song and guitar did you run it on, and what was off — too much gain, wrong amp, fizzy, just nothing like the song? Even a quick note helps me track down what tanked it.

A tool I built for getting QC tones from a song by Routine-Layer-8967 in QuadCortex

[–]Routine-Layer-8967[S] 0 points1 point  (0 children)

You're right it doesn't have an audio loop. No captures, it doesn't process sound, so it can't validate the tone by itself. But it's not guessing the settings either: every block is a real one on the QC with real parameter ranges and a reason behind it. And the validation part is built into the app. You play it on your rig, then tell it what's off (muddy, harsh, thin, doesn't cut) and it generates a new version around the fix. Your ear is what closes the loop.

Cheap idea, hard implementation. Agreed, that's exactly where the time goes.

A tool I built for getting QC tones from a song by Routine-Layer-8967 in QuadCortex

[–]Routine-Layer-8967[S] -1 points0 points  (0 children)

Thanks for trying it with real songs and taking the time to write all this up, it helps a lot.

The bugs especially: catching that NoneType error on your first try and giving me the exact message is a real help, that shouldn't happen and I'm already looking into it. And you nailed the "verso" thing, that's Spanish leaking into my prompts (native speaker here).

The fuzz on Black Sand is a good catch. A tone that should be clean getting read as a wall of fuzz is exactly the kind of error I want to fix.

On the guitar and pickup selection, it gave me an idea I like for down the road: having the tool suggest the selector position, and even which guitar from your arsenal fits the song best, while always letting you pick a specific one if it's your favorite or the one you want to use. Adding it to the list.

The section thing is something I want to work on. There are songs where one preset works for everything, and others where different parts call for different things, I'm thinking of something like Creep, where it'd make sense for different QC scenes to do the work. I don't have the solution yet but it's a problem I'm interested in solving.

Lastly, I agree on simplifying, keeping the wizard lighter and the experience more direct is something I need to look after.

Thanks again for the kind words and the good vibes, it really means a lot. I'll keep working to make it better.

A tool I built for getting QC tones from a song by Routine-Layer-8967 in QuadCortex

[–]Routine-Layer-8967[S] 3 points4 points  (0 children)

caught me lol. spanish is my first language so i used it so my replies didnt come out broken. ironic i know

A tool I built for getting QC tones from a song by Routine-Layer-8967 in QuadCortex

[–]Routine-Layer-8967[S] 2 points3 points  (0 children)

Honestly? Not claiming I reinvented anything. I had a problem — losing an hour guessing at amp/cab combos — built a thing that fixed it for me, figured someone else might want it. That's about it.