User feedback thread for v1.0

[dlr]

Thanks, Jeff. The only issue is when trying to use tabs (or other controls) on a separate window without the complementary control on the main window in view. I'm sure it could be done better, but that's how it will be for now. Once you get used to the small quirks it's easy to work around them.

Dave

[Jeff S.]

Not sure what other controls you're talking about?

[dlr]

Not sure what other controls you're talking about?

Controls are the screen items such as data entry scrollers, textboxes, etc. Microsoft definition is "components with visual representation". Sorry to use confusing terms, it's more than data entry, but most of WinPCD is data entry or text displays and buttons.

Dave

[mgagneur]

Hi Dave,

I have been using your program and found it a real step in the right direction. Thanks for working on this.
I have a situation I'm not sure how to handle. I have a SB17 woofer and am mating it to a big AMT heil. I set the mic on the heil axis and measure, heil, sb17 and heil / sb17 together. To get the summed response to match the overlay measurement I need to tell WinPCD the heil is actually behind the woofer, which is true. My problem happens when I type in a value greater than 0.024 or so for a z offest for the woofer meaning, I think, the woofer is in front of the heil. When I get the offset right the overlay and summed response match very well, but as the value goes beyond 0.024 I get an error message of "Driver distance is longer than listening distance..." and the program does not appear to be really happy.

Making the woofer offset positive is the only way I have been able to get the summed response to match the actual measured overlay.

Thanks for the help.

Regards,

[dlr]

To get the summed response to match the overlay measurement I need to tell WinPCD the heil is actually behind the woofer, which is true. My problem happens when I type in a value greater than 0.024 or so for a z offest for the woofer meaning, I think, the woofer is in front of the heil. When I get the offset right the overlay and summed response match very well, but as the value goes beyond 0.024 I get an error message of "Driver distance is longer than listening distance..." and the program does not appear to be really happy.

Making the woofer offset positive is the only way I have been able to get the summed response to match the actual measured overlay.

Glad to hear you're using it. I appreciate the feedback.

The intent of the message was to notify a user that the reference (listening/mic) position was set at an incongruent position. For example, you could have the reference behind the front baffle if, say, you set the reference such that a driver was more forward, i.e., you can set the values to have a mic behind a driver. It was intended more as an aid against accidentally setting a physically unrealizable reference.

I've done some quick testing and have been able to reproduce it. I didn't test much with drivers in front. Nothing stops you from using it with any settings, but the notification popping up is a problem. I could simply eliminate the popup, I'll consider other ways to inform or simply drop it.

I'll check it out. Not sure just how quickly I can get a fix ready, I'll want to test it better than I did the first time. That is if I don't decide to drop the message altogether. I may switch to something like a control flashing briefly or similar. But obviously, the check itself isn't working correctly.

This will be important as I have plans (down the road) to add more off-axis capabilities such as displaying multiple off-axis points simultaneously. It will be important for a user to have a proper spatial setup.

Thanks for letting me know.

Dave

[mgagneur]

Hi Dave,

I just want to say thank you for creating WinPCD. As I mentioned in a earlier post I have been working on a 2 way using a sb17 woofer and a heil tweeter. Over the years I have accumulated various versions of the modeling tools most folks use (Calsod, Lspcad, SE, PCD) and have found them to have their pros and cons. This time around I bought an omnimic wanting to make it my primary measuring tool. I tried my best to figure out how to import the data and use PCD but could never get the model to agree with omnimic. I'm sure I'm doing something wrong and someday I'll figure it out. Meanwhile, I came across WinPCD and after spending a bit of time getting to know it, it works great. I get excellent agreement between the model and the omnimic measured result. Small subtle changes are easily distinguishable and measurable.

Well done!

Regards,

Marty

[dlr]

The problem you had with the z-offset when the woofer is set positive relative to the tweeter has been fixed. The calculations were good, but the check for the relative position of driver-to-mic was not useful. The comparison is now only the z-axis offsets of mic/listener to driver and is correct insofar as I've tested it. There are two additional small functions included as well, raw driver SPL db shift and power response display as an option in the system graph.

Dave

[mike69]

just to say thanks