Seamlessly using GoProX on the same GoPro media from multiple computers? #50
victorhooi
started this conversation in
General
Replies: 7 comments 4 replies
-
|
Hi, There is nothing specific to a particular computer. You are correct the config file can be the same on multiple devices. However, if those devices do not share the same library, each of them will collect its own GoPro media files without sharing them with the other devices. For many use cases, that might be perfectly fine. These files can be merged together by hand, but the tool currently does not support any form of library merges. I suggest you try it and use the I hope this helps! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ah - in this case, each of the laptops/desktops would be pushing the GoPro media to a shared network drive (e.g. SMB share). However, is there any state in the actual Or is all state maintained on the GoPro SD cards themselves, as metadata files? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ok makes sense. There is very little state on the sd cards - just minimal flags (empty files) to ensure a card that gets re-mounted does not get re-imported. Once the card gets cleaned, all flags get removed. There is no state information of any kind in |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
OK - I'm going to give it a shot. I just had two other follow-up questions:
Also - I just did a quick test run (with just |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
As for the archive, One closing tip: If you are unsure what goprox does or how it does something, simply open the goprox file here on GitHub or in your favorite editor (e.g. Visual Code) and search for an option. Line 933 in 7ca8dff that Most SD card readers perform at 20-80MB/sec. Once the data is on an SSD, you will see 700MB/sec up to 1GB+ rates for anything Good luck! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for your help explaining things! I'd love to help with the docs (to make it easier from a newbies perspective) if you're OK with that? PerformanceOK, the run finished - this was a 1TB MicroSD card - it probably took around 10-ish hours. I'll do some more testing later - but rough napkin calculations, that's around 12 MBits/second? This is using the ProGrade Dual Micro-SD card reader - it's USB 3.2 Gen 2, so it should be much faster. The MicroSD card is a SanDisk Extreme MicroSD card. The performance seems a bit slow, so it does seem like it must be bottle-necked somewhere - what do you think? Archive followed by Import.From what I can tell, the Archive stage read directly from the MicroSD card to my network drive. However, the Import stage then read from the MicroSD card itself - not the Archived file: Is this what you would expect? If so, do you think there's any performance benefit to reading from the Archive file itself? GeoNames ConfigurationThanks for the tip about GeoNames account - I didn't know you had to create and configure an account before-hand. I did see this in my run just now: Does this mean that the Geonames part didn't run? I've just created a Geonames account - however, how do you actually add this to GoProX? This is the contents of my I do see a I'm not a bash expert - but checking here - it seems like I just need to put in the username? Is there no need for a password or anything like that? I couldn't see this documented anywhere in the GoProX project, let me know if you would like me to help with the docs? Also - if I have run the import with geonames already, and I didn't have the account setup, is there any way to run just the geonames part again, to fix those imported files? |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Yes, that is really slow. My uneducated bet would be this is due to SMB file shares. Never had any good performance experience with them. A few thoughts: Add Any tasks you run with For example, if you run In order to test importing from the archive you can simply run As for geonames simply put your geonames account name into your goprox config file. run Always do all the testing on local drives first - preferably SSDs. Terabyte sized volumes take time to process under the best of circumstances. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, I just updated my From the output it seems to have succeeded with no errors - but I'm not sure it actually did anything? Also, if I check the geonames.json file in each folder, the timestamp hasn't actually updated, so I assume the files weren't modified? Also, all of those Is there any way to verify that running Or do you see something wrong with what I'm doing above? |
Beta Was this translation helpful? Give feedback.
-
PerformanceAlso, I just ran it again, with a single 6.85 GB video file on the MicroSD card - totally processing time was around 4.75 minutes, which I think is around 200 Mbits/s, right? Still seems a bit slow, I might need to dig into it on my end to figure out the bottleneck. (Unless you can spot something that stands out in the above output). GeonamesAlso, it seems you also need to enable the free webservice, after you create a Geonames account - it might be worth documenting that in the README, I'm happy to file a PR, once I've collated all my experiences/findings as a new user: I've just done that - however, it still does seem like running |
Beta Was this translation helpful? Give feedback.
-
|
I just did another quick run on a 512GB MicroSD card - this time, instead of using the external USB-C MicroSD card reader, I used the Macbook Pro's internal SD card slot. I was still writing to the network share, via a 10Gbase-T network adapter. Total time was around 4.5 hrs (4 hrs, 36 minutes, 1 second, per calculator.net...lol). Archive tarball size was 494.25 GB, so about 260 Mbit/s. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding performance: Please do a local-only test, or you have no baseline of what is possible. Write to the local SSD for the archive, for example. You can then import directly from the archive and compare the read and write rates. It does not matter what 1/10/100Gb network you are on if the protocol is slow. The only way to eliminate that is to do it locally into an SSD. Even an external Samsung T7 will do 400-800 Mega Bytes per second by itself. That way, you can compare the various SD-Card readers. Once you have that baseline, you can compare it to your network numbers. Especially SMB shares are known to be very slow on Macs. Just google As for the In general |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there a recommended way, or workflow for using goprox from multiple end-user devices?
For example, if you have a single GoPro (and SD card), what is the best way of using GoProX with it from different laptops/desktops, without breaking anything?
(I'd like be doing this via a SD Card reader, rather than connecting the GoPro directly to the computer).
It seems like GoProX stores state using small metadata files on the SD card itself, right?
Should it be simply having the same configuration files from
~/.goprox, and copying this to each computer? Or is there more to it?Beta Was this translation helpful? Give feedback.
All reactions