-
Audioon 10/22/2010
Effects on the Master Output in Surround on V10
I have reproduced the 5.1 plug-in problems on the master bus and am in the process of addressing the issues for a future update of Vegas 10. On the issue of running old waves plug-ins on a newer 64-bit machine: I spent time early last year tracking down a number of issues related to 32-bit plugins on a 64-bit machine. I found and fixed many problems that caused vegas to freeze. If there are any more bugs associated with 32-bit plug-ins running on a 64-bit machine, please post them here and I will dig into the issue again.
-
Audioon 4/6/2010
BWF Import fails.
I just took a look at this issue in the latest vegas codebase. The issue is not the relative location of the bext chunk! We are properly loading the chunk wherever it appears in the file. The issue is that Vegas craps out when it sees that the OriginationDate or OriginationTime fields are set to NULL. I will admit that Vegas could be more tolerant of this situation, but I would also suggest that if any app is going to add a BEXT chunk, it should also add the OriginationDate and OriginationTime fields, setting them to the current date and time by default. Late update: I just got off the phone with Joe Ramos @ Sound Devices and informed him of my findings. It sounds like they may add a default OriginationDate/Time to files edited in wave agent to address the problem. Thanks for posting the topic here. If there are any other BWF issues you'd like Vegas to address, please post them on the forum!
-
Audioon 3/5/2010
VST plugin problem in Vegas 7
drbam: I just installed Vegas 7.0e, and my VSTs were picked up just fine. It sounds like you set up the correct path, so the problem may be that there is a plug-in giving vegas a problem. Have you tried re-scanning for plug-ins. The older version of the plug-in scanner in vegas7 sometimes took a few passes to get the job done when plug-ins crashed.
-
Videoon 3/1/2010
Audio question ... Vegas 8c Windows
With your drawn out event selected: 1) View->Edit Details 2) Double click the "Length" field. 3) Enter in 8 hours (in whatever time format you have selected). Done.
-
Audioon 2/15/2010
modelling my voice
Vegas 9.0c includes élastique pitch/formant adjustment technology. If you have 9.0c (or later) you should be able to right-click on an event and open the audio properties dialog. Once there, select "élastique" as the method, "pro" as the stretch attributes setting, then click the "preserve formants" checkbox, and enter in a formant shift amount. = Matt
-
Audioon 1/28/2010
Pitch and stretch glitchy in Vegas9, but not 8.
Johan, I have added your request to the list. Thanks for pointing this out!
-
Audioon 1/27/2010
Pitch and stretch glitchy in Vegas9, but not 8.
While testing stretch properties I discovered an issue with the Audio Event Properties Dialog: If you open up the Audio Event Properties Dialog for a un-stretched event and click "OK" it seems to mess up the stretch settings. If you then stretch the event the waveform stretched properly, but what you hear is a looped version of the file at the original tempo. Likewise, if you then go and set the stretch to "NONE" after this point, the audio will now play stretched, but the waveform draws looped. The only workaround I have identified is to undo the project back to the point before the Event Properties were changed. I have already added this to our bug database.
-
Audioon 1/20/2010
Footswitch for punch in?
For about 50 bucks you can put together a device that lets you plug-in a cheap footswitch and sends a MIDI message that you can map to record when the footswitch is pressed. One of our SQA guys built one to trigger a sequence on a synthesizer over its MIDI input during live performances. I think the synth trigger project was done on an Arduino, but there are several choices out there and many websites dedicated to projects with these devices.
-
Audioon 1/14/2010
Vegas9C UAD-1 Rendering problem
My recommendation for an optimal UAD experience is to use UADs alone, or with VST plugins (not DX) in vegas projects. Limiting the use of UAD to buses also increases reliability. This is a big generalization and there are instances where DX and UAD can coexist in a vegas project., but for simplicity's sake this is the best guideline I can give. The problem with UAD (and its lack of issues with Cubase, etc) is due to the fact that UAD designed their hardware to function with the Steinberg audio engine. UAD hardware demands a certain set of rules be applied in how and when fx processing occurs. We have been making incremental improvements in our handling of UAD, but the amount of work required to get 100% compatibility has been prohibitive. I am also aware that other DAW vendors have similar problems with UAD for the same reasons.
-
Videoon 1/12/2010
Vegas 9.0 64bit "Not Responding"
kosstheory: Could you update your system specs? That information helps us narrow down the problem and gives you a greater chance of creating a fix, or at least a workaround. Thanks, - Matt
-
Videoon 1/12/2010
Bluray and 5.1 surround questions
TeeTime: you write: " Looking at my 5.1 setup with the 6 wav files, do you see anything wrong here?" Here is what you can do to get better results: When you simply want to take 6 tracks and route each to a different 5.1 channel you need to route your audio tracks directly to the master bus, not Bus A,B, or C. Once this is done you can configure each track to route to the proper channel. Note that in order to send to the LFE channel you have to right-click on the panner and select "LFE Only". When you route an audio track to a non-master bus, the track->bus pan occurs in stereo, not 5.1. You can then pan the bus into 5.1 to the master, but this is often not the most direct solution. - Matt
-
Videoon 1/12/2010
Audio Plugins All Missing
Jerry, What version number shows up in WaveHammer's about box when you use itin Vegas 6.0? - Matt
-
Videoon 1/12/2010
Audio Plugins All Missing
Jerry It sounds like you may be running an older version of WaveHammer and somehow Vegas has lost track of the plug-in as you have installed and uninstalled software packages. If you open the plug-in's about box, what version number do you see? You might be able to recover WaveHammer's registration by manually unregistering the plug-in and then re-installing Vegas 9. To manually un-register the plug-in: 1) Find the folder that contains "sfhammer.dll" 2) Open a command prompt (Windows Menu->All Programs->Accessories->Command Prompt), then right click on command prompt and "run as administrator" 3) CD to the folder that contains the plug-in. 3) Enter the command "regsvr32 /u sfhammer.dll" After you re-install Vegas 9, drag and drop sfhammer.dll onto Vegas to re-register the plug-in. I hope this helps.
-
Audioon 1/8/2010
Functionality between AutoTune EVO & Vegas 9 Pro
Peter, Please post what you discover about Vegas and EVO Graphic mode here on the forum. If you continue to have problems I will take a look and see if there is something I can do to solve this on the Vegas side. Thanks, - Matt
-
Audioon 2/27/2007
Normalization minimizes rather than maximizes
Vegas doesn't have a "normalize" function, as it's not a desctructive editor. Vegas has a nondestructive normalize function, accessible from the menu you get by right-clicking the event. - select "switches" then "normalize". You can get a little more control of this by right licking on the event and selecting the "Properties..." item. I suspect what is going on is that there is a spike somewhere in the signal that is biasing the max gain of the clip. If this is the case, you can solve this by trimming the event so it no longer contains the spike. You can verify this visually, or by opening the event properties dialog, click "recalculate", then see what the calculated gain is. If it is negative, there's a spike in the event data somewhere.
-
Audioon 12/4/2006
Any news on pan to buss problem?
Not to be rude but why what this change made (to the current behavior)? I'm just wondering if I'm missing something here... others are calling it broken. I'm assuming it was more of an oversight. You are correct, vegas 7.0 did not introduce the change - it was made earlier - I was clarifying what the existing behavior in vegas 7.0 is. It has been a few years since we made the change, but if my memory serves, it was because at the time we had just added surround to the feature list, and given the time we had left in the project cycle, we couldn't come up with a satisfying solution to the problem of handling the surround case (when the master is a surround master). So, it was not “broken” or an oversight – it was what happens when you are running short on time and you have to find an interim workable solution. We are obviously at the point of exceeding “interim” so we are reviewing the signal flow and now is the time to suggest the ideal way this needs to work for you. The best input we can get is not just a “how” it should work, but a “what” are you using it for that would work better, and “why”. I would be especially interested in what your expectations are for how to handle panning when the primary route is to a surround Master, and there is a send to a bus. - Matt Logan
-
Audioon 11/30/2006
Any news on pan to buss problem?
ultrafinriz, As of Vegas 7.0 the Track pan is only applied to the main routing. Sends do not listen to the pan, whether or not the send fader is set to pre or post volume. Another possible workaround in your situation would be to send the track through one bus, which applies a pan and routes to another bus. That way, you get your pan, and the ability to copy pan envelopes easily We are evaluating our routing architecture – if you have a recommendation for what you would like to see changed, I’d love to hear it. The more detail you can provide, the better. - Matt Logan
-
Audioon 11/15/2006
Does Vegas Support Plug-in Delay Compensation
> Does Vegas Support Plug-in Delay Compensation Yes it does.
-
Audioon 10/17/2006
Is Vegas REALLY robust enough for audio work?
Unfortunately, we have recently discovered a major problem using UAD-1 plug-ins with the Vegas Audio Engine. The current engine does not process data in quite the way the UAD-1 wants, and therefore the UAD plug-ins go into a kind of native cpu software emulation of their hardware. This native mode is extremely CPU intensive. For a simple 5-track project with one UAD 1176LN plug-in on each track, a project running smoothly should consume about 4% cpu on my 2.8 gHz machine. Instead, I see a 37% CPU load. The bottom line: Vegas + UAD-1 performance currently sucks. We have a solution in mind for this problem, though it is a major overhaul that is typically the kind only released in a full version update. On the subject of Waves interacting with the audio engine: Some waves plug-ins don’t play nice with our multi-threaded architecture, and will crash. One solution is to disable track rendering. Another is to only use Waves plug-ins in the mixer. We are working with Waves to resolve this issue.
-
Audioon 8/25/2006
Shafted again.
People are reading more into my comments than I am even aware of. I posted one little guess about the future of one product. The absence of information about other products does not mean there will be zero development effort put toward them - it means I don't know anything about the other possibilities.
-
Audioon 8/25/2006
Shafted again.
From my understanding, the audio improvements in Vegas 7.0 consisted of absorbing the audio engine performance enhancements from Acid 6.0, adding some multi-channel rendering flexibility, and supporting rudimentary 5.1 audio importing. The last two versions of Vegas have had audio-light improvements because the more audio-centric engineers were assigned to Acid 6.0, and also spent quite a bit of time supporting the soundtrack creator product (CineScore). The future is really in flux right now, but I wouldn’t be surprised if future versions of Acid absorbed more Vegas editing features (like more useable takes, drag between tracks, grouping, ripple edit, etc.).
-
Audioon 1/27/2005
Problems w/ event pitch shifting & Rec. in 96/24 w/ delta 1010's
TubeLover, Bottom line: Don't use time stretch during a recording session if you can help it. Are you using ASIO? If so, what's the latency? The time stretch can be a CPU hog. It tends to induce periodic gapping if you have very low latency settings. The more time stretched events playing at one time, the more likely this is to occur. This can be reduced somewhat by choosing a less-intensive time stretch algorithm in the “Stretch Attributes” combo in the “Audio Event” tab in the event properties. The Stretch Attributes settings least likely to induce gapping are: MUSIC: A06 SPEECH: A08, A09 SOLO INTRUMENT A13 DRUMS: A17, A18, A19 On my Dual Xeon, I get 18 Tracks of gapless playback with A02, and 25 Tracks with A06. The default setting of A03 produces 23 gapless tracks. Almost makes you want do request a track-freeze feature, doesn’t it? :)
-
Audioon 8/12/2004
todo. (please)
Wazer wrote: “are you serious about your existing time-stretching methods? Why can not use that we had before : AUTOFADE TYPE at least (the only usable TS algo from SonicFoundry/Sony)?? A 3rd party (MPEX2-type) app integration should be the goal. (like Pro Tools, or Nuendo..) I think your 19 methods are unusable one-by-one.. And too much.” Yes, we are serious about our timestretch methods, and are always looking to improve them. What is it you are using timestretch for that makes the existing algorithms unusable compared to the AUTOFADE type from Vegas 4.0? Having the most useful timestretch is the goal. Unfortunately, at lest in Nuendo 2, MPEX2 is a non-realtime plugin. A quick test reveals it operates at something like 75% realtime on my fairly high end developer box. I have got some ideas for improving the stretching which might see the light of day.
-
Audioon 5/19/2004
Event fades, YUK
There is a perceptual problem with using linear fades when the end of the fade is reached. But there is no bug per se. Here’s what’s going on: On the meter side: ============= Let’s assume we’ve got a 60 second wave file that is all fade-out (the fade-out starts right at the beginning). Given a simple linear equation for the fade, the point where the fade reaches -60db is about 1/16th of a second before the end of the event. 1/16th of a second may be smaller than the meter update granularity on many machines. On the perceptual side: ================ The dBs per second of attenuation increases exponentially near the end – and since loudness is perceived in dB space, the signal sounds like it is cutting out very rapidly at the end. As a matter of personal preference, I much prefer Vegas’ smooth cubic fades (fourth from the top in the fade menu) or the log-curve (third from the top) when working with music At the file level: ============ You can actually see that the fade is working correctly if you try to fade a DC wav over a sufficiently long duration – then examine the end of the wave file.
SonyMLogan
Offline, Member since 2/2/2001