cant exit sounttap

[nir 0]

not the first time this is happening, on my windows 10 pro, sound tap is working well but does not exit, no matter what I do , even with task manager it can not be killed 

I can use a more aggressive task manager tools to kill it, or restart, very annoying

any idea ?

 

[Gekker 0]

Try reinstalling the program from http://www.nch.com.au/soundtap/index.html
If you keep having issues enter a support ticket at http://www.nch.com.au/support/index.html

[N_C_H_yusuf 0]

Hi Nir,

  I'm one of the developers of SoundTap. That is interesting, I've never faced such a problem in SoundTap. Could you explain the issue more so maybe I can identify a possible bug and fix it?

When that happens is SoundTap frozen, does windows give you "not responding" error? Does this happen while recording or on idle? What happens when you click exit when the issue occurs? How often do you think that problem occurs and is there anything in common between different occurrences, for example whenever I click here, or whenever I open this other program etc. ?

Thank you for informing us the problem, if I can understand and produce the problem, I will try to fix it as soon as possible.

Regards,

Yusuf 

[nir 0]

Yusuf, 

Sorry I did not see your answer, here is what happens, 

after almost every recording, soundtap stay up, I cant exit it nor can kill it using windows task manager, (i need process explorer to kill it) 

If I start recording again, it claims it has directory permission errors , other than that some menu items / buttons does not work, (and some does) for example help button does not do anything , option buttton does not do anything,  but start / stop recording does.

 

I can probably reproduce it easily , and can do a screen share if you want.

 

I'm a developer myself so if you want me to do some patching / troubelshooting, let me know.

if you want some kind of logs let me know as well.

 

thanks

 

 

 

[N_C_H_yusuf 0]

Hi Nir,

  That is all good, no worries.

  That is really interesting, I've never seen such a bug in SoundTap before. I appreciate If you could send a screenshot of the directory permission error message. Unfortunately, there is no log generated on release builds and I'm not sure if I'm allowed to share debug builds, most probably not. Maybe the error message might give me some clues. Thank you for all you help.

Best regards,

Yusuf

[johnrlee 0]

Here it is May of 2020 and I am having exactly the same problem in Windows 10.

In the SoundTap trial period, I was able to record a stream, start a new record of a new stream and finally exit SoundTap.  

Unfortunately, after my recent purchase, I can only record one stream.  When I try to start the recording process for the another stream, I get the "Directory Permission" message.  I also cannot exit SoundTap even by using Windows 10 Task Manager.

The only way to exit the program is to "crash exit" windows and reboot.

I am going to try the suggested reload of the program to see it that helps.

 

UPDATE: I Reloaded the program and recorded one audio stream.  The recording was fine, but SoundTap still  will not exit.

[flocken 0]

Hi there,

I've similar behaviour as tir reported here: http://nch.invisionzone.com/topic/26807-cant-exit-sounttap/?tab=comments#comment-68681
It sometimes happens, not every time. If it happens, I can't get the program closed normally. It seems to "register" click, but will not be closed. If I try with Task Manager, I can pick the process, click on "Task beenden" (OS German version), but it won't close either. The only solution is Windows restart. OS: Windows 10, HP laptop with I7:
https://drive.google.com/file/d/1cf5S7vCSR9h4DPKhUJ29NuxS1qc5ashN/view?usp=sharing

Regards,
flocken
 

[Kim 1318 0]

I recommend to submit a Ticket to NCH Technical Support Team, here https://www.nch.com.au/support/index.html

[WompWomp 0]

I'm getting the same issue with multiple users. Windows 10 latest version. Soundtap is requiring the host PC to be restarted after a recording is stopped or if it’s closed after first-time use as it will hang in the background processes but won’t re-open its interface. Even after killing those background processes it requires a full restart to actually open.