GraphWorks EQ Changelog, Feedback and Feature Request Thread

Please use this forum thread to submit feature requests and general feedback regarding GraphWorks EQ!

PLEASE DO NOT SUBMIT BUG REPORTS HERE! Use the in-app bug report feature instead as that sends logs!

We are actively working to make this the best available EQ tool, and so any feedback or suggestions are very welcome.

The changelog can also be found on the website here: GraphWorks EQ changelog | GraphWorks

LATEST UPDATE:

2 Likes

1.2.27 changelog:

Hi, guys. Thanks for making this tool. It’s certainly something that I’ll be using. The price is very reasonable too!

I do have a suggestion for a potential feature request. I’m not sure if this is within the scope of the app but obviously that’s up to the team.

  • ISO 226 equal loudness contours.

This is something I have implemented on my Windows PC via EqualizerAPO so I wouldn’t be able to keep using my method of level-aware dynamic phon curve compensation alongside the Graphworks virtual audio device. If this is accepted then the end user needs to be able to set their reference level in dB SPL so the correct cuts and boosts can be applied as they adjust gain.

For anyone interested, the way I’m doing this via EqualizerAPO is with a Python script that generates 100 peq txt profiles that I switch through using an AHKv2 script tied to a rotary encode on my keyboard. It’s volume aware since each profile also acts like a gain adjustment with the required phon adjustment built in.

I’ll happily share my work with the team if interested.

Are you guys considering a Linux version as well?

A linux version is planned yep! This will be in a month or two though. Main reason being that each platform means every update requires extra work, and so in the initial period where I’m working on feedback, bug reports etc now that it’s out in people’s hands, I wouldn’t be able to handle three platforms given the current volume of updates likely to occur in the first couple weeks.
Once the initial rush of changes slows down it’ll be fine, and at that point Linux version will be released too. (I do actually have a linux version working already, but it’s currently several versions behind the mac/windows ones)

Hello, it is not a bug that I report, but I am not sure if you use the correct “Pad description” for the Meze Empyrean II. It normally comes with two pad versions, the angled alcantara pads and the duo pads. Resolves measurements uses the term hybrid pads. These are the pads that normally come along with the Meze Elite. Did you really use these pads on the Empyrean II for the measurements or did you mean the duo pads?

1 Like

Thanks! I’ll fix that right now. Feel free to let me know if you catch any other labeling mishaps.

New update is out with a few fixes, but importantly: Built-in bug reporting.
Just click the bug icon and you can describe your issue, it’ll send us the message and your logs so we can get it sorted faster!

Does GraphWorks EQ down-res high-resolution signals such as 24/192 or DSD?

Is there a way to import measurements directly from a Squiglink URL?

Yesterday I found a measurement for the Hifiman Mini Shangri-La I wanted to use there and I didn’t see any export button. I would be super-cool if I could just give Graphworks EQ the URL. I know this may not be very easy to do.

Currently GraphWorks accepts up to 192khz input, but this will be increased to 768khz soon. (I wanted to have a week or two of it being out so I can tackle any bugs that popped up before enabling that).
DSD is not supported at present. DSD cannot be EQ’ed anyway since it’s 1-bit, so it would need to be converted to PCM first.

I could possibly look at adding a DSD to PCM conversion stage on the input, but I’d generally recommend for now that people just convert to PCM in their player first since if you’re EQ’ing it’s not possible to stay in DSD end to end no matter what

1 Like

Not at present.
This could be a fairly easy addition, BUT, I’d need to check with @listener and @Resolve as well as the terms of the various squig link sites. If a squiglink site has no export button then it’s reasonable to assume they do not want their measurements traced or otherwise exported and I wouldn’t want to go around that.

1 Like

I was under the impression that Graphworks EQ can export impulse responses, but all I could find is a way to import convolution files. So I asked Claude to make me a utility to do that, namely take the text file with PEQ parameters and generate .wav files for convolution. Here is the result.

You could incorporate similar functionality in the Graphworks EQ. If you wanted to play with the webpage you can grab it from here: https://drive.google.com/file/d/1mBZCwgdB3byZjols7b342uKzgSS00LpO/view?usp=drive_link

2 Likes

Convolution/impulse export is something I could add. It’s just a bit niche since there are few situations where you have to do DSP through something that supports convolution but not regular EQ.

It’s not perfect but Gemini can covert a screenshot of a graph to a FR txt file :slight_smile:. Close enough for EQ building.

1 Like

There’s also UsyTrace

On macOS when I put on (in?) my Airpods, the System Output automagically switches to the Airpods. If the System Output is Graphworks EQ this doesn’t work.

Could you submit a bug report in-app so I can have a look at the logs?

1 Like