Jump to content

MarvinR

Members
  • Content Count

    62
  • Joined

  • Last visited

About MarvinR

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Ormond Beach, Florida

Recent Profile Visitors

807 profile views
  1. Thank you. May peace and wellness be with you. These are indeed difficult times and the goodness of acts like yours is a welcome and encouraging presence. Peace.
  2. Thank you. Good to know the file size issue is being looked at. Your team is always on top of it. Appreciate it. Marvin "Butch" Reinhart
  3. The problem with the batch process crashing looks to be fixed in Beta 1.7.2.445 I just tested this morning against a batch of 8 .tif files using the same two macros used for earlier testing to find the crash and everything went Great. However, the problem in the file sizes still exists. Using the current release (1.7.1.404) the test file I ran through the batch process created a ,afphoto file with a size of 310MB and the same file when manually loaded and the same test macros run as were run in the batch creates a file of 117MB in size. That is a good bit of difference and would discourage someone from using the batch process to create a large number of .afphoto files. Thanks Marvin "Butch" Reinhart
  4. @GabrielM no problem with the delay. I realize you are all very busy. Here are the two macros that I tried to run in a batch process that I mentioned in my "Batch Process Fails with version 1.7.0.367" submitted on 7 June. For the problem stated in my "Batch Process Creates Very Large Files Ver 1.7.1.404" the macro I was running was just the macro "Create Layer for Color Efex Pro 4". Also, inclosed are rebuilds of the two 16-bit .tif files that I referred to in the report. The file ending in "2705_DxO.tif" is the file that when it was run in the batch process using both macros had a file size of 450mb and when I opened just the .tif file in Affinity Photo and ran the two macros only the size was 173mb. I have both of those resulting files but to try to upload them here won't work. I hope this information and the uploads are of help in the troubleshooting. Thank you very much. Peace Marvin "Butch" Reinhart Create Cleanup Layer.afmacro Create Layer for Color Efex Pro 4 -.afmacro D7100_Killdeer_06-06-2019_726_2705_DxO_.tif D7100_Killdeer_06-06-2019_726_2712_DxO_.tif
  5. Thank you very much. Also, yesterday I posted an update to this situation with the title "Batch Process Creates Very Large Files Ver 1.7.1.404". When I ran a test using a single macro in the batch process, it failed after creating two files. So, I simply restarted Affinity Photo and ran the macro manually. I saw that the .afphoto file created by the batch process was 359mb while the .afphoto file created by manually running the macro and saving as an .afphoto file was only 159mb. Thanks Marvin "Butch" Reinhart
  6. This is a follow-up to the previous bug report (with attachments) titled "Batch Process Fails with version 1.7.0.367" submitted on 7 June and updated that the same problem occurs under version 1.7.1.404. Today, I tried to run a batch process against 21 files that ran one macro which simply created a copy of the background layer and then renamed the new layer. Again, as with the two macro problem, it processed two files and then quit without an error. It was at that time that I discovered another error in that the .afphoto file created by the batch process is more than twice as large as the file that I created by dragging the same .tiff file processed by the batch process into Affinity Photo, running the macro to create a new layer and rename it, and then manually saved the file. The file size of the .afphoto file created by the batch process was 359mb the size of the afphoto file created by manually taking these steps was 159mb. There is something wrong in the batch process. If you need a copy of the macro I use or the files that were created I can upload them. Further, I would say that I have been running these macros for a long time under previous versions without any problem. Thank you.
  7. The problem with Affinity Photo quitting a batch process without an error still exists. The first macro makes a copy of the background layer and names it to "Color Efex Pro 4 - ". The second macro simply creates a new pixel layer and names it "Cleanup Layer". Both macros only have two steps. I attached copies of these macros to the original report above. I have run these macros successfully for many months. There was something changed in 1.7.0.367 that caused this situation to start occurring. The test that I just ran was to try running those macros in a batch process on 5 files. After the first two photos AP quit without giving an error message. As stated before the process will stop after 2 or 3 files are processed. I have tested this with and without parallel processing checked and get the same results. Please, before anyone tells me to combine the two macros, understand that I have a series of individual macros from which I will pick two or three to combine depending on what I am going to be doing with a particular photo. Thanks,
  8. Thanks for testing Carl. Hope you and your dog had a pleasant morning. Marvin "Butch" Reinhart
  9. I have done it with and without Parallel Processing on. Additionally, after I posted my initial problem I went back and looked at the size of the files created by the batch process. The size of the file created when the macros were run as a part of the batch process the size of the AP file created was 450MB. When I opened the same .tiff file and ran the two macros manually the size of the AP file created was 173MB. So, there is definitely something taking place in the batch process of running these two macros that is in error. Appreciate your info on the reason the Edit was greyed out. Should have realized that. Thanks Marvin "Butch" Reinhart
  10. I have two macros that I will run in a batch process against .tiff files to get ready for processing in Affinity Photo. The first macro makes a copy of the background layer and names it to "Color Efex Pro 4 - ". The second macro simply creates a new pixel layer and names it "Cleanup Layer". Both macros only have two steps. In AP 1.7.0.367 when I select say 12 files to run in the batch process and execute these two macros only 2 or 3 (it is not consistent in the number if will process) then the batch process will end without error and AP will shutdown. On restarting AP there is no indication that any sort of error has taken place. That is the mail problem. The second problem is that in the Library panel the option to Edit a macro is greyed out. I found this when I was going to open the macro to look at the code. The options to Delete Macro or Rename Macro are active but the Edit Macro is greyed out. I have attached an export of Editing Macros - Marvin.afmacros for your use in testing. In this library category the two files I am call in the batch process are "Create Layer for Color Efex Pro 4" and "Create Cleanup Layer". I call them in that order. These macros have been running for about a year without any difficulty in Batch processing batches containing as many as 40 .tiff files. The error I have described above is happening when I try a batch of only 12 files. Running Windows 10 with latest updates. Thank you Marvin "Butch" Reinhart Editing Macros - Marvin.afmacros
  11. Thanks for the update @dominik . I am still waiting to hear from DxO support. I imagine they are pretty busy. Butch
  12. @dominik yes the plugins look ok on my 1920x1080 screen running in demo mode both as a plugin and when I ran HDR Efx Pro,.
  13. Waiting to hear from DxO support on this issue dominik and will be sure to post when i get an answer. DxO support has been very good in the past about resolving issues. Everything except Veviza 2 works ok in the demo mode. So, I really think the activation situation can be addressed by them. Butch
  14. Downloaded the trial version and with the exception of Viveza 2 everything worked acceptably that I could see. Viveza 2 showed a heavy pink color cast and there were no changes I could make to the document color format that would correct the situation. However, since I was more interested in the other parts of the Nik Collection I went ahead and bought it. But, when I tried to activate any of the Nik products it failed with the message that I was not connected to the internet. I then tried to run one of the products standalone which worked just fine but again it failed when I tried to activate. Last night I submitted a trouble report with DxO and when they respond I'll post here how it worked out. Running Windows 10 latest updates. Butch Situation Resolved with not being able to activate DxO Nik Collection running on Windows 10. @dominik Got the response from DxO Monday, June 11, 2018 I heard from DxO Support a shot time ago. They resolved my problem of not being able to activate my copy of DxO Nik Collection running on Windows 10 with latest updates. These are the steps they had me follow: 1. Uninstall DxO Nik Collection 2. Go to the folder C:\ProgramData\DxO Labs\Licenses 3. Delete the two files nik2018demo.lic and nik2018.lic (you may only find one) In my case the file that was there was nik2018demo.lic 4. Reinstall DxO Nik Collection Following those steps I was able to activate my paid copy of DxO Nik Collection and run plugins in Affinity Photo. I hope this may be of help to others. Dxo Support was very prompt in working with this. I submitted my support ticket on Thursday. I started a dialog on Saturday and the situation was resolved on Monday. Given the support folks were responding to a new release I was very pleased with their support. Butch
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.