Release 1.216 is up. There’s not a lot of new features, but instead a lot of internal cleanup so be aware a lot has changed internally. Change list is at the link below.
1 Like
HAs anyone used this version and if so, have you found any bugs?
I’d like to install it but I’m not very comfortable with knowing that there’re might be quite a few bugs, according to Matt. 
I have used it for a bit and the only problem I have found, which has been around since previous releases, is that you get an exception error after running the Power THD vs Frequency plugin- after the first run, when you run it again at a different power level you will get the exception error at the completion of that run, but it will add the trace to the graph, so more of an annoyance.
1 Like
I’ve used it about ten times in the last few days. So far, I haven’t encountered any particular problems. Obviously, there may be bugs hidden in parts of the software that I haven’t used yet, but at the moment I haven’t noticed any particular anomalies in its operation.
1 Like
Hi @Var, you mean this error?
Hi @matt. I think @VAR was referring to the exception mentioned in this post. I must say that I also encounter this exception from time to time, as I mentioned in my post.
@matt- I was referring to error in the thread @Claudio referenced. If it will help, I can do a video of the problem.
I did a short video showing the error:
Hi @Var, I can’t repro this. Can you by chance setup a set of steps using loopback that will cause this to happen always? For example:
- Launch App
- File->New
- System in balanced loopback
- dBV->External Gain set to 6.02 dB
- Automated Tests->Pwr THD versus Frequency with following:
- Click OK and run test. Then I get
Resulting Plot:
Run again. This time changing to 2W. And I get this:
And then add to existing graph:
And the plot:
Does this work always for you?
Oh, I think I see it now: If the graph window is minimized (as you did in the video) when you try to add another plot, the error occurs…
Hi @matt. As I wrote in the previous post, the exception described by @VAR happens to me from time to time as well. I never identified the “trigger” that triggered the exception. I just completed 6 tests of the plug in: when the chart window is not minimized (3 tests), the test completes without any exception. However, when the graph is minimized (3 more tests) invariably there is the exception! I believe, matt, that you have identified the “trigger” 
@matt @Claudio- I hate to admit it, but I didn’t know anything about having the chart window minimized or maximized- I graph just pops up and I typically move it around and change the size by “dragging” the edges to fit into a screen recorder window. How do you set it for maximized plot windows ? I will repeat the test but am pretty certain I will come up with the same results as @Claudio
Hi @VAR. I noticed that the exception problem only occurs when the graph window is minimized, i.e., reduced to an icon (as @matt says). In other words, you don’t need to maximize the window to avoid the exception: any window size, as long as it is not minimized, does not cause the exception. To minimize the window, simply click on the “-” in the upper left corner of the window. In your video, at time 23 seconds, you minimize the window by pressing “-” and then the exception occurs!
This is fixed in the 1.217 test release in the link here: Max level/ headroom - #14 by matt
When the graph window is minimized, the graph width and height is zero, which is where the trouble originates.
Yes, @Var, you minimize the window as Claudio points out at 23 seconds. Not your fault, of course. But if you’d only shared the steps (and not the video) I’d not have caught it. So thanks for the time to make the video!
Thanks @matt . I did not realize the WINDOWS minimize tab was what was being referred to 
I will try this release as soon as I am able. A picture or video is worth a thousand words as the saying goes…
@matt- I just tried 1.217 and it gave me an abbreviated automated test menu which did not have the power vs Freq vs THD option:
Hi @VAR,
I’m not Matt but this is not a full release but rather a version where some specific requirement is being addressed. please take a look here.
Thanks for the explanation @peppermint!
1 Like
What is the general consensus with the 1.216 release? I’m still running 1.215 with no issues to speak of.
@restorer-john- I have been using it several times a week since it came out w/out any issues that I am aware of. Will be using it shortly on an old Marantz SS amp 
1 Like