Thank you, @pkane , it is working for me now! (I'm too tired to run through the test tonight, but I verified that v1.0.4 works on my computer.)
I see but on my i5 6600K, with all the possible instructions sets available, was struggling while on the Celeron N4100 with very low performance and limited istructions sets available all went smooth.Good to hear, @Hugo9000 ! Thanks for testing. I speeded up signal generation by about 3x compared to the previous version, mostly by eliminating a lot of floating point computations. My suspicion is that the large number of floating point computations was causing the slow-down with older processors, or ones without a floating point co-processor.
I see but on my i5 6600K, with all the possible instructions sets available, was struggling while on the Celeron N4100 with very low performance and limited istructions sets available all went smooth.
I encountered another issues: when moving the slider from-to the last 3/2 points it reset the values back to -60 (or -70 when I set the lowest value/Start vol to -120). Once happend that when I loaded my results and moving the slider throguh the data, it all went back to the value I set on the Start vol.
Back on my measurements for some reasons it set the dB SPL improperly (it happened often) in my first try so I check it again; looking at the ISO curve too to be sure I could have negative values too, and at around 1100Hz I now have a value of -9 dB SPL indeed.
Here is the RTA of my IEMs on the UMIK-1 while pushing the foam tip on the mic for a proper sealing:
View attachment 74944
Here is what I do: I open Earful (it sets the default settings, max vol -20dBFS, min vol -60dBFS and -0,5 vol step), then load my curve and because of the default settings (max volume at -60dBFS) the last two datas have a different value (which is not -60dBFS tho but -20dBFS), so I adjust the max volume to 0dBFS and I go through the data with the slider and when I reach the last two data points they just and go on a random valume (in my case something like -37dBFS) and if you then change them again to 0dBFS and go back on the third to last and move to the second to to last it will go back down again. It also happens something similar if you just adjust the max volume before loading my data (with 0dBFS on the last two points; and with this I mean the 31th and 32th points, with the default settings of 32 points) then load it and go throught all the data til the last two points and they somehow will just go down to a different value (same edit: It displays the 0dBFS correctly but when you reach the position it just go lower, at -37dBFS in my case).Not sure I understand how to reproduce this. Can you please describe the sequence, one step at a time?
Yes, I was going to tell you that. I kept seeing number of threads going up and down while playing audio on Earful with WASAPI output.BTW, I just noticed that the audio library I'm using is creating more threads than I expected when playing using WASAPI. These threads are not using any CPU when I look at them (all sleeping) but their number keeps growing. I'll investigate, perhaps this is what's causing the excessive CPU consumption on different hardware.
Here is what I do: I open Earful (it sets the default settings, max vol -20dBFS, min vol -60dBFS and -0,5 vol step), then load my curve and because of the default settings (max volume at -60dBFS) the last two datas have a different value (which is not -60dBFS tho but -20dBFS), so I adjust the max volume to 0dBFS and I go through the data with the slider and when I reach the last two data points they just and go on a random valume (in my case something like -37dBFS) and if you then change them again to 0dBFS and go back on the third to last and move to the second to to last it will go back down again. It also happens something similar if you just adjust the max volume before loading my data (with 0dBFS on the last two points; and with this I mean the 31th and 32th points, with the default settings of 32 points) then load it and go throught all the data til the last two points and they somehow will just go down to a different value (same edit: It displays the 0dBFS correctly but when you reach the position it just go lower, at -37dBFS in my case).
EDIT: and sometimes the Clear All button doesn't clear all the datas properly (mainly on the first point).
Yes, I was going to tell you that. I kept seeing number of threads going up and down while playing audio on Earful with WASAPI output.
Yes indeed but the issues is after adjusting the max vol and trying to get them back to 0dBFS.Got it! The data does get clipped when loading against the maximum volume setting to avoid exceeding it. I'll see if I can fix it so it gets properly displayed when you increase the the max setting. For now, you'll have to reload the data after adjusting maximum volume, assuming it was previously clipped.
Let's blow some woofersThe first data point after clearing data is set to the current volume on the volume slider. I'll fix this, as that's probably not what you'd expect, especially if you have a large subwoofer and the volume setting happened to be at 0dBFS
I found the issue with the extra threads. That's fixed now. I'll upload the updated version soon. Hope it resolves the performance issue with your tower computer.
Again, thanks a lot for all the testing and bug reporting!
Just downloaded and have to report I still have problems with the data points/slider like before.
if you have cleared all the data and set one of the points and go back or forward then all the data points will be set to the one you firstly set
That's already in v1.0.5. Only one thread is created for audio playback at any time. This was fixed with an update to the latest version of the audio library.[/QUOTE]Looking forward for the threads fix by the way.
This version puts my CPU below 1%, so that's a huge improvement for me!
Although I had clicked "Clear All" before I closed it last, it opened with the curves from my last session, but moved the 20 Hz point back down to the starting volume of -60 dB (that's how it's intended to work, yes?).
(I'm only 51, so who knows how much my hearing will deteriorate in the next few years.
My bad for not explaining myself properly. It is just about the datas on the graph that keep cheanging when it shoudln't .Which problem was this? The glitching? I'm thinking that one really has to do with your hardware/device driver combination. There's now no extra threads and the CPU utilization is so low as to be barely noticeable.
The clipping due to the change in maximum volume setting is not fixed in this version. It'll take some effort to fix due to how the maximum volume is implemented. I'll keep it on the to-do list, but it'll have to wait a bit until I'm ready to rewrite some of the internal logic.
It is related to the above. Try setting one in the middle and back or forward in a fast way yo the next/previous points and see what happens.Don't think I'm able to reproduce this. I clear the data, then set any of the points to say -20dB then move forward/backward and none of the other points change from the start volume setting (-60dB). Is there some step I'm missing?
I will look into it again then. I still have 33% CPU usage.That's already in v1.0.5. Only one thread is created for audio playback at any time. This was fixed with an update to the latest version of the audio library.
It is related to the above. Try setting one in the middle and back or forward in a fast way yo the next/previous points and see what happens.
Could it also be that I am on the comma version and some data is in decimals with a comma separator and not a point?
Both. The slider glitches and some points are untouched while with the arrows on the left all the points are set on the same value being firstly set (can't recall exacly now, my tower is shut down and I am about to go to sleep; didn't even finish to test my headphones cause I wanted to go for the 64 points).Nope, still can't make it happen. I even switched to comma as the decimal indicator. You're saying you have to go quickly between points? Do you use the slider or the arrows when this happens?
Both. The slider glitches and some points are untouched while with the arrows on the left all the points are set on the same value being firstly set (can't recall exacly now, my tower is shut down and I am about to go to sleep; didn't even finish to test my headphones cause I wanted to go for the 64 points).
Very important note tho. WASAPI exclusive or well, the option to tick and enable it, doesn't work. It says in shared mode. Just checked while playing a tone on your program and watching a YT video.