Skip to content

Instantly share code, notes, and snippets.

View silvernode's full-sized avatar

Mollusk silvernode

  • USA
View GitHub Profile
@silvernode
silvernode / software-mixer.txt
Created February 27, 2024 14:18
Software Mixer Help
A software mixer can be a huge help in managing and separating your audio sources for a stream. It gives you a lot more control over where different audio signals go, whether it's your game audio, Discord chats, or any other sources you're dealing with.
**VoiceMeeter** is one of the most popular options for this. It acts as a virtual audio mixer and allows you to route audio from different applications to different outputs. Here's how it could help in your situation:
1. **Separate Audio Channels**: You can route your game audio to one channel, your microphone audio to another, and your Discord audio to a separate one. This way, you have individual control over each audio source.
2. **Control Over What Your Audience Hears**: With everything routed through VoiceMeeter, you can decide exactly what audio gets sent to OBS for your stream. You can include your game audio and microphone but exclude your Discord chat, ensuring that your conversations remain private.
3. **Advanced Audio Manipulation**: Beyond just
Step 1. Install Deps
sudo apt install cmake valac libgee-0.8-dev libsqlite3-dev libgtk-3-dev libnotify-dev libgpgme-dev libsoup2.4-dev libgcrypt20-dev libqrencode-dev gettext libsignal-protocol-c-dev
Step 2. Clone Repo
git clone git@github.com:dino/dino.git
OR
git clone https://github.com/dino/dino.git
Step 3. cd dino
DKMS make.log for rtl88x2bu-5.3.1 for kernel 5.6.11-300.fc32.x86_64 (x86_64)
Tue 12 May 2020 05:45:55 PM MST
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.6.11-300.fc32.x86_64/build M=/var/lib/dkms/rtl88x2bu/5.3.1/build modules
make[1]: Entering directory '/usr/src/kernels/5.6.11-300.fc32.x86_64'
CC [M] /var/lib/dkms/rtl88x2bu/5.3.1/build/core/rtw_cmd.o
CC [M] /var/lib/dkms/rtl88x2bu/5.3.1/build/core/rtw_security.o
CC [M] /var/lib/dkms/rtl88x2bu/5.3.1/build/core/rtw_debug.o
CC [M] /var/lib/dkms/rtl88x2bu/5.3.1/build/core/rtw_io.o
CC [M] /var/lib/dkms/rtl88x2bu/5.3.1/build/core/rtw_ioctl_query.o
CC [M] /var/lib/dkms/rtl88x2bu/5.3.1/build/core/rtw_ioctl_set.o
@silvernode
silvernode / type-seqs.nim
Last active February 13, 2020 02:09
Learning types and seqs
import strformat
type
Character* = object
name*, location*: string
credits*: int
ship*: string
type
1. Edit `/etc/default/grub` with admin rights
2. Find line: GRUB_CMDLINE_LINUX_DEFAULT=" "
3. Add in quotes: GRUB_CMDLINE_LINUX_DEFAULT="processor.max_cstate=1 idle=poll"
4. Save the file
5. Rebuild grub boot menu: grub-mkconfig -o /boot/grub/grub.cfg
5a.Some distributions require: grub2-mkconfig -o /boot/grub2/grub.cfg
6. Reboot system
Notes: If you are using Fedora without UEFI and cannot regenerate your grub menu,
@silvernode
silvernode / greeter.log
Created April 7, 2019 06:32
GDM log: gretter errors
[root@voidpad gdm]# cat greeter.log | grep error
> Internal error: Could not resolve keysym XF86MonBrightnessCycle
> Internal error: Could not resolve keysym XF86MonBrightnessCycle
Gdk-Message: 20:15:48.248: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
Gdk-Message: 20:15:48.250: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
Gdk-Message: 20:15:48.251: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
Gdk-Message: 20:15:48.253: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
Gdk-Message: 20:15:48.257: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
Gdk-Message: 20:15:48.266: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024.
@silvernode
silvernode / site-status.sh
Last active February 13, 2019 16:15
[Bash] Check if a site is online or offline
#!/bin/bash
FAIL_CODE=6
if [ -z "${1}" ];then
echo "usage: ${0} example.com"
exit
fi
check_status(){
@silvernode
silvernode / C-states.md
Created February 11, 2019 06:14 — forked from wmealing/C-states.md
What are CPU "C-states" and how to disable them if needed?

To limit a CPU to a certain C-state, you can pass the processor.max_cstate=X option in the kernel line of /boot/grub/grub.conf.

Here we limit the system to only C-State 1:

    kernel /vmlinuz-2.6.18-371.1.2.el5 ... processor.max_cstate=1

On some systems, the kernel can override the BIOS setting, and the parameter intel_idle.max_cstate=0 may be required to ensure sleep states are not entered:

@silvernode
silvernode / tizonia.debug.txt
Created June 26, 2018 15:22
Debug log for Tizonia
This file has been truncated, but you can view the full file.
[stdout] 26-06-2018 15:20:06.171 - [PID:5508][TID:5508] [TRACE] [tiz.platform.rc] [tizrc.c:obtain_xdg_config_dir:576] --- XDG_CONFIG_DIRS [/snap/tizonia/188/etc/xdg:/etc/xdg:/usr/share/kde-settings/kde-profile/default/xdg] ...
[stdout] 26-06-2018 15:20:06.171 - [PID:5508][TID:5508] [TRACE] [tiz.platform.rc] [tizrc.c:obtain_xdg_config_dir:580] --- XDG_CONFIG_DIR - [/snap/tizonia/188/etc/xdg] ...
[stdout] 26-06-2018 15:20:06.171 - [PID:5508][TID:5508] [TRACE] [tiz.platform.rc] [tizrc.c:obtain_xdg_config_dir:604] --- Using config location /snap/tizonia/188/etc/xdg/tizonia/tizonia.conf
[stdout] 26-06-2018 15:20:06.171 - [PID:5508][TID:5508] [TRACE] [tiz.platform.rc] [tizrc.c:obtain_xdg_config_home:627] --- HOME [/home/mollusk/snap/tizonia/188]
[stdout] 26-06-2018 15:20:06.171 - [PID:5508][TID:5508] [TRACE] [tiz.platform.rc] [tizrc.c:tiz_rcfile_init:663] --- Looking for [3] rc files...
[stdout] 26-06-2018 15:20:06.171 - [PID:5508][TID:5508] [TRACE] [tiz.platform.rc] [tizrc.c:tiz_rcfile_init:676] --- Checking for r