Bug with Audio Resample Quality Setting?

Shredder wrote on 8/8/2002, 9:37 AM

Hi,

Is anyone else seeing the following issue:

In the New Project window, go to the Audio Tab and changle 'Resample quality' to 'Best', check 'Start all new projects with these settings' and then click OK.

Now, Start & new project and go back to the Audio Tab -- The Resample quality has gone back to 'Preview'. No matter what I do, I can't seem to get this setting to stick.

I can get the 'Full resolution rendering quality' to stick in the video tab, so theoretically the resample quality setting should work the same way.

Can someone please verify this?

Thanks,

Jon

Comments

salad wrote on 8/8/2002, 10:04 AM

I get the same behavior here.

Pat

owlsroost wrote on 8/10/2002, 4:09 AM

Me too (it's been the same in all versions of VV3 I've used)

Tony

salad wrote on 8/10/2002, 8:50 AM

OK, something just changed. Now it's working. I'm not sure if it's that important anyway, but this is wierd.
Open a blank Vegas and change everything in the audio properties, click "start all new projects....", and close Vegas, save the "blank" project somewhere, open VV again and check audio properties. Did it save the settings? It's working here, but it wasn't the other day.

Pat

Shredder wrote on 8/10/2002, 9:03 AM

Pat,

I tried what you did, and it worked as you described, but the reason it worked it because when you restarted VV3, it re-loaded your blank project. SO you you re-checked the audio properties, you saw the sample setting of that project (which does stick, or it would be a huge bug).

However, if you then create a New Project, and check the audio tab, it's back to preview.

Thanks anyway,

Jon

salad wrote on 8/10/2002, 9:20 AM

You're right, but check this......Open a NEW project, but this time right click on the audio mixer area and select audio properties.
Play around with that option of selecting audio prop's, and let me know.
It is behaving differently than from the File/Properties menu. I'm still getting BEST when I select from there, and Preview when using File/Prop's.

Pat

Shredder wrote on 8/10/2002, 1:19 PM

I see what you're saying, it's really wierd. If you create a new project, switch to the audio tab and leave the audio resample setting to preview, and then, after the project is created, go to audio properties either thru the mixer or file...properties, you can see that the project is using the setting you previously set to 'start all new projects with these settings'. Even if you change the qulaity on creation, the properties will show whatever the default is.

That's even worse, 'cuz you thing you created a project on preview or best etc., but it used whatever the hidden defualt is from 'start all prpjects...'

Now this bug is even screwier...

Try this... Create a new project - don't change the audio settings.
Then, Create a new project again, change the Audio Resample setting from Preview to Best. Then check out audio properties in the mixer. It's still preview.

However, if you modify the project, by dropping an event on the timeline or altering the properties, then when you create a new project the setting stick for that project.

You need to get the pop-up 'Do you want to save changes to Untitled?' for the Audio Resample setting to stick for a new project.

SoFo support really needs to look into this. Who knows how many people's projects are being screwed up, them thinking it's on the best setting when it's on preview...

Any comments SonicEPM or SonicDennis?

- Jon

salad wrote on 8/10/2002, 5:39 PM

If I open a single (fresh) instance of VV, and do nothing to it, and hit Alt+Enter(project prop's), I get: 48KHz/16/BEST.
Click Cancel, and hit Ctrl+N(new project), I get: 48KHz/16/PREVIEW.
Click Cancel, and drag in some DV footage, and do the Alt+Enter thing, I get: 48KHz/16/BEST.
So, it seems like it's holding the settings that were selected for "start all new projects.....". It just insists on showing PREVIEW in the "New Project" properties window. Other than that window, everything seems OK (for now). I'll change settings once in awhile to test it.

Keep playing with that. It doesn't seem like it's going to be a problem, just a source of confusion.
Is it behaving differently than this for you?

pat

SonyDennis wrote on 8/10/2002, 8:27 PM

> Any comments SonicEPM or SonicDennis?

I haven't played around with it, but it sounds like there's a bug there. We'll be sure to address it in a future version.

///d@