Its not saving its own patches when saving song in FL studio so track is ruined after load

[2blackbar]

Thanks for not telling anything about it.
Kinda ass issue dont You think.

[opless]

What version of the tunefish are you using and what version of FL studio?
Also what operating system are you running?

[2blackbar]

version 12 of FL studio, tunefish4 , i read that you have to make new patch in tunefish and save it but that doesnt solve the problem when you reinstall everything from 0, your patch is gone then and problem persists.
So that means you cant make any track with tunefish4 because it wont save your patches and recall them on load.Its using different patches on load, also when GUI of tunefish is not in focus then it sounds more silent, when its in focus then tunefish plays that particular sound louder, like what the hell. Its strange and too bad because thats genius piece of software besidse those problems, but i noticed its often like this with unorthodox pieces of coding work, some features work amazing but some basic features are totally destroyed.
I also know a lot of peopel have this issue with tunefish4 not recalling patches when you load your saved tracks.Ints a problem iin tunefish, i never encountered that with any syth before.

[opless]

This is what you should have opened with.

I can understand you're frustrated, but starting off ranting won't encourage any developer (on any project - not just this one) to look into an issue.

One last thing, what operating system are you using?

It may be relevant (I'm not a Dev on this project)

Best Regards

[2blackbar]

Win7, 64bit i dont think its gonna be fixed, this issue persists since a long time, it was a problem for people in KVR OSC in 2013 and its still not fixed, i dont think its gonna be fixed but it would be nice if devs would post about this kind of issue when you downloading, i spent 4 hours making a track, saved , opened and got disappointed so bad.I wish i could do tracks with this plugin but i cant cause i know that when i switch to other pc, tunefish4 tracks will be destroyed.
I think this sunth wasnt meant to be vsti at all, and got buggy along the way.

[paynebc]

sorry for the loss of your track, but saving instruments is not the task of the synth but the task of the DAW. The plugin provides methods of retrieving the patch data so the DAW can save it into its project file. At least that is how I know it from other DAWs. I cannot support all of them since I do not have the resources to do that. Luckily this is an open source project and anybody can provide fixes and patches to ensure compatibility on systems I cannot personally support.

[paynebc]

oh and yes tunefish was always meant to be a VSTi and AU. what else would it be? :)

[2blackbar]

I dont get why its like that, guys who made Sprike branch managed to get it right, Sprike saves patches and recalls them when i reload track in flstudio but tunefish 4 doesnt do that.

[bryc]

So is this something that normally works in other hosts? Automatic FXP save/recall inside the project itself. I also use FL12, and it doesn't appear to do this.

For years, using FL12, I assumed that the plugin was designed to only load presets directly from the bank folder located in AppData via the Save/Restore buttons. I've used hundreds of plugins in FL12 and very few fail to restore an FXP preset from a project file (one notable example is an old plugin called Edirol HyperCanvas and Orchestral). So in these cases I always thought it was designed that way.

Upon loading a project, it does recall the Program Number, but instead of loading internal FXP patch data, it searches for the .txt patch data of that Program Number, stored in AppData folder. So it's workable. One can save patches that way, working within the allocation of the 0-999 preset slots. Modifying an old patch without copying to a new slot will affect old projects however.