Skip to content
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

Open
rfcohen opened this issue Dec 11, 2020 · 5 comments
Open

How to know if RAPT is running? #6

rfcohen opened this issue Dec 11, 2020 · 5 comments

Comments

@rfcohen
Copy link

rfcohen commented Dec 11, 2020

I've had success running RAPT but not so much today. How to know if it's doing anything?

./run_rapt.py -a srr3496277
RAPT is now running, it may take a long time to finish. To see the progress, track the verbose log file /Users/rcohen/rapt/raptout_c7d9dee3bd/verbose.log.

No directory created with that name. And subsequently no output (logs or otherwise).

Trying:

./run_rapt.py --test       
RAPT is now running, it may take a long time to finish. To see the progress, track the verbose log file /Users/rcohen/rapt/raptout_436562b3bd/verbose.log.

No directory created with that name. And subsequently no output (logs or otherwise).

rcohen@iMac-Pro rapt % ./run_rapt.py -v
rcohen@iMac-Pro rapt % 

And well '-v' doesn't do anything.

Thanks.

@techshine2018
Copy link
Contributor

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 -v option it should eventually print out version information (still, it needs to download and run the image).

That said, there is an undocumented switch, --do-verbose-std, to turn off the silence mode. Launch run_rapy.py with that switch will essentially fork the verbose log to the console along the way.

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!

  • RAPT team

@rfcohen
Copy link
Author

rfcohen commented Dec 11, 2020

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 -v option it should eventually print out version information (still, it needs to download and run the image).

That said, there is an undocumented switch, --do-verbose-std, to turn off the silence mode. Launch run_rapy.py with that switch will essentially fork the verbose log to the console along the way.

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!

  • RAPT team

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)

@rfcohen
Copy link
Author

rfcohen commented Dec 11, 2020

Turns out RAPT was crashing with no error reporting!

@techshine2018
Copy link
Contributor

No output even with --do-verbose-std ?

@rfcohen
Copy link
Author

rfcohen commented Dec 14, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants