New Tool (3.1) Sononym Integration (PREVIEW)

#22

Okay Meef, some things to mention. Firstly make sure you’ve run (and created a library etc) in Sononym (to create the query.json file in the .config/Sononym/ directory.) Also make sure that you type your paths (and filenames) 100% correctly first time in this tool (in fact what I’d do is uninstall this tool, reinstall the tool and start from scratch.)

(Meef Chaloin) #23

Unfortunately it’s still the same for me. Uninstalled the tool, deleted my sononym directory, added a library, used the library, reinstalled the tool, set the paths and still says I need a valid config path. What was the other fix?

(lilith) #24

I also get an error message when the auto activate feature is enabled:

and RENOISE also freezes

(lilith) #26

Thanks I’ll try what you did! :grinning:

(Meef Chaloin) #27

Weird, I just went back to check my paths were indeed correct and before I changed anything it was working. Cool, thanks for the tips 4tey. Still would be nice to have drag and drop though.

(lilith) #28

Now it works! Thanks a lot! The trick was to give the pass to exe as

/home/marco/sononym-1.0.4/sononym

where the last “sononym” points to the program.

Great :slight_smile:

(lilith) #29

Renoise freezes when Sononym is closed and you start Sononym from the Sononym Integration Renoise-Tool. When you close Sononym Renoise is unfreezed again.

When starting sononym by hand from the terminal it works.

#30

Might be because os.execute is blocking (with Linux). You could specify os.execute("/path/to/program/sononym &") to execute the process in the background.

(danoise) #31

Renoise freezes when Sononym is closed and you start Sononym from the Sononym Integration Renoise-Tool. When you close Sononym Renoise is unfreezed again.

The way the tool currently works, this is to be expected: you need to start Sononym before making use of the tool. This is explained in a “show-once” dialog, but might indeed not be sufficiently clear.

You could specify os.execute("/path/to/program/sononym &") to execute the process in the background.

Woot, interesting. I’m definitely no linux expert - the ampersand is doing what, exactly?

#32

It will fork and execute the process in the background for you, so the os.execute call won’t block. You can see the effect simply. If you ever run a unix style os danoise you can try it yourself. Under a bash shell if I type:

$ ./sononym

This will start Sononym, but (naturally) notice that it won’t return control back to the shell until the user quits Sononym. However if I write:

$ ./sononym &

The shell will now start and fork Sononym, so it will immediately return control back to the shell and you will have Sononym running** :slight_smile:

Bit of trivia: The Amiga Workbench shell/cli had a similar mechanism using a command called ‘Run’ https://wiki.amigaos.net/wiki/AmigaOS_Manual:_AmigaDOS_Command_Reference#RUN

** Note that any stdout messages output from Sononym will also be mixed into the terminal shell :slight_smile:

(lilith) #33

Thanks for the answers, I didn’t have time to make a test.