Comments

rraud wrote on 7/26/2022, 11:39 AM

Welcome to the Magix Sound@AristotelesLfigueiredo-alf Forge users community .

Sorry, I cannot give any recommendations or opinions without more information

Do you have Sound Forge Pro or Audio Studio..
Do all file types exhibit the same behavior?
How much of the file's end are cut out?
Are the plug-ins in the chainer or applied on at a time
If using a plug-in chain in SF Pro, is the chain applied directly or rendered?.
Is this apparent in preview or after the file is rendered (or encoded) and played back,
After rendering, does the reopened file's waveform show the data that is not being played
What format are you rendering to.

AristotelesLfigueiredo-alf wrote on 7/27/2022, 1:46 PM

In this case I was using Sound Forge Pro, Plugins Waves Version 14 and 13, AR TG Mastering ST, L3-16 and Abbey Road Vinyl ST. But it has happened with other plugins. I'm using SF 14 because 15 freezes and doesn't complete my processing. I often chain up to 7 plugins to get to my target. it didn't happen before. My computer remains the same. I also use Slate, Plugin Alliance and IZOTOP. I use Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz 4.20GHz and 32.0GB (usable: 30.9GB) RAM. Windows 11, but on 10 it had already started to happen. But only now I decided to seek help.

rraud wrote on 7/27/2022, 2:49 PM

I would suspect the Waves plug-in has something to do with it. Searching this forum should show many issues with Waves / Sound Forge.
If you can experiment, take the Waves plug out of the chain an see if the behavior remains. I think the last Waves version that worked with SF was version 10.

You can email Magix staff for their opinion: infoservice@magix.net