NC1... very forgetful

TimD

Member
Ever since the last update, the NC1 forgets my settings. I have to go back to the 8 channels and set the 8 sources every time after I restart. Is there a remedy for this?
 
I would try deleting the 'session', it could be corrupted which is why the settings are not being saved.

Quit out of Connect and delete the folder 'NewTek Connect 1' found in 'C:\Users\NC1-IO\AppData\Local\NewTek'

Next time you start up the Connect software, it will build a new default session folder.

Also make sure you exit the application after you configure the software, so it can save the settings. If you reboot the system with the software running, it will likely not save for the next reboot.
 
I have exactly the same issue after upgrading to 7.8.220728. I can see the .Session file getting updated with correct input settings while I change them in the app. After I close the application, the .Session file has correct settings. However when I start it again, all settings for input channel are reverted to Local/Black. Output settings (at least for DVS audio) are kept. For now I am manually set all inputs after each reboot but I would gladly accept a solution for it :) Thank you for your time!
 
I have exactly the same issue after upgrading to 7.8.220728. I can see the .Session file getting updated with correct input settings while I change them in the app. After I close the application, the .Session file has correct settings. However when I start it again, all settings for input channel are reverted to Local/Black. Output settings (at least for DVS audio) are kept. For now I am manually set all inputs after each reboot but I would gladly accept a solution for it :) Thank you for your time!
would file this information as a bug :)
 
I have exactly the same issue after upgrading to 7.8.220728. I can see the .Session file getting updated with correct input settings while I change them in the app. After I close the application, the .Session file has correct settings. However when I start it again, all settings for input channel are reverted to Local/Black. Output settings (at least for DVS audio) are kept. For now I am manually set all inputs after each reboot but I would gladly accept a solution for it :) Thank you for your time!

From version 7-8-220728
- I also confirmed that this phenomenon occurs in the NC1IO supplied to our customer.
- Even the attached script file does not solve the problem.

Another problem is that the same symptom occurs with NC2IO.
The phenomenon I have experienced so far in NC2IO is as follows.

If i reboot the system after terminating the session normally, the NC2IO program will run immediately.

However, after rebooting, the Input source list is displayed as "None" because it was executed too quickly, and other sources are not visible even if you wait for a long time.
When you run NC2IO again after ending the session, other sources are displayed in the input source list, but the previously set source information is changed to "None" and must be set again.

Personally, I think the problem is that the program completes execution after rebooting before Windows services or important drivers are loaded properly.

If i run Task Scheduler and select a library to ensure that the NC2IO program runs 10 seconds after booting, an MMC error occurs. The same MMC error occurred on both NC2IO units that I checked, so I cannot change the start delay value for the NC2IO program.
- The same phenomenon (MMC error) occurs even after factory resetting two NC2IOs.

As a temporary measure, if you run the Powercell script below (a modified script received from NewTek to solve the NC1IO problem), the NC2IO program will be executed after the specified time (30 seconds) has elapsed after the system reboots.
If i reboot the system after terminating the NC2IO session normally, the NC2IO program will run after about 30 seconds and the settings before the session termination will be reflected.

$time = New-ScheduledTaskTrigger -AtLogon
$time.Delay = 'PT30S'
Set-ScheduledTask -TaskName "NC2IO" -Trigger $time

I am attaching the PowerShell script received from NewTek CS.

Best Regards
Steve Cho
 

Attachments

  • powershellScript.zip
    466 bytes · Views: 10
Back
Top Bottom