A new version of Snickerstream has been released, see the new thread over here!
-------------------------------------------------------------------------------------------
(I've posted this a while ago on /r/3dshacks - here - but people told me it was a good idea to post it here too - so here it is!)
If you're asking yourself "Why" or "How is it different than kit-kat/NitroStream" then please read this entire post: there are some very important reasons.
Note: This build is a Proof of Concept, and as such it should be considered highly incomplete. The main streaming functions work fine, but lots of features simply aren't implemented yet, the client might be buggy and the GUI might not be that much user friendly. This release is meant to prove that this client works, and also to give you a general idea of the project could become once complete.
Snickerstream is a completely new streaming client for NTR CFW. It aims to become a complete NTRViewer replacement with lots of extra features, including stuff such as better netcode, more screen layouts and less RAM usage. This is different than kit-kat/NitroStream as the formers still use NTRViewer as its internal streaming client while Snickerstream has been completely written from scratch, making it the first real NTRViewer alternative.
Now, I hear you ask, why reinvent the wheel? Why make this if there's already something that does a very similiar thing?
The reason is simple: I wanted to add some functions to NTRViewer, but some of the stuff I had in mind simply wouldn't be possible without altering its source code, and considering that NTRViewer wasn't properly updated in a while I took the opportunity of making this complete rewrite.
Here are some of the improvements of Snickerstream over NTRViewer that are already implemented:
Releases / Source (GitHub)
IMPORTANT NOTE: THERE'S A BUG THAT PREVENTS SNICKERSTERAM FROM RECIEVING FRAMES ON COMPUTERS WITH MORE THAN ONE NETWORK ADAPTER. Howerer, there's a workaround: read "MultipleNetworkAdaptersFix.txt".
Also, before reporting bugs, please read the Known Issues file!
Useful links:
Tutorial / Keyboard shortcuts / Known Issues / Multiple Network Adapters Fix
-------------------------------------------------------------------------------------------
(I've posted this a while ago on /r/3dshacks - here - but people told me it was a good idea to post it here too - so here it is!)
If you're asking yourself "Why" or "How is it different than kit-kat/NitroStream" then please read this entire post: there are some very important reasons.
Note: This build is a Proof of Concept, and as such it should be considered highly incomplete. The main streaming functions work fine, but lots of features simply aren't implemented yet, the client might be buggy and the GUI might not be that much user friendly. This release is meant to prove that this client works, and also to give you a general idea of the project could become once complete.
Snickerstream is a completely new streaming client for NTR CFW. It aims to become a complete NTRViewer replacement with lots of extra features, including stuff such as better netcode, more screen layouts and less RAM usage. This is different than kit-kat/NitroStream as the formers still use NTRViewer as its internal streaming client while Snickerstream has been completely written from scratch, making it the first real NTRViewer alternative.
Now, I hear you ask, why reinvent the wheel? Why make this if there's already something that does a very similiar thing?
The reason is simple: I wanted to add some functions to NTRViewer, but some of the stuff I had in mind simply wouldn't be possible without altering its source code, and considering that NTRViewer wasn't properly updated in a while I took the opportunity of making this complete rewrite.
Here are some of the improvements of Snickerstream over NTRViewer that are already implemented:
- Real time screen scaling (you don't need to restart the client anymore to scale up/down the screens)
- Pixel interpolation, which improves image quality if the window has been scaled
- Way less RAM usages (about half less than NTRViewer and around a quarter of kit-kat)
- Better netcode, it will automatically try to recover any lost frames if needed
- No DLL files needed, as it uses the Windows API to draw the GUI and GDI+ to draw the screens (keep in mind that kit-kat still uses DLLs, they just get extracted to a temporary directory)
- Native x64 version, for better performance on x64 computers
- More options that will make Snickerstream work better on crappy computers or networks
- MANY more screen layouts, such as single screen with popup secondary screen or multiple window mode
- Universal NFC patch
- Borderless fullscreen
- Screenshot function
- A function to ignore top/bottom screen frames, which will mean better performance on games that rely a lot on just one screen
- (Maybe) AVI recording function directly in the client
Releases / Source (GitHub)
IMPORTANT NOTE: THERE'S A BUG THAT PREVENTS SNICKERSTERAM FROM RECIEVING FRAMES ON COMPUTERS WITH MORE THAN ONE NETWORK ADAPTER. Howerer, there's a workaround: read "MultipleNetworkAdaptersFix.txt".
Also, before reporting bugs, please read the Known Issues file!
Useful links:
Tutorial / Keyboard shortcuts / Known Issues / Multiple Network Adapters Fix
Last edited by RattletraPM,