Output to different folders in process recipes
Hey,
I've tried to find out if I can output to several different folders in process recipes but to no luck.
Example:
I have a process recipes for:
Instagram
Wallpaper
Phone
I want these process recipes to output to different folders, but when I change output folder on one of the recipes all of the recipes changes output folder.
Is this really not possibe?
I've tried to find out if I can output to several different folders in process recipes but to no luck.
Example:
I have a process recipes for:
Wallpaper
Phone
I want these process recipes to output to different folders, but when I change output folder on one of the recipes all of the recipes changes output folder.
Is this really not possibe?
0
-
It is possible. Let's say you want to put them in Output\Instagram, Output\Phone, etc. Set the Output folder to Output in each recipe, then in the subfolder space just below that click the ... to get the submenu. Choose the token Sub name and drag it to the Format field in the dialog box.
Then for your instagram recipe go the File tab in the process recipe tab and type Instagram in the sub name field. Do similarly for Phone, and Wallpaper. You should not be good to go.
Ian0 -
[quote="Ian3" wrote:
It is possible. Let's say you want to put them in Output\Instagram, Output\Phone, etc. Set the Output folder to Output in each recipe, then in the subfolder space just below that click the ... to get the submenu. Choose the token Sub name and drag it to the Format field in the dialog box.
Then for your instagram recipe go the File tab in the process recipe tab and type Instagram in the sub name field. Do similarly for Phone, and Wallpaper. You should not be good to go.
Ian
Thanks but this is bascially sub folders, isn't it? I want to output to different root folders.0 -
I suppose that you could set the Output location to whatever is the common root of the locations you want, assuming they are on the same drive at least. So that might be D:\Images or something. If you wanted to have the Instagram ones at D:\Images\Publicity\Instagram, could you type in \Publicity\ and then the Subname token. For Phone you might have D:\Images\Social\Phone and type in the bits of the path between the overall output folder and the Phone bit. I'm not sure - I haven't tried it, but you could experiment, or someone might come along here who can advise you better. But if you wanted them to be on different drives, I think you might be stuck.
Ian0 -
Assuming you are using a different recipe for each output - which you really need to in this case anyway I would imagine - then in the File tab of the recipe in the Root Folder field open up the options, scroll down the list and choose "Select Folder".
You can then browse to the folder you wish to use or create a new one.
Once created it should appear as a previously used folder in the list if you create a new recipe at some point and wish to use the same location. The subfolder, etc., options should now work with that as the new Root folder for that Recipe. The Recipe will ignore the "Output Location" "Destination" field since you have not selected "Output Location" as the Root folder for the Recipe.
If you have already tried that and it does not work I would suggest you double check the naming conventions and the actual locations they point to just in case you have duplication of folder names confusing things. If you find nothing wrong there then create a Support Case and work through what you are seeing with the C1 Support Team.
HTH.
Grant0 -
[quote="SFA" wrote:
Assuming you are using a different recipe for each output - which you really need to in this case anyway I would imagine - then in the File tab of the recipe in the Root Folder field open up the options, scroll down the list and choose "Select Folder".
You can then browse to the folder you wish to use or create a new one.
Once created it should appear as a previously used folder in the list if you create a new recipe at some point and wish to use the same location. The subfolder, etc., options should now work with that as the new Root folder for that Recipe. The Recipe will ignore the "Output Location" "Destination" field since you have not selected "Output Location" as the Root folder for the Recipe.
If you have already tried that and it does not work I would suggest you double check the naming conventions and the actual locations they point to just in case you have duplication of folder names confusing things. If you find nothing wrong there then create a Support Case and work through what you are seeing with the C1 Support Team.
HTH.
Grant
That worked! Thanks! Wow that was not easy to understand at all.0 -
[quote="northern_fov" wrote:
[quote="SFA" wrote:
Assuming you are using a different recipe for each output - which you really need to in this case anyway I would imagine - then in the File tab of the recipe in the Root Folder field open up the options, scroll down the list and choose "Select Folder".
You can then browse to the folder you wish to use or create a new one.
Once created it should appear as a previously used folder in the list if you create a new recipe at some point and wish to use the same location. The subfolder, etc., options should now work with that as the new Root folder for that Recipe. The Recipe will ignore the "Output Location" "Destination" field since you have not selected "Output Location" as the Root folder for the Recipe.
If you have already tried that and it does not work I would suggest you double check the naming conventions and the actual locations they point to just in case you have duplication of folder names confusing things. If you find nothing wrong there then create a Support Case and work through what you are seeing with the C1 Support Team.
HTH.
Grant
That worked! Thanks! Wow that was not easy to understand at all.
I know what you mean ... but then once you have understood it I think you will find it is logical and very powerful taken in conjunction with the full use of the flexibility of the Recipe system.
It just takes a bit of time to become totally comfortable with everything.
That said I mainly work in sessions and leave the default Root Folder as the Session's Output folder (rather than your preferred Output target root folder) but make the output target a subfolder within the session. So I rarely need to override the default root folder at the session level. However, based on your needs as outlines, setting the specific root level required right in the Process Recipe seems to be the best approach and is exactly why that override (away from the more complex, in some ways, default settings) is available.
Anyway, glad you got it working as you want it to.
Grant0 -
[quote="SFA" wrote:
I know what you mean ... but then once you have understood it I think you will find it is logical and very powerful taken in conjunction with the full use of the flexibility of the Recipe system.
It just takes a bit of time to become totally comfortable with everything.
LOL my problem is I have to relearn it each and every time I make a change to recipes. It is powerful and logical but still confusing - because so many fields interact to create the final output. I'm going to bookmark your explanation since it is a concise description of one particular happy path - pun intended. 😊0 -
[quote="IanL" wrote:
[quote="SFA" wrote:
I know what you mean ... but then once you have understood it I think you will find it is logical and very powerful taken in conjunction with the full use of the flexibility of the Recipe system.
It just takes a bit of time to become totally comfortable with everything.
LOL my problem is I have to relearn it each and every time I make a change to recipes. It is powerful and logical but still confusing - because so many fields interact to create the final output. I'm going to bookmark your explanation since it is a concise description of one particular happy path - pun intended. 😊
I understand exactly what you are saying.
It's one of the few things in this type of software functionality where a graphical flow path via an interactive diagram screen might be very welcome.
If you always use the same, or nearly the same, output processes and they send to consistent, or nearly consistent, pre-defined locations then there is little to do each time you use them. Which is good but means you get little practise in setting things up for a new requirement should one arise.
If, however, some aspect change almost every time you use a recipe then remembering that you need to amend something AND what that thing is is not always as natural as one might expect when eagerly rushing to complete a job and see the final results. Especially if one's approach might be seen a little "over comprehensive" (or complex in other words) as mine sometimes seems to be.
For me it's often a question of reminding myself to slow down, think about that I need for the tasks on this run, double check the settings, and run single file output tests just to make sure the results are as required. Then run the rest of the processing.
However if needing multiple ouput runs from the same project where, perhaps, the files have been pre-grouped by an album for example, then the changes to remember and the process does not need to be checked for each "album".
I still think a graphical representation would be useful.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
8 Kommentare