-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to know if RAPT is running? #6
Comments
This silence mode behavior of RAPT is by design due to some feedback complaining the output to std is too lengthy and annoying. It could take some time (download the docker image) before the output directory is created and logs start to populate. But with That said, there is an undocumented switch, Sorry for the inconvenience and thank you very much to try our product. Please visit us frequently for new releases with more features and greater usability!
|
Really, no feedback is generally bad design. I don't know if it's working or not. It didn't even create the output directory after several hours. There was no obvious process running. IMO it was dead. I will try again with the --do-verbose-std flag. (Maybe that should be un-undocumented just to see if it's working/doing anything) |
Turns out RAPT was crashing with no error reporting! |
No output even with --do-verbose-std ? |
Didn't try with the --do-verbose-std. It started to work better and produce output. May have been a docker issue. Nonetheless, failing silently != good. |
I've had success running RAPT but not so much today. How to know if it's doing anything?
No directory created with that name. And subsequently no output (logs or otherwise).
Trying:
No directory created with that name. And subsequently no output (logs or otherwise).
And well '-v' doesn't do anything.
Thanks.
The text was updated successfully, but these errors were encountered: