Package Details: gopro-webcam 0.0.3-1

Git Clone URL: https://aur.archlinux.org/gopro-webcam.git (read-only, click to copy)
Package Base: gopro-webcam
Description: Utility to use a GoPro as a webcam
Upstream URL: https://github.com/NewoIsTaken/gopro_as_webcam_on_linux
Licenses: unknown
Submitter: Newo
Maintainer: Newo
Last Packager: Newo
Votes: 1
Popularity: 0.000000
First Submitted: 2021-08-05 18:53 (UTC)
Last Updated: 2021-08-06 16:41 (UTC)

Latest Comments

karolyi commented on 2023-03-03 18:04 (UTC)

I get the same message with my gopro 4. Not sure how this thing is supposed to work.

arsh commented on 2022-05-29 22:39 (UTC) (edited on 2022-05-29 22:39 (UTC) by arsh)

I get this error. Does anyone know what the useful message should be?

~/ sudo gopro webcam
[sudo] password for ap: 
Running GoPro Webcam Util for Linux [0.0.3]

       Launch Options     
==========================
 * Non-interactive:  0
 * Autostart:        0
 * Preview:          0
 * Resolution:       1080p
 * FOV:              linear
==========================

v4l2loopback is loaded!
v4l2loopback was unloaded successfully.
v4l2loopback was successfully loaded.
Please plug in your GoPro and switch it on. If it booted successfully (Charger icon on screen), hit Return


Guessing the GoPro's device name...
I can only make an uneducated guess wrt the name of the interface that the GoPro exposes.
For me the name of the interface is 'enxf64854ee7472'. This script will try to discover the device
that was added *last*, as you just plugged in the camera, hence the interface added last should be the one we're looking for.

Discovered: enp0s31f6.
Using enp0s31f6 to discover the GOPRO_IP.
Found 192.168.1.129
To control the GoPro, we need to contact another interface (GOPRO_IP ending with .51).. Adapting internally..
Now using this GOPRO_IP internally: 192.168.1.51
Error while starting the Webcam mode. # TODO Useful message.

darkace commented on 2022-05-25 00:17 (UTC) (edited on 2022-05-25 00:18 (UTC) by darkace)

@diegovelezg I had the same problem and this seemed to fix it for me <sudo pacman -Syu linux-headers>

diegovelezg commented on 2022-02-06 14:58 (UTC)

Got hits. Anu advise?

v4l2loopback is not loaded! v4l2loopback does not exist. Please either install v4l2loopback or get it from source via https://github.com/umlaeute/v4l2loopback

Hemann55 commented on 2021-09-27 08:54 (UTC)

@Newo

Testing on Hero Session. Gives the following error

Discovered: enp8s0. Using enp8s0 to discover the GOPRO_IP. Found 192.168.29.178 To control the GoPro, we need to contact another interface (GOPRO_IP ending with .51).. Adapting internally.. Now using this GOPRO_IP internally: 192.168.29.51 Error while starting the Webcam mode. # TODO Useful message.

Newo commented on 2021-09-21 02:17 (UTC)

@meetmarvin, thank you for letting me know! I added gopro-tools-git as a conflict.

meetmarvin commented on 2021-09-20 11:52 (UTC)

Having an error if gopro-tools is already installed.

Packages (1) gopro-webcam-0.0.3-1

Total Installed Size:  0.01 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                  [########################################################] 100%
(1/1) checking package integrity                                                                [########################################################] 100%
(1/1) loading package files                                                                     [########################################################] 100%
(1/1) checking for file conflicts                                                               [########################################################] 100%
error: failed to commit transaction (conflicting files)
gopro-webcam: /usr/bin/gopro exists in filesystem (owned by gopro-tools-git)
Errors occurred, no packages were upgraded.

Newo commented on 2021-08-05 21:50 (UTC)

@flyingpig, thanks for the reminder! I was going to change that but forgot.

flyingpig commented on 2021-08-05 21:10 (UTC)

Hello, I noticed that 60-gopro.rules makes use of /usr/sbin/service aka /usr/bin/service. However, I don't think this executable actually exists on Arch Linux, so it might be better to use systemctl from the systemd package instead.