ProScan: Official Software Thread

[ProScan]

ProScan Version 22.4 Just Released!

• Fixed - Importing conventional systems from the RRDB was creating separate systems for the same system.
• Added - Waterfall support for the SDS100 & SDS200 scanners.

Fastest way to turn on the Waterfall:


Options:


ProScan Website

ProScan is the most powerful and feature rich scanner software in the world !!!

 

[dave3825]

Thank you Bob for fixing the import issue. You got that fixed fast!. And of course, thank you for the waterfall, and everything else you have done to make @ProScan the best there is.

 

[ProScan]

Thank you Bob for fixing the import issue. You got that fixed fast!. And of course, thank you for the waterfall, and everything else you have done to make @ProScan the best there is.

You're very welcome Dave and thanks for the compliment.

 

[pinballwiz86]

Looks and works great with my SDS200!

 

[KC1UA]

I am having a bizarre issue; first time I've had such an issue with ProScan. Based on the above post I'm guessing it is maybe just me, but here is the info.

Using the front micro USB port as usual, same USB port on PC, same setup that has worked with countless versions of ProScan. I've rebooted everything, unplugged, replugged. Pic attached. I am seeing systems in the bar at the top of the screen next to ProScan so there is some level of connectivity, but as shown everything else is blank.

Not sure what to make of this. The proper scanner is selected, in this case the SDS200.

 

[K3HY]

I am having a bizarre issue; first time I've had such an issue with ProScan. Based on the above post I'm guessing it is maybe just me, but here is the info.

Using the front micro USB port as usual, same USB port on PC, same setup that has worked with countless versions of ProScan. I've rebooted everything, unplugged, replugged. Pic attached. I am seeing systems in the bar at the top of the screen next to ProScan so there is some level of connectivity, but as shown everything else is blank.

Not sure what to make of this. The proper scanner is selected, in this case the SDS200.

View attachment 155570

Same thing on my SDS100. I think it is related to the scanner type selection in the toolbar.
Using the SDS100, but changing the scanner type to BCD436HP, the screen looks good.
Changing scanner type back to SDS100 get an unhandled exception error in Proscan program.
I'll use the BCD436HP scanner type for now.
Hope that helps narrow it down with troubleshooting.

 

[KC1UA]

I should state that I did the update to the latest software version via running ProScan and following the prompts when advised a newer version is available. Not sure if there's any common ground there. I can remove activation, try a fresh install, and reactivate if necessary.

 

[KevinC]

I am having a bizarre issue; first time I've had such an issue with ProScan. Based on the above post I'm guessing it is maybe just me, but here is the info.

Using the front micro USB port as usual, same USB port on PC, same setup that has worked with countless versions of ProScan. I've rebooted everything, unplugged, replugged. Pic attached. I am seeing systems in the bar at the top of the screen next to ProScan so there is some level of connectivity, but as shown everything else is blank.

Not sure what to make of this. The proper scanner is selected, in this case the SDS200.

View attachment 155570

No help, but my SDS200 is working fine with the latest update (I'm using the LAN port though).

 

[KC1UA]

No help, but my SDS200 is working fine with the latest update (I'm using the LAN port though).

It was worth a try but same result. I need to replace the LAN cable I'm using. Despite it being STP it throws terrible interference when plugged in; maybe it's the scanner itself that generates it.

Anyway in my case, LAN or USB, same result, unfortunately.

Kevin, did you (or anyone else that's gone to the latest version) do a fresh install or the update as it's offered when running the software normally.

 

[KevinC]

Kevin, did you (or anyone else that's gone to the latest version) do a fresh install or the update as it's offered when running the software normally.

Update route.

 

[ProScan]

I should state that I did the update to the latest software version via running ProScan and following the prompts when advised a newer version is available. Not sure if there's any common ground there. I can remove activation, try a fresh install, and reactivate if necessary.

Before doing anything, send me an email with the config (ProScan.cfg) file so I can try to duplicate the problem. After that, stop ProScan then delete the ProScan.cfg file then restart ProScan.

I never advise uninstalling and reinstalling ProScan. All that does is replace the exe and dll files with the same files.

 

[KC1UA]

I sent the proscan.cfg file to your support email. Shut down ProScan, edit: deleted proscan.cfg and restarted. As I'm sure you're aware it reset the scanner type to a BCD996XT. When I switched to SDS200 I had a window pop-up labeled "Detail Error information" with this text within:

System.NullReferenceException: Object reference not set to an instance of an object.
at General.ReadSDSProfileColors(Boolean ShowMessage) in \ProScan\General.vb:line 9155
at RadioSpecific.Common(ComponentResourceManager resources) in \ProScan\RadioSpecific.vb:line 2808
at RadioSpecific.RS_InitRadioType() in \ProScan\RadioSpecific.vb:line 268
at FrmMain.ScannerTypeToolStripMenuItem_Click(Object sender, EventArgs e) in \ProScan\FrmMain.vb:line 10444
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.MenuStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

[pinballwiz86]

I sent the proscan.cfg file to your support email. Shut down ProScan, edit: deleted proscan.cfg and restarted. As I'm sure you're aware it reset the scanner type to a BCD996XT. When I switched to SDS200 I had a window pop-up labeled "Detail Error information" with this text within:

System.NullReferenceException: Object reference not set to an instance of an object.
at General.ReadSDSProfileColors(Boolean ShowMessage) in \ProScan\General.vb:line 9155
at RadioSpecific.Common(ComponentResourceManager resources) in \ProScan\RadioSpecific.vb:line 2808
at RadioSpecific.RS_InitRadioType() in \ProScan\RadioSpecific.vb:line 268
at FrmMain.ScannerTypeToolStripMenuItem_Click(Object sender, EventArgs e) in \ProScan\FrmMain.vb:line 10444
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.MenuStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Did you try restarting your computer?

 

[ProScan]

For anyone having the problem with the latest,:
Try downloading again. It's still version 22.4. The file version is 22.4.1.0

 

[KC1UA]

Did you try restarting your computer?

Yes, I had tried that; made no difference at the time.

For anyone having the problem with the latest,:
Try downloading again. It's still version 22.4. The file version is 22.4.1.0

Thanks Bob, it is working fine now.

 

[ScottPDX]

ProScan is such a fantastic product. Thank you Bob for continuing to develop and support it after all these many years.

So I did some searches here and looking through ProScan itself, but didn’t find a similar Q or A.

Is there anyway to have ProScan Loopback local playback audio to output other than currently selected Windows playback audio device?

I know I could close ProScan, change the current selected playback device in Windows, and then re-launch ProScan.

But in this particular situation, the ProScan computer is shared with other family user logins, and if I change the Windows audio playback device in the System Tray for the ProScan login user, when another family member goes to login, they have that new windows audio playback device also selected, instead of the desired default Windows audio playback device. I’m just wondering is this alternate audio Loopback output can be achieved within ProScan, or I need to resort to an outside audio redirection application like VAC (Virtual Audio Cable)?

 

[ScottPDX]

I think I may have found my own answer: I’m testing the settings under: Windows Sound Control Panel - Recording Tab - The “Line Input” Device - Properties - “Listen” Tab - Choose alternate sound output device in the drop-down menu.

Will report back if that isn’t the answer…..

ProScan is such a fantastic product. Thank you Bob for continuing to develop and support it after all these many years.

So I did some searches here and looking through ProScan itself, but didn’t find a similar Q or A.

Is there anyway to have ProScan Loopback local playback audio to output other than currently selected Windows playback audio device?

I know I could close ProScan, change the current selected playback device in Windows, and then re-launch ProScan.

But in this particular situation, the ProScan computer is shared with other family user logins, and if I change the Windows audio playback device in the System Tray for the ProScan login user, when another family member goes to login, they have that new windows audio playback device also selected, instead of the desired default Windows audio playback device. I’m just wondering is this alternate audio Loopback output can be achieved within ProScan, or I need to resort to an outside audio redirection application like VAC (Virtual Audio Cable)?

 

[ProScan]

ProScan is such a fantastic product. Thank you Bob for continuing to develop and support it after all these many years.

So I did some searches here and looking through ProScan itself, but didn’t find a similar Q or A.

Is there anyway to have ProScan Loopback local playback audio to output other than currently selected Windows playback audio device?

I know I could close ProScan, change the current selected playback device in Windows, and then re-launch ProScan.

But in this particular situation, the ProScan computer is shared with other family user logins, and if I change the Windows audio playback device in the System Tray for the ProScan login user, when another family member goes to login, they have that new windows audio playback device also selected, instead of the desired default Windows audio playback device. I’m just wondering is this alternate audio Loopback output can be achieved within ProScan, or I need to resort to an outside audio redirection application like VAC (Virtual Audio Cable)?

Go to the Audio Control - RSOIP tab. On the Payback side, change the Output Sound Device.

 

[KevinC]

For anyone having the problem with the latest,:
Try downloading again. It's still version 22.4. The file version is 22.4.1.0

I'm assuming if we don't experience the issue their is no need to update?

 

[ProScan]

I'm assuming if we don't experience the issue their is no need to update?

Correct