[Sam Rosenthal]

Hi.

I’m using Vegas 12 for Audio & Video; it doesn’t crash as often as you are describing with 15, but does crash more often then I’d like.

I often think about going back to an earlier Vegas, such as 9, for my audio work. Most of what I use Vegas for is music creation, and I don’t think Vegas has upgraded anything on the music side in a decade or more. Anyone else here using Vegas for multi-tracking music creation? What version of Vegas works best for you?

Sam

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

Nope. Creating a new folder to save the punch-ins in didn’t help. The strange thing is another session I am working on, at the same time, doesn’t crash at all. Something gets corrupt in the session, it seems. I do wonder if this is a Vegas on Windows running on a Bootcamped mac problem. Ie: nobody else seems to experience this.

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

Does anyone have advice for how to “set up Vegas” so it crashes less? are there places to assign how much Ram is used, how much is retained in cache, etc etc? I often wonder if Vegas crashes because it’s storing too much junk. Also, is there a place where you can clear out past edit memory? Or limit how much of that junk it holds onto?

Is there a place to read BEST PRACTICES for using Vegas?

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

I tried a lot of different things today, try to solve my problem. None of them worked

This sounded promising: (Tips) Clean up of Vegas Temp files. I followed the instructions, Vegas went longer between crashes, but crash it did.

Then I had a thought. I checked, and the folder I have been saving all my punch-ins in had 887 files in it! I’m wondering if Vegas is choking when it goes to that folder because of the number of files / total file size? I created a new folder to save in. I only had about 30 more minutes in the studio, but Vegas didn’t crash during that time! I will pick this session back up next week, and I’ll update if my problem is fixed.

For now, if you have any other thoughts & suggestions for things to try, please share them.

Thanks,
Sam

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

James. I have had a similar problem for years with clicks that occur at the exact same spot each play, but aren’t visually in the audio track. I have found that there is an “anchor” at the click point, usually in the volume envelope. If you delete and replace the anchor, it often (though not always) makes the click go away.

I have even found that I can mute the channel with the anchor, and the problem doesn’t go away. And you can sometimes mute every channel and the click doesn’t go away. I’m using Vegas PRO12, but it was there in earlier versions too.

I suspect it is the anchor interacting with a setting somewhere (not enough ram, i don’t know?) that causes this.

Is there an anchor at that point in any of your tracks?

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

Hello.

Your video is set to private. The pops are not caused by 2 point headed straight down, if that’s what “vertical drop” means. It’s slow sloping curves.

The pops generally sound like “pfffft!” Not blasting loud (except for once in a while), but definitely still audible.

I cannot reproduce the problem, a file will get corrupted and then they occur. I have 3 tracks on this album. Two of them are fine, one has the problem.

I was finally able to kill all the pops, and render the song into a .wav file that has is useable. The problem isn’t solved, just that it didn’t create any new pops and I was able to finish my work (unless I have to go in and re-edit anything).

Has anyone else had this problem?

S

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

Hi Paul —- Yes, these are the “anchors” for volume change envelopes.
A screen shot looks like any other vegas session. You cannot see the pops, because they are not in the audio tracks.

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

Thank You László — I decided to go with my V12, and upgrade to the latest build. But I screwed that up. See my new post.
: (

PRO12 Build 770
Running in Windows 7 on a Bootcamped Mac

[Sam Rosenthal]

Thanks for the suggestion, but this is not the problem.

[Sam Rosenthal]

Hi @John Rofrano – maybe you can help me with this question. I posted it as a separate thread, but no replies there. Thanks for your time…..

Hi all. I have been using Vegas for audio recording for 12+ years. In 2013 I got the latest iMac and installed Vegas PRO12 for video, running in the Bootcamp environment. This month, I began using PRO12 for audio as well.

Vegas runs fine; however, my Waves L1 Maximizer no longer appeares as a plug-in option. Figuring it was compatibility issues between the 12-year-old-Waves + new 64bit Vegas, I bought the L2 Maximizer from the Waves site. I had the same problem (not appearing as a plug-in option). After much dicking around, I was informed by Waves, “Please note, Bootcamped Mac is not oficially supported with Waves products, as it can produce various issues.”

Since then, I bought iZotope Alloy2, which does show up as a plug-in option and works fine. But it’s not as smooth, elegant, and effective as L2.

I’ve tried installing two free reverbs, yet both do not appear as a plug-in option.

Now. finally, my question: Do you have a recommendation on a free (or low priced) reverb that will work with on a Bootcamped Mac? And what about a very simple – but effective – compressor?

Thanks

Sam