deema Wrote:appdata/roaming has some nice config settings, any other folder paths holding config data?
Settings.dat has all the user settings.
deema Wrote:And what are .xst files? "States" of the specific players configuration settings, as the folder name suggests?
Xst are interface state files. They store anything that a skinner marked with the save_state keyword. Things like last frame that the animation was on.
deema Wrote:Are these text data that can be edited, is that how the cli will work? Possible to be clicked within windows and have the settings and such occur, bypassing the "need" for the cli, at times? (just lookin at every angle. CLI requires typing settings into script. The xst appears to already hold that data by visual manual placement, similar to splicons (one of the image types in Splindy).
.xst files. I'd just go with using the CLI.
deema Wrote:And I just realized that the custom made spectrums are not the "actual" analyzer, not the entity, and so this command /SetVisualisationPos=x,y, will not work for the custom ones, right? And the CLI option will only position the player, is that correct? And this command, /SetMainPlayerPos=x,y, will be associated with both the player and the custom analyzer. So I will need to position the analyzer prior, in PS, to be in the right spot, yes? How will it affect resource utilization if the player and spectrum are on a image canvass that is up to screen sized, potentially up to 1800x900+? And there is no way to have the spectrum in a separate psd, right? Or can it be in say the playlist or EQ psd? I will test this right now but posing question anyway
Correct, /SetVisualisationPos=x,y is just for the built in vis window. Usually people create a section on the main, playlist or equalizer windows to show the visualisation.
It might be possible to use a 1800x900 skin, as long as you're using transparent pixels in between. Otherwise the memory consumption and software rendering won't keep treat users well.
Feel free to give it a try though, I'm not entirely sure what you're trying to do.