Same as the test beat file in my first post
This is the original version:
Soundscapes is 100% lossless and adds zero latency. But some of the plugins are CPU hungry, and I suspect that your server may have too little.
Note that the “Bypass FX” button has been replaced by this:
Note that you need to either scroll down or enlarge your window to view the actual soundscapes config. It’s getting cut off because your window size is so small.
A good way to confirm that you server is lacking enough CPU would be to look at the logs for the JACK service. Under normal circumstances, it would not log anything after startup. If you see “xruns” it means your CPU can’t keep up.
mdickey@k1:~$ docker exec -it studio journalctl -u jack -f
Apr 02 12:39:30 k1 jack[74]: JackEngine::XRun: client = studiometers was not finished, state = Triggered
Apr 02 12:39:30 k1 jack[74]: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Also check the beginning of the log and ensure that it is running with realtime priority. If not, it will definitely cause these sort of problems.
Mar 29 04:04:31 k1 systemd[1]: Started Jack-Server.
Mar 29 04:04:31 k1 jack[74]: jackdmp 1.9.22
Mar 29 04:04:31 k1 jack[74]: Copyright 2001-2005 Paul Davis and others.
Mar 29 04:04:31 k1 jack[74]: Copyright 2004-2016 Grame.
Mar 29 04:04:31 k1 jack[74]: Copyright 2016-2023 Filipe Coelho.
Mar 29 04:04:31 k1 jack[74]: jackdmp comes with ABSOLUTELY NO WARRANTY
Mar 29 04:04:31 k1 jack[74]: This is free software, and you are welcome to redistribute it
Mar 29 04:04:31 k1 jack[74]: under certain conditions; see the file COPYING for details
Mar 29 04:04:31 k1 jack[74]: JACK server starting in realtime mode with priority 10
Also note that recording requires more CPU. Video is especially hungry, so disabling that can help. But likely the best solution would be to just provision more CPU. We give most managed studio session 8 vCPU (4 full dedicated high-performance cores) to avoid these sort of problems.
hmmm this server got 8 vcores and 16GB ram … about video card I did not look for now
arround 2GB ram loaded when I use the studio and 7GB space because software updates and security patches of docker
when I add more vcores ? how many should it be for 8 users?
-
400 GB SSD
-
16 GB RAM
-
8 CPU vCore
-
Serverstandort Wien, Österreich
-
30 Tage Geld-Zurück-Garantie
it’s only entry range
Now i have disabled „scsynth,scbroadcast,sclang“ service
Service renamed from cloud-init.target to multi-user.target
Fully disabled and stoped
This can be the issue sclang,scsynth and scbroadcast was enabled
I‘ll check it later this day … if the fx load is present ….
no this did not help to disable this services
the XRun error does not appear — so it must have enough cpu
I’ve setup a second box with 8 performance and 8 efficiency cores and 128GB RAM
but I can’t no longer connect to this box it shows me “Error: Initial TCP Connection timed out”
Did you assigned a unique local port number to the second box? Each instance of JackTrip running behind the same router needs its own local port number.
The jacktrip -o or --portoffset command-line option modifies the default UDP port (4464) for Jacktrip connections. It is essential for running multiple JackTrip instances on one machine, as each needs a unique port. Generally, increments of 10 or more are used to avoid conflicts (e.g., -o 10 sets the port to 4474).
ZHdK +3
Key Details on Port Offset
-
Default Port: 4464.
-
Function:
-o [number]changes the base port by the specified number. -
Use Cases: Necessary for multi-client servers (e.g.,
-o10,-o20) to allow separate network sockets. -
Consistency: Both server and client must use the same port offset to communicate.
-
Usage Example:
-
Server:
jacktrip -s -o 10 -
Client:
jacktrip -c [server_IP] -o 10
-
-
Available Ports: While 4464 is the default base, higher offsets like 4474, 4484, or higher are commonly used.
ZHdK +4
The port offset applies specifically to the receiving/bind port (UDP).
from the Linux box it self it works with offset(same modem)
the other modem with macOS don’t work without offset port or with Offset
it’s a special situation … I’ve got a router with 2 modem and this modems got each one ip(external) the linux box could connect to it self with the domain name … macOS not able to connect ….
it could be a provider problem … I’ve got 2 public ipv4 addresses
preparing room & measuring & connected << the first box
preparing room & measuring & connecting << the second box
it is a provider problem 
they gave me a private NAT address not a public IPv4 Address
this provider is cracking nuts all along the day
Nothing changed but for now i can reach the box via ssh
they let me crack their nuts
I‘m not really happy with my internet provider
They make more problems than I’ve got within others