![]() In fact you can argue against overly long FIRs for they allow you to do slopes so sharp you'll get audible pre-ringing. Anyway if double clicking to delete is a problem maybe I could use another way? How do other EQs do it?Īs for FIRs, length should have little to do with sound quality if done right, at least with linear phase. Photosounder SplineEQ | Tech Reviews | MusicRadarĪnyone else found this?That's weird, could be a Mac thing? I haven't been able to get much unwanted double clicks on Windows. Re clicks Im pretty sure its picking them up correctly.I also read in musicradar cons did say 'to easy to accidentally deactivate clicks' so Im not sure if they experienced the same thing. You shouldn't be able to do that with a single click (all the code for that is in the callback function that only gets called when a double click is detected), but given that this is a trackpad you probably get accidental double clicks?cool that sounds great with the scale I'll make the knob be like some of the other knobs (Resolution, Delay, Visualisation Gain, etc.) that remember their value at every session (although I recently realised that it probably doesn't work on most Macs because users don't have permission to write where I want to write the preferences file, I'll fix that in the next minor version by writing it in the appropriate place), so everytime you open it it will be the last value you set, but if you used different values in a saved project it will save the correct value. You shouldn't be able to do that with a single click (all the code for that is in the callback function that only gets called when a double click is detected), but given that this is a trackpad you probably get accidental double clicks? It seems like something to do with the spacing/timing of adjacent clicks.single clicks with a reasonable spacing it senses as double clicks?I'll make the knob be like some of the other knobs (Resolution, Delay, Visualisation Gain, etc.) that remember their value at every session (although I recently realised that it probably doesn't work on most Macs because users don't have permission to write where I want to write the preferences file, I'll fix that in the next minor version by writing it in the appropriate place), so everytime you open it it will be the last value you set, but if you used different values in a saved project it will save the correct value. It seems like something to do with the spacing/timing of adjacent clicks.single clicks with a reasonable spacing it senses as double clicks? Im demoing on a Macbook Pro using the trackpad - but there are times where a band appears after a double click, and times where I can make a band with a single click (tap).similar with deleting a band. Re the view - would it be possible to have the option to set the default range so for example the second marker was 6db.so each time you open it opens in a specified range? As for the way to turn bands on and off you double click to create, double click an existing band to delete it, is there a problem with that?that makes sense. ![]() ![]() I'll add a zoom knob in v1.1 (the one that's coming soonish right after I'm done with finishing that other project) which will allow you to reduce the dB range. I think that at 1024 (or maybe a bit more) at 96k it might be okay for you. I see, that's about 5.3 ms, and since it's 96k it might take longer to generate the filter, so that makes sense (it also depends on your machine's speed). Maybe the solution is just to ensure that that buffer is never too small. I guess I could try to make the transition not depend on that, but it's going to be much more complicated to do transitions over more than one buffer, plus you might have to transition between more than two states (let's say you have a band moving in the middle of a transition, you need to transition that too, for each state to transition between you need a convolution for each). I think that turning up the Delay knob might fix it too. Last time I heard someone having that problem their host had a buffer size of 64, it went away when they turned it up to 512. ![]() I like this EQ - but I assume it clicks audio slightly when changing the shape because its linear phase? Can this be improved?No it seems it has to do with my choice of making the smooth transition between one state of the EQ to the next happen within a single buffer (SplineEQ's own internal buffer that is, which is something yet different from the in/out buffers it gets, because of fast convolution).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |