Imaging cloud transfer to dropbox: "... JPEG marker segment length..."

[JRedV]

Arrgh. I set up Nikon Imaging Could and am successfully transferring files to a Dropbox account. Easy?! Maybe.

I'm on Mac, and when I double-click the image name (no preview shown), the image opens in Apple Preview just fine. But if I'm trying to open it on Photoshop or preview it in Adobe Bridge, or NX Studio the image displays an error : " Could not open “DSC_2005.JPG” because a JPEG marker segment length is too short (the file may be truncated or incomplete)." It appears something gets truncated in the transfer that the sophisticated programs. can't handle.

I've tried resaving the file as a similar name and switching from .JPG to .JPEG to no effect.

I tried converting the files in NXStudio, but the operations can't be completed on "unsupported files"

I don't want to have to open every file in Preview to get it to be seen by other programs. Can anyone point me to a source for instruction to set this up better? Here's the set up screen from NIC, shoiwing thr transfer took place to dropbox.





I climbed the mountain to get the transfer to work, I'd hate to think it was wasted effort. Many thanks in advance.

 

[Schteeks]

Commenting to follow. I haven’t tried this feature of Imaging Cloud yet, but possibly interested. I think SnapBridge has a similar auto transfer feature, but I don’t think it goes all the way to Dropbox and only transfers to the phone.

 

[Barleyman]

I did a compare of my files from Imaging Cloud and they are identical to the files on the camera.

Maybe dropbox is changing them?

 

[jthomas39]

I did my usual troubleshooting first step, google the phrase.

This Photoshop Elements forum member had the same message from Dropbox files.

There's the usual conflicting advice in the replies. But there seems to be a dropbox fix that was to roll out in 2023.

https://community.adobe.com/t5/phot...t-length-is-too-short-quot-error/m-p/13462028

And an inconclusive i-cloud thread:

Loading…

discussions.apple.com

So there does seem to be some incompatibility with cloud jpg storage. That surprises me.

~~

Try this: download one of the bad jpgs from dropbox to your computer. Will it open correctly then?

 

[JRedV]

Thanks for getting farther in a web search than I could!

I'll dig in and see if it leads to anything. I'm fairly (80%) certain my dropbox app has been updated in the last 6 months.

I was able to view all the JPEGS after a mass open in Preview, as suspected. But that leaves the RAW files still untouchable.

Do most people who are using imaging cloud just manually download the files?

I'm so over clouds.

 

[JRedV]

The file is not corrupted if I manually download from NIC. I submitted this request to Dropbox support:

When transferring JPEGs or RAW files from Nikon Imaging Cloud automatically to my Dropbox (ver 224.) on my local iMac (OS 15.2), I observe an error that says "Could not open “DSC_2005.JPG” because a JPEG marker segment length is too short (the file may be truncated or incomplete)."

If I download the same image directly from Nikon Imaging Cloud to my desktop, the error does not occur. The JPEG opens as expected in Photoshop and is previewable in Adobe Bridge. Something is happening to the file when Dropbox receives it to change data that makes it unrecognizable.

The JPEG image is openable in Mac Preview and can then be edited, but I do not want to have to manually open each file before I can edit in PS. Can you point me to a solution?

 

[Joep van Steen]

Arrgh. I set up Nikon Imaging Could and am successfully transferring files to a Dropbox account. Easy?! Maybe.

I'm on Mac, and when I double-click the image name (no preview shown), the image opens in Apple Preview just fine. But if I'm trying to open it on Photoshop or preview it in Adobe Bridge, or NX Studio the image displays an error : " Could not open “DSC_2005.JPG” because a JPEG marker segment length is too short (the file may be truncated or incomplete)." It appears something gets truncated in the transfer that the sophisticated programs. can't handle.

I've tried resaving the file as a similar name and switching from .JPG to .JPEG to no effect.

I tried converting the files in NXStudio, but the operations can't be completed on "unsupported files"

I don't want to have to open every file in Preview to get it to be seen by other programs. Can anyone point me to a source for instruction to set this up better? Here's the set up screen from NIC, shoiwing thr transfer took place to dropbox.

I climbed the mountain to get the transfer to work, I'd hate to think it was wasted effort. Many thanks in advance.

JPEGsnoop is good for trouble shooting JPEG issues, it will decode the JPEG byte-by-byte and tell you if it finds anomalies.

Loading…

github.com

If you share one of the offending files then maybe someone here can spot what's wrong with it.

But if it's related to uploading or something via some client it's probably something you can not solve.

 

[AlainCh2]

....

Do most people who are using imaging cloud just manually download the files?

I'm so over clouds.

I'm a Dropbox user from the beginning.
I love the way it works, and you get the full W10 way on Explorer inside any of my PCs to manage files as the local ones.

I NEVER USE DROPBOX MANUALLY

I tested passing images via ImageCloud to Dropbox. It works fine for me on Zf & Z50II.

I usually use another Dropbox method:
I connect the Bodies to a Powered Hub, which is connected to an old dedicated laptop.
Dropbox does the job, dealing with the pics. The hub charges the batteries. Even in my Car or in a Hotel, it's quite an efficient mode. First, the images are saved on the Local disk, then transmitted to the cloud when and if a Net connection is available.

Note:
Having used both ImageCloud -A N D- Dropbox-direct on the same body, on the same shooting session...

...Dropbox managed not to have a double copy of the same images.

I also tested the connection via UsbC to the Xiaomi Cell, and the Android-Dropbox App did its job perfectly.





( Dropbox also renames files for me with a standard name [YYYY-MM-dd HH.mm.ss] )

 

[JRedV]

Hi all:

I'm marking this solved-mostly.

Here's the update:

Dropbox support asked me to try to mark the files that are transferred from NIC as "available offline". After I did this, the file was completely viewable and actionable. JPEGs and NEFs.

So, there's an extra step to take, but it's one click and can be a batch operation. I'm still asking Dropbox if this means the files is stored locally, or does some mid-way operation to get it ready for use. Kind of defeats the purpose of cloud storage.

Thanks for all the suggestions and input.