Topic: Play-to-File Over-Writing Source?

Version 1.610:

From Plug&Play tab, if I open a ".mid" file and Play-to-File (.wav, in the same folder), a new ".wav" file is created. But if I select and open files from the File & Folders pane (Files in Folders), Play-to-File (.wav, to the same folder) overwrites the ".mid" files (without changing the file type); however, Play-to-File (.mp3) behaves correctly, creating a new file. If I save the ".wav" file to different folder, it creates a new "wav" file, but labels it as ".mid".

Re: Play-to-File Over-Writing Source?

OK!

Re: Play-to-File Over-Writing Source?

(Not fixed in 1.611?)

Re: Play-to-File Over-Writing Source?

You are right! I was working on it when I was distracted by the bug making reading of certain Unicode strings from midi files hiding the mixer. A very strange bug! Strange as I myself could never reproduce it - it never happened for me, but for the user that reported it, reading the same file. Excuses... excuses...

Thanks for reminding me!

Re: Play-to-File Over-Writing Source?

@Kenneth, this is what it says:

7588: ApplicationEvents1Activate
7588: >> ReadSavedProgsFile Arr = C:\Users\Jack\Documents\Google\SynthFont Arrangements\zeldametalnew.sfarr
7588: newversion: <!defaultfgh>,<C:\Users\Jack\Documents\Google\SynthFont Arrangements\[Orchestral [1]]-[000;!defaultfgh].fxp>
7588: LoadPreset - use params
7588: LoadPreset - OK
7588: Load from file: C:\Users\Jack\Documents\Google\SynthFont Arrangements\[Orchestral [1]]-[000;!defaultfgh].fxp
7588: ReadSavedProgsFile done
7588: Chunk file = C:\Users\Jack\Documents\Google\SynthFont Arrangements\[Orchestral [1]]-[000;!defaultfgh].fxp
7588: LoadPreset - use params
7588: LoadPreset - OK


Ignore the fact my SynthFont Arrangements are in a folder called Google inside My Documents, one day SynthFont just starting saving them all there!

This is the FXP it generates: http://dl.dropbox.com/u/28476963/%5BOrc … fgh%5D.fxp

Which is nearly empty.

Re: Play-to-File Over-Writing Source?

This file is not a chunk file but a 'parameter list' file (VSTs offer two choices: chunk files which are completely proprietary and you have no control over the contents; and an 'old fashioned list' of the parameters offered in the editor. Both are stored in a fixed binary form, though. If you have a binary editor you can easily distinguish between these two: at offset 08 there are four characters, typically 'FxCk' or 'FPch'. The P character tells it is a chunk file. ). But it doesn't matter what kind of file it is for this exercise, it is indeed mostly empty, which could still be correct.

Anyway the last line in the output says 'LoadPreset - OK', so no error occurred during loading. But this doesn't guarantee that the contents of the file is valid.

What I do NOT understand is why it was saved in the Google folder, as the code explicitly calls for the Arrangement folder!! There's something VERY FISHY going on here!

I'll make a new version and add even more debug output.

7 (edited by Elven Spellmaker 2012-02-02 09:54:34)

Re: Play-to-File Over-Writing Source?

The google folder has a subfolder called SynthFont Arrangements which it saves arrangements to. I don't think it's too fishy, I think somehow the default arrangement folder has just changed to there instead. All my arrangements are there and so are the VST presets as well.

I don't think the Google folder thing has anything to do with it, it wasn't saving the changes I made within the VST BEFORE the folder was created.
I.e. I think my SynthFont.ini points to the Google folder for arrangements.

The only reason the Google folder is there is because I saved Google's homepage a while back (for some reasons) and SynthFont just started using that folder for its arrangements.

Re: Play-to-File Over-Writing Source?

OK!