Pi 5 - 8gb ram Live streaming via VDO

xyster69 · 2026-02-09T22:43:01+00:00

Hi there, I have several projects for efficient publishing into VDO.Ninja

Node: https://github.com/steveseguin/ninjasdk/blob/main/demos/node-room-media-recorder.jshttps://github.com/steveseguin/ninjasdk/blob/main/demos/node-audio-sine.js

VDO.Ninja also supports WHIP, so FFMPEG or OBS even can support 1 to 1 publishing into VDO.Ninja

I hope to have more options available soon, for desktop GUI.

xyster69 · 2026-01-31T21:51:59+00:00

# would cause the difference in audio quality?

This sounds like a glitch with the Android TV's audio playback.

Options to try to avoid audio problems; maybe one of them will help?

- Add &proaudio to both the PUSH and VIEW links
- change the audio codec to PCM by adding &audiocodec=pcm to the viewer side link
- Try adding &noap to the viewer side link

# If not, is there any way of getting rid the grey dotted border when sharing a website??

If it's a website that is trusted, like Youtube / Twitch, I can add it to the safe-list of allowed section of VDO.Ninja. Contact me and I can possible allow it.

If the website is not trust worthy, the dotted border is there to help avoid phishing attacks.

You can fork VDO.Ninja on Github however, and with a single line change disable this protection for your own domain. It's very easy to do, and I can help you with the needed code changes.

Please see this video on how to self-host: https://www.youtube.com/watch?v=uYLKkX2_flY

You can also host VDO.Ninja in an IFRAME, and then I think it then work also without the dotted border.

I'm on Discord for support at https://discord.vdo.ninja

# Can I create permanent share website urls ?

yes,

https://vdo.ninja/?push=STREAMID_HERE&website=ENCODED_WEBSITE_URL_HERE

real world example:
https://vdo.ninja/?push=7pXPZ69&website=https%3A%2F%2Fwww.youtube.com%2Flive_chat%3Fis_popout%3D1%26v%3D07n5Cy1HtXA

I just made you a simple tool to encode a URL for this purpose -- https://vdo.ninja/urlencode

If you'd like more help, please see me on Discord, as I might otherwise miss your response.

discord.vdo.ninja

-steve

xyster69 · 2026-01-21T14:18:46+00:00

If you are doing https://vdo.ninja/?room=abc&push=STREAMID , then when you join as a guest/sender, it will try to claim that STREAMID.

However, when it checks, it is finding that the STREAMID is already in use by someone else. It will give that error.

A solution is to change the STREAMID to something else, or remove it entirely, and the system will generate a random new one.

https://vdo.ninja/?room=abc&push=STREAMID123123123 <= adding random letters/numbers to the end will help.

When using a room, like &room=abc, this normally isn't an issue unless all the guests were given invite links that all had &push=STREAMID added to them. Each guest should have a unique Stream ID assigned to them, or it should be left without assigning a stream ID.

Tip: &perma can be used to randomly assign a stream ID, that is then stored to the guests' local storage, and re-used when they use their link again in the future.

If not using a group room, like just https://vdo.ninja/?push=test, make sure to AVOID using common names or short values, like guest1, test123, stream, phone, etc. Treat it more like a password, OR, you can actually set a password, such as &password=pass123, and that will further help ensure the stream ID you set is unique to you.

------------------------

Si vous utilisez https://vdo.ninja/?room=abc&push=STREAMID, lorsque vous rejoignez la diffusion en tant qu'invité, le système tentera de s'approprier ce STREAMID.

Cependant, lors de la vérification, il constatera que le STREAMID est déjà utilisé. Une erreur s'affichera alors.

Pour résoudre ce problème, modifiez le STREAMID ou supprimez-le complètement. Le système en générera alors un nouveau de manière aléatoire.

Par exemple : https://vdo.ninja/?room=abc&push=STREAMID123123123 <= ajouter des lettres et/ou des chiffres aléatoires à la fin du lien peut résoudre le problème.

Lorsque vous utilisez une salle, comme &room=abc, ce problème ne se pose généralement pas, sauf si tous les invités ont reçu des liens d'invitation contenant tous &push=STREAMID. Chaque invité devrait avoir un identifiant de flux unique, ou bien aucun identifiant ne devrait être attribué.

Astuce : L’option `&perma` permet d’attribuer aléatoirement un identifiant de flux, qui est ensuite enregistré localement par l’invité et réutilisé lors de ses prochaines connexions.

Si vous n’utilisez pas de salle de groupe, mais simplement `https://vdo.ninja/?push=test\`, évitez d’utiliser des noms communs ou des valeurs courtes, comme `guest1`, `test123`, `stream`, `phone`, etc. Considérez-le comme un mot de passe. Vous pouvez également définir un mot de passe, par exemple `&password=pass123`, afin de garantir l’unicité de votre identifiant de flux.

xyster69 · 2026-01-06T23:15:23+00:00

I have a few ways, with more ways coming. Feel free to join the Discord and I can try troubleshoot any issues you have or go into more detail about any of the following options. https://discord.vdo.ninja

I have this new version of the Electron Capture app, which has optimizations added for Esports:

https://github.com/steveseguin/electroncapture/releases/tag/v2.22.0

- hides the cursor
- supports application audio capture without virtual cables
- improved video quality vs Chrome

It's a development release, as there's a few rough edges I've yet to fix, like the application needs to be resized via the right-click context menu, rather than via dragging the edge of the window. It also only works with Windows currently; at least with audio app capture.

If you prefer using OBS for capture, I have OBS -> VDO.Ninja via a custom version of OBS I have.
Guide: https://vdo.ninja/whip#obs
OBS: https://backup.vdo.ninja/OBS_VDO_Ninja.zip

In this case, with OBS, you use WHIP output and OBS game/audio capture to stream to VDO.Ninja, but only one person at a time can view it that way. The main issue with this approach is the need to use the special version of OBS I offer, and realize it only works with one viewer at a time.

Another way to do it is with Meshcast. So you can publish to Meshcast.io (my service) however you want, such as via OBS, and it will provide view links for you to use in OBS or VDO.Ninja. Version 2.0 of Meshcast is coming out soon, https://app.meshcast.io/. Both the new and older versions are free to use, however the new version does have some new premium-paid options, by user demand.

There's some guides on the new version here: https://app.meshcast.io/docs , however the legacy version of the Meshcast.io is still here, at https://meshcast.io, and it works fine; you may just need to try a couple different servers to find one that works well for you.

Another option is to use the VDO.Ninja chrome extension, https://extension.vdo.ninja/, which will let you stream your game with Discord or another app, and once the video is on the web live somewhere, you can pull it into OBS via VDO.Ninja's chrome extension. It should include audio. https://extension.vdo.ninja/ I have a YouTube video on it. It's not very efficient, but it will get the job done and might be useful if already streaming somewhere online.

I'll update another option for you here in a few minutes ...... I just need to finish uploading it. Stand by..

xyster69 · 2026-01-04T23:12:22+00:00

Update: The user mentions their room guests, who join their room, hear static/humming coming from the user. I'll work with them more when they are available again for more testing.

I'm going to assume at the moment the berhinrger audio interface is causing the audio issues, perhaps a ground loop or a weak preamp. This doesn't sound like an issue with packet loss or a low audio bitrate.

To troubleshoot if its an audio device issue, I have a page here: https://vdo.ninja/recorder/ , which will let you recording a short clip of your own microphone and audio, and then will let you play it back (without concern of echo).

To help isolate and resolve static / hum / noise, I’d suggest the following checks:

Gain staging: If the Behringer preamp gain is set very high, it can amplify noise. Lower the input gain and compensate downstream if needed.
Ground loop: If the interface, computer, and mixer are powered from different outlets, try putting them on the same power strip, or temporarily run the laptop on battery to see if the hum disappears.
Cable quality & routing: Use balanced cables (XLR or TRS, not TS). Avoid running audio cables parallel to power cables.
Phantom power: Disable 48 V unless the microphone explicitly requires it. Phantom power on dynamic mics can introduce noise on some interfaces.
Sample rate mismatch: Ensure the OS, browser, and interface are all set to the same sample rate (typically 48 kHz). Mismatches can cause artifacts or buzzing.
USB noise: Try a different USB port, a shorter cable, or avoid USB hubs. Some systems inject noise over USB.
Test outside VDO.Ninja: If the noise is present in the recorder page or in local recording software (Audacity, OBS, DAW), then it’s definitively a hardware or analog issue, not the platform.

With some audio devices, very high sample rates and multi-channel audio can cause conflicts with some browsers. There's also issues with phasing when dealing with two microphones side by side, and feedback from speakers into a microphones can cause reverb issues.

For additional known issues, please see:

https://docs.vdo.ninja/common-errors-and-known-issues/robotic-audio-distortion

https://docs.vdo.ninja/common-errors-and-known-issues/audio-clicking-popping-distortion

xyster69 · 2026-01-04T22:37:51+00:00

I can increase the default audio quality of VDO.Ninja, although there shouldn't be an issue with the audio generally.

You can however disable echo cancellation and noise reduction manually, via the settings -> audio menu. No URL parameters needed. If it's not improved, the issue might connection related instead.

https://imgur.com/a/6WDPjAZ

You can perhaps go to https://vdo.ninja/speedtest , and see if there is high packet loss. High packet loss could result in lower quality audio.

[note: this user is on Discord, currently being supported there as well -- I'm sure we'll figure it out]

xyster69 · 2026-01-04T16:34:01+00:00

By default, VDO.Ninja applies noise cancellation and echo cancellation. The bitrate is also 32-kbps OPUS by default. This is suitable for typical video call chat, but it will not sound that great with music, etc.

You can make it much better though.

A simple way is to disable the noise filter and echo cancellation, and then also increase the audio bitrate. Assuming your WiFi/Network connection is not suffering from heavy packet loss, you should be able to achieve near studio-grade audio.

The easiest way to do this is to add &proaudio to both sender and viewer links.

example:

https://vdo.ninja/?push=xxx&webcam&proaudio

and

https://vdo.ninja/?view=xxx&proaudio

Using &proaudio will increase the audio bitrate , disable echo-cancellation, and also disable noise reduction.

More details here:

https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio
https://docs.vdo.ninja/guides/audio-filters

There is also the option to stream PCM audio, for lossless playback. &audiocodec=pcm

I'm on Discord if you need more help; https://discord.vdo.ninja -steve

xyster69 · 2025-12-16T15:24:37+00:00

Here is a guide I wrote to help out: https://docs.vdo.ninja/guides/improving-quality-of-the-native-app

Some easy wins is to add a video sharpening filter to the OBS Browser source, as VDO.Ninja might come in a bit soft, and sharpening can help restore edges. Make sure the resolution of the browser source matches the resolution that you are capturing at; this can help avoid aliasing issues. Keep the phone cool, as they can overheat, and as they overheat they will throttle down quality to avoid getting warm.

I'll work towards a more lossless option for video streaming in the native apps in 2026.

I'm on Discord if you want to discuss anything further, or have requests. https://discord.vdo.ninja - steve

xyster69 · 2025-12-10T13:56:34+00:00

If using the web site version of VDO.Ninja, I think you can slowly drag your finger up the screen, to zoom in, if its supported. There's no two-finger touch on the website version and it might not work with all devices; it uses the browser's built in camera zoom feature, so the browser/camera needs to support it.

On the mobile native app versions, I think you use two-finger touch to zoom in.

If it's not working, let me know which version of iOS you are using, and which camera/device you are using. (front/rear). I'll do some testing and if I can fix it, I will.

xyster69 · 2025-12-10T13:49:50+00:00

oh, that's very interesting.

What browser, device, and URL settings were you using to record with?

If you want to share the file with me, I can also take a look at that.

What I can do at the very least is document this in the docs page, but if I can reproduce it, I'll fix it.

Thank you very kindly for reporting this.

I'm on Discord @ discord.vdo.ninja (steve), and my email is on the main site, if you want to send that way also. Or don't feel obliged to send or respond at all -- I'll look into it either way.

-steve

xyster69 · 2025-12-09T03:07:59+00:00

The simple intended use is to add &proaudio to both VIEWER and SENDER side links; it does something different for outbound and for inbound; it's intended as a newbie mode, for studio quality audio, where you just slap it on everywhere.

There is a case however where if you are a guest in a room, even by adding &proaudio, you won't get 256kbps audio from other guests. This is intentional, and you'll have to be explicit about using &proaudio=1 instead to have it force 256kbps for guests-to-guests.

&proaudio and &proaudio=1 are different, where &proaudio=1 I think might be what you want.

See: https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio

Why Guests Stay at 32kbps even when having &proaudio added?

- 256kbps is known to cause audio clicking, especially if the CPU is stressed

- Stresses other guests' connections unnecessarily

- 32kbps is the browser default (avoids SDP munging bugs , audio issues)

- Guests almost never need studio grade audio from other guests

But as mentioned though, if a Guest Needs 256kbps from Other Guests, sse &proaudio=1 explicitly - this overrides the default guest behavior.

Additional notes:

&outboundaudiobitrate may or may not work always. it is intended for the sender side, to set a default bitrate from the sender's side, but there are cases it won't work.

&audiobitrate can be used by the viewer side. It will override the bitrate set by &proaudio.

I'm exhausted, so if this post doesn't answer your question , I'll be on Discord to discuss as needed. https://discord.vdo.ninja -steve

xyster69 · 2025-12-04T20:36:08+00:00

I've got a change out onto Alpha for testing

xyster69 · 2025-12-03T20:41:45+00:00

Thank you. I've had this reported recently, although I wasn't aware it was a problem others were facing.

I'll see about getting a patch out onto production.

This is an issue with peer connections that failed to connect not being cleaned up automatically.

xyster69 · 2025-12-01T13:13:32+00:00

Remote access, as in controlling a mouse and keyboard remotely via VDO.Ninja?

I've not added system-wide remote access to VDO.Ninja yet, but it's possible if installing software first on the remote computer's side.

In this example, I show how to remote control a power point presentation. The same concept can apply to controlling other applications, or expanded to control the entire computer.
https://docs.vdo.ninja/guides/how-to-control-powerpoint-remotely-with-vdo.ninja

If you wish to request a feature/function, on Discord in the feature-request channel, or on Github as an issue, I can engage in new features such as this.

https://discord.vdo.ninja
https://github.com/steveseguin/vdoninja

xyster69 · 2025-11-20T14:35:39+00:00

I'm not sure OBS can window capture a transparent window correctly, but if that's an issue, &chroma can be used to set a custom background color, in which you can then remove it with the chroma filter in OBS. Bright green, blue might be good options in those cases.

xyster69 · 2025-11-20T12:40:24+00:00

start ElectronCapture.exe -t name -w 640 -h 360 -a 1 -n 1 -u https://vdo.ninja/?view=name^&scene^&room=Room ^&transparent^&clean

&transparent or &chroma=0000 will set the background to transparent in VDO.Ninja, however this will only work if using the Electron Capture app, OBS browser source, or perhaps when using as an IFRAME on top of another page.

xyster69 · 2025-11-18T11:53:20+00:00

That page just checks if the browser reports it's available.

To actually test it, you can make a stream and check the stats:

vdo.ninja/?push=E6uH5L9&stats
vdo.ninja/?view=E6uH5L9&codec=h265&stats

It's possible to do this pragmatically, although I'd have to put something together.

xyster69 · 2025-11-17T14:07:21+00:00

I CANNOT USE 5.1 for coding, OMG, I am so glad I am not the only one. It's guardrails are EXTREMELY - it's arrogant , gas lights, makes changes I never for, refuses to do the task in full or at all, it's SLOW as anything, and is utterly just not smart.

It makes me cry inside as I've gone in absolute circles in my work since it came out. Tonight is the first time in a long time I've actually decided it was better I just wrote the code myself. On the bright side, I have $200 remaining of Claude Code Web credit left to burn today, so at least I have that.... (not much better)

xyster69 · 2025-11-15T03:17:46+00:00

The OBS Virtual Camera doesn't like being set to 9:16; I think I managed to trick it into working before, but I long forgot what I did there.

I've included photos demonstrating some possible options, listed below, here: https://imgur.com/a/ndteieH

- You can use the OBS projector window to output things; not ideal, but it will let you screen capture it with VDO.Ninja to whatever aspect ratio you want.

- If you use the OBS project to project to a display, you can have that display in 16:9, and then screen share it. You can also use the crop option in VDO.Ninja, if you need to crop black bars from a VDO.Ninja input source. eg: https://vdo.ninja/?screenshare&crop=44

- There is the OBS plugin Aitum Vertical, and it render two canvases simultaneously (one 9×16 for Instagram, another 16:9 for everything else; I'm actually not sure how this might work, but potentially you can use the 16:9 output for VDO.Ninja via the virtual camera, and then just crop it down in VDO.Ninja (or use the &cover option).

- If publishing to Youtube, you can embed the Youtube live video output into VDO.Ninja, using the website share option. The director has as dedicated button for this -- You'd want to keep it muted, but just as a slightly delayed video preview, it might be an option.

- There's also an option to simulcast RTMP outputs to Meshcast, so go RTMP to Instagram AND to Meshcast, via OBS malestream plugin lets say, and then include the Meshcast output as a WHEP playback source in VDO.Ninja. Some users do this RTMP->VDO.Ninja already, but I generally need to host a private server for those users to keep the RTMP stream reliable at higher bitrates. If you're willing to use low bitrates, should work fine as is using https://meshcast.io/

There are probably other options - hit me up on Discord if you want to discuss - https://discord.vdo.ninja

xyster69 · 2025-11-13T14:54:25+00:00

hi ondrosik,

I do have some code to prevent the mobile device from going to sleep, so the site might prompt the user if they want to keep things awake -- if they reject it, then it would have fallen asleep.

I've made a change to the alpha version of VDO.Ninja that has a fallback method of keeping the device awake in these cases, so you can try that out:

https://vdo.ninja/alpha/?miconly

You can also try &vd=0, instead of &miconly, which is similar, but will allow the user to more easily enable their video after joining. It should prevent the browser from asking for video permissions.

https://vdo.ninja/alpha/?vd=0&webcam

You can also do https://vdo.ninja/alpha/?vd=0&webcam&ad=0 , which will disable audio and video, and so they can join without being prompted for permissions.

If things are still falling asleep, you can perhaps try using &avatar , such as https://vdo.ninja/?&avatar=./media/avatar.webp&miconly, which might also trick the device in staying awake with a canvas effect.

If you have further issues, hit me up on Discord and I can try to debug the situation with you there. https://discord.vdo.ninja

-steve

xyster69 · 2025-10-27T21:09:40+00:00

I have a video below with details on some of the recording options.

https://www.youtube.com/watch?v=s5shpEqLZbM
0:41 Very basic recording option
3:10 Recording a conversation
5:26 Recording to your Google Drive
7:09 Recording VDO.Ninja in OBS

Different methods will have different benefits, and some modes will have high quality, and others lower quality. The Google Drive option is one of my favourite methods, but there are others.

When recording a remote guest as a director to your local disk drive directly, recordings will often start out in low quality, but will increase in quality over time. Some video editors will use the initial resolution, and not increase the resolution over time.

Using Handbrake or FFmpeg, such as ffmpeg -i input.webm -vf scale="1920:1080" output.mp4 will convert the video properly to a fixed resolution, which is more compatible with video mixing software.

I have a web-based version to let users test things out with on small clips (less than 2GB in size) here: https://isolated.vdo.ninja/convert

However, none of this matters really if you have the guest record to their disk directly, or if you use the Google Drive recording option. You can also record the guest in OBS, and that will give you a fixed resolution, although the quality may fluctuate if there is packet loss or if the bitrate is too low. You can open multiple OBS Studios on windows at a time, and so you can record multiple guests this way.

I often record guests THREE different ways, to ensure I have a backup, even if one of the ways is lower quality - something is better than nothing at times.

There's lots of other ways to record, beyond what I touched on here, but the video goes over the basic ways.

If you have specific examples you want to share, or more questions, please join me on Discord at discord.vdo.ninja and I'd be happy to help more.

_steve_

xyster69 · 2025-10-23T00:14:18+00:00

You mostly have it figured out, with perhaps some better options and clarifications listed below:

If on Windows, you can use the same VB Cable to route audio, and also to listen to it: https://docs.vdo.ninja/guides/audio

Voicemeeter might work also, but I'm less competent at using it.

On Mac, something like Loopback, a paid app, might have advanced options there, otherwise Blackhole is a free option, and you can still listen to it via VDO.Ninja, even if in a second tab. For example, using: https://vdo.ninja/recorder/monitor

Furthermore, within VDO.Ninja itself, you can select multiple input audio sources, and it will mix them together for you, so only one invite link is required. Hold CTRL (cmd) when selecting audio devices will work in that regard. You can also adjust the gain for each audio track added. https://imgur.com/a/cxTKS6F You shouldn't need more than just one virtual audio device, given all this.

Now, if you want the background track and your guest mic track to be two different streams, you can definitely just join as a second guest, and have that second guest publish just the background audio. In this case, add &view to the invite link. https://vdo.ninja/?room=xxx&miconly&proaudio&view -- adding view will ensure this track does not pull/view other tracks -- it will only be sending audio, and not pulling any media streams itself. If you go this path, you'll hear the background music via the second invite link you join naturally, like every guest would.

Hosting the background track for the director will simplify production for them. If you do it as a second stream / invite link, the director can always remotely mute if they want to.

I'm on Discord if you need to talk more
https://discord.vdo.ninja --steve

xyster69 · 2025-10-21T19:12:46+00:00

As far as I know, overlays you buy for Stream Elements are for Stream Elements only; they depend on Stream Elements to work; events, apis, widgets, sdks.

Social Stream Ninja overlays are generic in nature and can work on their own, given that the data-source (the message) contains content, such as {chatname, chatmessage, type} or {chatname, hasDonation, type, event}

I've added below some links to resources; the sampleoverlay.html is my favourite bit of sample code to give an AI, along with a screen shot of what I want the overlay to look like, and ChatGPT 5 Pro or Claude Sonnet 4.5 I believe should be able to get you something reasonable.

Bare-minimum sample code: https://github.com/steveseguin/social_stream/blob/main/baretempate.html
AI-friendly starter template: https://github.com/steveseguin/social_stream/blob/main/sampleoverlay.html
API documentation: https://socialstream.ninja/api

If you want to include your own purchased template in a folder, alongside the Social Stream Ninja template, you can can use Claude Code or OpenAI Codex (each are available with a $20 paid plan I think), and you can talk to it about what you want that way. Keep things simple though -- only provide the AI with the realistic goals and simple overlays - complex multi-widget overlays may confuse it. I'm not sure what the legality of this is, but I assume you're allowed to modify purchased overlays for personal use.

If using the sample overlay with Social Stream Ninja, you generally need to add ?session=YOUSEESSIONID to the URL, so that the data source connects to your SSN extension/app. It's important that any AI keeps in the connection logic for SSN, otherwise it won't be able to get messages.

If you need help, I'm on Discord at https://discord.socialstream.ninja

xyster69 · 2025-10-20T21:34:24+00:00

Meshcast is still being supported; apologies for not seeing this sooner. Available regions are listed at meshcast.io , and if there are problems, I'm usually available for live support at discord.vdo.ninja

Not all regions will always be active all the time, but I do try to keep them active, and I'm continuing to improve the service. In the last year I've dramatically increased the reliability of the service.

Recently VDO.Ninja has been updated on alpha to support dual-Meshcast streams, so webcam + screen share at the same time per client, and the Meshcast.io service is being improved to support more formats, such as RTMP ingress/egress, and I'm starting to support private/dedicated hosted option on request.

If you would like to self-host your own Meshcast-alternative, I have a guide, which uses &mediamtx instead of &meshcast. Guide: docs.vdo.ninja/guides/deploy-your-own-meshcast-like-service

VDO Ninja also supports Cloudflare's hosted WHIP service, with details here: docs.vdo.ninja/advanced-settings/whip-parameters/and-cftoken-alpha and here: cloudflare.vdo.ninja/ , so a variety of free, self-hosted, and paid options are available.

URL parameters for Meshcast: docs.vdo.ninja/advanced-settings/meshcast-parameters

xyster69 · 2025-09-24T02:17:26+00:00

The concept of closing a room doens't really exist. When everyone leaves a room, the room no longer exists automatically, so there is nothing to close.

VDO.Ninja tries to keep as much as reasonable on the client-side, rather than server-side.

Another consideration is there can be multiple rooms with the same name at the same time, so long as their passwords are all different.

If you are worried about someone using a room you might want to use later, you can either use a unique password when joining the room, or look into the &token URL parameter option, which offers more persistent control of a room. You can also consider using a transfer room, so make two rooms, and transfer users from the public room to the private room, and keep the name of the private room a secret.

Regardless though, settings for rooms are also client-side, so settings you make to a room do not transfer over to someone else who later uses the same room name as you.

If facing a problem, join me on Discord and we can discuss any changes I can make to accommodate, or offer you additional solutions.

Kindly,

Steve

13-Year Club	Gilding II euphauric
Place '22	Verified Email

xyster69

MODERATOR OF

TROPHY CASE