Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gopro: Prelude.read: no parse #7

Closed
mateuszdrab opened this issue Mar 13, 2022 · 3 comments
Closed

gopro: Prelude.read: no parse #7

mateuszdrab opened this issue Mar 13, 2022 · 3 comments

Comments

@mateuszdrab
Copy link

First of all, thank you for creating this tool!
It saved me from having to manually download each video from the cloud, now that I'm about to cancel the subscription.

Just wanted to flag an issue to you, the gopro sync and gopro fetchall commands were failing with gopro: Prelude.read: no parse

I eventually figured out the list of all media and ran the refresh command on each of them, after that, I was able to download them.

A specific issue example:

gopro refresh xxxxx
I: Processing batch of 1
gopro: Prelude.read: no parse

Not sure exactly why it's failing, but my library of 65 items had 2 errors.

Perhaps if you added a printout of the response from the API request into the verbose option, it would be easier to figure out as adding -v currently doesn't do much.

I've got a month left on my subscription so happy to help you figure out why the error happens before all my content is deleted from there.

Regards
Matt

@dustin
Copy link
Owner

dustin commented Mar 14, 2022

Hmm... That's interesting. There aren't that many options. One of the areas that this might occur has to do with medium types that aren't in the original set I built code around. I see this now:

        PHOTO: "Photo",
        VIDEO: "Video",
        TIME_LAPSE: "TimeLapse",
        TIME_LAPSE_VIDEO: "TimeLapseVideo",
        BURST: "Burst",
        CHAPTERED: "Chaptered",
        LIVESTREAM: "Livestream",
        LOOPED: "Looped",
        LOOPED_VIDEO: "LoopedVideo",
        BURST_VIDEO: "BurstVideo"

Several of those won't be processable by my code. I can fix that relatively quickly and also perhaps make a better error in the case this grows again.

I've got a lot of media uploaded, but almost all of it is uploaded by my own tools, so I wouldn't have, e.g., a LoopedVideo upload because I just treat that like a normal video. I'm not even sure how to get some of these other ones, but at the very least, I can support them in code.

@dustin dustin closed this as completed in f48a6f9 Mar 14, 2022
@dustin
Copy link
Owner

dustin commented Mar 14, 2022

I'm uploading a change that includes support for these new types. You should be able to sync assuming that was the problem. Let me know if that's not the case.

@mateuszdrab
Copy link
Author

mateuszdrab commented Mar 14, 2022

That did the trick, it downloaded the missing video (that I previously downloaded manually).
Thanks again for making this tool! Life saver, should be an official tool from GoPro. ❤️

Quick question, is there a difference between sync and backupall commands? I noticed the sync command was running downloads into a .cache folder but I already downloaded all content. Can I use the content form the backupall command to upload things back into gopro cloud in the future using gopro upload (will it upload the metadata)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants