UpTilDawn wrote:I am really concerned about the prospect of having to keep three versions of SAW/SAC - from 32 bit, to 64 bit, to my decision to give plugins clearly defined purpose prefixes

2 weeks. (word of warning - this is talking to the boss speak)

jmh wrote:I had considered apostrophes in file names in my .ini builder and decided that no one in their right mind would include them, therefore my script would not address them.

By the way, before vacation (if visiting in-laws qualifies), I made great headway on this. But I made a discovery that impacts some older code I wrote (for something else) that I believe will address an inconsistency in that older code, so I was following that wormhole before I forgot about it.

Anyway I think I will leave that as it is. If ' is a legal file name character, you'll have to re-name that one by hand - it will leave you with something to do.

Looks like apostrophes are a gray area. According to Google AI (which is never wrong):

[INDENT][INDENT]Yes, apostrophes (single quotes) are generally okay in Windows file/folder names for basic use, but they can break scripts, commands, and older programs because they are reserved characters that can prematurely terminate a string, so it's best to avoid them for maximum compatibility, using double quotes or backslashes (escaping) when they appear in paths.[/INDENT][/INDENT]

MMP wrote:UAD DSP version plugins were affected by the naming length issue. Previous to the update, unnesting the plugins was a workaround.

Ah. Gotcha.

UpTilDawn wrote:This came with the v2.3 release -

A new update to Version 2, now Version 2.3 fixes a minor issue with VST3 Plugin loading.

Version 2.3
Enhancements
*

Bug Fixes
* Modified code to fix path name length to handle vst3 installs with extra long path lengths due to multiple folder nesting of the install path.

>---<


Bob L

---------------

There does still appear to be a limit, since I discovered one install that goes too many folders deep, while setting up this new pc. I'll need to retrace my steps a bit to be able to be specific... maybe I can do that today.

Ah. Gotcha.

jmh wrote:It's funny this came up:
puff n' grunt

I had considered apostrophes in file names in my .ini builder and decided that no one in their right mind would include them, therefore my script would not address them...

Anyway I think I will leave that as it is. If ' is a legal file name character, you'll have to re-name that one by hand - it will leave you with something to do.

...

Well, just to be clear, I have no intention of using anything but letter, numbers, dashes, underscores and periods in the names I give the plugins.

------

I am really concerned about the prospect of having to keep three versions of SAW/SAC - from 32 bit, to 64 bit, to my decision to give plugins clearly defined purpose prefixes -


or even to keep at least two operational pcs handy for those (increasingly rare) instances that I need to revisit old sessions with the hopes of having the sessions open intact. All the more reason to carve out more time to print and commit all processing to all tracks, when a project is "completed", I suppose. Keeping old generations of computers around is beginning to feel like keeping at least one of every tape system I've used for "serious" recording in my life. Maybe it's not so bad that I've never owned anything bigger than a 16-track digital recorder, before switching to the pc.

It's funny this came up:
puff n' grunt

I had considered apostrophes in file names in my .ini builder and decided that no one in their right mind would include them, therefore my script would not address them.

By the way, before vacation (if visiting in-laws qualifies), I made great headway on this. But I made a discovery that impacts some older code I wrote (for something else) that I believe will address an inconsistency in that older code, so I was following that wormhole before I forgot about it.

Anyway I think I will leave that as it is. If ' is a legal file name character, you'll have to re-name that one by hand - it will leave you with something to do.

___________

...on a side note, and in the right mind department, I have a configuration file that accommodates hiding and renaming plugins that does have apostrophes in it. While yet another file might not sound like a solution - if you go through waves upgrades, you will rejoice (in the cause of writing this, I just upgraded - only to find I blew up a whole bunch of 32 bit edls that use waves - so as usual, a waves upgrade will still suck the joy right out of you, and remind you why you never want to use one of their plugins again). Hopefully I will be done soon, and stop hijacking every thread.

UAD DSP version plugins were affected by the naming length issue. Previous to the update, unnesting the plugins was a workaround.

Dave Labrecque wrote:Maybe I'm just getting old and forgetful, but what changes are you referring to? I don't recall anything new in that regard. :confused:

This came with the v2.3 release -

A new update to Version 2, now Version 2.3 fixes a minor issue with VST3 Plugin loading.

Version 2.3
Enhancements
*

Bug Fixes
* Modified code to fix path name length to handle vst3 installs with extra long path lengths due to multiple folder nesting of the install path.

>---<


Bob L

---------------

There does still appear to be a limit, since I discovered one install that goes too many folders deep, while setting up this new pc. I'll need to retrace my steps a bit to be able to be specific... maybe I can do that today.

UpTilDawn wrote:By the way - I appreciate the changes you made for the sake of vst files installed within nested folders. It's helping.

Maybe I'm just getting old and forgetful, but what changes are you referring to? I don't recall anything new in that regard. :confused:

Okay. I think I've got it worked out now... thanks to your nudge, Bob.

Much of it is/was the 32 bit and 64 bit being mixed in the presets folders. I probably forced the more recent 64 bit presets to save into the familiar 32 bit folder for convenience - not realizing that SAW was actually creating new 64 bit folders as I would first save a new preset and I was bucking the system by insisting the save be dropped into the "original" folder for that named plugin.

There's also the new issue I've created for myself, by wanting to give the ini file a name that defines the plugin's purpose in the new pc - naming the "puff 'n grunt" ini file "Dist puff 'n grunt", for instance. That way it's listed with the other distortions in the All list inside of SAW.

Simply copying the original puff 'n grunt plugin from the old pc to the new preset folder named Dist puff 'n grunt on the new pc isn't enough. I get that error message when I try that. In my mind, it should work, because the actual dll is the same and the ini file would point to it regardless of the name I give to the title of the ini file. I am obviously wrong about that.

That is why I'm taking my time installing vsts to this new pc. It's a process.....
By the way - I appreciate the changes you made for the sake of vst files installed within nested folders. It's helping.

Were the old presets created on the 32 bit SAW version... version 2.3 is 64 bit... the 64 bit and 32 bit presets are currently not compatible....perhaps I can try to expand the code to possibly convert the presets on the fly.... let me take a look.

Bob L

I'm in the process of setting up SAW64 v2.3 on a "new" pc.
Everything has gone smoothly - as expected from SAW.

But now, I've run into a snag.
I'd like to copy all of the relevant vst plugin presets saved in SAW's vst presets folder, from the old pc to the new pc.
But when I do that, although the plugin opens just fine, preset files from the old pc won't load -
I'm getting this - Incorrect Preset Format for this Plugin - message.
To be clear, these are SAW preset files, created with the blue triangle menu and not a user preset (if even offered) of the vst plugin, itself.

I've tried exploring creating a fresh preset in both old and new pcs - trying to open the presets on the other pc and get this message every time.
Isn't it possible to copy the fairly extensive accumulation of saved presets for these vst plugins to a fresh install of SAW?
It seems like it should be a simple task, or a simple edit and redirect at least.