Replace SudoVDA with VDD? Or at least let us choose which to pick?

[psorincatalin]

I see that VDD now has a GUI for better management of the virtual displays. I am streaming 4k@120 fps and I have an animated wallpaper. SudoVDA seems to stutter a bit when there are multiple particles on screen so I did a test and replaced it with VDD, which works without frame dips. However, I miss the integration that SudoVDA has with Apollo/Artemis so I had to revert it back to SudoVDA. Wouldn't it be a good idea to chose which Virtual Display Manager to go with?

[ClassicOldSong]

No. VDD has known and unresolved performance issues, it's just random whether you met stutters with either solution.

VDD has pretty poor implementation, that's why I started with a fork of it but later re-write completey.

If you're on an AMD system, you can try install 0.3.7-hotfix.1 to see if it's better. I'll release a newer version with optional frame pacing config for the stuttering issues emerged from 0.4.0.

[ClassicOldSong]

Usually preople only use one virtual display which doesn't expose the problem much.

While Apollo originally started as Widecar and I only intended to use it for remote desktop, multi-stream is a requirement and Apollo actually does it well with multiple instances. I plan to separate the capturing and encoding out from session management someday but your're already separating WGC out, which might be a good starting point.

[Nonary]

Sounds great, looking forward to it!

Well, it turns out I won't be contributing towards sunshine anymore. Let's just say me and RA don't get along very much anymore... it's a long story but that's beside the point. I'm sure you're all to familiar with that situation. And yeah I also got banned from his discord lol

Anyways I'm going to be creating a new fork called JANUS

I was sort of inspired by you, since you named it after Apollo.

Basically I have big plans for sunshine, such as integration with Playnite (such as automatically syncing recently played games to sunshine itself) and also rewriting the entire frontend and configuration handling.

I'll submit a PR with my windows graphics capture changes.

But I would love your opinion on how I should branch out my features in the future.

Basically I'm going to be changing A LOT of the original code, but I also don't mind if other forks use my code or not I just need some guidance on how I should use that from a git standpoint? I don't want to make my changes unmanageable to where it can't be easily merged despite rewriting most of the codebase.

Can you add demon.cat to your discord, I'd like to discuss further if you don't mind?

[ClassicOldSong]

And yeah I also got banned from his discord lol

LOL

Anyways I'm going to be creating a new fork called JANUS

Why not working together on Apollo? There's no need for a more fragmented community. I have big plans too, working together can make all the good things better.

I have considered Playnite integration but there're future problems like what should we integrade on Linux and macOS, and the current game list implementation is not suitable for loads of games, which means there need client side changes as well. Luckily Artemis Desktop now already have people working on, so we can make bolder changes in the future without worrying about compatibility.

My handles are mostly the same everywhere so you know how to find me on Discord.

[Nonary]

And yeah I also got banned from his discord lol

LOL

Anyways I'm going to be creating a new fork called JANUS

Why not working together on Apollo? There's no need for a more fragmented community. I have big plans too, working together can make all the good things better.

I have considered Playnite integration but there're future problems like what should we integrade on Linux and macOS, and the current game list implementation is not suitable for loads of games, which means there need client side changes as well. Luckily Artemis Desktop now already have people working on, so we can make bolder changes in the future without worrying about compatibility.

My handles are mostly the same everywhere so you know how to find me on Discord.

My intent is not to fragment the community but basically I need my own fork because I need my own sandbox in a sense where I can do whatever I want without approval from anyone else. I don't want to be tied up in code reviews in the sense where most of the complaints is something trivial like doxygen usage (that literally nobody reads). Or the infamous "oh nothing is wrong with your code, it's just not how I would have done it" type of reviews.

There's just too much to work on that I need to have that authority to stay sane basically.

Sunshine or Apollo is more than welcome to merge in my code changes if they wanted though, I just wouldn't be actively involved in that.

[ClassicOldSong]

basically I need my own fork because I need my own sandbox in a sense where I can do whatever I want without approval from anyone else

That's what git solves with branches

You can keep your own experiments in different branches and make them easier for other branches to merge back, or track changes from different branches

Speaking of code review, it is necessary to keep the basic maintainability of a project so everyone has to bear with it somehow, but I won't request way too tedious changes to code style or subtle implementation disagreements, these parts I can fix myself, unless they're way too widely disturbing.

I know this is a pain of crowd sourced development but due to the nature of it, there's no good way to handle the problem unless the project is backed by a funding and not really open for contributions.