JKL preview audio level issue?

redpaw wrote on 7/30/2014, 7:50 AM

I cannot find any mention of it on the forum, so i'm wondering is it only me?

so, when you're using JKL for playback/pause and go from J (playing back) straight to L (playing forward with 1x speed) the audio level drops.

i recorded this sample:

audio level sticks between -6dB -> -3dB
after pressing J it plays back with 1x speed, the audio level drops to -15 -> -12,
that's fine, then pause, L for play and we're back at -6 / -3.
but if i go from J to L (so it plays forward with 1x speed) without pausing it first
the level stays at -15 / -12.
if i pause and press L again it jumps back to -6/-3

that cannot be right, right?

can anyone else reproduce it?
i'm pretty sure it was the same in vegas 12.

Comments

videoITguy wrote on 7/30/2014, 8:53 AM

Redpaw, please tell us VegasPro version and build number?

Also for the record you are using motherboard sound without any other audio hardware processing aboard your platform? Version and make of the audio driver set?

redpaw wrote on 7/30/2014, 9:01 AM

latest build, veg 13 b.373, happens to me in all v13 builds and from what i remember in all v12 too.

no difference if it was build-in audio card (asus p8z77-v motherboard - audio driver ver. 6.3.9600.16384) or separate Sound Blaster X-Fi Xtreme Audio).

so, am i right in assuming that it doesnt happen to you then?

NormanPCN wrote on 7/30/2014, 9:39 AM

I just tried this and it does not reproduce for me. VP13 b373

I did notice that when going from forward (L) to backward (J) playback the master bus VU meters were no longer updated. They just froze where they were. If I first paused (K), and then played backwards then the VU meters were updated.

redpaw wrote on 7/31/2014, 4:35 AM

thanks Norman, good to know that it's just me then (or at least not everyone)

btw. that happens on my system as well (freezing of meters when going from forward to backward)

Rory Cooper wrote on 7/31/2014, 6:12 AM

Normally when I am checking if the cuts are to the marker or pace and if it is working I will KL together, the audio is droney but the level won’t drop ..vs 10

john_dennis wrote on 7/31/2014, 6:20 AM

I tried it on two machines using version 12, one with on-board audio and one with a PCI card and the level didn't drop for me.

redpaw wrote on 8/4/2014, 5:37 AM

thanks guys, i will try to work it out then

set wrote on 8/4/2014, 7:14 AM

Just tried here too, no problem.

pwppch wrote on 8/4/2014, 8:49 AM

@redpaw

Do you have any audio fx in your mix when this happens?

When Vegas plays at a rate != 1.0 (forward or reverse). FX are bypassed. If any of these FX have a gain stage, they will be bypassed. This bypass is held until playback is stops and restarted at 1.0 (forward).

Simplest way to test for your project is to bypass all fx, or try a simple project with no FX.

Peter

redpaw wrote on 8/4/2014, 9:21 AM

i was actually doing it right now, Peter.
notice that it's the 'track compression' that causes it. (have it usually applied to the track, but when added only to the clip the same thing happens).

thanks Peter, it actually would make sense then, if the FX is bypassed until it is stopped (or paused), and it looks like that's the case...
however, i (personally) think the moment you're going back to playing it back to x1.0 it should turn the FX automatically back on.

(btw it looks the the FX are bypassed in -1.0x as well)

pwppch wrote on 8/4/2014, 7:00 PM

"(btw it looks the the FX are bypassed in -1.0x as well)"

Yep. Anything other than 1.0 will always cut out the plugins until stopped and restarted.

Why? The reverse is done at the last stage of the mix, we don't run the audio through the fx in reverse. So. What you would get would be really ugly, especially for look ahead or tail generating plugs.

When running at rates > 1, this can (could) task the system when this was implemented a very long time ago. Perhaps it is time to revisit,

How ever the intent of shuttle/scrub is more about locating than listening, so we chose to bypass. It is not a rendering option, but about previewing.

Bringing FX back on line when we hit back to 1.0 would be odd as well, especially with tails and such, and if your consider the pass through of 1.0, it could produce some odd sounding audio as well.

Peter

redpaw wrote on 8/5/2014, 3:48 AM

oh, yeah... i agree that for speeds other then 1.0x (forward) there's no need for it (including reverse, i was just stating the fact rather then complain),

i use JKL a lot, so every time i have to hit K between J and L to get back to the 'proper' audio adds up to a lot of time that could be saved, especially if accidentally i press KL at the same time making it play forward in slo-mo... then need to go back again etc...

anyhow, at least now i know what caused it, and that it's nothing wrong with my pc.

thanks for the help Peter, and everyone who checked it for me,
dom