syeve issueshttps://framagit.org/ZettaScript/syeve/-/issues2022-08-01T12:41:23Zhttps://framagit.org/ZettaScript/syeve/-/issues/2Allow more settings to be set via configuration file or at runtime rather tha...2022-08-01T12:41:23ZLyam WitherowAllow more settings to be set via configuration file or at runtime rather than at compileSo I stumbled across this.
Most crates have a binary that is produced when doing `cargo build --release` or `cargo install` and the binary also typically has the distinct name (syeve) so it's harder to forget. I notice that the settings...So I stumbled across this.
Most crates have a binary that is produced when doing `cargo build --release` or `cargo install` and the binary also typically has the distinct name (syeve) so it's harder to forget. I notice that the settings appear to be in rust itself, but I'm not going to change them, so I did the following:
```
# Get source
git clone https://framagit.org/ZettaScript/syeve
# Build release binary
cd syeve
cargo build --release -p conference
# Place binary in system-wide location and rename to syeve
sudo mv ./target/release/conference /usr/local/bin/syeve
# Make sure it is treated as an executable
sudo chmod +x /usr/local/bin/syeve
# Run server
syeve server 0.0.0.0:8080
# Connect client, set compression level low, fps to 30
syeve client 192.168.1.10:8080 -c 1 --fps 30
```
I think having a configuration file or a way to set the compression settings (whether to use brotli or not) at runtime will make it much simpler for performance testing, benchmarks.
Notes:
Wayland is not supported. There's no real indication that it's not working. Might be good to catch that and stop the process because otherwise I might think that I misconfigured something.
![image](/uploads/3f23f95fc6fec85460bc26b0f0d69ebd/image.png)
Even on a fairly modern system, I don't think that high compression settings are going to be particularly useful for this application. Just for testing, I increase the FPS to a really high number and see how fast it can actually go. It might be good to run a FPS counter.
There's some blocky-ness to the output. This is probably a known issue, but if not, it may be just a gnome thing?
![Screenshot_from_2022-07-31_22-30-01](/uploads/46f7893e76223e0cdd5c8015b6ec2166/Screenshot_from_2022-07-31_22-30-01.png)
The README.md could benefit from something like "The server is the one that will have the video playing on it, the client will be sending it data"
The stream isn't particularly reliable at higher FPS such as 30 and beyond. I'll upload a video demonstrating this.
If trying to send a 4K stream, I run into memory allocation problems from trying to allocate 8.6 Zetabytes
--------------
Overall, I'm quite impressed that you were able to get such low latency out of this simple project.https://framagit.org/ZettaScript/syeve/-/issues/1error: type parameters must be declared prior to const parameters2021-12-13T17:55:54ZJourdeluneerror: type parameters must be declared prior to const parametersHi, I have this error when I try to build this crates^^.
`error: type parameters must be declared prior to const parameters
--> /home/jourdelune/.cargo/registry/src/github.com-1ecc6299db9ec823/packed_simd_2-0.3.6/src/codegen/llvm.rs:2...Hi, I have this error when I try to build this crates^^.
`error: type parameters must be declared prior to const parameters
--> /home/jourdelune/.cargo/registry/src/github.com-1ecc6299db9ec823/packed_simd_2-0.3.6/src/codegen/llvm.rs:20:54
|
20 | pub unsafe fn __shuffle_vector2<const IDX: [u32; 2], T, U>(x: T, y: T) -> U
| ----------------------^--^- help: reorder the parameters: lifetimes, then types, then consts: `<T, U, const IDX: [u32; 2]>`
`