Problem with 2.1.0 b2

[Claudio G.H.]

Hello everybody, I'm new to this nice forum.

I have tested TX16Wx downloaded on last December, and have had some problems which caused to crash Reaper. So I updated to the latest version.
However even this last version downloaded today causes a problem: when Reaper scans for VSTs it show the following message:

Plug-in 'TX16Wx.dll' executed invalid operation during scanning

Reaper does not crash by itself, but the plug-in is not added.

My system: W7 64 bit, Reaper v4.31/x64 rev.7d61bf

Further information.
Before this update previous version caused the same problem at the first scan, however after that first scan TX16Wx loaded successfully and I had the chance to test it and enjoy this nice instrument. Until today, when tweaking on LFO the plug-in caused to crash Reaper with no way to reload it anymore.

Also, I have a couple of questions:
1. Why the DLL have version 2.100.2007.573 which is not consistent with the setup version (2.1.0 b2 x64, as shown in the filename) ...where to read the plug-in version (other then from setup filename)?
2. Do the plug-in stores status information somewhere? If yes, where?

Thank you.

[Claudio G.H.]

I just read few minutes ago you uploaded a new version while I was writing the previous message. I downloaded also this file (download time 15:38 CET 9 Jan 2013), but the problem is still there.

An other information. I installed TX16Wx in a subdirectory of drive D (where I have all VSTs and samples), not the drive C as suggested by default.

[elcallio]

Hello everybody, I'm new to this nice forum.

I have tested TX16Wx downloaded on last December, and have had some problems which caused to crash Reaper. So I updated to the latest version.
However even this last version downloaded today causes a problem: when Reaper scans for VSTs it show the following message:

Plug-in 'TX16Wx.dll' executed invalid operation during scanning

Reaper does not crash by itself, but the plug-in is not added.

My system: W7 64 bit, Reaper v4.31/x64 rev.7d61bf

Further information.
Before this update previous version caused the same problem at the first scan, however after that first scan TX16Wx loaded successfully and I had the chance to test it and enjoy this nice instrument. Until today, when tweaking on LFO the plug-in caused to crash Reaper with no way to reload it anymore.

Could you provide some more details on what you where doing to make it crash? And if possible, provide the project file + samples? Might be relevant.

The problem you are describing could be a number of things, but just a first step, could you check your "c:\Users\<username>\AppData\Local\TX16Wx" folder, and see if renaming/deleting the "settings.ini" file changes anything? And please, make a copy of it and send me in case this actually helps.

Also, I have a couple of questions:
1. Why the DLL have version 2.100.2007.573 which is not consistent with the setup version (2.1.0 b2 x64, as shown in the filename) ...where to read the plug-in version (other then from setup filename)?
2. Do the plug-in stores status information somewhere? If yes, where?

Thank you.

1.) Its the MS standard DLL versioning scheme. 2.1.0 translates to 2.100.<build no> in DLL version. This is the same version you can se on the setup page as well. 2.1.0 == easier to read for humans.
2.) See above. "c:\Users\<username>\AppData\Local\TX16Wx\settings.ini"

Cheers
/C

[Claudio G.H.]

What I've done before crash:

Before it crashed I was tweaking on the LFO1. I selected a group, the wav sound were a cowbell pithed along two octaves (no fixed sound), I added a loop so that the bell rang continuosly while keeping a note ON, then I changed in mod table the firs row (the other were empty) selecting as source the LFO1 and destination the loop start time, set the amount to 25.00; so I began to tweak on the LFO1 knobs: rate, amp, and fade in, when I turned fade in down to zero again Reaper popped up a messagebox with the message of crash.

Remark: this was with the previous version of TX16Wx, the one available on December 31st (when I downloaded it the first time).


I've saved the content of the directory: c:\Users\<username>\AppData\Local\TX16Wx\, then I deleted the file settings.ini as suggested. No luck.
Within that directory I found also a subfolder named 'preset' with a further subfolder named 'modulation' containing a file (zero byte in length) named 'New preset.modulation'.
I also tested deleting the whole content of the ...\AppData\Local\TX16Wx directory with no success.

I've uploaded the saved content of such directory, please copy the following link and swap the * sign with forward slash:
www.avibi.tv*cld_temp*TX16Wx.zip

About the project, I had no the chance to save the project since the crash happened while I was experimenting

[Claudio G.H.]

I uploaded also the reaper project, and the sample which I was tweaking on when it crashed.
Please point your browser here: www.avibi.tv*cld_temp*ReaperProject.zip
(Change * with / )

Files will stay there for only a couple of days.

[Claudio G.H.]

Update.

Yes, it is somewhat stupid, being I an experienced programmer, not to think to restart the system to see if the failure resolves, but it is what is happened

Today I restarted the PC (which usually I don't, since my computers are always on) and noticed that scanning again for VSTs in Reaper, the TX16Wx were loaded correctly.

What is happened, I think, was a first crash, the one that I described in the opening post, which clearly left a dead process, so that restarting Reaper caused to reload the same (corrupted) piece of code still running in memory (or a new one anyway going in conflict with some shared, corrupted, resources?)

I haven't had the idea to snoop into the task manager to see if any process related to TX16Wx (or Reaper) were still active.

Now I will try to tweak again the LFO1 to see if happen the same failure.
I will keep you up to date.

Cheers,
Cld

[Claudio G.H.]

Replicated the error.

Action performed:
1. added a loop to a sample
2. selected for the group of that sample to loop start at loop1
3. added to the first row of mod table: as source LFO1, as dest. loop1 (group still selected), amount 34.0 ms, no frz checked.
4. clicked on the small '+' button located at the bottom side of the modulation table, near the dropdown list on the right: the plug-in causes Reaper to crash which show the following message:

Runtime Error!

Program: C:\Program Files\REAPER (x64)\reaper.exe

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Hitting OK the application die.

Running the application again lead to the same runtime error.
Unfortunately I haven't found any entry in the processes list of Task Manager clearly related to either Reaper or TX16Wx. So now I try to restart the pc.

Cld

[Claudio G.H.]

Update.

Despite restarting the system (after having cleared any content in the folder AppData\Local\TX16Wx\), I'm not able to load anymore TX16Wx. Reaper start and scan it correctly, but when I try to add it into a new track (on a new project), Reaper crashes.

So my conjecture about the dead piece of code still in memory seems to be flawed.
Notice. This morning I restarted my computer cause an operating system update.


Cld

[budweiser]

Same problem on cubase 7 (7.0.1 32bit on w7 64 bit). Crash during the initial vst scan, restart, no tx16 in the plug list, new scan of the vst plugs, crash.

By the way, another problem, in cubase 6.5 this time : double click in the "wave editor" upper part leads to a crash 100% of the time.

But i'm really happy to find a successor to my tiny shortcircuit (the only sampler until tx16 that allows drag n drop from the main cubase window !)
I'll be more than happy to buy the tx16 pro !





edit : for any reasons, it's now working with cubase 7... But the "wave editor" bug is still here.

[Claudio G.H.]

Update.

I'm baffled. I restarted again Reaper just few minutes ago, PC never restarted from last crash. Now TX16Wx is loaded successfully
The only thing I've done in the meantime was to use Reaper with a new project and loaded an other VST (Piano One), at the end closed Reaper.

I like so much this sampler, and I would like to help in finding out the problems.
Also I have some ideas for improving the sample layering, but I'll talk about this next time, now I think it is far more important to make stable this VST.

Cld

[elcallio]

Update.

I'm baffled. I restarted again Reaper just few minutes ago, PC never restarted from last crash. Now TX16Wx is loaded successfully
The only thing I've done in the meantime was to use Reaper with a new project and loaded an other VST (Piano One), at the end closed Reaper.

I like so much this sampler, and I would like to help in finding out the problems.
Also I have some ideas for improving the sample layering, but I'll talk about this next time, now I think it is far more important to make stable this VST.

Cld

I think you've experienced two different bugs:
* One was that the dialog code would fail on your second project in the same DAW instance, due to windows classes not being set up correctly.
* The problem with LFO + modulation preset was an old bug that did not show itself until the b1 release. Basically, it failed creating a preset file. Though it actually succeeded. Even worse, if the file ended up corrupted, you would not be able to load the plug-in any more.

I've hopefully fixed both these issues. There is a b3 release available now, please try it out and see how it fares.

Cheers
/C