Unable to read .png files after downloading. How do I get older .jpg files?

[boring-pilot]

On a w7 system, I am unable to display the downloaded .png files. The error states the images are corrupt or too big. Is is possible to get the older .jpg files?

[tareko]

Hello @boring-pilot,

Thank you for your report. Could you please help us with the following information:

1. Do the images work inside a browser? e.g., this direct link

2. Do they work inside GIMP or some other image editing tool?

3. If (1) and (2) are true, where is it failing and how? i.e., which image viewer.

4. How are you downloading the images? Because they are on GITLFS, that may be causing problems too.

Here is the file type and size of the above file, print_guide-01.png:

$ file print_guide-01.png 
print_guide-01.png: PNG image data, 717 x 500, 8-bit/color RGBA, non-interlaced
$ ls -l print_guide-01.png 
-rw-rw-r-- 1 x x 56069 Feb 19 07:43 print_guide-01.png

Thank you for your help,

tarek : )

[boring-pilot]

Tarek,

1. The files look OK inside the browser in Github,
   2,3) None of the image viewers I had, including Libre Office Draw, could read the file, similar error mesages/
2. I downloaded the whole thing as a .Zip file, unzipped on disk. and then tried to open individual .PNG files in the subfolders of media folder.
   LibreOfficeDraw just displays some text -- example from assembly-01.png ...
   version https://git-lfs.github.com/spec/v1
   oid sha256:e43f0b05b6061012cc26d39b6fa63287fe83f8b5725bf9e8711c0a956847330c
   size 1585302

[boring-pilot]

Tarek, I replied on Github, just adding here that I am building it for my gal, a retired Audiologist. She will give it a good working over... Also, a lot of the Amazon references are not "orderable" -- it may be because you are in Canada and I am in USA.... --Mark

…

On Sun, Feb 18, 2018 at 9:49 PM, Tarek Loubani ***@***.***> wrote: Hello @boring-pilot <https://github.com/boring-pilot>, Thank you for your report. Could you please help us with the following information: 1. Do the images work inside a browser? e.g., this direct link <https://media.githubusercontent.com/media/GliaX/Otoscope/master/media/print_guide/print_guide-01.png> 2. Do they work inside GIMP <https://www.gimp.org/> or some other image editing tool? 3. If #1 <#1> and #2 are true, where is it failing and how? i.e., which image viewer. 4. How are you downloading the images? Because they are on GITLFS, that may be causing problems too. Here is the file type and size of the above file, print_guide-01.png: $ file print_guide-01.png print_guide-01.png: PNG image data, 717 x 500, 8-bit/color RGBA, non-interlaced $ ls -l print_guide-01.png -rw-rw-r-- 1 x x 56069 Feb 19 07:43 print_guide-01.png Thank you for your help, tarek : ) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATf6lFt8kGdXsAgNyz-TXZI8pfvoSC72ks5tWQtVgaJpZM4SJ32N> .

[tareko]

Hi @boring-pilot,

It appears that the problem is that you are getting stuck with Git LFS. Git does not keep the LARGE files, but instead puts them in the LFS (large file storage). When you download the zip, you are actually downloading the reference. I didn't realize that the ZIP option wasn't LFS aware, though it is reported in this bug and the issue appears unresolved.

How do you workaround this bug? By either using the web interface and downloading manually, or by using git to do a 'git clone' through the command line or Github's desktop application or any other Git client.

Is there any reason not to just look at the README's while online?

tarek : )

[tareko]

@boring-pilot: Regarding your second point about the Amazon links, I have opened and closed Issue #2 with some explanation. We welcome contributions as to other parts that appear to work, but our team will not pursue alternatives actively. Think of the links more as documenting what we used rather than being a definitive list of what others should use.

tarek : )

[boring-pilot]

I can use the pictures on line. I was just dutifully reporting things that didnʻt seem to work. I have ordered the parts (yes, I used the Amazon links as documentation) and have started printing, trying to use PETg, some success.

…

On Tue, Feb 20, 2018 at 10:31 PM, Tarek Loubani ***@***.***> wrote: Hi @boring-pilot <https://github.com/boring-pilot>, It appears that the problem is that you are getting stuck with Git LFS. Git does not keep the LARGE files, but instead puts them in the LFS (large file storage) <https://git-lfs.github.com>. When you download the zip, you are actually downloading the reference. I didn't realize that the ZIP option wasn't LFS aware, though it is reported in this bug <git-lfs/git-lfs#903> and the issue appears unresolved. How do you workaround this bug? By either using the web interface and downloading manually, or by using git to do a 'git clone' through the command line or Github's desktop application <https://desktop.github.com/> or any other Git client <https://git-scm.com/downloads/guis>. Is there any reason not to just look at the README's while online? tarek : ) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATf6lNXktg4wqWdQBtHQ6YobuKtau8MDks5tW7hEgaJpZM4SJ32N> .

[tareko]

Amazing! Thank you for the report - I've been trying to figure out if LFS is right and this helps in making the decisions. Good luck with the PETG. I'm curious how it turns out. Please do post images!

tarek : )

[boring-pilot]

Where should I post images? The wiki? Facebook? 3d printing done, waiting for parts.

[tareko]

Congrats! Maybe https://imgur.com is the best place to post pics like that publicly?

[Reveta]

2022 year. It`s still a problem :(

[shababo]

Hi, I had a similar problem trying to get image from a different repo - found this thread trying to solve it. Neither cloning nor downloading files provided more than the links. However, downloading the assets director of that repo using this web tool did work. Hope this helps anyone else.