You are not logged in.
@hunter0one:
Have you tried Ralph's advice?
(in a terminal):
Switch to the root user (which means su -; enter the root password, not sudo)
lsusb will show all connected usb devices
enable write access for the other user on the EasyCap device: chmod o+w /dev/bus/usb/001/015
Without rebooting, try qv4l2 & see if now it will allow you to see your vhs screen in the window.
I very much want to work with you to get my script to work with other devices (such as yours) & get a good result to allow folks to stream it to disc.
For devices you get c==character (bytes) or b==block (hdd, etc).
That is a root.root user.group & you will need to use sudo if you wish it to be changed.
It seems that there's only a few bits of capture hardware that are capable of doing the job. Sorry that yours is not one of them.
For some reason the capture image format and image size can't be changed in QV4L2
That is academic. ffmpeg is near miraculous; it will change a video from any format to any other format. My script has the wrong fps AND pixel dimensions for your supply (the script is using "-s 720x576 -r 25" which was correct for my VHS signal, but not yours) but ffmpeg would happily make that change.
The issue for you is hardware & region (as best as I can tell).
v4l2-ctl --all is giving a full, error-free readout of the input video device.
arecord -l is accurately recording the audio hardware as 'hw:2,0' ("card: 2, subdevice: 0")
Only region remains (for me, the picture only appeared in the V4L2 screen when I changed the region from the default NTSC to PAL; ymmv).
If you cannot find a combo that works then the answer may be that zero signal is arriving at the input. Do you have a broken wire?
You seem to have the correct hardware devices. In your position I would change to the root user & try again. If you cannot get the picture to appear in the V4L2 screen then it is bad.
Try all the various options with the V4L2 utility. It took me a while to find the correct mix before I got the video to appear. However, if you cannot get it to appear then throw the hardware in the bin & try something else.
Good luck.
PS
From the v4l2-ctl --all output, the fps in the script should be switched from 25 to 30. However, do not touch anything until you get V4L2 to work. Only if it will work there will the script work (using the same setup options).
13 Sep update: made clear re: fps I was referring to the script, not V4L2.
I've made the ffmpeg-recommended fix (search for "vsync is deprecated") to the bash-file & uploaded it. No checks, but the change is most modest & should work.
It is telling you there are errors on both the VIDEO_DEVICE=/dev/video0 + AUDIO_DEVICE=hw:2,0. It seems that the hardware that you are specifying (which happen to also be the defaults embedded in the script) are wrong. No point in going any further until those are checked. Either the precise devices are wrong or your user is wrong.
What are the results of v4l2-ctl --all + arecord -l or arecord -L or cat /proc/asound/cards?
I see that you were using the qv4l2 tool (QT v4l2 test utility). Very sensible - I used that as well (mostly to check REGION). However, if you cannot get the screen to appear in that utility then the bash-file will never work. The idea is to try different setup options until a picture appears. You can then supply the different options appropriately. Whatever options allow the V4L screen to show your VHS/Camera/whatever are the precise options to use with the bash-script.
Pay attention to your user. Your ls -l results show that you will have permission errors unless you go root. Or try the advice in the Wiki link: sudo chmod a+r /dev/video0. I'm pretty sure that that is why you are getting the 'input/output error'.
I'll also try to fix that -vsync error in the script.
I was hoping to find options that you used, results of tests, error messages, ...
Only OUTPUT_NAME is required.
Defaults for other options are:
VIDEO_DEVICE = '/dev/video0'
AUDIO_DEVICE = 'hw:2,0'
REGION = 'PAL'
PIX_FMT = 'yuv420p'
If those defaults do not match your system, and particularly video or audio hardware, then do not be surprised if it throws an error.
But ok I can tell that you are not bothered, so let's forget it.
alexkemp wrote:encode_stream
Thanks. I tried your script but some of the options like AUDIO_DEVICE and REGION did not work, and I got an input/output error when given just the device and output file.
Did you bother to use the help option (-h)?
usage: $0 OUTPUT_NAME [AUDIO_DEVICE] [VIDEO_DEVICE] [REGION] [PIX_FMT]
Encodes input from a VHS / Camera / Cassette stream to a mp4 video.
OUTPUT_NAME filename of mp4 video (DEFAULT; no need for mp4 suffix )
or, filename of m4a sound file (needs m4a suffix )
or, filename of mp3 sound file (needs mp3 suffix )
VIDEO_DEVICE eg 'dev/video0' (try "v4l2-ctl --all" )
AUDIO_DEVICE eg 'hw:2,0' (try "arecord -l" or "arecord -L" or "cat /proc/asound/cards" )
REGION eg 'PAL'
PIX_FMT eg 'yuv420p' (v4l2 default is yuyv422, but that prevents display on some devices)
Note:
Only use "q" to quit from the running process in the terminal
See:
V4L-Capture (Mirror of the v4l Utilities Written by Andrew Sayers)
Encode-Stream (BASH Script to encode VHS / Camera / Cassette Streams)
My copy on desktop machine of encode_stream script is dated Dec 21 2021, and I have not used it recently, but I know of zero reason why it should not work today.
Wow! I am sorry if I came across as being offended.
...and I'm sorry if I over-reacted.
I wrongly expected the digikam package to trigger installations required to meet dependencies or notify me of those that were not available.
…and that is why I used the words 'skew-whiff'. It was NOT intended as a comment on you personally, the comment was aimed at your situation.
I've personally been in the classic Linux situation of dependency-hell. I was running an internet server at the time (CentOS, which was derived from RHEL). My guts therefore squirm in sympathy with anyone finding themselves in a similar situation.
Anyone that has been in that state will also know the classic response from the Distribution maintainers / long-term users to such a problem (the image is of a set of people all placing their arms in front of their chests into the sign of the cross & mumbling the words "all your own fault, nothing to do with me, guv").
Credit to Debian for attempting to escape from Dependency Hell with a well-maintained & documented Repository system that, by majority, keeps everyone's system clean & responsive.
Credit to Devuan for attempting to escape from the brand-new SystemD Hell, a process of escape that echoes many of the characteristics of ridding a forest of Japanese Knotweed, and a virus that promises a level of software Hell lower & more pernicious than any previously known in human experience.
In the face of your situation I tried to help by reporting on my system's (also Daedalus) response to searches on your problematic binaries.
My system is also Daedalus. Recently upgraded to kernel 6.1.0-12. Something must be skew-whiff in your system. In the following, I do not have DigiKam installed.
$ apt show libtiff.so.5
N: Unable to locate package libtiff.so.5
N: Couldn't find any package by glob 'libtiff.so.5'
N: Unable to locate package libtiff.so.5
N: Couldn't find any package by glob 'libtiff.so.5'
E: No packages found
$ locate libtiff.so
/usr/lib/x86_64-linux-gnu/libtiff.so.6
/usr/lib/x86_64-linux-gnu/libtiff.so.6.0.0
$ apt search tiff
# …
libtiff-tools/stable,now 4.5.0-6 amd64 [installed,automatic]
TIFF manipulation and conversion tools
libtiff6/stable,now 4.5.0-6 amd64 [installed,automatic]
Tag Image File Format (TIFF) library
Please stop full-post quoting almost *every* reply, that is just childish nonsense. If you wish to indicate what you are replying to, then edit the text down to the minimum. These forums are noisy enough as they are without scores & scores of full-text quotes.
I can't copy information from the terminal. I press ctrl+c but nothing
If you are using the "xfce4-terminal" (see menu:Help | About) then the command to copy highlighted-text is shown at menu:Edit | Copy (key-command is Shift+Ctrl+C).
firexox: speling
$ apt search firexox
Sorting... Done
Full Text Search... Done
# (nothing)
Could be the source of your problems.
There are a number of what seems from my desktop to be useful answers to your specific use-case here (stackoverflow).
First signs of the wall breaking.
Thanks for that, swanson (I was so close yet so far away!).
A very good link for the whole process:
Using UUID to Update FSTAB
I'm *very* surprised that, after all this time, there isn't a programmable way to do the whole thing. That manual step puts a big block in uptake.
Here is blkid on my system. sda1 is a usb-connected hdd and one of the main reasons for the modern use of UUIDs:
$ sudo blkid
[sudo] password for alexk:
/dev/sdc1: LABEL="SG-2TB" BLOCK_SIZE="512" UUID="5DB88E2B4D416357" TYPE="ntfs" PARTUUID="82de246a-01"
/dev/sda2: UUID="689f9e16-2d78-4635-b9c1-d68a8994e668" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="924dc2aa-fbd2-4747-b356-3cf070a966df"
/dev/sda3: UUID="f10d59d3-426b-499e-afa1-8715920318c3" TYPE="swap" PARTUUID="54a5a38e-ae7f-41e7-8c88-f0014e7cefe0"
/dev/sda1: UUID="4CD1-6816" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="75179c70-b3b4-4c5e-9684-21cf493e8438"
Look at the mount help files. Use UIDs (cannot recall actual name). Then you will have unchanging mount points that Audacious will always be able to find.
I'll add the name of those unchanging-IDs if I can find them (I've never used them personally).
What to do with browsers?
Use the command terminal to discover the state of your firefox install (or whichever of the 200 different browsers you want to use).
the following piece of code is issued from a Terminal
it is likely that you will need to type sudo before issuing the command
the apt command requires that you are the root user before you issue it
sudo is a "do as root" command.
If you do not yet have sudo installed then follow the instructions in this link (one-time only);
the '$' prefix indicates that you are working in the command window as an ordinary user;
a '#' prefix would indicate that you are the root user (only ever do that for administration; always work as an ordinary user);
you do NOT have to enter either char to get the prefix
$ apt search firefox-esr | head
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Sorting...
Full Text Search...
firefox-esr/stable-security,stable-proposed-updates,now 102.14.0esr-1~deb12u1 amd64 [installed]
Mozilla Firefox web browser - Extended Support Release (ESR)
firefox-esr-l10n-ach/stable-security,stable-proposed-updates 102.14.0esr-1~deb12u1 all
Acoli language package for Firefox ESR
firefox-esr-l10n-af/stable-security,stable-proposed-updates 102.14.0esr-1~deb12u1 all
Afrikaans language package for Firefox ESR
The important part of the result is the word "[installed]". If that does not exist then do a apt install firefox-esr or use synaptic to install it. Once you have done that you will get a menu-link under the "Internet" sub-link for Firefox. Once you get used to your Desktop you can place logos as links for your most-common utilities within the Panel.
Cheers!
Some small notes to try to quickly key you in to the way Devuan works cf Windows.
The original Windows was a text-based OS that later (1995) got a graphical desktop added to it. They then later tried to convince the world that Windows was a graphical masterpiece and oh, there was a sort-of command window added to it.
Devuan is a software kernel (common to all versions of 'Linux', which is the Operating System (OS)) which has options for a terrifyingly-large number of user-shells. The shells - only one of which is required - are the means for a human to interface with the underlying OS to 'get stuff done'.
Software writers tend to be used to dealing with text, and therefore are used to working within a command-terminal, which is a text-terminal. Confusingly, these are often called "Terminal Emulators". There are a great many of them available (Linux's problem is usually "too much stuff" rather than "too little stuff"). The most common OS for the terminal is BASH, known as the "GNU Bourne-Again SHell" (first was the 'Bourne Shell", known as 'BSH'). There are also lots & lots of different shells that can be used in a Terminal.
The great advantage of text-terminals is that they require far less resources than graphical shells, and that makes them inherently far, far faster.
The next option to operate your computer is via a Graphical shell which, for Linux, is normally a version of the X Window System. Linux *always* starts in text-mode, then at a point during startup it will launch startx (or maybe the local-shell's version of that command), and the X-Session will begin showing you a GUI ("Graphical User Interface") rather than a TUI ("Text User Interface").
The default GUI for Devuan is XFCE which is renowned as a stable, lightweight Desktop. There are scores of others that can be used.
The final point to make is that, with Devuan, both GUI & TUI are on an equal footing. BASH is extremely stable & useful as an interface, as is XFCE.
That's a heck of a lot of 'small notes'. HTH.
Use "yt-dlp". Seems old (March) but is actually upto date & works fine.
I've got to amend my own advice.
The Repository version of yt-dlp is still stuck at March & I found recently that YT has managed to throw another spanner into it's works, stopping it from downloading. I placed the GitHub linux version into .local/bin & it throws up errors but does get the job done:
$ /usr/bin/yt-dlp --version
2023.03.04
$ ~/.local/bin/yt-dlp --version
2023.07.06
Thanks for the advice, Ralph.
I've been through the process before (just the once), but since golinux said that s/he was going to choose the ones s/he wanted I was leaving it in h/er/is hands. I'm a bit busy with other stuff (it's Thursday & the bins are emptied today & I've missed them yet again as I'm preoccupied with other stuff).
You are welcome to add them to Devuan's git (GPL3). Not something I can do as best I understand the case (I can do a pull but not a push, since I'm not root there.).