You need to use mpv | Installation

Just go the usual
sudo apt install mpv

and you should be fine.

then you can run without any problem :
mpv youtube-url --no-video

Install V4l2 Loopback
GitHub – umlaeute/v4l2loopback: v4l2-loopback device

NB: On Debian/Ubuntu, works best to install the package v4l2loopback-dkms

$ sudo apt-get install v4l2loopback-dkms

Once installed, you should load the virtual cam.
First check which video devices you have.
$ ls -l /dev/vidoe*

For instance on mine I had /dev/video0 to 4 so I then create a virtual cam on 5 using :

$ modprobe v4l2loopback video_nr=5 card_label=“Virtual cam”

Add OBS plugin for loopback output : obs-v4l2sink

NB: Not working yet.

Clone obs-v4l2sink

(If you wanna try without the plugin: check the convo Hello CatxFish… Any way to install OBS-virtual-cam on ubuntu? · Issue #17 · CatxFish/obs-virtual-cam · GitHub )

cmake -DLIBOBS_INCLUDE_DIR="…/…/obs-studio/libobs/" -DLIBOBS_LIB="…/…/obs-studio/libobs" -DCMAKE_INSTALL_PREFIX=/usr …

Step 1: Generate the mock data

Go to Mockaroo a random Data Generator and API Mocking Tool | JSON / CSV / SQL / Excel

Download as SQL / include Create if you want

Step 2: Prepare a database accessible remotely

Create a database and user somewhere online.
For instance with a service like

Step 3: Import the data in the database

mysql -u user -pPasswords -P 3306 -h < data.sql

Step 4: Check

You can use phpMyAdmin on remoteSQL website to check your data was processed in properly

Setting up the dev environnement

Install the command line tool

  • npm install @google/clasp -g

Then you login :
clasp login

Then you create a script :
clasp create YOURSCRIPT

NB: You need to create the folder where you put your code first

You can open it online using :
clasp open

NB: Seems like you need to at least open it this way once before you can pull and push.

Then you can pull it :
clasp pull

This will pull all the files you just created using the clasp open command

Then after you make local modifications you must use :
clasp push

Pretty straightforward

Deployment :

clasp version "First version"
clasp deploy 1 "First deployment"

Failing to keep a routine does not mean you cannot fix it the day after.

Should always strive to deliver – even if less than anticipated than delaying to try to over deliver.

IE : you deliver more often – not just more quality – and more often is a more sure way to reach more quality than delaying delivery