Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Waldbaer

Members
  • Posts

    26
  • Joined

  • Last visited

  1. Trying out would work nicely as a work flow if the batch dialogue's settings were saved, so you'd only have to set the new input files to finally run the batch. As this is not the case, you have to repeat all settings which not only takes time but also provokes errors. So yes, different destination is always to be recommended, but the workflow gets not really better including testing of each batch operation, I think.
  2. Just to let you know: This seems to be fixed in the latest beta. I just ran some batches in Affinity Photo 1.7.0.135 and it runs perfectly (it did fail before the update download was completed), also with my macros imported from Affinity 1.6.7 and parallel processing enabled (and of course the new width/height expressions ).
  3. This is still really weird... should not be so complicated to add some Play/Pause/Stop buttons to the panel, is it? It's still not that unusual that I find that the output of a batch is not exactly what I wanted it to be and besides having to setup everything again just to tweak one setting, I at first have to force quit Affinity Photo to stop the current batch. Useable, but neither intuitive nor user-friendly...
  4. Same problem on my iMac 2017 since I upgraded to Mojave last week. On High Sierra, everything went fine, so I suspect that the upgrade broke something. Unchecking Parallel Processing fixes the Problem, the Βeta does not. The Βeta worked fine though as long as I did not run my imported macro on the files (but actually just converted them). I'm looking forward to any updates; if you change something in the Βeta that might help here, please let us know in this thread! BTW: Why is still the only possibility to stop a batch to force quit the app? Please consider adding a stop/abort button to the batch pane. Or did I miss something?
  5. I did not set any application folders manually. I think it takes some automatically, though. I found two checkbox options maybe connected to this: "Select most recently used file in open dialogues" (checked) and "use current folder of the file in save dialogues" (unchecked)... I still do not understand why it seems to return the save path correctly but then it is not used. I thought DFX only is active with the standard macOS file dialogues and does nothing else, but maybe I'm wrong...
  6. Hi R C-R, thanks for jumping in! I'm using the most recent version (currently 5.2.5). Thanks for the heads-up concerning the app exclusions! I really appreciate DFX's services at other parts of Affinity though, e.g. it intelligently recalls my recent folders or even files for open/save/export and facilitates access on different places using Finder windows or shortcuts (e.g. if I work with different applications on the same project and folders). Probably I'll just leave everything as it is for the moment and just doublecheck if the batches really do what they should and deactivate it as soon as I notice there is a problem...
  7. Thank you again for checking this out! The interesting thing for me is still that it works sometimes and sometimes not and the path is always entered into the dialogue. I'll send this thread to stclairsoft, too; as far as I experienced, they have a really nice and responsive customer support, too, and this is really the first time I have an issue with it although I'm using its enhanced dialogues nearly all the time and everywhere.
  8. Hm, I have another idea where the problem might be: I use the third-party app Default Folder X to help my file managing tasks. I swear I have deactivated it once before and the batch did not work anyways, but now I've quit it for the video and everything works fine. As soon as I launch and use it, the batch goes to nowhere as described in this whole thread. The Batch dialogue does show all files and also the output path the same way with and without DFX, though, so I still wonder why this might be a problem. Maybe you know how you handle the path data during the process and could contact StClairSoft about their handling so you might find the problem? I'm sorry that this is so complicated, but I'd really appreciate using both apps simultaneoulsly (works great most of the time already, just the described "sometimes" not). I'll send you the videos in a minute, I'm just compressing them right now.
  9. OK, I'll take a screenrecording showing the process. I don't like to post it to the public though, so I'll send you a download link as private message, same with my macros. Default macro does not work, too; even no macro at all (just conversion) does not work (as described above). Thanks for you support, I know that these questions are not to bother me but to find the problem. I really appreciate that you take so much time for my problem and hope that we might tackle it soon!
  10. I'm running Affinity Photo 1.6.7 on macOS 10.13.6. Thanks for your efforts!
  11. Thanks for your continued support! I tried your reset and was quite shocked when I realized that it deleted all my macros. Well, I should have read what was selected and resetted, but I was lucky having a time machine backup and figured out which file to replace to get my macros back (~/Library/Containers/com.serflabs.affinityphoto/Data/Library/Application Support/user/macros.propcol). After that, I started again with a completely reset app, rebuilt my macro (simply turn 180°, so two times 90 and that's it) and retried the batch with the same files and folders that did not work before. Things I noticed while doing that: saving the macro only worked in a new, but not in the "Default" category. If I try to save in the default, after clicking "save" it shows me the category, but without my macro being added and without further notice. Is that the way it should be? still no saving of target files without further notice I tried the same batch but without any macros at all but it still won't save the files Since the problem seems to be not connected to the macros, I tried some other things: I took the other files (no corresponding names, so no overwrites anyway!) out of the target folder and started the same batch as before - hooray! - it worked. I repeated the batch with other files from the same source and target folders (did not work before, too) - no problem, too. I deleted the files resulting from 1 and 2, put the previous files back into the target folder, tried again and it did not work again. What is going on here, is there maybe some kind of security mechanism that the batch does not write to folders containing more than x files?
  12. That's what I already tried and referred to as "multicore-processing" in the first post... sorry, did not help in this case, too. Hm, interesting that it seems that I'm the only one encountering the problem. So there is no kind of log or something like that to get more information from the app itself, is it? I'll continue observing this issue and if I get new information I'll report them here.
  13. Hi Dan, thanks for your support! All folders in my user's documents (sub/sub/sub... but the same folders sometimes work and sometimes not; path length alone does not seem to be the problem) and the "other folder" was just a folder directly beside the lowest or the parent folder. No protection, not case-sensitive, just a MacOSExtended (Journaled) volume (a fusion drive now, but the problem also occured sometimes on my old system with just a simple HD as far as I can remember). Sometimes even the "original folder" option does not work, it does not even overwrite the source files. The process might run slightly faster than with saving, but it just goes through the list and even says "saving [file format]". It seems to edit the files but the result is to be found nowhere. ...and the next time it works as it should, only change is a (slightly) other target folder (exactly same settings don't work repeatedly, they always result in the same kind of fail). I just have no idea where a systematic problem could be other than that affinity sometimes might not get the target folder from the dialogue (no idea why this should be the case). Is there any kind of log I could activate/have a look into? Is there even any possibility to stop the batch process other than (force) quitting the application?
  14. Hi serif, I use the batch processing quite often and today I have again the big problem that Affinity Photo just does not save the processed files on my mac (10.12). In a project's folder, I use to have different subfolders for the different saving formats, such as "srcTIF", "processAFPHOTO", "exportJPG". So quite often I use the "save in" option. Sometimes it works as expected. Sometimes not. In the last case I tried to restart the application and even the computer, tried it without multicore-processing - No change: As long as I fire the same batch on the same files, it seems to work, but there is no output, just no files appearing in the target folder. The only way out, that I know until now, is saving the files to another folder and then collect them and move them manually to the correct folder. Do you know this problem? I encounter it quite often, but still don't understand the problem, since sometimes it just works as expected... might I be doing something wrong? Is there any place where AffinityPhoto might report problems to (I don't find anything related in the console). Thanks for your help! Waldbaer
  15. You're right, in most cases I don't even notice the difference. Biggest problem: The Windows 10 printer driver does not support zoom/scaling but reads the dpi, so it's difficult to extract and/or print specific pages from the pdfs.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.