Nothing specific. I shut down creator when I was done using it and then next time I tried to start it up I got the problem described. I agree something must have changed but whatever it was is quite opaque. It does seem like after the first time I launch creator the next time I launch it with player.exe it has the above problems.
The system itâs running on is a Intel Core i7-6700 with 16GiBs of ram. I have an 120GiB SSD for my windows drive and a 6-drive raid-10 array totaling 6TB for storage. I use a dedicate raid card to handle the raid array for performance reasons (I need high sequential write throughput for real-time lossless video recording). The system runs Windows 10.1 Pro 64bit. Anything else specific?
Like I said, I believe the issue was âuniqueâ to me because I was launching via âplayer.exeâ instead of âSyrinscape SoundSet Creator.exe.â When I created the quick launch shortcut I did not realize the creator was actually two separate processes working together.
But the approach I used for creating said quicklaunch shortcut is pretty standard and Iâd assume anyone else that does the same would have similar problems. I can only assume no one else has done so. From experience a lot of your average computer users donât realize they can pin shortcuts to the taskbar for quick access.