Skip to main content
Inspiring
November 8, 2016
Released

P: Ability to export more than 15 photos at a time

  • November 8, 2016
  • 81 replies
  • 2218 views

Here is our conversation about CS and me
Naveen GK: Hello! Welcome to Adobe Customer Service.
Naveen GK: Hi Yeung
yeung y: Hello
yeung y: i have a question
yeung y: how can I do unlimited dng export to jpg on my iOS and android Lightroom mobile
Naveen GK: I understand that you would like to use Lightroom free trial on ipad. Is that right?
yeung y: Correct
Naveen GK: Let me check and help you with that.
Naveen GK: May I place this chat on hold for a minute or two, while I check the information for you?
yeung y: Of course, thank you
Naveen GK: I'm sorry, Yeung . It's taking time please allow me few more minutes.
yeung y: Please
Naveen GK: Thank you for staying online
Naveen GK: I checked and see that there is no subscription under this account: [removed]
Naveen GK: Since you are using the trial version, I'll transfer the chat to our technical team to check and help you better. Please stay online
yeung y: And also one more question
yeung y: and also when I'm using android Lightroom mobile , For example I have 5 dng files convert to jpg , once I tag the photo from left to right , e.g : 1.dng , 2.dng , 3.dng , 4.dng , 5.dng , the final concert files is not in sequence , like 3.jpg , 1.jpg , 2.jpg , 5.jpg , 4.jpg . Is it normal?
Naveen GK: Yeung, we are from customer service team and our technical team will be able to check and help you with that. Please stay online
yeung y: Thank you so much info: Please wait while we connect you to a representative.info: You are now chatting with Priyank Dubey. Please don’t close the chat window or browser tab since it will end our chat session.
Priyank Dubey: Hello! Welcome to Adobe support.
Priyank Dubey: Please allow me 1-2 minute(s) to review your account details.
yeung y: Thank you
Priyank Dubey: DNG is only available for iOS not for Android yeung y: It's work android as well
yeung y: The latest Version
Priyank Dubey: Allow me one minute
Priyank Dubey: Oh Yes I am sorry it is only for specific Phones support Raw format
yeung y: It's work on iOS and android
Priyank Dubey: I am sorry but can you elaborate what you mean by unlimited dng Export?yeung y: Because I can only export 15 dngs file to jpg every time
Priyank Dubey: What if you try to select more, Are you getting any error?
yeung y: Got the message from the app
Priyank Dubey: What message?
yeung y: I need to run the app now, may be disconnect our conversation yeung y: How can we keep chating ?
Priyank Dubey: You can send the screenshot here
Priyank Dubey: contact us back and refer to case # 0220217102
yeung y: Your file was successfully uploaded: image.png.
yeung y: Cannot click over 15 files
yeung y: It happened any convert not even dng file
Priyank Dubey: There are no such Issue that has been reported
Priyank Dubey: You may try to create another collection and then check
yeung y: Pls wait
Priyank Dubey: ok
yeung y: Pls wait 1-2mins
Priyank Dubey: ok
yeung y: What do you mean another collection?
Priyank Dubey: Allow me some time
Priyank Dubey: okay, I have just checked on my end, You can only export 15 images at a time yeung y: Ohhhhhh
Priyank Dubey: There is no way to increase that Limit
yeung y: Even I join the Adobe plan ?
Priyank Dubey: Yes
yeung y: Both happen android and iPhone ?
Priyank Dubey: Yes
yeung y: It's bad news for some user like me when use iPad Pro to run Lightroom mobile app , when we edit all the raw photo . It's only export 15 images at one time .
yeung y: I like to use iOS system to run your app more than Mac or Windows because of the weight and very convenience
Priyank Dubey: You can sync as many images as you want and Use Lightroom Desktop to Export as many pictures
Priyank Dubey: but Lightroom Mobile is a very light version with only minimum functions
yeung y: I understand your point
yeung y: This is not a big problem for every users yeung y: As I told you I like using iPad to edit the photo when I travel or on the train
yeung y: Hope you discuss your engineer team to get a better performance on next version , nice to talk to you Mr. Bubey
Priyank Dubey: You can also post your suggestions on feedback.photoshop.com
yeung y: Just refer the case #0220217102 to the website?
Priyank Dubey: No
Priyank Dubey: You need to type in your actual problem
Priyank Dubey: case # are for Support only
yeung y: Ok , thank you for your sharing , bye
Priyank Dubey: Bye Bye!
info: Your chat transcript will be sent to [removed] at the end of your chat.

81 replies

Participating Frequently
April 11, 2018
I know I risk turning this into a technical discussion rather than focused on personas and user intent, but since this looks like an engineering-driven decision based on Victoria’s original post, I’ll add an additonal remark to Antoine’s excellent list of workarounds.

From my measurements it seems like the biggest bottleneck with exporting is image processing and encoding, not “saving” as in saving to disk. I’ve been an iOS engineer since the dawn of the AppStore and iOS makes no restrictions nowadays to how many files can be saved or shared at the same time, since this is an iOS controlled task. It does, however, limit background processing time.

How about doing this image processing on the Adobe’s servers instead of the device (and therefore completely avoid this “background processing” issue)? Adobe already has all the raw files, and already does a lot of processing to generate smart previews, already makes media resources available through creative cloud in other apps etc. From my perspective as a software engineer it seems technically possible to process and encode “full previews”, which sync to the app, and can export without iOS limitations.

Now, please take all of this with a grain of salt, no amount of engineering knowledge can mitigate the fact that I have no idea how things are architected internally at Adobe, so everything I’m saying can be plain nonsense. However, since we’re talking to engineers here, I thought I’d share my thoughs.
Antoine HLMN
Known Participant
April 11, 2018
OK, iOS limits the background tasks, but other iOS apps allows to handle big files without any issue. Here are some workarounds:

1) Just notify the user -> keep the app open and it might take a while...
1bis) I don't know if technically possible, but do it in the background and allow to use LR in the meantime.
2) Allow multitasking with another app! We could keeping LR as the smallest window, giving plenty of usable real estate for another app.
3) Ok, let's assume the processing stops. Big deal? resume it when we open LR again ? Maybe with a popup "Reume / Cancel"?

I don't really get the attitude saying: "It's the way iOS wokrs, this is the best for you". And on the other side, LR allows editing keywords but they are not synced, without ANY warning, here.
Participating Frequently
April 11, 2018
Yes, I open them all individual images in Luma Fusion.

EDIT: I’ll add that for my individual use case having Lr create a movie out of the selected images would be just as good.
Inspiring
April 11, 2018
Thanks for the feedback, Victor. Question for you: once you process your timelapse images, what do you use to create your final product? Are you importing those images into another app on your mobile device?
Participating Frequently
April 11, 2018
Another approach could be to make the app’s UI responsive so that it can be used side by side with other apps on the iPad with iOS 11. Currently we can still multitask, but the Lr UI stays fixed in size.
Participating Frequently
April 11, 2018
I can also share my use case if helpful: timelapses. I shoot individual frames that I’d like to edit in Lr. See one of my above comments for more details.

I’ll also repeat that I’m perfectly happy with keeping Lr mobile in the foreground. Many apps have batch export or background processing that takes time and they send a push notification asking to bring the app into the foreground every once in a while, which is also acceptable to me.

Other use cases and opinions might be different, of course.
Inspiring
April 11, 2018
Because this is a mobile app, not a desktop app. The vast majority of people don't want to lock their device into a single task--we're all used to using computers that can do multiple things at the same time.

If you really want to help, could you answer my questions above?
TMM101
Known Participant
April 11, 2018
I still don’t understand why the amount of time Lightroom can spend in the background matters. Just give us a warning when exporting more than 15 images that they may not all export if we open another app and give us the option to have Lightroom force the screen to stay on for the duration of the export.
Inspiring
April 11, 2018
Hey Scott, just to be clear, our intentions are *only* to provide the best software to help photographers accomplish their goals.

The reality is that there's plenty of reasons why we created the (admittedly) arbitrary limit of 15 files at a time. Could we have made it 16? Sure. 17? Sure...and where does it end? iOS does not allow background processing for anything but very limited purposes (think maps and music). Anything other than that only can be used up to 15 minutes, provided that another process doesn't require the memory (and processing a raw file takes a lot of memory, so it's highly likely that you won't get the entire 15 mins). At that point, no app may open up a processing thread without the user explicitly opening the app (for battery and privacy / security purposes).

The real question is, why are you exporting multiple images out of the app? Help us understand your workflow (everyone) so that we can improve the app. 

What'd be really helpful is to understand:

1. Why are you looking to export a large number of images? Are you sending to a client, are you looking to back them up, etc.
2. What format do you need those images to be in?
3. What is missing for your workflow (though the answer may be covered above) with the ability to create an online shared album from which people can download full resolution images with all edits applied?

The more info we have, the better.
Participant
April 11, 2018
Thanks Victoria. Sorry... I’m without my Mac and find reading these posts a bit cumbersome on my iPhone’s small screen. I see that they responded. Also see that many other users expectations weren’t met. If technical limitation, then the lesson learned is that Adobe should have made this more clear upfront; not buried in a help room discussion. Takes too much time and effort. For something so critical and fundamental as Export Workflow, one would expect Adobe to make clear upfront that LM is severely restricted. Switching mindsets... if they’d told us going in that LM is great for quick ingest while on the road, great at culling and useful for small batch sharing and edits, but for the time being batch export and file storage migration need to be handled on the desktop, then I think most people here would be happy, rather than upset. For me, this is a problem of failed expectations and (considerable) time wasted trying to do what any reasonable user would expect to be able to do. Hopefully Adobe takes this message to heart.