Open GoogleCodeExporter opened 9 years ago
I experimented and put images taken by another camera maker (Sony and Casio) in
the Subfolder A directory. When I did so, the images showed up properly in
Flickr.
However, for pictures taken with my Canon camera, they do not get uploaded to
Flickr.
Original comment by dya...@gmail.com
on 17 Aug 2011 at 6:46
Same problem here. Tried uploading 4 images taken with a Canon EOS, 2 of them
upped correctly, others not.
Original comment by pete...@gmail.com
on 4 Sep 2011 at 6:34
The above comment however, occurs to me in debian running 'python uploadr.py' -
no windows.
Original comment by pete...@gmail.com
on 4 Sep 2011 at 6:35
The photos that I had that didn't upload properly were taken on a Canon
PowerShot S3 IS. But interestingly enough, pictures that I took on a Canon
PowerShot A70 (a model from about 9 years ago) uploaded just fine.
I experimented with another camera "maker" (my iPhone 3GS camera) and found
that images taken with my iPhone 3GS upload just fine.
Original comment by dya...@gmail.com
on 9 Sep 2011 at 2:43
Also uploading batches of pictures from various cameras, and hit the same snag
as you folks with the Canon Optura400. (I highly doubt it matters, but I'm
running the python code in Windows.)
Original comment by ThaiB...@gmail.com
on 19 Sep 2011 at 8:58
A workaround is to comment out the Canon exif data handling from exif.py.
About line 1576 in the file exif.py, comment the section out so it looks like
this:
# Canon
# if make == 'Canon':
# self.dump_IFD(note.field_offset, 'MakerNote',
# dict=MAKERNOTE_CANON_TAGS)
# for i in (('MakerNote Tag 0x0001', MAKERNOTE_CANON_TAG_0x001),
# ('MakerNote Tag 0x0004', MAKERNOTE_CANON_TAG_0x004)):
# self.canon_decode_tag(self.tags[i[0]].values, i[1])
# return
I must admit that I really do now know what consequences this has to the
uploading of pictures - but it works.
Original comment by pete...@gmail.com
on 19 Sep 2011 at 9:12
Hi Pete,
Thanks for the work-around! It seems to preserve the camera model information
when a photograph is uploaded, so I have no idea what commenting those lines
out means either.
Oh well... whatever works :)
Original comment by ThaiB...@gmail.com
on 19 Sep 2011 at 9:35
Could someone upload a new exif.pyc file for me? I am not a programmer and
don't know exactly how to modify the exif.py file and generate a new exif.pyc.
Thanks!
Original comment by dya...@gmail.com
on 20 Sep 2011 at 5:39
I'm not sure if my exif.pyc file will work for you. We can read the same .py
code, but once it is compiled (hence the "c" in .pyc) on our individual
computers, it is specific to the machine. I'll upload it anyway in case I am
completely wrong about this.
If it doesn't work, maybe it's time to download python :)
Original comment by ThaiB...@gmail.com
on 20 Sep 2011 at 6:49
Attachments:
Thanks for posting, but you're right: when I slap that exif.pyc file into my
library.zip archive and then run uploadr.exe, it shows an import error and says
that it cannot find exif.py.
Guess I'll have to figure out how to compile.
Original comment by dya...@gmail.com
on 24 Sep 2011 at 12:11
[deleted comment]
[deleted comment]
[deleted comment]
Windows EXE 1.0 does not work for me either. Sets not created; images not
uploaded. I'd love to get this to work since i just got Flickr Pro and would
like to upload my 75GB of photos already organized in folders! Thanks for the
help.
ERROR.LOG:
tags2set: Cannot create set
<type 'exceptions.IndexError'>
tags2set: Cannot edit set
<type 'exceptions.AttributeError'>
tags2set: Cannot create set
<type 'exceptions.IndexError'>
tags2set: Cannot edit set
<type 'exceptions.AttributeError'>
tags2set: Cannot create set
<type 'exceptions.IndexError'>
tags2set: Cannot edit set
<type 'exceptions.AttributeError'>
(<type 'exceptions.MemoryError'>, MemoryError(), <traceback object at
0x0249DA30>)
(<type 'exceptions.MemoryError'>, MemoryError(), <traceback object at
0x024A0468>)
(<type 'exceptions.MemoryError'>, MemoryError(), <traceback object at
0x024A81C0>)
ERRORS in DEBUG.LOG:
2012-11-10 14:55:15,062 DEBUG Getting EXIF for D:\Flickr\TestDir\IMG00001.JPG
2012-11-10 14:55:15,608 ERROR (<type 'exceptions.MemoryError'>, MemoryError(),
<traceback object at 0x024A81C0>)
Original comment by shigad...@gmail.com
on 10 Nov 2012 at 8:02
I faced the same issue yesterday, so I decided to read the source code of
exif.py in order to implement what is described in comment #6. In the top of
the source code, there's a comment that points to the project's link
(http://sourceforge.net/projects/exif-py/) but project was moved to
https://github.com/ianare/exif-py.
I downloaded the latest version of exif.py, backed up the original one and
replaced it with the new version (filename must be in lowercase). It worked
perfectly!
To check if the errors are solved with the new version, you can execute (on a
problematic picture):
$ python exif.py <filename> (exif.py new version)
$ python exif.py.orig <filename> (where exif.py.orig is the old version. It
should return a LOT of errors)
Hope it helps!
Original comment by lopezrig...@gmail.com
on 28 Jan 2013 at 2:39
I have had the same issue... and fixed it using the new version 1.2.0 of
exif-py from
https://github.com/ianare/exif-py...
I am using Ubuntu 13.04 and actually have 18.000 Fotos uploaded with
folders2flickr :-)
Give it a try...
Original comment by jensmah...@gmail.com
on 13 Jun 2013 at 7:18
Original issue reported on code.google.com by
dya...@gmail.com
on 17 Aug 2011 at 6:20Attachments: