Jump to content

MarvinR

Members
  • Content count

    61
  • Joined

  • Last visited

About MarvinR

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Ormond Beach, Florida

Recent Profile Visitors

612 profile views
  1. 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
  2. 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
  3. MarvinR

    Script Error in Help on 1.7.2.434 Beta

    Same error for me when entering help. If I select Yes to Continue Running Scripts then I can click on any of the major menu headings such as "Introduction", "Get started", "Layers" and so on, then the submenus are displayed without error. However, clicking on any of the submenus the error is reported as "Line: 232" and "Char: 3" with all other error information the same as the initial error. Windows 10 Home with latest updates
  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. Yes, I appreciate that information. But, I am only using the beta for testing and am doing real work using the released version which doesn't have that problem so I wasn't looking for a work around, rather I was making a report on the beta so that the released version would not have this problem. I just did test the work around as you mentioned AlainP just to see the results and the same error I initially reported occured. I am confident the developers will have a fix in place when making the next clean release. Peace
  6. It was not listed as being an item fixed in beta .424. However, I retested anyway and found that the situation remains as I originally reported on Windows 10. If you use the Clone Brush set to operate on the Current Level there is no error. But, when you use the Clone Brush on a blank pixel layer above the background layer with it set to operate on Current Layer and Below or Layers Beneath AP will shutdown 100% of the time without giving an error on shutdown or restart. In my testing on Windows 10 with latest updates, I find the situation with beta .424 unchanged from my original report. Since, there was nothing in the change list indicating work being done directly on the Clone Brush in beta .414 I would assume what has given birth to error that causes the crash is the side effect resulting from another fix and may be hard to track down because of that and because it appears to slip through error checking. The developers will track it down. As an end-user my job is to be patient.
  7. In Beta 1.7.2.414, using the Clone Brush will cause AP to shutdown without giving an error. This happens after you select the source area and just as you begin to paint the area to be cloned when you are using a Pixel layer and have Source set to current layer and below. If you use the Clone Brush directly on the image your bring in to AP with the source set to current layer this error will not occur. However, if you create a blank pixel layer above the original image and the source is set to "current layer and below" or "layers beneath" AP will shutdown 100% of the time without giving an error on shutdown or restart. I think this is a serious error because a lot of people use the blank pixel layer above original image method to have a non-destructive workflow. I am using Windows 10 with latest updates.
  8. 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
  9. 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.
  10. 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,
  11. Thanks for testing Carl. Hope you and your dog had a pleasant morning. Marvin "Butch" Reinhart
  12. 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
  13. 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
  14. MarvinR

    Meta Data Missing Beta 1.7.0.284

    Ran into a problem testing on the Mac laptop. I downloaded and installed the Mac beta. However, every time I opened the .tif file in Affinity Photo Beta the application would simply shutdown without a message. So, what I ran the test using the latest released version of Affinity Photo for the Mac and got the same results as I got yesterday with the Windows beta version. I have uploaded the files from the Mac test. I used the same raw file used in the Windows test but just changed the name of the file to start with the word Mac and followed the same steps I followed under Windows. I have removed the beta copy of Affinity Photo from my Mac laptop. Hope this help. Peace Marvin
  15. MarvinR

    Meta Data Missing Beta 1.7.0.284

    I just uploaded the files from Windows 10. I am setting up my Mac laptop and will make sure I use the same versions of the PhotoLab 2 and Affinity Photo to run the same test on the same Nikon .NEF file. The only change I'll make is to change the name of the files to include the word "Mac" in the file name. Thanks Peace Marvin
×