Failed to load tracks from Json config file

General Elk Discussion
1

Hi everyone. I have made it far enough to load my board with the ISO and log in. However, when I try to start some of the synths I get the following error:

Failed to load tracks from Json config file

I am a bit confused as to why this would occur. Im just trying to call the plugin examples that come preloaded on the OS. Is this a common issue/error? How do I get around it? My goal is to connect the synth to a midi controller I have connected so I can get audio out. Any help would be greatly appreciated.

Shaikat

2

Hi @shossa3,
could you please copy here the output of /tmp/sushi.log, the JSON you are using and the command line?

3

Hi @Stefano,
I’m having similar issues. I’m trying to run Sushi on Linux following instructions on this link.

When I try to run this command:

$ ./Sushi-x86_64.AppImage -j --connect-ports -c config_files/play_vst3.json

I get the message:

SUSHI - Copyright 2017-2022 Elk, Stockholm
SUSHI is licensed under the Affero GPL 3.0. Source code is available at github.com/elk-audio
Failed to load tracks from Json config file

This is the /tmp/sushi.log ooutput:

[2023-12-05 17:20:46.075] [warning] #############################
[2023-12-05 17:20:46.075] [warning]    Started Sushi Logger!
[2023-12-05 17:20:46.075] [warning] #############################
[2023-12-05 17:20:46.080] [info] [plugin_library] Setting base plugin path to: /tmp/.mount_Sushi-IJrVdH/usr
[2023-12-05 17:20:46.082] [info] [jsonconfig] Setting engine sample rate to 48000.0
[2023-12-05 17:20:46.082] [info] [main] Setting up Jack audio frontend
[2023-12-05 17:20:46.105] [info] [engine] Track main successfully added to engine
[2023-12-05 17:20:46.105] [info] [engine] Connected engine output 0 to channel 0 of track "0"
[2023-12-05 17:20:46.105] [info] [engine] Connected engine output 1 to channel 1 of track "0"
[2023-12-05 17:20:46.108] [error] [vst3] Failed to load VST3 Module: /tmp/.mount_Sushi-IJrVdH/usr/mda-vst3.vst3 is not a module directory.
[2023-12-05 17:20:46.108] [error] [engine] Failed to initialize processor mda JX10 with error 8
[2023-12-05 17:20:46.108] [info] [processor] Destroyed processor 1()

Json I’m using:

{
    "host_config" : {
        "samplerate" : 48000
    },
    "tracks" : [
        {
            "name" : "main",
            "channels" : 2,
            "inputs" : [],
            "outputs" : [
                {
                    "engine_bus" : 0,
                    "track_bus" : 0
                }
            ],
            "plugins" : [
                {
                    "path" : "mda-vst3.vst3",
                    "name" : "mda JX10",
                    "type" : "vst3x",
                    "uid" : "mda JX10"
                }
            ]
        }
    ],
    "midi" : {
        "track_connections" : [
            {
                "port" : 0,
                "channel" : "all",
                "track" : "main",
                "raw_midi" : false
            }
        ],
        "program_change_connections" : [
            {
                "port" : 0,
                "channel" : "all",
                "plugin" : "mda JX10"
            }
        ]
    }
}

Thanks!

4

Thanks for the logs @drajina .

The issue is that the path in that example are relative (e.g. mda-vst3.vst3), and by default a normal Linux build will use the CWD for the basepath.

However, the AppImage sandboxes the CWD under that path that you see in the logs - in that case, try to pass the option --base-plugin-path to Sushi giving it the absolute path of the parent directory where you have the MDA plugins.

1 Like
5

@Stefano
First of all, thank You for such a prompt reply!

The problem with the option You suggested is that the path from the logs is created during runtime, and one part of the directory name is randomly generated each time I run the AppImage:

/tmp/.mount_Sushi-IJrVdH/usr
                  ^~~~~~^

So I can not know the path name in advance.

6

Hi @drajina, the path that you need to specify is the absolute path of your Linux system where you have the MDA plugins.

So for example, assuming that you have downloaded them under e.g. /home/foo/mda-vst3.vst3, you need to use

--base-plugin-path=/home/foo