TrackSpacer - First plugin by Wavesfactory

[Ivan_C]

Hello c_voltage ! Could you share the two audio files you are using in your example so I can try to reproduce the exact same issue and solve it ? Thanks in advance, and thanks for having already shared that example

[c_voltage]

Hello c_voltage ! Could you share the two audio files you are using in your example so I can try to reproduce the exact same issue and solve it ? Thanks in advance, and thanks for having already shared that example

Yes, ofcourse. Here i bounced both instrument lines, so, two wave files in archive. (I did check trackspacers as well with this rendered waves in project - the same result). Project tempo 95.
http://www.mediafire.com/file/65xj0kahl ... t.zip/file
And for good reproduce please do not forget set the Amount knob in trackspacers to maximum level (as in video).
As well, if anyone has MTonic and ARP2600v2 and Studio One v3 (and both Trackspacers respectively) i can share test project, if need.

[virtualpt]

Anyone else having licensing problems when trying to have both old & new versions installed?

I find that if I just install the new version then it licences fine. If I install both versions, using the previous instructions in this thread, then the new version reverts to demo mode & won't license. I have emailed support, but no response.

Have reverted back to old version as I use this plugin a lot & don't want to rely on new version yet until the bugs have been ironed out.

[Ah_Dziz]

does anyone have any experience using this in classical music? or ambient beat-less soundcapes?

I've used it extensively for scoring. So that would be orchestral music but not exactly classical in style.
Basically I have a few extremely low frequency percussion sounds that are awesome for adding impact at a transition or something. I buss all these (extra large orchestral bass drum, giant taiko and such) together and then trigger trackspacer on my other sections to shave a couple of decibels off the low end and make room for the mega bass. It is great at making space in a mix with barely audible artifacts. It makes the difference between a muddy mess that's at the edge of clipping and a nice heavy duty bit of sub coming in here or there.

[Captain]

Hello c_voltage ! Could you share the two audio files you are using in your example so I can try to reproduce the exact same issue and solve it ? Thanks in advance, and thanks for having already shared that example

I have the exact same issue here. I already noticed it the first time I tried v2.5, but just thought "maybe it has always sounded like that". Now I compared the new version with v2, and realized there's definitely something seriously wrong. V2 sounds silky smooth, while 2.5 has this strange distortion going on all the time. It might be hard to notice in a mix or if you don't specifically listen for it, but once you compare with the old version, the problem is crystal clear.

Also, don't know if this is intentional or not, but apart from the artefact, the two versions seem to produce totally different results with identical settings. Check the screenshot behind the link - it's two bounces of a simple bass-kick sidechain using TS2 & TS2.5. Filters set to min & max, ratio at max. I know it's a new version and everything, but is it really supposed to sound that different?
https://drive.google.com/open?id=1kLkFp ... NTafOW3pU1

Logic Pro X 10.4.1, OS X 10.13.4. Does not seem to matter which other plugins or audio sources I use, it's always the same result.

Anyone else having licensing problems when trying to have both old & new versions installed?

I find that if I just install the new version then it licences fine. If I install both versions, using the previous instructions in this thread, then the new version reverts to demo mode & won't license. I have emailed support, but no response.

Yes, it just started doing the same here after I reinstalled the old version to compare it with the new. Slightly irritating, to say the least.

[Caine123]

hmmm did you sent a mail to them?
they dont get here often

[c_voltage]

I have the exact same issue here. I already noticed it the first time I tried v2.5, but just thought "maybe it has always sounded like that". Now I compared

Ok thank you for confirm. Btw what intresting, i googled parallel top at Gearslutz, and there one user asks about possible changes into sound in new version, so, another user reply to him:

I'm not part of Wavesfactory but I can say testing it thoroughly today, it actually sounds better than previous version. The low end is somehow better preserved and with level matched sources, one can easily hear more perceivable low end.

https://www.gearslutz.com/board/showpos ... tcount=445

That as well strange to hear
I do not even know, maybe the problem is local. Well,i mean, maybe the v2.5 behave differently on different types of CPU? (new AVX instructions etc)

[Captain]

I'm not part of Wavesfactory but I can say testing it thoroughly today, it actually sounds better than previous version. The low end is somehow better preserved and with level matched sources, one can easily hear more perceivable low end.

https://www.gearslutz.com/board/showpos ... tcount=445
That as well strange to hear
I do not even know, maybe the problem is local. Well,i mean, maybe the v2.5 behave differently on different types of CPU? (new AVX instructions etc)

Strange indeed! I have this happening on two different computers, a Mac Pro 2013 and MacBook Pro 2017. I’ll also email their support asap.

[wavesfactory]

Hi guys,

First of all, thank you for all your messages.

The authorisation issue will be fixed in the next version. For now there is a workaround:
Go to Library/Application Support/Wavesfactory/Trackspacer
and create a folder called "License". Then, authorize the plug-in normally and it will work.

Ivan and I are working on a fix for the distortion issue. @c_voltage, are the attack and release parameters matched in the comparison?

[zvenx]

until c_voltage answers.

from about 45 seconds into his video he shows a the attack release

rsp

[c_voltage]

@c_voltage, are the attack and release parameters matched in the comparison?

As already Zvenx reply - yes, ofcourse, all was in video.
Need say this is first things what i adjusted when did hear distortion (attack\release settings in 2.5 slightly different by default than in 2.0, but this did not affect to this artefact anyway.)

[wavesfactory]

Hi guys,

New version 2.5.2 uploaded with these changes:
- Fixed: attack and release ballistics matched with the ones in version 2.0. This fixes the distortion issues some users were experiencing.
- License folder is created on macOS if Trackspacer doesn't detect it. This fixes the issue some users were having when trying to authorize.

Download here.
Mac: https://trackspacer-wavesfactory.s3.ama ... 02.5.2.pkg
Windows: https://trackspacer-wavesfactory.s3.ama ... 02.5.2.exe

[Ivan_C]

By the way, if you still experience some kind of distortion artefacts, you can play with the attack/release time constants until everything sounds right to you. What happened before in short is that the ballistics filter behaviour was acting way too fast, like when you play with a compressor with the lowest possible settings (and even more lol) for attack and release. But now everything should be fine anyway, and working like in the previous version of Trackspacer

Feel free to test and tell us your remarks

And thanks again c_voltage for the detailed report and the shared files !

[c_voltage]

Hi wavesfactory, Ivan. Thank you for work. I did test just now, what i observed now:

- markers of actual values of attack\release knobs slightly different in 2.05 vs 2.52. by visual position. (Just as info, it's not a problem ofcourse, even perhaps such was before, frankly i initially guided just by visually position (without attention to digits values), what also apply to my video.)

- now, in v2.52 the increase of attack to about 0.70ms can eliminate distortion actually - it's good. (regarding release knob, let's take average standard value, about 50ms, in both versions)

- small attack values (about 0.20ms and less) still produce the same distortion in v2.52, what especially good audible at very short attack like 0.6ms, while in v2.05 we can't reproduce such distortion in any value, even at 0.1ms, all clean. But:

- i found that works of attack curve at big values in v2.52 produce pretty interesting (distinctive) result, which very different from what happens in v2.05 during the same values.
As example for reproduction this (for compare) - Attack 3.70ms, Release 50ms
The 2.05 during this setting has a much more neutral\weak character.

I would even say - I like this 2.52 "big" attack behavior a bit more than "neutral" in 2.05, but i partly doubt in his "normality", (although I can be mistaken, maybe exactly this behavior can be called as normal or properly, or conceived by the author initially, I do not know).

In general, i would say, currently it;s two different plugins, which are both interesting. Good this or bad.

[c_voltage]

Ehh, no, after some tests i can suppose that clarity need be around 0.30ms-0.70ms too, since i found this quick range can be useful as well. (again, i compare with 2.05)
In general, guys, i don't know. Maybe I do not understand something.