Current Version/Release Notes for Luminar 2018 1.3.0 (Mac)
Latest Version: Luminar 1.3.0 (5235)
Download link: https://luminar2018.s3-accelerate.amazonaws.com/Luminar_2018.dmg
What’s new in Luminar 2018 for MacOS?
- IMPROVED Raw Develop. The Raw Develop filter has improved handling of the Lens and Transform effects. Effects are not shown on the left side (Before) when using the Compare option. The effects are also not blended with original when using the Filters Amount slider.
- IMPROVED Sharpening. The Sharpening filter is more responsive and accurate. As you adjust the controls all changes are visible in high resolution with real-time feedback.
- IMPROVED Batch Processing. You can now export to several file formats including new options for PDF and JPEG-2000.
- IMPROVED LUT Mapping. You can now easily scroll through your LUTs in the LUT Mapping filter. Just hover your mouse over a LUT and it updates in real-time.
- IMPROVED Language Support. Luminar offers eight Improved localizations: Chinese, Chinese Simplified, French, German, Japanese, Portuguese, Portuguese (Brazil), and Spanish.
- IMPROVED Image History. It is now possible to use the “Save History” option when saving a file with the “Windows Compatible” option. Additionally, White Balance presets are now displayed in an image’s history with the preset name when using the RAW Develop and Develop filters.
- NEW Plugin Support. The following third-party plugins can now be used via the Plugins menu: Imagenomic Noiseware 5, Imagenomic Portraiture 3, Imagenomic Realgrain 2, and DxO FilmPack 5.
- IMPROVED Filter Controls. To save you time, all filter checkboxes can be enabled or disabled by clicking on the control name or the checkbox. Additionally, be sure to try scrubbable number sliders. Just mouse over the value for a filter and then click and drag left or right to move the slider.
- IMPROVED JPEG Controls. Take precise control over JPEG and JPEG-2000 compression. You can see a numeric value for the Quality slider. You can also click on the number and enter a precise value.
New Camera Support
This recent update supports the following new cameras:
- Canon EOS 3000D / Rebel T100 / 4000D
- FujiFilm X-H1
- FujiFilm X-A20
- FujiFilm X-A5
- FujiFilm X-E3
- Olympus E-PL9
- Pentax K-1 II
- Panasonic DC-GF10 / Panasonic DC-GF90
- Panasonic DC-GX9 / DC-GX7MK3
- Panasonic DC-TZ200 / DC-ZS200 / DC-TZ202 / DC-TZ220 / DC-ZS220 / DC-TX2
- Sony A7 III
-
@Denis - only with favourites, it takes a while to load the previews, then eventually it will freeze when selecting between some of the presets. If I force quit and go back to the individual preset groups its fine.
screenshot : http://esportsranks.com/wp-content/uploads/2018/07/luminar-ss.png
-
Could you please send us your Mac's hardware configuration, and the screen recording of the issue?
Click on Apple logo in the top left corner of your screen, click About This Mac, and make a screenshot of the window that opens.
Here's how to record your screen on Mac:
https://support.apple.com/guide/quicktime-player/record-your-screen-qtp97b08e666/mac
Here's how you can send us the recording:
- Visit https://wetransfer.com/
- If it's your first time visiting this website, it might ask you to purchase a subscription. Simply select to proceed with the free version.
- Click Add your files.
- Select the file(s) on your computer.
- After you see all the files you need to send appear in the list, click the icon to the left of the Transfer button (the icon looks like a circle with three dots in it).
- In Send As select Link.
- Click Transfer.
- After the files have finished uploading, click Copy Link and paste it into your reply.
-
@denis screenshot here:
How to reproduce:
Open an image and edit.
Save at least 15 presets as favourite, and open favourites on the bottom menu.
Save/close window.
Open new file.
Presets loading takes long/freezes. Repeat editing/opening window until eventual total freeze which needs a force quit of the progam.
-
Hi Govind,
Your computer specs might be an issue - but if possible, can we get some additional information from you? You can send the info requested below to support@skylum.com
First - Please send us a screenshot of your Mac info. Click on Apple Logo in the top left corner of your screen, select About This Mac > make a screenshot (Command+Shift+3) and send it to us.
Second - Can you provide us with a detailed description of the process that leads to the crash? A numbered list of steps would be the most convenient. For example:
1. Launch Luminar.
2. Load the file named X with an extension Y.
3. Apply Z filter.
4. Set S slider to U value.
5. etc. etc.
Finally - please provide us with a crash report:
1. Open the Finder
2. Go to the Menu Bar and open the "Go" menu.
3. Select the entry: "Go to Folder..."
4. Enter the following path: ~/Library/Logs/DiagnosticReports
5. Find the most recent files whose names start with "Luminar" and drag them into an e-mail.
Thanks in advance!
-
Hi,
the current version 1.3.0 is completely unusable in MacOS High Sierra for the Luminar's bugs, I cannot do really anything with it because of the quickly developing freezing issues, and it's freezing the whole computer. I learned from your input that you know the defect and it's been fixed already, but there's still no update available. What are your intentions on this?
- Tero
-
Hi Tero,
I'm sorry you've had these issues with Luminar. For now, as a workaround, please install the previous version:
Luminar 2018 1.2.0 (4245) MAC
https://www.dropbox.com/s/s1yejnmxt6f3wcq/Luminar2018_Distribution_v1_2_0_4245.zip?dl=0In the meantime, have you already created a support ticket by contacting support@skylum.com? If not, please send us an email with the following information:
First - Please send us a screenshot of your Mac info. Click on Apple Logo in the top left corner of your screen, select About This Mac > make a screenshot (Command+Shift+3) and send it to us.
Second - Can you provide us with a detailed description of the process that leads to the crash? A numbered list of steps would be the most convenient. For example:
1. Launch Luminar.
2. Load the file named X with an extension Y.
3. Apply Z filter.
4. Set S slider to U value.
5. etc. etc.
Finally - please provide us with a crash report:
1. Open the Finder
2. Go to the Menu Bar and open the "Go" menu.
3. Select the entry: "Go to Folder..."
4. Enter the following path: ~/Library/Logs/DiagnosticReports
5. Find the most recent files whose names start with "Luminar" and drag them into an e-mail.
Thanks in advance!
-
As a suggestion, this kind of bug fixes should be sorted out more often. It looks like you've been selling a badly defected product for a half an year or so now, and still with no update to fix the obvious issue that makes the product unusable. This looks more like a issue in Skylum's software development practices, individual defects in software are not such an issue if the development team can push out a new release often. The information I've received from you is that the issue in code has been fixed, but there's still no patch available. I don't get this.
-
Another 2 months go by without any update. I’m a new user and it crashed for me 8 times in my first day using it, on a brand new MacBook Pro with 32GB RAM. Skylum, why are you languishing? Your apathy almost gives the impression that you’re about to go out of business altogether. ????
-
Hi Dan,
We have an update coming out on November 1.
As for your issues with the software crashing - do you already have an open support ticket? If not, please send the following to support@skylum.com and we'll be happy to look into the problem.
First - please send us some information about your Mac: click on Apple Logo in the top-left corner of your screen, select About This Mac > make a screenshot (Command+Shift+3) and send it to us.
Second - please send us the original sample file(s) so that we can test it on our side. If the files are too large to email you can upload the file(s) to www.WeTransfer.com & send us shared for everyone link.
Please specify which adjustments exactly have you applied.
Third - please provide us with a crash report and specify which steps preceded the crash so that we can reproduce this issue on our side:
1. Open the Finder
2. Go to the Menu Bar and open the "Go" menu.
3. Select the entry: "Go to Folder..."
4. Enter the following path: ~/Library/Logs/DiagnosticReports
5. Find the most recent files whose names start with "!!!NAMEOFTHEAPP" and drag them into an e-mail.
Thanks in advance!
-
What you are asking me to do will take a non-zero amount of time on my part to complete. It's stuff I shouldn't have to do. Still, I would do it anyway if I had hope that it would lead to the work-destroying crash bugs being fixed. However, given that people have been complaining about crashes for months - in this very thread - without Skylum even saying "We are tracking this particular bug, the fix will be in the next release" - leads me to believe that I would be doing this work of gathering data for you for no benefit. The fact that Skylum continues to ship v1.3.0 with months of confirmed work-destroying crash bugs is further confirmation.
Angela, I realize you're just doing your job - and I highly appreciate you dealing with an angry customer like myself. But with no direct bug acknowledgement or published fix, with Skylum continuing to ship this v1.3.0 work destroying build of Luminar 2018, it really just looks like Skylum is ignoring both you AND the customers complaining of crashes.
-
Hi Dan,
I understand your frustration, and that our request takes your valuable time, but if you do decide to send the requested info, we'd greatly appreciate it.
I'll also check with our support team and see if there is a specific issue causing the crashes listed above, and if it will be rectified in the upcoming update.
-
I found yet another bug... Luminar is reloading the source image for a project, despite having an original copy inside the .lmnr file.
Steps to reproduce:
(1) In Capture One, select a variant and click "Edit With". This will create (to your specs) an image file like a PSD, then automatically open it in Luminar. (I don't think you need Capture One to reproduce this, I'm just telling you how I did it.)
(2) Make some changes in Luminar. Save your .lmnr file. Export the image back to PSD again, saving it to the same path that Capture One handed to Luminar for the source image.
So far so good.
(3) In Luminar, close the lmnr file and re-open it. Click on the base layer image. Note that it is showing the version you just exported! NOT your original base image, which is contained inside the .lmnr file! This leads to all of your filters effectively being applied twice, if you were to export at this point!
(4) For further proof, close Luminar, move your original source file elsewhere, then re-open the .lmnr file. Click on the base layer. Note that it is now showing your original source image. So simply changing the name/location of the original source file stops this "bug", but it shouldn't be re-loading the source file when it already has a copy inside the .lmnr file.
Is this a bug? Is it a known bug? Or is it expected that Luminar will ignore the base image inside the .lmnr file if the original input file still exists in its original path?
-
@Angela - Did you see my post from 6 days ago that starts with "I found yet another bug..."? I just tested on Luminar 2018 v1.3.2 and the bug still exists. Is this a known issue or something we can expect to be fixed soon? If you need more details about this issue I am happy to provide.
-
Hi Dan,
I did not see your post from 6 days ago - sorry about that! It may have been approved by another admin.
We will definitely need some additional information from you. Please send your PSD (as exported from Capture One) along with your .lmnr file to support@skylum.com and reference this thread.
If the files are too large to download you can use WeTransfer.com and then send us the shared download link.
We'll look into it and see what is happening. Thanks for pinging me and bringing this to our attention!
Please sign in to leave a comment.
Comments
31 comments