There is a ‘server’, which is the 3rd component of the Application. (It runs locally and does the database and transcoding and all that.
Might it not be starting for some reason? (broken sample) (blocked by virus checker or malware protection)?
Player opens without issue or complaint.
There is a log file.
Here:
C:\Users[YOURUSENAME]\AppData\Local\Syrinscape\Syrinscape SoundSet Creator
It’s called “server”
You might have to set:
enable_server_logging = true
in the config file
playing a game with friends atm, will be done in ~20 minutes. I’ll check it then.
1 Like
Coolies.
Definitely check out the:
A broken sample is stopping Syrinscape from starting
Here:
Here’s a screenshot to help explain. Changed “enable_server_logging =” to true and restarted the creator. No log entries. Also don’t have a creator icon in the system tray (seems like that was a thing last time I used it).
I’ll try the sample issue workaround next.
Out of curiosity, the local-server component… what’s the filename for it’s executable? Wanted to look for it in the process list. (BTW, I’m a professional computer tech so I can dig into the technical stuff)
Looked through the DB, none of the rows in soundsets_sample are lacking a transcoded_audio_file entry
Mysterious…
If there’s no tray icon then it looks like the server component is not running at all. Interesting.
I’ll have a root around for the process name. 
Ok so I seem to have solved the problem but I’m having a hard time seeing how the cause relates to the effect.
I re-downloaded the creator installer and run an on-top install (didn’t uninstall first). Once I did that the problem was resolved. And now that I think about it I had to do this once before.
As you said, it’s somewhat mysterious.
btw the server process appears to be “Syrinscape SoundSet Creator.exe” while the status window applet thingy is “player.exe”
Maybe you’re needing admin privileges to run it?
So , right click on the shortcut and select:
“Run as administrator”?
…maybe? 
hmm, I duno. I shouldn’t. I made a point not to install it to Program Files specifically to avoid that scenario. Installed it to D:\Apps\Installed\Syrinscape\ instead. But I dunno what it’s accessing and all.
Next time this problem happens I’ll try that.
Nope, running it as admin doesn’t prevent the problem. Reinstalling only seems to fix the problem every few times I do it.
Is it possible to have too many samples? I downloaded a lot of sound sets to build a library of various elements I could start from…
At what point do you have to reinstall to get it going again?
Have you checked if the problem occurs on different browsers?
You’re absolutely positiv that it isn’t any security measure interfering?
How much are a lot of soundsets you have installed in the creator?
36 sound sets
I’ve done further playing around and noticed I the shortcut on my taskbar was targeting “player.exe” and not “Syrinscape SoundSet Creator.exe.” For some reason this is only a problem some of the time. Usually when “player.exe” is launched it also runs “Syrinscape SoundSet Creator.exe.” Apparently something happens that breaks this behavior and a reinstall fixes it with poor consistency. I changed the shortcut to launch “Syrinscape SoundSet Creator.exe” instead and it now runs both itself and player.exe consistently. So, for clarity, launching “Syrinscape SoundSet Creator.exe” reliably runs both required processes while launching “player.exe” does not.
The reason this is a problem is this: In windows 7 and newer the standard approach to creating a quicklanuch icon in the taskbar is to launch the application you want a quicklaunch icon for, right click on its icon, and select “pin to taskbar.” When attempting to create a taskbar/quicklanch shortcut for syrinscape creator, however, the only process visible in the taskbar is player.exe. The obvious/simplest solution would be to make sure that if player.exe fails to connect to the server component it checks if the server component is running locally and launches it if not. This would improve usability on Windows 7 and newer systems.
I meant what happened before the message you mentioned in the OP occurred? In post 15 you said that over installing solved the problem for a while. But obviously it came back. What happened before that? If it worked then,something must have changed later.
Could it be started only once and upon next start the error reoccurred?
It is strange though that you seem to be the only one getting that erratic behaviour of the Creator. Can you give more details of the system you’re running it on?
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.
Hi, same thing happened to me. I haven’t been able to solve it yet. I tried re-installing several times with no success.
I’m no computer tech, so any suggestions of how I can fix this? Or at least what can I try?
Thanks!
Are you running Windows 10, too? Do you get the exact same error message? Also - did it work for you at any time or haven’t you been able to start the Creator ever? Have you checked, if you can log in into the regular website?