Waveform adds a few milliseconds of silence during rendering

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hello everyone, hope you're all doing well!
To be honest I don't like creating new accounts on forums but couldn't find a solution to my issue yet.
I'm working on a lathe cut vinyl at the moment. The audio needs some tweaks / fixes before sending off the files to the pressing plant. All wav-files were cut in Audacity beforehand to an exact time, like 01:08:000 (min:sec:ms).

After importing the song (yes, to the beginning of the track :) ) I'm using some plugins:
Image

To render / export the audio I'm clicking on that field at the beginning of the track
Image

and then render / export with these options (Render to a new track)
Image

To compare both tracks (the original and the rendered one) I put them into Audacity and saw that the rendered track is just a few milliseconds longer now, like 01:08:019.

After checking the settings in Waveform I found this:
Image

I changed it - just for testing - from 480 to 2048. After rendering even more ms were added.

Now just for fun I thought "what if I render the new rendered song once again?". So I did about 30x. In the end, the rendered song was 1 sec longer than the original tracks. I once again compared them in Audacity. They were still in sync but it was clearly visible that there's silence added to the end of the track.

You might ask why this is important. Sure, I could cut off those additional ms again but that's one more step to work on. And it's important when doing a vinyl (and of course a CD) production that the track lengths are correct. I guess when some ms here and there add up that it could cause some issue maybe when sending the VTM file to the pressing plant.

Long story short: Why does Waveform add these milliseconds and doesn't leave the tracks as they should be? Where's the issue here? "Welcome to Waveform" is not a valid answer. :D

Appreciate your help & have a great day!
Alex

OS: Windows 10
Waveform V12.5.5 (but same issue with the version before that)

Post

It actually adds at the start also, shifts the phase by a fraction. So renders don't null with the original audio.

Post

dysjoint wrote: Sun Jul 09, 2023 10:34 pm It actually adds at the start also, shifts the phase by a fraction. So renders don't null with the original audio.
Is it a bug or intended? If the latter I ask myself what's the point?

Post

It sounds to me like what you're getting is a whole number of cleared buffers.

6240 lots of 10.9ms comes to 68.016s according to Excel and
1466 lots of 48.4ms comes to 68.0224s.

Is it enough to notice or matter? At the end of the day. 0.019ms is less than a fiftieth of a second.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post Reply

Return to “Tracktion”