So first off.. full disclosure, then I'll get to the problem.........

For several years I've had all my presets/tables/noises on another drive, using symlinks (which maybe isn't needed anymore, but I digress). I installed TCD v1.363b3 probably a half year ago or so, and since then, those symlinks still worked great, but my Serum would occasionally kill playback after I tweaked parameters a bit. This got to be pretty frustrating. I decided to uninstall, and try again... that fixed the initial problem, but possibly created a new one.

I have this weird thing happening now, and I'm not sure if this is normal (a new feature.. or maybe an old feature my custom skin hid from me?) or if something isn't working right. I even went so far as to revert back to having all my presets/tables/noises in the default documents folders, and rebuilt the db file.

The Problem:
I'll use an example... Triple Spire Audio Moondust. Some presets do a weird thing, some don't.
ATMO - At Dawn preset looks like so (how I'd expect all presets to kinda display):


ATMO - Beginnings preset looks like this, though (note the red on TSA_013 and TS_021):


I can actually click on TSA_013, and find it listed in the list of tables, and when I select it, the red highlighting goes away. But only for that particular instance.. if I reload the preset, the red highlighting is back.

My question though... is this red highlighting normal (my gut tells me it probably is)? Does it just mean the preset has modifications to the wavetable file, perhaps??? I had a custom theme before, and right now I'm using the default, so I'm wondering if this is just a normal thing that the custom skin I was using had essentially hidden from me by not coloring those table names.

If this is not normal, does anyone have any ideas??? As mentioned, I've gone back to everything on the c: documents folder, and rebuild the db file.

 

Last edited: Aug 15, 2023

go to the pen to edit the wave and then you have to save the waves again without any changes i had such a problem before but it can also be that the waves are completely reinstalled in the same place without any changes after that it should be back work normally if not then I was able to help further up to here This red coloring actually only means that the waveform is missing and not saved. It can also be possible that the waveform and the presets have to be saved together

 

I have never seen it do this. But one would imagine, it knows what wavetable filenames the preset should contain from your tables. And it's not finding it there when it attempts to load it. That can be wrong location, incorrect permissions, renamed or deleted files.

I would do a quick hd search and see where either of the listed wavetable files are. You will get a better idea where you have it looking (and not looking) for that sample.

 

Last edited: Aug 15, 2023

Haven't read anything that has been typed here but just wanted to say that if you got ANY problems with an xfer stuff you can just either mail Steve Duda himself or reach out to him on reddit/discord and he pretty much always responds. Really nice guy he is

 

OK phew after resolving this new issue of missing or corrupted tables, I managed to move the whole "%USERPROFILE%\Documents\Xfer\Serum Presets" folder to "E:\VSTs\Port\Data\Xfer\Serum Presets".

I then created a Symlink as so:
mklink /D "%USERPROFILE%\Documents\Xfer\Serum Presets" "E:\VSTs\Port\Data\Xfer\Serum Presets"

Everything appears to be working as intended now, including the very initial problem that I was trying to fix - parameter changes causing Serum to mute sound (EDIT: looks like this muting problem may have returned, but I'm not going to worry about it.. Hopefully a future version fixes this). All good, and thanks again to the two of you for your suggestions.

 

Last edited: Aug 16, 2023