TX16Wx 3.1.1c released

[elcallio]

Hello all.
Semi-major update finally out. Bunch of nice fixes and improvements. Some of you might have used the beta version. Now it is graduating.

TX16Wx 3.1.1b

• Fixed encryption issue on Win7

TX16Wx 3.1.1b

• Fixed regression in chunk reader
• Fixed regression in wave writer

TX16Wx 3.1.1a

• Fixed linkage/CRT regression on Win7
• Fixed DPI regression on Win7
• Fixed automation regression

TX16Wx 3.1.0 changes:

• Added native FLAC streaming
• Added native OGG streaming
• Added per region sound parameter offsets
• Added offline activation support (TX16Wx Pro)
• Added FX preset management support (TX16Wx Pro)
• Added "region" round robin source - default in key switch (TX16Wx Pro)
• Filter frequency modulation now in cents (pitch) instead of hertz
• Improved missing file search initial path selection
• Improved dialog sequence
• Improved import of other program formats (SFZ/SF2/AKP/EXS). TX16Wx now generates much leaner and easier to navigate programs from these sources
• Fixed OSX file dialog layout behaviour
• Fixed OSX modal dialog behaviour
• Fixed MIDI note overflow in rendering causing hang

Downloads as usual at www.tx16wx.com.
Happy sampling.

[pigfront]

Cant open in any host, Windows 7 x64

[mccy]

Same here , not working at all. Reaper / Ableton Win 7 64

back to old version, working again. 3.1. does not work here.

[elcallio]

Ugh, Win7. I thought we had stopped doing that.
Stupid CRT incompatibility issue. I've patched it and uploaded new builds. I had hoped to wait longer until 3.1.0a, but here we go.

Seriously though, you should really upgrade your OS.

[mccy]

Do you have any tip for upgrading to win10 and moving a complete audio-house with all it's registrations, activations, workarounds etc... I think I would need about 1 Week fulltime to update All this has become so complex over the years...

There is no 'update'-possibility, is there? I have to build from ground up!?


Thank you for the fast solution! It works now.

[carlosigls]

Hello, I have the next problem. When I try to change the name, numbers etc. two characters are written in the vst2 version. In version vst3 I don't have that problem.

[mcbpete]

There is no 'update'-possibility, is there? I have to build from ground up!?

Here's the upgrade guide: https://pureinfotech.com/upgrade-to-win ... windows-7/

You don't need to wipe your machine to go from 7->10 - I've updated over the years from v7 to the latest Win10 v1903 without ever having to start 'from the ground up' and everything still functions perfectly. Even stuff I'd installed back in 2012 when it was running Win7 still works fine on my current OS build.

[sinkmusic]

There is no 'update'-possibility, is there? I have to build from ground up!?

Here's the upgrade guide: https://pureinfotech.com/upgrade-to-win ... windows-7/

You don't need to wipe your machine to go from 7->10 - I've updated over the years from v7 to the latest Win10 v1903 without ever having to start 'from the ground up' and everything still functions perfectly. Even stuff I'd installed back in 2012 when it was running Win7 still works fine on my current OS build.

+1

THank you for the 3.1 update, Callio.

[elcallio]

Hello, I have the next problem. When I try to change the name, numbers etc. two characters are written in the vst2 version. In version vst3 I don't have that problem.

Which host are you using (and os, version etc)?

[carlosigls]

Hello, I have the next problem. When I try to change the name, numbers etc. two characters are written in the vst2 version. In version vst3 I don't have that problem.

Which host are you using (and os, version etc)?

Hello, I've been trying other Daws and it's a problem in Mixcraft 8.1 Pro Studio but only in vst2 version, vst3 works fine. I'm Windows 10 Pro 64.

[pigfront]

Cant open in any host, Windows 7 x64

Thanks, for update, but in Renoise doest not show GUI, only black empty window.

[elcallio]

pigfront - funny little error with DPI detection on Win7 (some). Fixed in 3.1.0b build.

[pigfront]

Thanks, now works.

[elcallio]

Mostly due to me sucking, the 3.1.0 build has inoperable automation mapping. That is really bad. I've updated the builds to 3.1.1. This should fix (and improve somewhat) both doing and saving/loading mappings.

[eddycb]

Can you check if it's still working in Mixcraft 8 Pro Studio. when TX16Wx 3.1.0 was in beta, the program was working at first, but the next time booted up Mixcraft 8 i got an error: https://i.imgur.com/7Rc2N0l.png and then when i tried to load one of projects it couldn't load the vst2 version of TX16Wx (https://i.imgur.com/weLKrVT.png), and both vst3 and vst2 were gone. I tired everything from repairing, reinstalling the beta TX16Wx to rolling back on an older version (which the installer told me to exit windows explorer and to reboot my computer for some reason) and reinstall Mixcraft 8 which in the end didn't work since TX16Wx (vst2) was still gone; as for the vst3, it was back at least.
When using the vst3 on a older non-beta version, again at first it was fine but when i loaded it back, it couldn't load what .sf2 i edited in TX16Wx (regions), it seem to remember what i've edited in regions but not what i had edited on and then while playing the rest that looked fine, TX16Wx was spammed some of beats on some soundfonts when it worked fine the first time, ex: there was a track going one beat at a time, it was working for the rest of the instruments in mixcraft and for TX16Wx (vst3), but when i tried to load back to the project and played, TX16Wx spammed the beat on the soundfont that was working before.
By the time TX16Wx 3.1.0 became stable, i installed it and both TX16Wx vst2 and vst3 were gone again. Now in 3.1.1A, TX16Wx (vst3) is back but i can't load up my last project unlike in 3.1.0 (stable): https://i.imgur.com/dh8Vzdf.png
Please work on stability in TX16Wx, with other VST software it's mostly works fine in Mixcraft 8, but TX16Wx seem to make mixcraft buggy.
OS:win 7