Flac audio cut off in V13

Laurence wrote on 9/4/2014, 2:25 PM
I've been noticing that the ends of flac files seem to get cut off in V13 lately, but today I noticed something different. I loaded up a project to re-edit that I had done several years ago(in Vegas 10), and that particular project had a flac audio voiceover. At the time in an older version of Vegas, this flac VO played back perfectly, but today it clipped off the end just like Vegas 13 does with all flac audio files. The difference is that the waveform audio file was still there to the end (since it was drawn in the older version of Vegas). Anyway, I am even more certain than before that something is broken in V13 that worked just fine before. V12 also had this problem. V11 never worked for me so I don't know about that version. In V10 flac audio worked fine.

Comments

MissingTheFOUNDRY wrote on 6/9/2015, 10:39 AM
You're not crazy. Sound Forge v11 has the broken flac I/o plugin too. I started athread on the SF forum

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=3&MessageID=926343
john_dennis wrote on 6/9/2015, 12:06 PM
Not sure if it is related but I burned a CD from the timeline in Vegas Pro 13 with 48/16 WAV on the timeline and the last track on the CD ended before the end of the music was done. Source was a 45 minute recording.

Here's what the last track looked like when I put it back on the timeline.

https://dl.dropboxusercontent.com/u/40618156/2015-06-09%20Audio%20Ends%20before%20track%20end/Stop%20before%20the%20end.png

I was able to render the audio as wav for DVD/Blu-ray without fail. Seeing this lowered my estimation of the usefulness of burning a quick CD from the timeline.

PS
I still have CD Architect.
rs170a wrote on 6/9/2015, 2:02 PM
John, I'm wondering if your problem is because an audio CD wants 44.1K while a DVD wants 48K.
FYI, I've burned several CDs (short and long) from a Vegas timeline and never had any problems, only up to Pro 12 though as I don't have Pro 13.

Mike
john_dennis wrote on 6/9/2015, 2:09 PM
"[I]John, I'm wondering if your problem is because an audio CD wants 44.1K while a DVD wants 48K.[/i]"

That may be, but given the offer of simplicity of burning from the timeline, I assumed that the program would have handled that detail without a lot of herky-jerky motion.

I rendered the 48 kHz source to a 44.1 kHz file, put it back on the timeline, muted the 48 kHz track and burned a CD with repeatable results.

Screenshot here.

At a minimum, I think there is a bug in the "Tools / Burn Disk / Disk-at-Once Audio CD.." function when experienced people of above average intelligence can't seem to find a combination that produces an acceptable result.

I've reproduced this bug in Vegas Pro 12 and 13 on two different machines.

Geoff_Wood wrote on 6/9/2015, 4:34 PM
48K to 44K1 on CD burn - Vegas is supposed to (does) deal with that automatically. So it's presumably something else.

geoff
john_dennis wrote on 6/10/2015, 12:43 AM
Today, while I was waiting for the caulk around the bathtub to cure, I created projects in Vegas Pro 9, 10, 11, 12 and 13. The Project Properties were all set to 44.1 kHz - 16 bit. I chose an audio file that I created in Sound Forge that was 44.1 kHz - 16 bit. After creating 13 CD tracks in a Vegas Pro 9 project, I opened the project in 10, 11, 12 and 13 and burned a CD without error.

I have yet to burn a complete CD from a 48kHz - 16 bit project. I usually start my projects as 48 kHz - 16 bit and burn CDs as an after-thought. That's the reason I would choose to burn a quick one from the timeline.

I know what I'll do. I'll read the manual again...
john_dennis wrote on 6/12/2015, 1:00 PM
[intellectual honesty]

After thinking about this and trying different scenarios for burning a CD, I've decided that my expectation that Vegas Pro should burn a CD properly from a project originally conceived as a Blu-ray project is unwarranted. There is no program defect in Vegas Pro, rather my expectations are invalid.

I produced a working CD in 32 minutes including converting 16 audio files for inclusion into a 44.1 kHz / 16 bit project, setting the CD tracks, burning and verifying the CD.

While burning a CD from my original project produced the anomaly described above (and possibly others have experienced the same thing), setting up a more appropriate project to burn a CD worked as expected. Doing it the right way from the start, beats struggling to reuse an existing project any day of the week.

[/intellectual honesty]
Geoff_Wood wrote on 6/12/2015, 6:01 PM
Would be nice to understand exactly what was upsetting things though, cos it should have done the CD OK.....

geoff