eeva/jamulus
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

added a comment regarding using and old OPUS version (#252)

Browse source
This commit is contained in:
Volker Fischer 2020-05-22 18:52:25 +02:00
parent 50a9cb51ab
commit e014301b58
2 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
ChangeLog
View file

@ -19,6 +19,9 @@
- save client settings on Linux cmdline termination signal, coded by pljones (#70) - save client settings on Linux cmdline termination signal, coded by pljones (#70)
TODO in mono mode we should not show the Pan controls

10
distributions/raspijamulus.sh
View file

@ -1,6 +1,16 @@
#!/bin/bash #!/bin/bash
# This script is intended to setup a clean Raspberry Pi system for running Jamulus # This script is intended to setup a clean Raspberry Pi system for running Jamulus
# Regarding the old OPUS version (#252): I just tried out the following:
# * Do not use OPUS in shared library but use the version which is included in the jamulus source code:
# instead of 80 % load I get 90 % load on my Raspberry Pi Zero
# * Do not use OPUS in shared libaray but use the version which is included in the Jamulus source code
# but try to compile in fixed-point: I get compilation errors so this is not possible right now
# * I replaced the opus-1.1 with OPUS="opus-1.3.1" in the raspijamulus.sh -> OPUS version 1.3.1 has a
# known bug with the custom interface. If I use that version as a shared libaray, I get a runtime error
# on starting Jamulus. So this is also not possible. We have to wait for the next official OPUS version.
# Therefore it is the best to keep the opus-1.1 version.
OPUS="opus-1.1" OPUS="opus-1.1"
NCORES=$(nproc) NCORES=$(nproc)