Hello everyone,
When I export a paint history seq or a paint action seq
File> Export> Paint History Sequence
or
File> Paint Action Sequence Presset
when I place it in the correct folder, it does not appear in the list of Presset.
This is probably because the file produced by SA is a "document" type and not an "executable unix file" type.
How to fix this?
Replies
To get back to your original question.
If you export a PASeq preset to the PASeq preset category currently displayed in the preset browser in studio artist 4, that new preset does not immediately appear in the list of presets in that category.
However, if you mouse down on the category popup at the top of the preset browser, then that category reloads and you will see that new preset you just exported.
So this could very easily be what you are seeing, and the cause of some confusion.
Now a perfectly legitimate question is, why isn't studio artist smart enough to just do that current category list update automatically. Good question indeed.
We did fix that in V5, so for now you have to do it manually, but in the future it will happen automatically.
Thank you for the technical explanation of this problem.
"However, if you mouse down on the category popup at the top of the preset browser, then that category reloads and you will see that new preset you just exported."
I have tried several times, restart the App, but the setting still does not appear in the list.
I redid the whole process, but nothing to do…
I ran that test in V4 before i posted that comment above. So that is the behavior.
Why don't you attach the specific PASeq preset you exported here, so we can take a look at it.
And tell me the exact pathname where you put it on your computer.
There could be 2 different things going on.
A: it's not where it really is supposed to be located to show up as a PASeq preset in the preset browser.
B: You thought you exported a PASeq preset, but you accidentally exported a different preset type. So then it would not show up when the preset browser was displaying the category it's in.
Favorites categories are a good way to work with custom preset files, since they will display and open any preset types located in them. That is not true of any of the specific factory category folders associated with specific op types.
Bingo!
The right file in the right folder, that was the problem.
I placed the test file generated by "Export Paint Action Sequence Preset" in Paint Action Sequence> Art Still PASeq > Render Styles and indeed it appears in the list.
So the generated file is OK.
Not easy to understand these subtiles differences.
I'm a newbie and I'm not very fluent in English, which does not facilitate the detailed understanding of the 576 pages of the guide !!!. ;))))
Thank you for your help
Google translate works fairly well for our various blog tip posts since je ne parle pas francais.
Although we did notice it was translating 'paint action sequence' into 'pain actions' the other day, ha,ha.
Bonjour Max, bienvenu sur le forum !
Tu peux me contacter si tu as besoin d'infos
Studio Artist Preset files aren't executable unix file types.
Are you on a mac or windows?
Studio Artist preset files specifically adhere to apple's APP and FILE Type ids for our different file types. Which are officially registered with apple computer.
'SYNA' // studio artist application type
So if apple followed their own guidelines, any synthetik file type would show up in the finder as being a synthetik file type, not some weird 'unix executable file'. But i guess they can't be bothered to care about little details like that. The mac finder gets very little love these days.
Thank you for that…
I'm MacUser.
Strange ... look at my Type files. And SA does not see them.
Default files are signed "executable Unix file" (?!)
The history of this kind of thing is fascinating. So let us begin, to give you some insight into my underlying frustration, which i hope you didn't take the wrong way in my initial reply to your question.
When the original mac was created back at the dawn of time, they came up with (or borrowed from Parc) the concept of user files that had 2 hidden parts, the data fork and the resource fork.
This was actually a brilliant advancement beyond the old idea of a user file being a single file. The mac operating system hid all of this from the user, so the user only saw one file, and all of their physical interactions or manipulations with that user file were via manipulating a single file object.
Behind the scenes, the user file was actually 2 separate files. And some additional apple specific id information associated with the data fork.
For example, there were also two 4 letter ids (defined as an apple OSType) associated with every mac file, the creator type id , and the file type id. The creator id told the operating system which application the file was made in, or belonged to. The file type was specific to a particular creator type. So in studio artist, the creator id would say the file was a studio artist file, and the file id would say it's a PASeq preset, or a paint synthesizer preset, etc.
You need to register your companies creator id type with apple computer, which Synthetik Software did many years ago. Here it is:
'SYNA' // studio artist application type
When you installed a new application file on your mac when this all worked properly, the operating system was smart enough to extract all of this information out of said newly installed application file, and then things just worked perfectly from that point on. You'd see the files appropriately marked in the finder, clicking on one opened it in the appropriate application etc.
Other computers, like windows for example, did not have advanced features like this. So you had to add a physical file extension to a file name in order for the operating system to even have a clue about what kind of file that file was, so that it could actually do something with it. This is a really clumsy and lame way to deal with these kinds of file identification issues.
After Next computers staged their take ever of Apple computers at the end of the 90's, the Next people seemed to hate all things uniquely mac, and sought to get rid of them out of spite or perhaps misguided ignorance. So things like the extremely well thought out scheme for using creator and file type ids to make the mac and it's interactions with user files run smoothly started to be ignored by people at apple. Like certain apple software releases didn't even support the well documented standard mac programming practices for using these ids.
And you see the result of that deterioration of what was once a well oiled and properly functioning mac operating system in your screen shot above, where studio artist preset files are showing up marked as unix executable file types.
Where specifically did you place the PASeq preset file? Complete pathname please.
Did you put it in a specific PASeq category folder, or loose inside of a collection folder? It won't show up if it was that second option.
If you did place it inside of a correct PASeq category folder, if you reload that category into the browser, does it show up then?
Here's a tip on preset folder organization.