ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
7,895
Location
Ontario, Calif.
The fix will be in the next release. The problem is the length of the folder name and file name must be less then 260 characters. For a workaround, you could edit the system, department, channel names, or whatever you are using and/or uncheck the "Append TO [Time] which add an additional 12 characters.
 
Last edited:

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
7,895
Location
Ontario, Calif.
Regarding the problem with the Recorder grid showing Grey rows. The problem is the Windows path and filename maximum allowed length is 260 characters. Problem never noticed before until the BCDx36HP's came along with longer names than the 16 chars before them.

I could do one of three things to the Recorder as follows:

1. Limit the path and filename to 260 characters. Actually it would be 12 less than that because of the Append ' TO hh:mm:ss' adds 12 chars. I don't think this would be acceptable

2. Don't show an entry in the grid at all if exceeds 260 chars. I don't think that would be acceptable as no indication that something is wrong.

3. Do nothing and leave it as it is with grayed out rows. I think this is the way to go so you will have an indication that the recording is not on the hard drive and you can check the format specifiers that you don't have too much info in the filename and/or edit the sys, dept/site/group, and/or channel name.

It looks like MS may lift the 260 character restriction which is another reason to go with number 3 above.
https://mspoweruser.com/ntfs-260-character-windows-10/
 
Last edited:

kb7gjy

Member
Feed Provider
Joined
Feb 13, 2011
Messages
256
Location
Bonners Ferry, Idaho
Regarding the problem with the Recorder grid showing Grey rows. The problem is the Windows path and filename maximum allowed length is 260 characters. Problem never noticed before until the BCDx36HP's came along with longer names than the 16 chars before them.

I could do one of three things to the Recorder as follows:

1. Limit the path and filename to 260 characters. Actually it would be 12 less than that because of the Append ' TO hh:mm:ss' adds 12 chars. I don't think this would be acceptable

2. Don't show an entry in the grid at all if exceeds 260 chars. I don't think that would be acceptable as no indication that something is wrong.

3. Do nothing and leave it as it is with grayed out rows. I think this is the way to go so you will have an indication that the recording is not on the hard drive and you can check the format specifiers that you don't have too much info in the filename and/or edit the sys, dept/site/group, and/or channel name.

It looks like MS may lift the 260 character restriction which is another reason to go with number 3 above.
https://mspoweruser.com/ntfs-260-character-windows-10/

Might take some more programming, but maybe a popup box that says that when it attempted to record there was a problem, (No disk space, to long of a file name, etc). with suggestions to fix the problem. Just a thought.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
7,895
Location
Ontario, Calif.
Might take some more programming, but maybe a popup box that says that when it attempted to record there was a problem, (No disk space, to long of a file name, etc). with suggestions to fix the problem. Just a thought.

I think that would be annoying with a popup keeps popping up and requires user intervention. I just updated the "Colors Defined" box
 

Attachments

  • Colors.png
    Colors.png
    9.1 KB · Views: 404

K4EET

Chaplain
Premium Subscriber
Joined
Feb 18, 2015
Messages
2,426
Location
Severn, Maryland, USA
Audio Alerts Driving Me Nuts...

Well, I've checked something that I've come to regret. But I cannot find what I did. I am receiving audio and text alerts every time my scanner breaks squelch; regardless of the channel or talkgroup. I thought it was the Hot Event Audio Alert but I do not have that checked. So what else causes an audio and text alert like the picture shows every time the scanner breaks squelch? Thanks in advance for helping me find what I did that I cannot find... LOL! 73, Dave K4EET :confused:

Hot_Event_Audio_Alert.jpg
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
7,895
Location
Ontario, Calif.
Well, I've checked something that I've come to regret. But I cannot find what I did. I am receiving audio and text alerts every time my scanner breaks squelch

Does the audio says "Alert Alert Hot Event In Progress"?
What do you mean by text alert? That text box doesn't look familiar? Do you have some other software running that would cause this?
Is the RSOIP Client connected to a server?
What version are you running?
Can you copy the ProScan.cfg file to something else in case you need to revert back to the same config and then delete the ProScan.cfg file and restart ProScan to see if it happens again.

{edit} The Hot Alert on the RSOIP client has nothing to do with a channel breaks squelch. It triggers when a RSOIP Server operator turns it on.
 
Last edited:

K4EET

Chaplain
Premium Subscriber
Joined
Feb 18, 2015
Messages
2,426
Location
Severn, Maryland, USA
Does the audio says "Alert Alert Hot Event In Progress"?

No, the only audio is a chime sound from the speaker.

What do you mean by text alert? That text box doesn't look familiar? Do you have some other software running that would cause this?

The text box in the lower right of the screen is the text alert that I refered to. As for other running software that would cause this, not that I know of.

Is the RSOIP Client connected to a server?

No, not at this time.

What version are you running?

Version 11.5

Can you copy the ProScan.cfg file to something else in case you need to revert back to the same config and then delete the ProScan.cfg file and restart ProScan to see if it happens again.

{edit} The Hot Alert on the RSOIP client has nothing to do with a channel breaks squelch. It triggers when a RSOIP Server operator turns it on.

The only configuration file that I found in the ProScan directory is named "ProScan.exe.config". When I move it to another directory, the program started with the same options and did not return to the defaults. The configuration file also did not regenerate itself in the ProScan directory.

The only thing that I had not done was to reboot the computer. That I just did and after the reboot the alert is no longer occurring. I have no idea what caused it or how to regenerate it again. If it ever happens again, I'll try to recall what I was doing immediately preceding the event. Perhaps it is not ProScan generating this alert since you do not recognize it as part of your GREAT software. For now, we'll put this on the back burner until it happens again.

Merry CHRISTmas and Happy New Year! 73, Dave K4EET
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
7,895
Location
Ontario, Calif.
Whatever it was, it sounded like some neat program. I wish I had thought of that.[edit] Now that I thought about it, maybe not a neat program after all.

BTW, Windows puts all program generated files in the VirtualStore folder when running 64 bit OS -AND- not running ProScan in admin mode -AND- installed in the Program Files(x86) folder.

ProScan.cfg file located in C:\Users\[user]\AppData\Local\VirtualStore\Program Files (x86)\ProScan

You have a Merry Christmas and Happy New Year too.
 

ProScan

Software Provider
Premium Subscriber
Joined
Jul 2, 2006
Messages
7,895
Location
Ontario, Calif.
Bob is there any chance of the TRX line getting added in the future.

negative buddrousa, sorry about that. I've got a lot of stuff planned for ProScan and just not enough hours in the day plus last I checked, the Whistler's scanners are very limited in the Protocol area.
 

Magpie

Member
Joined
Apr 26, 2009
Messages
86
1 kb PCM audio clip error

Hi all, I have 6 sessions running daily, 3 x 780 and 3 x BCT15X. Every now and then 1 of the sessions has the problem that the recorded PCM (8000) files are only 1 kb big and give an error message in Winamp. It happend with OS XP and W7 and on several Proscan versions. I now switched to MP3 (8000 / 96) to check if that solves the problem.

Does any fellow user recognise this issue? Would love to find a solution :)

Happy holidays to all group members.
 

Magpie

Member
Joined
Apr 26, 2009
Messages
86
Hi all, I have 6 sessions running daily, 3 x 780 and 3 x BCT15X. Every now and then 1 of the sessions has the problem that the recorded PCM (8000) files are only 1 kb big and give an error message in Winamp. It happend with OS XP and W7 and on several Proscan versions. I now switched to MP3 (8000 / 96) to check if that solves the problem.

Does any fellow user recognise this issue? Would love to find a solution :)

Happy holidays to all group members.
What I did was change from PCM recording to MP3 recording. No errors or 1 kb files :)

MP3 settings Samples p Second: 11025 and Bitrate: 96.

What I did notice is that recorded files are actually 64 kbps instead of 96 kbps. Am I doing something wrong here? Can someone explain? MTIA.
 
Top