New SPL Copy Software - Please Help Test

[seattle_ice]

Latest Version 1.0.4.5 Posted 7:00 pm PST 10/7/09

Keep the feedback coming. I appreciate the effort from everyone who tries this. I plan on making it as full featured as I can.

IMPORTANT: Partially tested with Vista. Please let me know if you are running Vista or Win7 and having any problems.

For bug reports, please report the bug in this thread, but send the details to my PM or email: seattle_ice@hotmail.com. I would like to keep the posts short and succinct in the thread.

After squinting at the screen and hitting enter 400 times over and over, I decided to try and automate the tasks of converting FRD and ZMA Graphs to files, and vice versa by writing a small software application similar to SPLTrace, but more automated.

I would just like to ask for a little help in testing. All feedback will be appreciated, good and bad.

For testing purposes, I have set it up as a one-click install, which means it will install from the web, but also that it will check for updates and information every time it starts. I will change that once it is finalized so it will load almost instantly.

If you need a graph to test it, you can find hundreds at Zaphs site, or many other places.

This is designed for LOGARITHMIC frequency/impedance style graphs.

This is what it looks like right now, subject to improvements and updates:



The software can be found here:

http://www.nthtechnologies.com/Speakers/SPLCopy/install.htm

HISTORY:

• FIX: 9/28/2009 - Error when manual entry made to frequency combo box. Frequencies are now limited to existing entries.
• FIX: 9/28/2009 - Error when entering manual amplitude numbers. Manual entries are now allowed and should work fine.
• FIX: 9/28/2009 - Dialogs would get trapped behind Help form. Help form does not stay on top anymore, to view it while working you must move it to the side.
• ----------------------------------------------------------------
• ADDED: 9/28/2009 - Ability to handle Impedance data.
• FEATURE: 9/28/2009 - Logarithmic calculating and drawing functions have been sped up aproximately 3-400%.
• FIX: 9/28/2009 - Manual entries are allowed for Impedance values.
• FIX: 9/28/2009 - Impedance colors and text not reading right.
• FIX: 9/28/2009 - Impedance values not reading correctly.
• -------------------------------------------------------------
• ADDED: 9/29/09 - Color choice for tracer.
• ADDED: 9/29/09 - Prompt for manual input via arrow keys if tracer gets stuck.
• ADDED: 9/29/09 - Whole new level of AI on the tracing functions. It now will track trends up to a depth of 10 points along your line, to help stay on the correct line when multiple lines intersect.
• -------------------------------------------------------------
• ADDED: 9/30/09 - Ability to open and display *.frd and *.zma files.
• ADDED: 9/30/09 - 5 options to handle duplicate frequencies showing up to due pixel width. You can keep, remove or average forwards/backwards.
• ADDED: 9/30/09 - Trace handling for the graph line going off the edge of the graph before the user limits were hit. This would cause a fault.
• FIX: 9/30/09 - Index out of range fault when processing duplicates.
• FIX: 10/3/09 - Tracking lines were being drawn offset when graph was visible with scroll bars.
• ADDED: 10/4/09 - 3 options for different impedance scales
• FIX: 10/4/09 - Error when loading a file that contained points that resulted in duplicate pixels being drawn on the map.
• FIX: 10/4/09 - Data Point Save forms were not properly remembering the last percentage setting. Now the last choice is persisted.
• ADDED: 10/7/09 - Start the trace anywhere on the line, instead of before the selected ranges only.

Current Version 1.0.4.5

[maynardg]

Where would you like bug reports?

Running Vista.


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at SPL_Copy.frmFrequency.HertzFromComboString(String hzText)
at SPL_Copy.frmFrequency.btnOK_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SPLCopy
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/mgmj/AppData/Local/Apps/2.0/J5JMNX0P.PA9/TAHEZC0A.8YL/splc..tion_e2d132f18e466ecf_0001.0000_647f8cb147da ef94/SPLCopy.EXE
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[5th element]

Yeah I get an unhandled exception too. Windows 7 x64 RC.

If you try to set the first frequency boundary and type in a number, rather then selecting an option from the drop down box, you get another unhandled exception.

The zoom function doesn't work either.


----------

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at SPL_Copy.frmFrequency.HertzFromComboString(String hzText)
at SPL_Copy.frmFrequency.btnOK_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SPLCopy
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Matt/AppData/Local/Apps/2.0/QCNL2755.65Q/TBYZNNRR.9DK/splc..tion_e2d132f18e466ecf_0001.0000_647f8cb147da ef94/SPLCopy.EXE
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Then upon running you get another unhandled exception too.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Parameter must be positive and < Height.
Parameter name: y
at System.Drawing.Bitmap.GetPixel(Int32 x, Int32 y)
at SPL_Copy.Main.ExtractFRD(Point startPoint, Color lineColor)
at SPL_Copy.Main.picGraph_MouseDown(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SPLCopy
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Matt/AppData/Local/Apps/2.0/QCNL2755.65Q/TBYZNNRR.9DK/splc..tion_e2d132f18e466ecf_0001.0000_647f8cb147da ef94/SPLCopy.EXE
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Rudolf]

Works nicely, but it does not accept Amplitude values, which I type into the Select field. I have to select one of the given values. Is that correct? I have diagrams which are devided into 6 dB steps, not 5 dB.

If the Help window is in the foreground and I select a frequency, the "Select a Frequency" window will pop up behind the Help window, which is not active, can not be activated and can not be moved to the side. I needed to kill the task to get out of that trap.

[seattle_ice]

Thanks guys. I had not tried it on Vista (Or win7 which will probably work the same).

I will load a version and do some testing.

I will also allow other amplitude values. I think there may be some charts that use other than base 1/10 for amplitude also.

[maynardg]

BTW, thas for your effort!

Talented people like you make it easier for less talented people like me to play in the hobby.

[Nwalmaer]

This is simply awesome. I've wished for an application like this for a long time.
Works just great here, too. Running Vista 64bit.

[Dennis H]

Very cool, thanks! I got it to go in XP with no problems other than figuring out a couple of quirks. I was concerned that the duplicate entries at the same frequency might bother LspCAD but it loaded them fine so I'll be using it at 100% data. I'll second the request to be able to enter your own SPL and frequency numbers. For example, you might want to trace something plotted between 0 and -48 dB.

[seattle_ice]

Very cool, thanks! I got it to go in XP with no problems other than figuring out a couple of quirks. I was concerned that the duplicate entries at the same frequency might bother LspCAD but it loaded them fine so I'll be using it at 100% data. I'll second the request to be able to enter your own SPL and frequency numbers. For example, you might want to trace something plotted between 0 and -48 dB.

Thanks, Dennis. If there are duplicates of a frequency, but with different amplitudes, or vice versa, it is because the graph goes straight up or straight over for more than one pixel on the screen. It shouldn't bother any of the programs, at least not that I have seen, since in many cases they belong there.

Now, if there are actual duplicates (Same exact DB and FREQ) then I would want to get rid of those.

For now, I have updated the program to allow manual entries for the amplitude, but not for the frequency. The Logarithmic nature of the frequency values makes it more complicated, especially when you are dealing with images that might have been resized, cropped, changed, etc.

People might think that halfway between 100hz and 200hz would be 150, but that is not so. It would 10 ^(1 + (pct of distance from 100 to 1000/100))

[Dennis H]

If there are duplicates of a frequency, but with different amplitudes, or vice versa, it is because the graph goes straight up or straight over for more than one pixel on the screen. It shouldn't bother any of the programs, at least not that I have seen, since in many cases they belong there.

Well, if it were a real measurement, there would only be one SPL for each frequency. It's converting them to a bitmap that's giving pixels stacked in a column. I traced one of Brandon's horn measurements and it has a big vertical line up high. It also looked like thick lines could confuse things even when the slope wasn't steep. I suspect LspCAD is only using one of the numbers for each frequency. I'll take a look later and see if I can figure out which one.

19105.1400 99.8113 0
19105.1400 99.5283 0
19105.1400 99.2453 0
19105.1400 98.9623 0
19105.1400 98.6792 0
19105.1400 98.3962 0
19105.1400 98.1132 0
19105.1400 97.8302 0
19388.3100 97.5472 0
19388.3100 97.2642 0
19388.3100 96.9811 0
19388.3100 96.6981 0
19388.3100 96.4151 0
19388.3100 96.1321 0
19388.3100 95.8491 0
19388.3100 95.5660 0
19675.6800 95.2830 0
19675.6800 95.0000 0
19675.6800 94.7170 0
19675.6800 94.4340 0
19675.6800 94.1510 0
19675.6800 93.8679 0
19675.6800 93.5849 0
19675.6800 93.3019 0
19675.6800 93.0189 0
19675.6800 92.7359 0
19675.6800 92.4528 0

Edit: okay I checked and LspCAD appears to be taking the first number in the list. I dunno, should we be averaging them and just listing a single number? That would take care of fat lines as well. Or maybe some other algorithm like highest on the way up and lowest on the way down? Tough call.

Edit again, I guess that highest/lowest thing would mean using the last one in the list. Pseudo code: if nextF > thisF then record else ignore.

[Dennis H]

Edit: deleting my long diatribe -- I figured out what's going on with Praxis. I opened the file in the demo version of Praxis and saved it again. Praxis uses only the last number in the list.

Praxis has all kinds of cool post-processing you can do in the demo version. If you want minimum phase data to use in XO design software:

Open in Praxis
Remap to FFT frequencies
Do a Hilbert transform to get phase
(Optional) remap back to log frequencies
Save

[Wilk]

Very nice.

It worked fine for me on Windows 7 RC

Do you intend to keep going so it can handle impedance data (.zma) as well?

Actually, it can propably handle that already can't it? I would just need to change the file type.

Hmmm................. Now I saw a program over at FRD that extracted minimum phase.

This is really nice,and useful great freaking job!!!!

[Dennis H]

You've gone viral, Darryn. Should get lots of downloads from the PE crowd.

http://techtalk.parts-express.com/showthread.php?t=213419

[seattle_ice]

Well, if it were a real measurement, there would only be one SPL for each frequency. It's converting them to a bitmap that's giving pixels stacked in a column. I traced one of Brandon's horn measurements and it has a big vertical line up high. It also looked like thick lines could confuse things even when the slope wasn't steep. I suspect LspCAD is only using one of the numbers for each frequency. I'll take a look later and see if I can figure out which one.

Edit: okay I checked and LspCAD appears to be taking the first number in the list. I dunno, should we be averaging them and just listing a single number? That would take care of fat lines as well. Or maybe some other algorithm like highest on the way up and lowest on the way down? Tough call.

New version posted 1.0.2.1 as of 9 pm PST 9/28/09.

I am not sure the best way to handle this situation. Obviously, there are limits to converting real data to pixels on the screen. I could handle it using a number of different methods, but figuring out the best way is usually the hard part.

Know the math for the FFT and extractin the phase info? I could incorporate it into the program. I will look around and see what I can find.

Thanks for the input, we will figure it out.

[Dennis H]

New version posted 1.0.2.1 as of 9 pm PST 9/28/09.

I am not sure the best way to handle this situation. Obviously, there are limits to converting real data to pixels on the screen. I could handle it using a number of different methods, but figuring out the best way is usually the hard part.

Know the math for the FFT and extractin the phase info? I could incorporate it into the program. I will look around and see what I can find.

Thanks for the input, we will figure it out.

The more I think about it, I think I like the Praxis method of using the last one on the list. Otherwise, you'll miss the tops of peaks and the bottoms of dips.

I'm a little vague on the Hilbert-Bode transform to get phase. I know you need to convert to samples with linear frequency spacing, keeping in mind that your LF resolution is only as good as the spacing. Then it's some kind of trig thing thing to separate the real and imaginary parts and get the phase. Best bet would be to contact Jeff Bagby as he's already written a free one for Excel (probably using VBA) and I'm sure he'd be glad to help with the math. His email is on his web page.

http://audio.claub.net/software/jbagby.html

[seattle_ice]

The more I think about it, I think I like the Praxis method of using the last one on the list. Otherwise, you'll miss the tops of peaks and the bottoms of dips.

New version posted, and some thoughts..

I have been thinking about the duplicate frequency issue. I think I might make this a selectable option with these choices:

1. Leave duplicates alone (You can always reduce the Data Point % and this will remove many of them)

2. Keep the last entry in the line with frequency duplicates, and average the previous ones back to the last non-duplicate entry.

3. Keep the first and last entry in the line with frequency duplicates, and ditch the rest.

4. Keep the first entry in the line with frequency duplicates, and average the previous ones up to the first non-duplicate entry.

Let me know what you think.

[Dennis H]

Darryn, it seems like none of your options will reduce the data down to one entry per frequency. Or am I misunderstanding?

[---k---]

I would imagine that any time you have two values for the same frequency, one of the two values is going to be very very similar to an adjacent value. I'm picturing a horizontal line that then goes vertical. You don't need to capture the horizontal point, you need the vertical. So ditch the Y value that is the same as the previous value. Or the reverse if the reverse is true.

Make sense?

Post a snippet of actual data and I think it would become very obvious what the solution should be.

[seattle_ice]

Darryn, it seems like none of your options will reduce the data down to one entry per frequency. Or am I misunderstanding?

#2 and #4 would be remove the duplicates

I would imagine that any time you have two values for the same frequency, one of the two values is going to be very very similar to an adjacent value. I'm picturing a horizontal line that then goes vertical. You don't need to capture the horizontal point, you need the vertical. So ditch the Y value that is the same as the previous value. Or the reverse if the reverse is true.

Make sense?

Actually, there are some graphs where the amplitude (or impedance) goes up or down very rapidly to a peak or a trough. This can result in a fair number of points where the X axis will stay the same for multiple entries based on a pixel width on the screen, but the y axis changing significantly.

In reality, especially on the higher end of the graph, where one pixel might cover a frequency range of several hz, you would have to have as many pixels as points on the X-Axis for it to be perfect.

If you think about #2 that I posted, if you ended up with this for part of the plot:

303.443, 41.546
305.398, 46.982
306.366, 47.546
306.366, 48.236
306.366, 49.563
306.366, 50.332
306.366, 51.442
308.523, 52.988

Then you would take the last of the duplicate frequencies (306.366, in blue) and average from that value back to the first non duplicate (305.398, in red)

So only the last one would retain its X-Axis value, the others (in bold) would get averaged backwards to even increments from the blue to red value.


So you would get something like this:

303.443, 41.546
305.398, 46.982
305.591, 47.546
305.785, 48.236
305.978, 49.563
306.172, 50.332
306.366, 51.442
308.523, 49.567



The #4 option I listed is the same, just in reverse.

[JoshJK]

Know the math for the FFT and extractin the phase info? I could incorporate it into the program. I will look around and see what I can find.

You may not want to bother to include this functionality in your software. Unless we design an infinite baffle (or in-wall flush mounted) speakers, we always add baffle step loss and diffraction effects to generate in-box responses before applying the Hilbert-Bode transformation. But if it is easy to include, why not? Just wanted to let you know how people would use traced data.

This will be a great tool for the DIY community!

Josh

EDIT: oh, but for the impedance data, phase extraction will be worthwhile.

[seattle_ice]

You may not want to bother to include this functionality in your software. Unless we design an infinite baffle (or in-wall flush mounted) speakers, we always add baffle step loss and diffraction effects to generate in-box responses before applying the Hilbert-Bode transformation.

This will be a great tool for the DIY community!

Josh

Yeah, this is just one of those, "ok, cool" kind of things. I actually had planned on finishing the functionality to open the raw frd and zma files and show them on a graph like SPLViewer. SPLViewer has never worked for me, it always crashes.

[seattle_ice]

New update available. 1.0.4.1

I added some options to handle adding/removing/averaging of duplicate frequencies, as well as a number of error checking and handling routines.

[Dennis H]

Nice! Small nit, the help file needs a scroll bar. Not sure if I could read all the way to the bottom or not on this 768 pixel CRT.

[seattle_ice]

Nice! Small nit, the help file needs a scroll bar. Not sure if I could read all the way to the bottom or not on this 768 pixel CRT.

I didn't realize people would be running this on their Iphone :E

I will make the help form scroll when necessary.

[Dennis H]

Hey, I'm old school. I've got a couple of old 21" monitors that still work just fine. I've played with running them at higher resolution but overall they display the best at 1024x768. You'd think, since I bought them to do CAD and spent $2K+ for each of them, I'd want all the pixels I could get but not true. Less artifacts (moire, etc) with the lower rez and the pixels are still close enough together to make text or lines look solid. Call me a Luddite but they look better for graphics to my eye than any LCD I've tried.

[seattle_ice]

Hey, I'm old school. I've got a couple of old 21" monitors that still work just fine. I've played with running them at higher resolution but overall they display the best at 1024x768. You'd think, since I bought them to do CAD and spent $2K+ for each of them, I'd want all the pixels I could get but not true. Less artifacts (moire, etc) with the lower rez and the pixels are still close enough together to make text or lines look solid. Call me a Luddite but they look better for graphics to my eye than any LCD I've tried.

I know how that goes, somewhat. I am still using my LaCie 22" CRT because I cannot duplicate the fine pitch and high resolution with an LCD. I run everything at a minimum of 1920 x 1440 and it is very, very crisp.

I found an error in my code that was processing the duplicates. It would return an index out of range error. I just updated it.

[seattle_ice]

I fixed a problem with the mouse tracking when there were scroll bars visible. Evidently there are a fair number of people using this with smaller screens.

Version is now 1.0.4.3.

Thanks for the continuing feedback, people.

[seattle_ice]

Dennis: I never heard back if the changes to the duplicate handling options work for you. Let me know when you have time to try it.

Thanks,

Darryn

[Dennis H]

Dennis: I never heard back if the changes to the duplicate handling options work for you. Let me know when you have time to try it.

Thanks,

Darryn

Works great Darryn! Last only, 100% data is good enough for me.

Try tracing this one to exercise your trend thing. The red line at the center is enough of a different color that it worked before on 5% color tolerance with no trend feature. I'd expect it to get confused at the 20K notch but, even at 3 pixels trend, it stops several other times above 9K.

About ZMA tracing, it works great but it's not all that uncommon to see a log ohms scale in factory data sheets.

[b_force]

Great program!!

With this version you can only select a linear impedance scale.
There are some diagrams (Peerless I believe) that are exponential (and sometimes logarithmic), so you have a problem...

[seattle_ice]

Great program!!

With this version you can only select a linear impedance scale.
There are some diagrams (Peerless I believe) that are exponential (and sometimes logarithmic), so you have a problem...

It wouldn't be that hard to add the capability for this. I would just add a user selectable choice for the scale type.

All I need is to know what scales to include.

[seattle_ice]

I added some choices and handling for Base 2 and Base 10 Impedance scales. It will need some testing to verify that they work.

I also fixed a couple of small errors that I found while working with it. The program didnt handle data points that were so close together in a file they would create duplicate pixels, and a couple of the user settings were not being saved and persisted.

Darryn

[JoshJK]

Finally I tried the SPL Copy. Excellent. Very easy and intuitive to use. One minor suggestion. I found that it works only if the starting point is between top and bottom amplitude (or impedance) bounds specified by the user. This does not have to be. Those bounds can be used not only to interpolate but also to extrapolate points.

Not a big deal, but I think it can be a little more flexible without complication. Initially it took more than 10 minutes for me to figure out why it would not work.

Josh

[seattle_ice]

Finally I tried the SPL Copy. Excellent. Very easy and intuitive to use. One minor suggestion. I found that it works only if the starting point is between top and bottom amplitude (or impedance) bounds specified by the user. This does not have to be. Those bounds can be used not only to interpolate but also to extrapolate points.

Not a big deal, but I think it can be a little more flexible without complication. Initially it took more than 10 minutes for me to figure out why it would not work.

Josh

Sounds a whole lot easier than it is. Extrapolating the points is easy. I am already doing that whenever you move your mouse around. The hard part is for the program to know when you are out of bounds before, during, or after a trace. There are 9 different combinations of where you could click on the graph, and a bunch off the graph before it even starts tracing.

Would you like it to cook you breakfast while I am at it? :

Actually, I already added a rough draft of this capability to the next version, which I will be publishing in about 5 minutes.

[b_force]

I didn't check it, but is it also possible to trace by hand (just like the old one)?
Whit very difficult graph that's sometimes the only option.

I don't know what scales you can use for logarithmic and/or exponential. You can use the graph from Peerless for an example.

[grantnsw]

SPL Copy...GREAT progamme.. thanks!

Hi, just to bump this thread,

Wow, it works great for amplitude (when colors changed from axes of course),

but I can't get it to work for impedance. The lower Z limit sets ok but the higher Z axis is blanked out? So I can't trace impedance. :E

I'm running XP home 2002 SP3 at 800 by 600 on a cheap 30 inch plasma TV monitor.

Any clues most appreciated, please see attached screenshot. Also , does it matter that the frequency and SPL limits seem to 'bounce' slightly when the limits are set? I'm not complaining its a great prog!

cheers, Grant

[seattle_ice]

Why don't you send me the graph pictured and I will check it out.

The "bumping" I would guess is either the mouse moving slightly, or the pointer might be between pixels on the screen, so when the line gets drawn, it moves a little.

[grantnsw]

Hi Darryn,

thanks for your quick reply. :T , the file is Eminence Beta-15A:

http://www.eminence.com/pdf/beta-15a.pdf

I (roughly) changed changed the Z curve to orange. Is 800 x 600 resolution too low for it to fit properly on the screen, I wonder? Trouble is, that's all this cheap Soniq plasma will do. The Help page doesn't quite fit either.

Also, how do I check the version/build # please? I d'l'd it on 7/22/2010.
Thanks... Grant

[frank58]

My problem is Spl Copy overshoots last limits and is not stopping. How can i fix it ?
Another problem is when i close it, I can't change the file loaded before.
Thanks for this software.

[seattle_ice]

My problem is Spl Copy overshoots last limits and is not stopping. How can i fix it ?
Another problem is when i close it, I can't change the file loaded before.
Thanks for this software.

Try changing the color of the line at the limit you want it to stop. It is just trying to follow the pixels that are the same color. If that doesn't work, post a link to the file you are using and I will try to figure out what is happening.