Taperssection.com

Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: Taper Chris on January 12, 2017, 12:22:09 PM

Title: audacity>cdwave
Post by: Taper Chris on January 12, 2017, 12:22:09 PM
Why does the work get shortened by about 3.5 seconds per hour when transferring from audacity to cd wav?
Example, file is 02:04:53 but when I tracked it out on cd wave and put track list into winamp it totaled 02:04:46. I found out playing back on winamp. Everything is 44.1k 16b from recorder to audacity.  And if I put the audacity track into winamp the length of project is the same. Thanks.
Title: Re: audacity>cdwave
Post by: Taper Chris on January 12, 2017, 01:26:33 PM
I think its the winamp. I went to tracks folder, highlighted every track and went to properties. The total time for the tracks is 02:04:53. But whats interesting is the audacity track in winamp also came out to 02:04:53.
Title: Re: audacity>cdwave
Post by: morst on January 12, 2017, 02:16:10 PM
I bet it has to do with rounding seconds.

If we had three files that were 10.6 seconds long, one might say it's 33 seconds total (11 x 3) but one might only say 32 seconds (10.6 x 3, rounded up)
Title: Re: audacity>cdwave
Post by: F.O.Bean on January 13, 2017, 05:28:52 AM
Chris, have you ever tried FooBar 2000? I would try that and see what the total length is :)
Title: Re: audacity>cdwave
Post by: Taper Chris on January 13, 2017, 12:10:58 PM
Chris, have you ever tried FooBar 2000? I would try that and see what the total length is :)

woooord. It seems to be the win amp, since the wav files properties ( I highlighted all 19 tracks ) say the tracks equal the untracked mix in time. So as long as the work flow and flac upload isn't corrupted, Ill be ok if my playback is a lil rounded up or down.

I'll see wsup w foobar though, thanks!!!!