Free VSTi Sampler : TX16Wx 0.9beta *update 11*

[elcallio]

Another quick question: How do you get the sustain pedal to work?

v0.9.05 out now. Adds sustain/hold pedal support. Also fixes incompatibility with FL Studio and some other hosts.

[larsalt]

Thanks for the pedal support! That was quick.

[audiojunkie]

Really Cool! Thanks!

--Sean

[larsalt]

So, here's a somewhat severe bug it seems. Many of the programs sound different after I load them back in. There's a slight clicking noise in the attack phase that I can't get rid of.

Here's an example of a very simple program: Just one single wav file. The first part of the clip will play the program when it was just create. The 2nd part in the clip is after I restarted the host and loaded the program back in. You can hear it best at the very end of the clip (at about 16 seconds in).

Here's the clip:
http://www.mediafire.com/?bqe6fp5183u5h91

[elcallio]

So, here's a somewhat severe bug it seems. Many of the programs sound different after I load them back in. There's a slight clicking noise in the attack phase that I can't get rid of.

Here's an example of a very simple program: Just one single wav file. The first part of the clip will play the program when it was just create. The 2nd part in the clip is after I restarted the host and loaded the program back in. You can hear it best at the very end of the clip (at about 16 seconds in).

Here's the clip:
http://www.mediafire.com/?bqe6fp5183u5h91

Weird. What host did you do this in? Could you provide the project and files? Also, if you take the freshly created bank (when it sounds right) and save it as a .txbank (with full copy), then clear and reload, does the same thing happen? Did you run with 'save all waves in host project/fbx'?

I would love to reproduce this.

[larsalt]

I tried it in a couple hosts (energyXT and cantabile) a couple different ways. Saving just the program, saving the bank (from the sampler) and now saving as fxb (including samples). All with the same result. I also went back a couple versions of the software to see if this was around longer (yep).

Here is the FXB file.The program is very basic. I just dropped in the two wav files and adjusted attack/release a bit. Sounded fine, but when I save and load the FXB (after clearing the bank or even completely restarting the plugin), the clicking noise is back.

I did this with a couple different samples as well, so it's not just the wav files that are screwed up. If you actual slow down Attack, the clicking get's a bit worse.



http://www.mediafire.com/?r96ywqbnfsj9idq

[larsalt]

One more thing: The clicking noise is not on every key. If you move the start for the sample it may fix the clicking for one key, but then another key starts to click.

[elcallio]

One more thing: The clicking noise is not on every key. If you move the start for the sample it may fix the clicking for one key, but then another key starts to click.

Sorry, but could you send me the original wave files as well? I would like to compare the actual sounds data from the FXB vs. Wav.

[larsalt]

One more thing: The clicking noise is not on every key. If you move the start for the sample it may fix the clicking for one key, but then another key starts to click.

Sorry, but could you send me the original wave files as well? I would like to compare the actual sounds data from the FXB vs. Wav.

Sure:
http://www.mediafire.com/?1sqgdglfqbyo0x7

[larsalt]

I think I got it. AFter loading the file and adjusting Decay and Level 1, the clicking went away.

[larsalt]

I think, if they fit, I just left them at the default. They must be not saving correctly if they are never adjusted and then be loaded with different values other than the default values when create a new group.

[larsalt]

Actually, it looks like Decay1 and Level1 are not loaded at all even if you do change them.

[elcallio]

Thanks to larsalt, I identified a few places where parameters where not saved/restored properly. Expect new drop very soon. Also, I addressed some other issues with saving/loading tx-files.

Which leads me to a question: What's your opinion on naming program/performance files? Right now, the name of a program/performance is actually fully separated from the file name on disk when saved. The reasons for this is are mainly
1.) File names have character restrictions that are annoying for program names.
2.) The XML is embeddable, i.e does not have to come from file

A perhaps somewhat unintuitive result of this is however that if you create a program, name it 'Monkey', then save it. TX will now suggest the file name 'Monkey.txprog'. So far so good. However, if you now rename the program to 'Elephant' and choose 'Save Program' again, the file name will not change. It will still be Monkey.txprog (since the program was previously assigned a file path). Even 'Save As' will still suggest 'Monkey.txprog'. While logical and following the rule of separation of name and file, it might also be somewhat unintuitive.

How does people feel it should work? I could tie the file name to the program name, so that every time you change the name, the remembered file path is changed as well (as with waves), not a big problem. But what should happen if you choose 'Save As'? Should the name of the program change with saved path as well? And if so, mangle down to allowable characters?

I'm having a hard time deciding whats best here. Suggestions appreciated.
Cheers

[larsalt]

I think it may make sense to have the suggested filename = program name. If you change the program name from Monkey to Elephant, that may be because you created a variation of Monkey. By changing the suggested filename you run less of a risk of overwriting a file. Just my two cents

[larsalt]

A Minor bug: When loading multiple wav files at once the file that is selected last will show up first in the list of loaded samples.

E.g. selecting C1, C2, C3,C4 will show up as C4,C1,C2,C3