Topping E30 DAC is supported nearly out of the box on Ubuntu Linux 20.04 (This is my current OS)
Only minor tweaks to /etc/pulse/daemon.conf are required to achieve the best audio quality:
avoid-resampling = true enable-remixing = no default-sample-format = float32le default-sample-rate = 44100 default-sample-channels = 2 default-channel-map = front-left,front-right Without the changes it will still work, but you won’t be able to achieve the best audio quality
Background I have been running into issues on my main desktop system running Ubuntu, under high disk IO the system would lock up for couple seconds for no apparent reason (it was locking up for longer than could be expected).
After going through numerous websites, the conclusion I have reached is that by having a lot of memory, the system would cache a sizeable amount of data in RAM before flushing to disk.
I have stumbled on a problem when running Dungeon Siege II on Linux (Ubuntu), I’m trying to run the game via Steam and in order unlock Broken World extension there is a .bat file that must be executed.
Running the script directly using wine doesn’t work because Steam stores it’s configuration somewhat hidden behind WINEPREFIX.
It turns out that the trick is to set up WINEPREFIX correctly before running anything, like that:
This post is an overview of the existing Lightning Network tools, during my research I have found a number of different tools/libraries and decided to summarize them in this list.
The list is nowhere near being complete, I’m including only some of the programming related tools that I stumbled upon and found worth saving for future reference.
APIs ln-service https://github.com/alexbosworth/ln-service
Node.js interface to LND
Core implementation of the lightningj API implementations.
This blog post attempts to summarize the status of Lightning Network by providing an overview of existing full Lightning Network daemons.
The focus of this post is only to provide high-level overview of the daemons.
Lightning Network Daemon - lnd
Language: Go Github link: https://github.com/lightningnetwork/lnd BOLT compliance: 11/11 Status: Usable and actively developed Notes: Probably most mature daemon implementation; for most people this will be the default version to try out.
Today I’m going to show how to effectively use conditional expressions in logback.
This pattern has many use cases, for example:
Use different log output on server vs when application is running locally (JSON on server, regular logs on localhost) Send ERRORs to your monitoring service - but only when application is deployed to production Use different prefixes depending when application is running Setup In order to use conditional expressions in logback you need 2 things.
This is a guide how to use Consul’s DNS service from your local macOS machine.
Test resolution by hand Run this command to see if you can communicate with consul correctly and it resolves domain names for you:
dig vault.service.consul @$CONSUL_IP -p 8600 As response you should get the A record that will look similar to this (look for ANSWER SECTION):
;; ANSWER SECTION: vault.service.consul. 0 IN A 188.8.131.52 (the IP address will be different in your case)
Background After more one year of (inactively) using Wordpress for my blog I have decided to give Hugo another go. I became first familiar with Hugo around 3 years ago when I was in the process of migrating off Octopress because I had so many issues with configuring ruby environment across different projects and I was always running into incompatibility issues.
Back then I decided to fall back to Wordpress and was using it to host my blog for since then.
I was recently setting up remote backups for my QNAP NAS and came across a problem.
QNAP NAS by default doesn’t seem to be able to create backups of the TMBackup directory it uses to store TimeMachine backups. You are unable to sync this directory with remote server or cloud storage/backup service.
I was googling around and noticed that few people had this problem, for example here and I have found a solution.
The following post is a quick tutorial how to use Trezor hardware wallet with Bitcoin Testnet.
Connect your Trezor like you normally would Click on “Wallet settings” Delete contents of this field and enter “https://testnet-bitcore1.trezor.io/" instead Click “Save & Reload” This is how the wallet page should look Notice that in the right left corner it says “Custom backend”, this is expected. I already have 0.20 testnet BTC there.
This is how “Receive” tab looks like, there is information that you are running on testnet This is how “Send” tab looks like, there is information that you are running on testnet Unfortunately there’s no way for the Trezor wallet to remember this setting and you are required to repeat those steps every time you plug in your wallet into computer.