Testing

[derflacco]

👋 Welcome!

Here we can discuss about the project, and fine tune it for the best experience.

[derflacco]

@VirtualGIT20 done :)

[derflacco]

@VirtualGIT20I think it's the Tegra flags in the helper again. Well, i'll nuke them, tegra don't need them anyway.
About the Go: it's heavy. Good screen, good handling, but it's heavy :| The good part is that I can avoid buying a new PC for my TV since I can dock it! Also, performance with Moonlight is astonishing!
I got the lowest performing model, the Z2 Go 16/512, for €370, almost new :)
Tested it with Tainted Grail: Fall of Avalon. With low settings I can do 40-70fps 35W, or locked 48fps at 25W custom. Battery is meh with AAA games, with only about 2-2.5h of play. The Z1E 32 Nebula was tempting me, but owning one now, 1000 cucuzze is too much for this toy. Even with a more powerful processor, these consoles are not worth more than 600€, imho. The power \ efficiency is just not there.

[VirtualGIT20]

@derflacco

I think it's the Tegra flags in the helper again. Well, i'll nuke them, tegra don't need them anyway.

Maybe that could be it, although ideally it would be great to keep the lower latency when it starts without the aggressive drop.
Also, I tested Quality a bit more and I’m happy to report that on Shield this mode works really well!
Around 1.3 ms average decoding latency and no stutters so far. I can still reproduce the issue when changing frame pacing mid-stream, but aside from that it feels pretty solid. With this frame pacing option, latency fluctuates between 0.8 and 1.6 ms, but without any noticeable stutter, which is really good for me.

Another thing I noticed on Shield is that disabling Performance Hint Manager and Prefer Big Cores seems to reduce stutters, I will try the other frame pacing options to confirm this behaviour (also, I’ll try the same settings on my Samsung devices as well)

Regarding the Legion Go: that’s a really good price you got it for!
It seems like a great device to dock under the TV while still having the flexibility to take it elsewhere. I also totally agree about pricing, and that’s exactly why I haven’t pulled the trigger on any of these handhelds yet. At current prices, especially new, they don’t feel worth it to me either.

[derflacco]

@VirtualGIT20 shame on me, i'm almost done rebuilding the new branch. It's now based on stock pacings (GPU raw might be out too), with fixes for my stuff, some of the better bits from my experimental work, plus new and more stable features. I took out the Perf Hint it helped on my X6 Pro but was too inconsistent. Also made major fixes to FSR for huge perf gains (fixed a bug), though I know you might not be using it.

[VirtualGIT20]

@derflacco

shame on me, i'm almost done rebuilding the new branch. It's now based on stock pacings (GPU raw might be out too), with fixes for my stuff, some of the better bits from my experimental work, plus new and more stable features.

No worries!
Just hoping to see "Quality" being similar to the latest build because it was almost perfect for my Shield, maybe with the fix regarding switching frame pacing.

Also made major fixes to FSR for huge perf gains (fixed a bug), though I know you might not be using it.

I am using it (EASU+RCAS) with my A52s since I've converted it to a small gaming console with Gamesir X5 Lite controller (I was nostalgic of my old broken PSP lol).
Using it with lowered resolutions (66%, so 1920x864) and enabled FSR I managed to get the decoding latency to around 5ms.
I'm still experimenting with FSR tho, I saw some strange things with grass and foliage but I need to test further.

[derflacco]

@VirtualGIT20 kek,I still own a white PSP "fat" model, stored in my drawer. I'm also using FSR on my tablet, to reduce the decoding delay. In the rework i want to optimize FSR for very low resolutions (e.g., 960x600 to 1920x1200), which is challenging. I expect to achieve acceptable results eventually this was the main motivation for integrating FSR.

Just hoping to see "Quality" being similar to the latest build because it was almost perfect for my Shield, maybe with the fix regarding switching frame pacing.

About quality pacing in that build, essentially is the same as "Max Smoothness" in stock Artemis \ , but it utilizes the experimental Artemide renderer. Therefore, the experience may differ in the upcoming rework (I'm curious to hear your feedback).
Ps. if you want a preview:
https://fromsmash.com/Artemide-rework

[Prostoy-user]

Thank you for your work. Does the latest release on GitHub (test) include these fixes?

[derflacco]

No, but its not a fix, is just a revert for test :)

[BaidDSB]

Which version would you suggest for Helio G99???

[theloouis]

@theloouis about cpuboost i ve already noticed that, and fixed it. https://fromsmash.com/Artemide-rework-fixcpuboost note: lfr disabled in this build, as it not needed anymore with other changes i made

well, I haven't done any extensive comparison but now it seems balanced works best without anything, no FSR, GI or boost ... just plain balanced with 60fps. even boost seems to introduce more noticeable skips

GPU Raw still works wonders @120, with GI and with or without boost... however, those 10-11ms (without CPU boost) was probably something on background boosting the clocks... now it stays at 13-14ms (tested both versions from your links)

I think I'm going to settle with 2 profiles for 60 and 120 and use them when according to the game I'm playing

All testing done at 1340*800 at 30Mbps.

[derflacco]

Overall, this GPU Raw setup I mentioned is the best result, pacing and decoding wise, I had since you started your wonderful work on the Mediatek issues. I'll tinker a bit more with 60FPS + GPU Raw latter... but if it's something you can solve on your side ,I'd say the G99 situation is as good as it will get.

For better 60hz streaming with gpuraw (or non balanced pacing), you'll need to set also a frame limiter on the host.
You can do it with rivatuner, fpsmon, or amd\nvidia\intel arc control panel

[theloouis]

Alright, I don't really know how to even start troubleshooting this.

I installed 6.5.1 over the first sync stable branch to compare FSR and balanced configs. I used the balanced equivalent from this version adaptx vsync and to my surprise I had the smoothest pacing yet, I had FSR turned off at this moment.

Then some hours later I went without changing anything and the pacing started to behave like on sync stable. Even the decoding times went up2, 3ms.

Something similar happened when I installed the first rework over 6.5.1.... do you have any ideia what would cause this?

[derflacco]

Sorry, i ve missed this. Maybe something host side? If it does again try to reboot apollo/sunshine. Wich device you are testing with?

[theloouis]

@derflacco so I'm okay with the latency till about 15ms. On Artemis test 3

The tab is galaxy a11 with 8gb ram helio g99. And has 90hz, 1340x800.

What I am doing now is doing 2000x1200 at 90hz with 80 mbps bitrate.

And using cpu boost. It's doing 13-14 ms decode.

If I do 1800x1080, everything else same, the decode is 11-12ms.

So... Anything i can do? Not using fsr.

Hello @BaidDSB , just out curiosity, could you report the refresh rate of your display when using this test https://testufo.com/refreshrate

Thanks in advance.

[derflacco]

Hello everyone!
Happy new year!

If someone wants to test, this is what im currently working on:

Artemide stable:

Started from scratch, and I mean really from scratch,removing unsafe and extremely experimental commits along the way.

• Removed LFR, no longer needed.
• Stock pacings
• GPURaw
• Tons of FSR fixes aimed at reducing the toll on the hardware.
• Fixes for FastGL (the old Direct Present).
• Nuked CPUAffinity; without root it is impossible to achieve correct pinning (anyway, from Android 12+ CPUsets are blocked under SELinux, so it is really useless).
• Lighter CPUBoost, same effect.
• UI/Overlay tweaks.
• Conservative performance tweaks.

What's new:

• E2E latency: In my fork, I expose pure decoding latency to see the effect of my changes directly on the decoder. With E2E ("Delay" in Perfoverlay Mini), we also account for network and jitter.
• Overlay glyphs: This is mostly for me while testing. When enabling Lite Mode, you will see some letters on the right: for example, R if you have GPU Raw enabled, B for Balanced, S for Max Smooth, etc.

In the experimental branch, I've reintroduced Async Decoding, and I'm forcing the OpenGL path via FastGL.

Async Decoding is used in ChromeOS, for example, and in combination with FastGL it yields really good results, better than standard Sync decoding. This results in a bit more input latency but in much better pacing.

For now, to reduce my stress, in the experimental branch I'm forcing GPURaw and exposed an in-app button to force VSync (basically Balanced Pacing).

I also made a fix to make GPURaw work with non-standard display Hz (e.g., 59.94).

link:
https://fromsmash.com/artemide-020126

[derflacco]

@VirtualGIT20 Buonasera! Thank you as always for all the testing!

• Smoothest works well, with minor to no microstutter. I was able to set the dequeue value to 1500 without running into progressive latency buildup issues.
• Balanced and Balanced FPS don’t work well for me, showing constant stutters and presentation issues. Enabling fastVsync doesn’t seem to change the behavior.
• Low Latency works reasonably well, with occasional stutters and hiccups. I tried enabling both VSync and fastVsync to mitigate those, but they don’t seem to make much of a difference. Still, it’s not too bad overall.
• GPU Raw behaves similarly to Low Latency; in this case, fastVsync seems to help slightly.

For Min Latency / GpuRaw, try setting it to 500µs it really helps with microstutter. CapFps is honestly terrible; I don't even test it, as it performs poorly even with Moonlight/Artemis on my S20 FE, which is otherwise excellent at streaming.
I don’t understand why Tegra “hates” Balanced mode, which is actually the best pacing we have it uses Android’s Choreographer (fantastic at what it does!), and it works wonders on my low-end devices.

Overall, with this version with Smoothest is very usable, although still a bit slower than the sync version. I’m using a laptop as a latency reference, and the sync branch feels to me closer in terms of responsiveness.

Because I'm forcing Fast GL (direct present) in the async branch, which inherently adds more input latency. I'll make it a user choice again. I had only forced it to get more feedback and to further test the GL path ,the one that enables FSR in my fork.

I wanted to ask, do you have any insight into why the Shield behaves this way? From Moonlight to Artemide, the fundamentals seem consistent: Smoothest and Low Latency work best, while Balanced tends to have issues.

Perhaps the issue lies between Choreographer and surface presentation they might not be properly aligned. To be honest, without locally checking the logs, I can't pinpoint the exact cause. For example i've discovered that:
My Poco X6 Pro with a Dimensity 8300 Ultra can't stream correctly at 120Hz, as it only renders between 108 and 112 fps while spamming in the logs:
BLASTBufferQueue: acquireNextBufferLocked: Can't acquire next buffer. Already acquired max frames 4 max:2 + 2
The only workaround is to stream at 60 or 90Hz, which honestly sucks, and i can't really do much to mitigate it (maybe only request 90hz refresh, if it's possible).
Btw, you can try with MinLatency @ 500us + FastVsync?

[VirtualGIT20]

@derflacco Buongiorno!

Btw, you can try with MinLatency @ 500us + FastVsync?

Tested MinLatency with 500us and honestly it didnt make that much of a difference compared to higher dequeue values.
Also tried 500us + FastVsync and I noticed that occasionaly the stream begin to stutter for some time (also experiencing i/r fps drop), then back to normal.
What is interesting to me is that using MinLatency + ImmediateFrameDelivery (0us) the stream is more consistent and less prone to microstutter.

Have a good day!

[BaidDSB]

can you redo the in streaming settings?

@BaidDSB It's alot of work, and can introduce so many bugs that i won't do it anymore sorry.

Is it possible for a button combination to get the performance counter and full keyboard?

I use reWASD to access the full Windows keyboard while streaming. Alternatively, you can enable the on-screen keyboard gesture in the app settings. Using a button combination may conflict with alot of things during a stream. You can still enable it from the back menu under Advanced Settings.

what about the performance counter? sometimes enabling or disbling it interfers with a game and kicks me out and stops the game itself

[derflacco]

For performance counter what do you mean?

[BaidDSB]

For performance counter what do you mean?

the stats. the decoding times, frame times etc.

[Zayr64]

I cant enable FSR 1 on the lastest Artemide build, i tried using the lower suggested resolution and it still does not enable itself. Any idea of what im doing wrong?

[derflacco]

@Zayr64 I can on my devices, note that FSR will be grayed out when HDR is enabled, because the two are not compatible.

[Zayr64]

I am indeed using HDR. You think using FSR 1 from Lossless Scaling would help as well?

[derflacco]

I will not be the same. But you can try :)

[derflacco]

Hello everyone! Did something about the ui:

APK

Let me know your feedback :)
Ps: you may find bugs, as it's a total rewrite of the ui. Let me know!

[Zayr64]

Pretty nice changes. I noticed some cropped settings on my Galaxy S25+.

[Zayr64]

The ordering on the video resolution is not that great, why not do like the video frame pacing menu?

Separate by default (720p, 1080p), native (3120x1440), custom and lower native (56% for example)?

While also changing do descending order.

[VirtualGIT20]

Hi @derflacco!

I finally had the chance to take a look at the new UI, and I really like the idea of organizing options into different sections, overall it feels much cleaner and more structured.

That said, for me there might be a bit too much nesting between menus and submenus. Maybe some sections could be grouped a bit more, while still keeping the current section titles. For example, I was looking for the four-finger tap option for the full keyboard under “On-screen keyboard & special keys”, but it was actually under On-screen controls.

Another thing I noticed is that some pages are missing a visible “title”, like the main settings page and the controls page have. Adding those might help with orientation.

Overall though, the idea is really good, and once it’s fully polished I think it can become a very nice and much cleaner than before.

P.S. I noticed there are options for async and sync decoding, are those already ready to be tested, or are they still work in progress?

As always, great work!

[derflacco]

@VirtualGIT20
Hello there! (Definitely not a Star Wars reference, lol)
That UI ended up being way too deeply nested. It was a lot more work than I expected (I didn’t realize it would get this heavy), and it also broke too many things, so I unfortunately dropped it.
Now I’m thinking of doing something much simpler: a single “Artemide Tweaks” tab. I don’t want to overcomplicate the app especially because this damn carpal tunnel doesn’t let me spend the time I’d like on the project. And honestly, the UI is important, but I’d rather focus my energy elsewhere.
The build I’m working on is completely unlocked: you can choose async or sync freely. I also brought back “Prefer lower delays” for async (LFR). Before I was forcing it on, but it’s probably better to make it a preference again. I’ll ship stock, safe defaults for people who don’t want to tweak anything, while still letting advanced users customize whatever they want.
I think this is the best approach for now at least until, with your help, I understand what’s actually worth keeping and what isn’t. In the end it’s true that I’m building it, but I rely a lot on your feedback too :)
That’s also why I unlocked sync/lfr/etc again: so we can figure out whether async really brings benefits or not. As soon as I’m back on the PC, I’ll post a testing APK here :)

[VirtualGIT20]

The build I’m working on is completely unlocked: you can choose async or sync freely. I also brought back “Prefer lower delays” for async (LFR). Before I was forcing it on, but it’s probably better to make it a preference again. I’ll ship stock, safe defaults for people who don’t want to tweak anything, while still letting advanced users customize whatever they want.

Completely agree on the approach, and also I think that it might be beneficial to understand what works on which device.

I think this is the best approach for now at least until, with your help, I understand what’s actually worth keeping and what isn’t. In the end it’s true that I’m building it, but I rely a lot on your feedback too :)
That’s also why I unlocked sync/lfr/etc again: so we can figure out whether async really brings benefits or not. As soon as I’m back on the PC, I’ll post a testing APK here :)

Happy to support the development and honestly I have fun testing and learning.
Lately work has been a nightmare but I will try to do my best to give my feedback as soon as I can!

[BaidDSB]

@derflacco i have a separate request as well. can you look into this https://github.com/wjbeckett/artemis ?

i use this heavily on my pc to connect to another PC, and i think it can be improved.

[derflacco]

Will definitely try it on my legion go S, but I dont think I will try to mess with it, i dont have the time frankly :)

[mastersteak]

Posting here to add another Nvidia Shield stuttering data point, for those who come after.

I was having significant intermittent stuttering issues on v20.3.0-experimental.9 for many months, to the point where I thought this was the nature of the Shield and game streaming. I put up with it as it otherwise worked.

Switching to Artemide_Experimental_Async_0.2 has been stutter free on as-is settings, running 4K60.

"Downgrading" to v20.2.6 also fixed the issue, but I'm happily running Artemide_Experimental_Async_0.2 for now.

Thank you!

[derflacco]

Hello! Glad it works good for you too :)

[BaidDSB]

@derflacco whats your plan when google wants you to sign something for artemide?

[derflacco]

Hello, you should be able to install the APK via ADB anyway. Let’s see what happens first.

[latency99]

Thank you for your excellent work.
I tested your fork on two of my devices: the Oppo Find X9 and the Google Pixel 7.
I have a question: can the network latency be reduced? On the Pixel 7, it seems perfect with 2ms network latency.
But on Find X9, a 2025 flagship, the network latency is around ~10ms, which is terrible. Both devices use Wi-Fi 6, 5GHz band.

[derflacco]

Hello, every device behaves differently. You can try disabling aggressive wifi background scanning on the Oppo. There’s not much I can do about that. Eg: for some reason, my G99 tablet has lower network latency than my X6 Pro and S20 FE. Try tweaking the bitrate and resolution settings. :)

[latency99]

That's weird. On my Find X9, when I leave everything idle, the network latency is 3ms, but when I move, it jumps to 10ms.