Hi SwissBear,
Is it consistent (always happen with a given path name)?
Can you reproduce it at will?
Does it also happen when dropping settings files?
Does the "save to clipboard" / "load from clipboard" functionality work for you?
Is it consistent (always happen with a given path name)?
Can you reproduce it at will?
Does it also happen when dropping settings files?
Does the "save to clipboard" / "load from clipboard" functionality work for you?
Pos,
It's been happening since the new version. But I have not rebooted my laptop since then. I will do that to avoid you loosing time on this issue. I will report if the issue remains.
Thanks.
It's been happening since the new version. But I have not rebooted my laptop since then. I will do that to avoid you loosing time on this issue. I will report if the issue remains.
Thanks.
Wait, I will send you a test version with a beefed up clipboard system.
Even if rebooting your computer could resolve the problem (but I doubt it, albeit I don't know the innards of that clipboard implementation...), your system as it is now is probably a good test bed.
Even if rebooting your computer could resolve the problem (but I doubt it, albeit I don't know the innards of that clipboard implementation...), your system as it is now is probably a good test bed.
rePhase 1.1.1 is out: http://sourceforge.net/projects/rephase/
It should correct the bugs found in the recently released version 1.1.0 🙄
It should correct the bugs found in the recently released version 1.1.0 🙄
Code:
1.1.1 2016-10-29
New features:
- added a 64 bit IEEE-754 output format to accommodate BruteFIR:
[url]http://tinyurl.com/htqvln8[/url]
Bug corrections:
- fader focus bug solved: [url]http://tinyurl.com/ztbp7cl[/url]
- beefed-up clipboard handling to avoid bugs when loading measurements
by dragging them over the interface: [url]http://tinyurl.com/jygt7jx[/url]
- removed the final optimization step that was recently added in
version 1.1.0 as it had some ill side effects in specific scenarios
Adjustments:
- renamed measurement "compensate" function to "invert" to avoid
confusions: [url]http://tinyurl.com/j76wm5w[/url]
- reworked focus and entries editing in paragraphic EQ tabs:
* using the tab key now goes from one entry to the other as
expected, making it faster to edit multiple EQ points in a row
* clicking on an entry does select the entire content for ease of
editing
* middle click or double left click on the dB/° entry used to reset
the value to 0. This is now gone, but the same result can still
be achieved with a middle click on the fader
- internal DPI scaling adjustments
Last edited:
@pos
Great!
But I saved the 64 bit setting with the RC and you changed the file suffix to "dbl". Now my projects don't load anymore (error message that the output file format doesn't exist). Is there a way to get around this?
Great!
But I saved the 64 bit setting with the RC and you changed the file suffix to "dbl". Now my projects don't load anymore (error message that the output file format doesn't exist). Is there a way to get around this?
Hello John, nice to see you here 🙂
The ideal scenario would be 17 EQ points of constant Q type (same as DCX2496) with arbitrary resolution frequency (might get converted internationally, but is no less that 0.1Hz in the audio range), arbitrary resolution Q value, and almost arbitrary range (graphical limitation is +/- 96dB, which is already impracticable for this EQ type anyway).
Is the output format fixed? If not then a JSON object would be ideal, but I can of course parse the standard format.
This would be excellent! 
rePhase EQ settings in REW would be a sweet option. Hope you can make it happen.
rePhase EQ settings in REW would be a sweet option. Hope you can make it happen.
Hi SwissBear,
Thinking more about it, rather than showing an automatically guesstimated minimum-phase curve, I could include an impulse and step response graph to be able to judge these things directly...
One more thing added to the todo list 😀
Nice, I'll try to implement it as soon as it is out, most probably using the text format 🙂
Gain precision can go up to 0.01 dB by the way, if that matters
Gain precision can go up to 0.01 dB by the way, if that matters
Hi Pos,
Having thought again, I believe you might not have to do that.
If, instead of adjusting the phase to zero at Nyquist inside rePhase, I do it inside REW prior to exporting the measurement, the adjustment of the phase with the minimal phase in rePhase/REW is much easier, as the convolution inside REW is applied to a shifted measurement.
So no need to spend time at least for this usage.
Thanks 😊
Hi SwissBear,
Playing with time offset in rephase or REW should normally bring the exact same result.
If you do it in rephase then of course when reimporting the FIR into REW you will have a delay. But why are you reimporting the FIR into REW?
rePhase should accurately show you the effect of the convolution of the FIR on the measurement(s) you load. Is it that you want to see the resulting impulse and step response in REW?
By the way, just to make things clear(er), when shouting for a 0-ish phase response at Nyquist (and ignoring any rapid phase change up there, due to either breakups of early low pass), you are in essence "erasing" most of the phase shift of the system's low pass.
This makes correction easier but is not fully correct, and if you use phase EQ to really flatten any phase deviation up high you will surely get preringing.
That is why I advised to only play with phase EQ around the actual crossover (not only filter) points, and only as a complement to proper "filters linearization".
In reality a perfectly time-aligned textbook crossover should not need any phase EQ beside these "filters linearizarion" things. This is for example the case with the JBL M2 where phase linearization in the passband is just a matter of adding the inverse allpass of a 36dB/oct LR filter at 750Hz.
Of course passive systems are a different story, most of the time, and will require additional phase EQ to compensate for the compromises used to build a (mostly-)phase-coherent crossover.
Playing with time offset in rephase or REW should normally bring the exact same result.
If you do it in rephase then of course when reimporting the FIR into REW you will have a delay. But why are you reimporting the FIR into REW?
rePhase should accurately show you the effect of the convolution of the FIR on the measurement(s) you load. Is it that you want to see the resulting impulse and step response in REW?
By the way, just to make things clear(er), when shouting for a 0-ish phase response at Nyquist (and ignoring any rapid phase change up there, due to either breakups of early low pass), you are in essence "erasing" most of the phase shift of the system's low pass.
This makes correction easier but is not fully correct, and if you use phase EQ to really flatten any phase deviation up high you will surely get preringing.
That is why I advised to only play with phase EQ around the actual crossover (not only filter) points, and only as a complement to proper "filters linearization".
In reality a perfectly time-aligned textbook crossover should not need any phase EQ beside these "filters linearizarion" things. This is for example the case with the JBL M2 where phase linearization in the passband is just a matter of adding the inverse allpass of a 36dB/oct LR filter at 750Hz.
Of course passive systems are a different story, most of the time, and will require additional phase EQ to compensate for the compromises used to build a (mostly-)phase-coherent crossover.
Last edited: