charlyw wrote:
Could it be that you are still stuck in the way Aperture (you are more heavily invested in than anyone else here) does some things and thus never adapted to the new software properly.
That very well may be, especially given that I have at least heavily influenced the way the workflow was designed in Aperture and made it fit my needs Still I find it a natural behavior that every person is looking for a tool that suits their needs the most, and only if no such tool exists do people change their habits. For me, having to import all photos of a folder into C1 and not just a subset is a no-no, so that app is out, for instance. I fully understand that I may be the only person out there who work that way; LR allows me to work that way, which is good, and I put up with many of its shortcomings in return.
As for the performance issues that LR previously had, they were mainly located in the import/culling workflow and the library/develop transistion - both things you will hardly have any experience in and thus are ill qualified to comment on because you don’t really use the corresponding parts.
I don't believe you read my comment correctly. Every weekend I import 1500 photos from a basketball game, for instance. The speed of LR6 certainly bothered (bothers) me, but I can do that import over lunch, dinner, or overnight. I still bitch about it but at least I'm not staring at the screen. The atrocities in the Develop module that LR7 introduced however I have to look at, every time I move a slider. That's the reason I'm still with LR6 and not LR7, because I want to minimize the time I'm in front of the computer.
I am wondering what you throw at LR to make it hang, not even several panorama calculations while contuing to cull and import do slow it down much on the GUI...
Read this thread. It has a raw file attached to it with XMP that illustrates this problem (today's update didn't fix it).
charlyw wrote:
Could it be that you are still stuck in the way Aperture (you are more heavily invested in than anyone else here) does some things and thus never adapted to the new software properly.
That very well may be, especially given that I have at least heavily influenced the way the workflow was designed in Aperture and made it fit my needs Still I find it a natural behavior that every person is looking for a tool that suits their needs the most, and only if no such tool exists do people change their habits. For me, having to import all photos of a folder into C1 and not just a subset is a no-no, so that app is out, for instance. I fully understand that I may be the only person out there who work that way; LR allows me to work that way, which is good, and I put up with many of its shortcomings in return.
As for the performance issues that LR previously had, they were mainly located in the import/culling workflow and the library/develop transistion - both things you will hardly have any experience in and thus are ill qualified to comment on because you don’t really use the corresponding parts.
I don't believe you read my comment correctly. Every weekend I import 1500 photos from a basketball game, for instance. The speed of LR6 certainly bothered (bothers) me, but I can do that import over lunch, dinner, or overnight. I still bitch about it but at least I'm not staring at the screen. The atrocities in the Develop module that LR7 introduced however I have to look at, every time I move a slider. That's the reason I'm still with LR6 and not LR7, because I want to minimize the time I'm in front of the computer.
I am wondering what you throw at LR to make it hang, not even several panorama calculations while contuing to cull and import do slow it down much on the GUI...
Read this thread. It has a raw file attached to it with XMP that illustrates this problem (today's update didn't fix it).
charlyw wrote:
Could it be that you are still stuck in the way Aperture (you are more heavily invested in than anyone else here) does some things and thus never adapted to the new software properly.
That very well may be, especially given that I have at least heavily influenced the way the workflow was designed in Aperture and made it fit my needs Still I find it a natural behavior that every person is looking for a tool that suits their needs the most, and only if no such tool exists do people change their habits. For me, having to import all photos of a folder into C1 and not just a subset is a no-no, so that app is out, for instance. I fully understand that I may be the only person out there who work that way; LR allows me to work that way, which is good, and I put up with many of its shortcomings in return.
As for the performance issues that LR previously had, they were mainly located in the import/culling workflow and the library/develop transistion - both things you will hardly have any experience in and thus are ill qualified to comment on because you don’t really use the corresponding parts.
I don't believe you read my comment correctly. Every weekend I import 1500 photos from a basketball game, for instance. The speed of LR6 certainly bothered (bothers) me, but I can do that import over lunch, dinner, or overnight. I still bitch about it but at least I'm not staring at the screen. The atrocities in the Develop module that LR7 introduced however I have to look at, every time I move a slider. That's the reason I'm still with LR6 and not LR7, because I want to minimize the time I'm in front of the computer.
I am wondering what you throw at LR to make it hang, not even several panorama calculations while contuing to cull and import do slow it down much on the GUI...
Read this thread. It has a raw file attached to it with XMP that illustrates this problem (today's update didn't fix it).
charlyw wrote:
Could it be that you are still stuck in the way Aperture (you are more heavily invested in than anyone else here) does some things and thus never adapted to the new software properly.
That very well may be, especially given that I have at least heavily influenced the way the workflow was designed in Aperture and made it fit my needs Still I find it a natural behavior that every person is looking for a tool that suits their needs the most, and only if no such tool exists do people change their habits. For me, having to import all photos of a folder into C1 and not just a subset is a no-no, so that app is out, for instance. I fully understand that I may be the only person out there who work that way; LR allows me to work that way, which is good, and I put up with many of its shortcomings in return.
As for the performance issues that LR previously had, they were mainly located in the import/culling workflow and the library/develop transistion - both things you will hardly have any experience in and thus are ill qualified to comment on because you don’t really use the corresponding parts.
I don't believe you read my comment correctly. Every weekend I import 1500 photos from a basketball game, for instance. The speed of LR6 certainly bothered (bothers) me, but I can do that import over lunch, dinner, or overnight. I still bitch about it but at least I'm not staring at the screen. The atrocities in the Develop module that LR7 introduced however I have to look at, every time I move a slider. That's the reason I'm still with LR6 and not LR7, because I want to minimize the time I'm in front of the computer.
I am wondering what you throw at LR to make it hang, not even several panorama calculations while contuing to cull and import do slow it down much on the GUI...
Read this thread. It has a raw file attached to it with XMP that illustrates this problem (today's update didn't fix it).
Still I find it a natural behavior that every person is looking for a tool that suits their needs the most, and only if no such tool exists do people change their habits. For me, having to import all photos of a folder into C1 and not just a subset is a no-no, so that app is out, for instance. I fully understand that I may be the only person out there who work that way; LR allows me to work that way, which is good, and I put up with many of its shortcomings in return.