Capture Video from USB Grabber using ffmpeg on Windows 10 Command Line

Find out the capabilities of the grabber using the following command:

cd c:\program files\ffmpeg\bin
ffmpeg  -f dshow  -list_devices true -i dummy

This will produce a list of devices on the system like:

C:\Program Files\ffmpeg\bin>ffmpeg  -f dshow  -list_devices true -i dummy
ffmpeg version N-85750-ga75ef15 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 6.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-zlib
  libavutil      55. 61.100 / 55. 61.100
  libavcodec     57. 93.100 / 57. 93.100
  libavformat    57. 72.101 / 57. 72.101
  libavdevice    57.  7.100 / 57.  7.100
  libavfilter     6. 88.100 /  6. 88.100
  libswscale      4.  7.101 /  4.  7.101
  libswresample   2.  8.100 /  2.  8.100
  libpostproc    54.  6.100 / 54.  6.100
[dshow @ 0000000000eb6400] DirectShow video devices (some may be both video and audio devices)
[dshow @ 0000000000eb6400]  "Microsoft® LifeCam Cinema(TM)"
[dshow @ 0000000000eb6400]     Alternative name "@device_pnp_\\?\usb#vid_045e&pid_075d&mi_00#6&24444fbd&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global"
[dshow @ 0000000000eb6400]  "USB2.0 Grabber"
[dshow @ 0000000000eb6400]     Alternative name "@device_pnp_\\?\usb#vid_05e1&pid_0408&mi_00#6&3829e82&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{77e95fd6-7a3d-4f69-9723-582a8dd5c0a1}"
[dshow @ 0000000000eb6400] DirectShow audio devices
[dshow @ 0000000000eb6400]  "Desktop Microphone (3- Microsoft® LifeCam Cinema(TM))"
[dshow @ 0000000000eb6400]     Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{59A9B105-DBCD-4397-BA77-C2C9E12AE0DE}"
[dshow @ 0000000000eb6400]  "Digital Audio Interface (USB Audio Interface)"
[dshow @ 0000000000eb6400]     Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{1E77847A-3A5B-49C7-AAF1-9A74B1771A9B}"

Here we can see a system with “USB2.0 Grabber” and a “Microsoft┬« LifeCam Cinema(TM)” webcam.

To get the capabilities of a device use:

ffmpeg  -f dshow  -list_options true -i video="USB2.0 Grabber"

This will return the capabilities of the named device “USB2.0 Grabber” in this instance. This happens to be a STK1160 USB video interface.

C:\Program Files\ffmpeg\bin>ffmpeg  -f dshow  -list_options true -i video="USB2.0 Grabber"
ffmpeg version N-85750-ga75ef15 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 6.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-zlib
  libavutil      55. 61.100 / 55. 61.100
  libavcodec     57. 93.100 / 57. 93.100
  libavformat    57. 72.101 / 57. 72.101
  libavdevice    57.  7.100 / 57.  7.100
  libavfilter     6. 88.100 /  6. 88.100
  libswscale      4.  7.101 /  4.  7.101
  libswresample   2.  8.100 /  2.  8.100
  libpostproc    54.  6.100 / 54.  6.100
[dshow @ 00000000000b6420] DirectShow video device options (from video devices)
[dshow @ 00000000000b6420]  Pin "Capture" (alternative pin name "0")
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=640x480 fps=5 max s=640x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=160x120 fps=5 max s=160x120 fps=30
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=176x144 fps=5 max s=176x144 fps=30
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=320x240 fps=5 max s=320x240 fps=30
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=352x288 fps=5 max s=352x288 fps=30
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=720x480 fps=5 max s=720x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=uyvy422  min s=720x576 fps=5 max s=720x576 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=640x480 fps=5 max s=640x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=160x120 fps=5 max s=160x120 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=176x144 fps=5 max s=176x144 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=320x240 fps=5 max s=320x240 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=352x288 fps=5 max s=352x288 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=720x480 fps=5 max s=720x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuyv422  min s=720x576 fps=5 max s=720x576 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuv420p  min s=640x480 fps=5 max s=640x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuv420p  min s=160x120 fps=5 max s=160x120 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuv420p  min s=176x144 fps=5 max s=176x144 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuv420p  min s=320x240 fps=5 max s=320x240 fps=30
[dshow @ 00000000000b6420]   pixel_format=yuv420p  min s=352x288 fps=5 max s=352x288 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=640x480 fps=5 max s=640x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=160x120 fps=5 max s=160x120 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=176x144 fps=5 max s=176x144 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=320x240 fps=5 max s=320x240 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=352x288 fps=5 max s=352x288 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=720x480 fps=5 max s=720x480 fps=30
[dshow @ 00000000000b6420]   pixel_format=bgr24  min s=720x576 fps=5 max s=720x576 fps=30
[dshow @ 00000000000b6420] Crossbar Switching Information for USB2.0 Grabber:
[dshow @ 00000000000b6420]   Crossbar Output pin 0: "Video Decoder" related output pin: 1 current input pin: 0 compatible input pins: 0 1
[dshow @ 00000000000b6420]   Crossbar Output pin 1: "Audio Decoder" related output pin: 0 current input pin: 4 compatible input pins: 3 4
[dshow @ 00000000000b6420]   Crossbar Input pin 0 - "Video Composite" related input pin: 4
[dshow @ 00000000000b6420]   Crossbar Input pin 1 - "S-Video" related input pin: 4
[dshow @ 00000000000b6420]   Crossbar Input pin 2 - "Video Tuner" related input pin: 3
[dshow @ 00000000000b6420]   Crossbar Input pin 3 - "Audio Tuner" related input pin: 2
[dshow @ 00000000000b6420]   Crossbar Input pin 4 - "Audio Line" related input pin: 0

You can then grab the video using a chosen format using something like:

"C:\program files\ffmpeg\bin\ffmpeg.exe" -f dshow -pixel_format yuv420p  -video_size 640x480 -i video="USB2.0 Grabber":audio="Digital Audio Interface (USB Audio Interface)" c:\data\video.mp4

This command saves the captured data to a file c:\data\video.mp4 using the Video grabber “USB2.0 Grabber” and the audio interface “Digital Audio Interface (USB Audio Interface)” using the video format yuv420p with a video size of 640×480 pixels using direct show.

Recover Data off a Western Digital MyBook Live Drive

If you happen to have a Western Digital NAS that has failed – but suspect that the drive is OK then you may be able to recover the data using the following steps.

Note this is a destructive process for the case work – and should be attempted if your aim is to get the data off the internal drive.

You will need a machine running a recent version of Linux (e.g. Debian, Ubuntu, System Rescue Boot Linux USB), and some way to connect a SATA drive e.g. USB drive caddy.

First break apart the enclosure to reveal the NAS electronics and 3.5″ hard drrive.

Remove all the electronics so you have just the 3.5″ Western Digital internal SATA drive.

Place the drive in a USB caddy and connect to a machine running linux.

Login as root or similar privaledged user.

Check the drive with fdisk -l:

 Disk /dev/sdb: 111.8 GiB, 120034123776 bytes, 234441648 sectors
 Units: sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disklabel type: dos
 Disk identifier: 0x8d6ae933
Device     Boot     Start       End   Sectors   Size Id Type
 /dev/sdb1  *         2048 217913343 217911296 103.9G 83 Linux
 /dev/sdb2       217915390 234440703  16525314   7.9G  5 Extended
 /dev/sdb5       217915392 234440703  16525312   7.9G 82 Linux swap / Solaris

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
 Units: sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 4096 bytes
 I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
 Disklabel type: gpt
 Disk identifier: B681229E-AF4B-44BE-818B-BA1200E02213
Device       Start        End    Sectors  Size Type
 /dev/sda1  1032192    5031935    3999744  1.9G Linux RAID
 /dev/sda2  5031936    9031679    3999744  1.9G Linux RAID
 /dev/sda3    30720    1032191    1001472  489M Microsoft basic data
 /dev/sda4  9031680 3907028991 3897997312  1.8T Microsoft basic data


On this system we can see that device /dev/sda is the 2TB drive from a Western Digital MyBook Live. The partition with the data is /dev/sda4 (the device sdX will vary depending on the your system).

Now make a mount point using:

mkdir /mnt/wd4

Now mount the data using:

fuseext2 -o ro -o sync_read -o allow_other /dev/sda4 /mnt/wd4

You should now be able to access the data with normal commands 

ls /mnt/wd4

You may need to install fuse using your package manager if not already installed with:

apt-get install fuseext2

Copy all the data off the original drive using rsync or similar e.g.

rsync -avr /mnt/wd4 /mnt/nas

Install Logitech Media Server on a Virtual Ubuntu Machine on a QNAP NAS

See this video over on YouTube

Using a QNAP TS-253

Virtualization Station

Ubuntu 16 Desktop LTS

Summary of command line instructions used:

Install Logitech Media Server (using a wildcard *)

cd ~

sudo dpkg -i ~/Downloads/logitech*.deb

Install Lame

sudo apt-get install lame

Install CIFS utils

sudo apt-get install cifs-util

Mount the drives

sudo mkdir /mnt/Multimedia

sudo mount -t cifs -ousername=admin,password=admin //TS253A.local/Multimedia /mnt/Multimedia
  • Change username, password and hostname (TS253A.local) to match your environment

Autostart OpenHome Media Player at Boot time on Raspberry PI

The OpenHome .org Player for Raspberry PI is easy to download and install from http://openhome.org/pages/use/downloads/pi.html

The player is normally started from the command line using

openhome-player

The OpenHome Media Player can be made to start with the operating system at boot time after the network has started.

Using the following commands.

Create/edit the oh.service file using:

sudo nano /etc/systemd/system/oh.service

Add the following to oh.service file

[Unit]
Description=OpenHome Player
Wants=network-online.target
After=network.target network-online.target

[Service]
User=pi
ExecStart=-/usr/bin/openhome-player
Restart=on-failure

[Install]
WantedBy=multi-user.target
Alias=openhomeplayer.service

Initialise the service using

sudo systemctl daemon-reload

Start service with

sudo systemctl start oh.service

Enable the service to start after a  reboot

sudo systemctl enable oh.service

Thanks to the OpenHome forum post for this information here: http://forum.openhome.org/archive/index.php?thread-1443-4.html

Installing Logitech Media Server (SlimServer / Squeezebox Server) On QNAP

Squeezebox Server used to be a supported App within the QNAP standard library – but QNAP removed support in 2015/2016.

SSODS used to be another solution – but is complex and fragile to install.

Use the QNAP Docker solution “Container Station” to load a pre-built image.

This procedure should work on any QNAP that supports the ContainerStation App.

Here are the Steps:

Install QNAP ContainerStation App from the QNAP web interface

Open Container Station

 

Click + Create Container

Search image for “justifiably”

Click “Create”

Click “Advanced Settings”

Click “Network”, change Network mode to “Host”

Click “Shared Folders”, Click “Add” in the “Volume from host” section. Select the music share e.g. /Multimedia and specify the mount point withing the Container e.g. /mnt/Multimedia

Click “Create”

It will take a few minutes to install (network sped dependent). Click “Overview”

Click the “Start” button.

You should now be able to access the Squeezebox Server web interface at port 9000 e.g. http://<ip address of the QNAP>:9000

Click “Next”

Set the Local Music Folder to be /mnt/Multimedia – click Next

Set the Playlists Folder to be /mnt/Multimedia (you could specify another shared folder when creating the Container if necessary). Click Next and Finish

Your Music library should now scan and you should be able to play music.

Confirmed Working

This procedure has been used to install Logitech Media Server (LMS) / Squeezbox Server / Slim Server on  the following devices:

  1. QNAP HS-251+ (firmware 4.3.3.0299)

Not Working

Any QNAP NAS that doens’t support “Container Station”

  • TS-210
  • TS-212P
  • etc

Manually Repair QNAP RAID 5 Array

I have a QNAP TS-421 that has a failed RAID5. The Web interface shows the RAID as in degraded mode. Drive 2 has failed. I’ve replaced drive 2 (/dev/sdb) with a new 2TB drive to match the other (working) three drives.

The Web interface fails to rebuild the array. Whilst the data is still accessible on the RAID it is in degraded mode and has no fault tolerance.

Resorting to SSH / PUTTY to fix this:

Check each of the drives:

with:

fdisk -l /dev/sda

fdisk -l /dev/sdb

fdisk -l /dev/sdc

fdisk -l /dev/sdd

Each drive yeilds similar to:

[~] # fdisk -l /dev/sda

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 66 530125 83 Linux
/dev/sda2 67 132 530142 83 Linux
/dev/sda3 133 243138 1951945693 83 Linux
/dev/sda4 243139 243200 498012 83 Linux

Check the status of the RAID with mdadm

mdadm --detail /dev/md0
/dev/md0:
 Version : 01.00.03
 Creation Time : Tue Jan 24 17:34:17 2017
 Raid Level : raid5
 Array Size : 5855836608 (5584.56 GiB 5996.38 GB)
 Used Dev Size : 1951945536 (1861.52 GiB 1998.79 GB)
 Raid Devices : 4
 Total Devices : 3
Preferred Minor : 0
 Persistence : Superblock is persistent

Update Time : Wed Jun 7 09:25:11 2017
 State : clean, degraded
 Active Devices : 3
Working Devices : 3
 Failed Devices : 0
 Spare Devices : 0

Layout : left-symmetric
 Chunk Size : 64K

Name : 0
 UUID : f15b5712:01afc7a3:61851d59:5d6f8393
 Events : 4391

Number Major Minor RaidDevice State
 0 8 3 0 active sync /dev/sda3
 1 0 0 1 removed
 2 8 35 2 active sync /dev/sdc3
 3 8 51 3 active sync /dev/sdd3

As expected we can see /dev/sdb3 is missing from above.

Make sure that the drive we want to add into the array isn’t mounted using

umount /dev/sdb3

Next add the drive into the array (this will delete any existing data on the drive being added /dev/sdb in this case)

[~] # mdadm /dev/md0 --add /dev/sdb3

Now check the details of the array again

[~] # mdadm --detail /dev/md0
/dev/md0:
 Version : 01.00.03
 Creation Time : Tue Jan 24 17:34:17 2017
 Raid Level : raid5
 Array Size : 5855836608 (5584.56 GiB 5996.38 GB)
 Used Dev Size : 1951945536 (1861.52 GiB 1998.79 GB)
 Raid Devices : 4
 Total Devices : 4
Preferred Minor : 0
 Persistence : Superblock is persistent

Update Time : Wed Jun 7 09:27:20 2017
 State : clean, degraded, recovering
 Active Devices : 3
Working Devices : 4
 Failed Devices : 0
 Spare Devices : 1

Layout : left-symmetric
 Chunk Size : 64K

Rebuild Status : 0% complete

Name : 0
 UUID : f15b5712:01afc7a3:61851d59:5d6f8393
 Events : 4421

Number Major Minor RaidDevice State
 0 8 3 0 active sync /dev/sda3
 4 8 19 1 spare rebuilding /dev/sdb3
 2 8 35 2 active sync /dev/sdc3
 3 8 51 3 active sync /dev/sdd3

 

Here we can see that /dev/sdb3 is now part of the array and rebuilding

The Web GUI should now also show the array rebuilding.

Demonstration of a Web Browser Control of a Blackmagic Designs ATEM Production Studio 4k Switch: Source

I posted a video sometime ago showing the control of a ATEM 4k Studio using a web browser – mainly to gain easy control of the AUX output.

I’ve now uploaded the NodeJS code to the downloads section of this site…

I’ve used this on our switches running on Raspberry Pi and also full Linux distribution such as Debian or Centos.

https://youtu.be/W7DIEU_caSk

Clean and create Disk with DiskPart

Start DiskPart

C:\>Diskpart

List all the drives

DISKPART> List Disk

Select the target drive

DISKPART> SELECT DISK 1

Zap the drive an all data using

DISKPART> CLEAN

Create a primary partion

DISKPART> CREATE PARTITION PRIMARY

Select the new partition

DISKPART> SELECT PART 1

Format and label the selected partiion

DISKPART> FORMAT FS=NTFS LABEL=DATA QUICK

Mount the drive at a given drive letter (e.g. N)

DISKPART>ASSIGN LETTER N

 

Recovering Data Off Netgear ReadyNAS

So I have a 4 bay Netgear ReadyNAS NVX that has stopped working.

The unit has TWO drives configured as a RAID 1 mirror (this will only work with units with two or less drives fitted).

I suspect that the power supply has failed (a common problem).

I’m going to recover the data off drive to a QNAP NAS (HS-251+ in this case).

Steps..

  1. Remove one drive from the ReadyNAS caddy
  2. Connect the drive SATA and power cables to a standard PC (remove/disconnect all other drives to avoid confusion).
  3. Boot the PC from a System Rescue CD – this can be downloaded here: https://www.system-rescue-cd.org/SystemRescueCd_Homepage
  4. Once at the command prompt you can list the drives with:
  5. fdisk -l
  6. root@sysresccd /root % fdisk -l
Disk /dev/loop0: 353.1 MiB, 370208768 bytes, 723064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 30AC9B24-F06D-4CE1-BBB5-ED9443790F5F

Device Start End Sectors Size Type
/dev/sda1 4 8388611 8388608 4G Linux RAID
/dev/sda2 8388612 9437187 1048576 512M Linux RAID
/dev/sda5 9437189 2930272064 2920834876 1.4T Linux RAID


Disk /dev/sdb: 58.6 GiB, 62932647936 bytes, 122915328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x455dc590

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 122915327 122913280 58.6G c W95 FAT32 (LBA)


Disk /dev/md0: 4 GiB, 4294955008 bytes, 8388584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md1: 512 MiB, 536858624 bytes, 1048552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md2: 1.4 TiB, 1495467311104 bytes, 2920834592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes


Disk /dev/mapper/c-c: 1.4 TiB, 1490085216256 bytes, 2910322688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes

The drive is 1.5TB and the device we are interested in is /dev/mapper/c-c

Mount this drive with:

root@sysresccd /mnt % mkdir /mnt/readynas
root@sysresccd /mnt % mount /dev/mapper/c-c /mnt/readynas

We can now look at the files on the ReadyNAS drive:

root@sysresccd /mnt % ls /mnt/readynas
aquota.group aquota.user backup home lost+found media squeezeboxserver

Next I’m going to mount the QNAP drive so that I can copy data from the ReadyNAS drive to the QNAP NAS. I need the IP address of the QNAP from the QNAP Finder application (in my case this is 172.31.1.69 – more typically 192.168.1.x).

Mount the Public folder on the  QNAP drive using:

root@sysresccd /mnt % mkdir /mnt/qnap
root@sysresccd /mnt % mount -t cifs -ousername=admin,password=YourQnapPassword //172.31.1.69/Public /mnt/qnap

I can now copy the data from the ReadyNAs drive (/mnt/readynas) to the QNAP (/mnt/qnap) e.g.:

rsync -av /mnt/readynas/media /mnt/qnap/media

 

Raspberry Pi Audio with AudioQuest DragonFly

 

AudioQuest Dragonfly Red

After booting Raspbian for the first time on my latest Raspberry Pi 3 (Jessie) I started to play with audio.

I have an Audioquest Dragonfly Red connected to one of the USB ports.

 

 

pi+dragonfly-red

First list the available device names using aplay -L

pi@raspberrypi:~ $ aplay -L
null
 Discard all samples (playback) or generate zero samples (capture)
pulse
 PulseAudio Sound Server
sysdefault:CARD=ALSA
 bcm2835 ALSA, bcm2835 ALSA
 Default Audio Device
dmix:CARD=ALSA,DEV=0
 bcm2835 ALSA, bcm2835 ALSA
 Direct sample mixing device
dmix:CARD=ALSA,DEV=1
 bcm2835 ALSA, bcm2835 IEC958/HDMI
 Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
 bcm2835 ALSA, bcm2835 ALSA
 Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
 bcm2835 ALSA, bcm2835 IEC958/HDMI
 Direct sample snooping device
hw:CARD=ALSA,DEV=0
 bcm2835 ALSA, bcm2835 ALSA
 Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
 bcm2835 ALSA, bcm2835 IEC958/HDMI
 Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
 bcm2835 ALSA, bcm2835 ALSA
 Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
 bcm2835 ALSA, bcm2835 IEC958/HDMI
 Hardware device with all software conversions
sysdefault:CARD=v10
 AudioQuest DragonFly Red v1.0, USB Audio
 Default Audio Device
front:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 Front speakers
surround21:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 4.0 Surround output to Front and Rear speakers
surround41:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 Direct sample mixing device
dsnoop:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 Direct sample snooping device
hw:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 Direct hardware device without any conversions
plughw:CARD=v10,DEV=0
 AudioQuest DragonFly Red v1.0, USB Audio
 Hardware device with all software conversions

As you can see the Raspberry Pi has the inbuilt sound chip (bcm2835) capable of audio output on the HDMI and the 3.5mm jack. I also have an AudioQuest Dragonfly Red attached to the USB port.

The list of devices is shown using the command aplay -l

pi@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
 Subdevices: 8/8
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
 Subdevice #2: subdevice #2
 Subdevice #3: subdevice #3
 Subdevice #4: subdevice #4
 Subdevice #5: subdevice #5
 Subdevice #6: subdevice #6
 Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: v10 [AudioQuest DragonFly Red v1.0], device 0: USB Audio [USB Audio]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

Initially I was getting no audio out of the Dragonfly.

I tried using alsamixer command. The device shows up, the volume control works. But no audio played.

Back to the command line using aplay

I copied a sample wav file (44.1kHz 16bit)

aplay ~/sample.wav

resulted in an error:

aplay sample.wav
Playing WAVE 'sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: set_params:1233: Sample format non available
Available formats:
- S24_3LE

The Device needs to be specified (plughw:CARD:v10) as follows:

pi@raspberrypi:~/Music $ aplay sample.wav -v -Dplughw:CARD=v10
Playing WAVE 'sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Plug PCM: Linear conversion PCM (S24_3LE)
Its setup is:
 stream : PLAYBACK
 access : RW_INTERLEAVED
 format : S16_LE
 subformat : STD
 channels : 2
 rate : 44100
 exact rate : 44100 (44100/1)
 msbits : 16
 buffer_size : 22050
 period_size : 5513
 period_time : 125011
 tstamp_mode : NONE
 period_step : 1
 avail_min : 5513
 period_event : 0
 start_threshold : 22050
 stop_threshold : 22050
 silence_threshold: 0
 silence_size : 0
 boundary : 1445068800
Slave: Hardware PCM card 1 'AudioQuest DragonFly Red v1.0' device 0 subdevice 0
Its setup is:
 stream : PLAYBACK
 access : MMAP_INTERLEAVED
 format : S24_3LE
 subformat : STD
 channels : 2
 rate : 44100
 exact rate : 44100 (44100/1)
 msbits : 24
 buffer_size : 22050
 period_size : 5513
 period_time : 125011
 tstamp_mode : NONE
 period_step : 1
 avail_min : 5513
 period_event : 0
 start_threshold : 22050
 stop_threshold : 22050
 silence_threshold: 0
 silence_size : 0
 boundary : 1445068800
 appl_ptr : 0
 hw_ptr : 0

Sweet Music from my AudioQuest Dragonfly Red!

To make the AudioQuest Dragonfly USB the default sound device can be achieved by disabling the on board sound (snd_bcm2835):

$ sudo nano /boot/config.txt

Comment out the section that loads the snd_bcm2835 by adding the # symbol as shown – then reboot for the changes to take effect:

# Enable audio (loads snd_bcm2835)
#dtparam=audio=on

Next set the required device to use for the audio by editing ~/.asoundrc

nano ~/.asoundrc

This should be as follows:

pcm.!default {

type plug

slave {

pcm "hw:0,0"

}

}

ctl.!default {

type hw

card 0

}