It seems to have gone away thank God

I hate it when that happens. You can never be sure that one day god might just get pissed off with you again, and it'll come back !

geoff

>oddboy
> It seems to have gone away thank God


I hate it when that happens. You can never be sure that one day your god might just get pissed off with you again, and it'll come back !

geoff

Yes that must be the case now! I have sunken to voodoo computing. I am recording digitally in lightpipe from a yamaha 01v. the o1v is the master and the echo is slave
(that how you do it with echo) Im locked at 44k aqnd am running 2 or 3 track sessions. Sometimes even 1 track of naration along to video.

Its WeaK!!!!!! I can bring in a video clip that has audio and the audio will pop and click, but when I "launch external" and preview in SoundForge there are no clicks in the soundfile!!!

With this kind of performancew I never know if clicks a being recorded or are playback artifacts!!! Its causeing a 50% slow down in production time!!!

no clicks in any other apps on this system!


Heres what tech support said "well....it shouldnt do that..."

wow, that kind of support makes my day

Amazing!!! As soon as I post my complaints, the poping stopped! Is this some kind of twilight zone thing or am I going mad??????????

Perhaps take a good look at your tosslink cords. I"ve come across a bad one that caused me nightmares. Your playing back through the board?

Yes I am monitoring through the board. youre talking about the optical cords right?
I have considered that but 1. the optical cables I have are new. 2. they are $%^$#^$# expensive!!

But i can see getting new ones jsut to make sure...might save me a lot of grief.

I was thinking about getting Monster but was not sure there would be a big difference with glass....

>Posted by: oddboy (Ignore This User)
>Date: 12/2/2002 12:41:43 AM

>Amazing!!! As soon as I post my complaints, the poping stopped! Is this some kind >of twilight zone thing or am I going mad??????????

You know how when you start up, Vegas dials up Sonic Foundry. Well, it's really not *just* to notify for new versions. They are actually secretly dicking with your computer to fix faults. If it gets really bad, they re-format your drive for you, and reinstall Vegas.

Geoff
(jesting)

I find that on my SPDIF opticable if you are less than diligent about pulling it out straight, the plastic coating on the male bit of fibre cracks and can even come right off, which probably doesn't help.

geoff

Geoff

Whats up with all the propaganda about secret start up operations? Are you serious ?

Absolutely! But a double layer of aluminum foil tightly formed to your head will prevent all but the most diligent of intruders from gaining access.

I believe its probably a system issue

It sounds like you have it setup correctly when recording into your PC with Vegas...Set the 01V to "internal clock" and the Layla to "spdif". Now when you're playing back you should do the reverse, of setting the Layla to "internal" or is it "sync" now?...anyhow.. and then the 01V to "external 44.1Khz". A general rule of digital setup for your clock...if you don't have a master word clock setup.....is to make wherever the audio is being generated from the master clock, and then everything else to daisy chain off of that as "external" clock.

You probably are already doing this, unless the 01V is getting it's word clock from some other device, because usually a Yamaha mixer will give you a word clock error and not output any audio....or as I mentioned it might be getting it's word clock from some other device, and they aren't matching with the word clock from your Layla, thus causing clicks.

I would think that you'd be better setting the Layla as the clock source and tell the O1V to slave to it. You shouldn't have to keep changing clock prefs, and the clock in the Layla is most likely better than that in the O1V.

Mike K

Echo says when you record digitally the sorce must be the master...i know, its strange.

But I have been testing and Im gettting playback clicks galore EITHER way in vegas.

Like I said, I can bring in a file and its snap crakle pop! If I choose "open in audio editor" (SF) there are no pops.

That's correct, and exactly how digital word clock works if you understand it. "The source must be the master", so it should be changed if you're playing back or recording. Unless as I stated you have a master word clock generator, and all your devices have a word clock input.

I still dont understand why audio is poping and clicking in Vegas but that same audio does not pop or click in SF....even while both are open, and launching the audio from vegas.

What version of the Echo drivers are you using?
Win9x or Win2000/XP.

You might try switching to the latest drivers from Echo that have their Pure Wave drivers. Set the Purewave buffering to around 128-512 samples. You can then set Vegas' buffering to around 100 ms. This has cured a number of playback issues and should help performance in general.


Peter

What version of the Echo drivers are you using?

6.05


Win9x or Win2000/XP.

XP

Set the Purewave buffering to around 128-512 samples.



Are you talking about in the echo control panel?

That's weird- echo told me to raise it....So you are saying lower it in the echo control panel?

You can then set Vegas' buffering to around 100 ms.


Are you talking about playback buffering? that is measured in Seconds....please calirify


Or recording .....If the recording buffer, is 1.00 100 ms?

Thanks

>>Set the Purewave buffering to around 128-512 samples.

>Are you talking about in the echo control panel?

That's weird- echo told me to raise it....So you are saying lower it in the echo control panel?
<
Yes, in the Echo control panel. Lowering it actually makes things work better. Too high a setting causes the hardware to slam against the buffer sizes that Vegas uses.

>>You can then set Vegas' buffering to around 100 ms.

>Are you talking about playback buffering? that is measured in Seconds....please calirify

Or recording .....If the recording buffer, is 1.00 100 ms?
<
Yes. Set Vegas' buffering to around 100 ms (0.10 seconds in the audio prefs page.) The default is 350 ms (0.35 seconds) You may have to play with this to find the best settings. 100 ms works pretty well with my Layla and Mia on XP.

Hi Peter,

I set the echo to 128 or 256 or 512

and Vegas to 0.100 playback

and recording to "automatically"

No real improvment. Sporadic behavior. at fisrst I thought it had helped but I still ended up having to run "pop redos" on the audio of every movie I rendered tonight.

Bounce out>audition for pops>go back re-record problem bites>re render> audition for pops>go back re-record problems bites>rerender>...........................................................................................

Just a question, what's your computer system? It might just be a windows problem too or you have another soundcard inside that vegas gets its clocking without you knowing it.