Comments

SonyIMC wrote on 3/4/2003, 3:31 PM
Can you descrive what is not working with your installation of acoustic mirror?
Also your machine and sound card specs and the driver model that you are using for playback.

Thanks
Ivan
PeterVred wrote on 3/4/2003, 6:49 PM
AMD1800+ 512mbRam-7200rmp drives, Echo Layla card. never had any probs with VV2.0f

i read in the manual, that my new 4.0 has problems with accustic mirror and i am surely having them. I get grunge sounds at regular intervals when using chicago theatre on snare and hats. so i am surprised that SonicIMC is wanting to help, didn't think there was a fix.
PeterVred wrote on 3/4/2003, 7:05 PM
i forgot a very important thing...i am running in ASIO.
i know that when running windows driver, Acc.Mirror works.
but i thought ASIO was really important to i am trying to use it.

however i also note that i cannot use input monitoring when using ASIO either.
the sound is all crappy sounding. and i think maybe monitoring/latency is the reason for ASIO in the first place.

am i trying to solve too many things at once?
pwppch wrote on 3/4/2003, 10:35 PM
Acoustic Mirror is very tough on low latency i/o. In fact you will NOT beable to do real-time input monitoring through any track (or bus that a track is routed too) that has an AM plugin installed.

Why: AM is what is known as "non-inplace". In AM's specific case, it MUST recieve n seconds of audio BEFORE it can produce any output. "n" is how long the impulse file is that you are using.

Also, if you are using AM, don't use it on tracks. Set up an assignable FX send or a sub bus with a AM as an insert. Use the send to on your track(s) to process through AM then. You will not only save CPU, but limit the latency effect caused by the non-inplace nature of AM.

Again, and I can't stress this enough, don't use AM ANYWHERE when input monitoring - or at least nowhere near the signal path that your input monitoring track(s) follow. This means keeping it off the master bus and any sends/FX that a track is routing through. It wont work.

Peter





gjn wrote on 3/6/2003, 7:02 AM
very big problem ,vegas 4; acid4 and acoustic mirror ...!!!
no problem with soundforge....why?????
CDM wrote on 3/6/2003, 9:54 AM
thanks Peter
gjn wrote on 3/6/2003, 12:16 PM
my acoustic is versiuon 1.1a build 198.info in soundforge6.

problem with long reverb....clic stop...bug..!!!
no problem with soundforge.
my pc is great
2,2 giga p4
2 giga rambus

dd 120 giga..;
graphic cart 4200 128 meg...!!!
WXP PRO;
sound cart creamware asio2;
pwppch wrote on 3/6/2003, 4:35 PM
Sound Forge is not real-time. Sound Forge used VERY large buffers for audio playback.

Peter
pwppch wrote on 3/6/2003, 4:38 PM
You cannot compare Sound Forge with Vegas or ACID. They are VERY different audio engines. AM was designed for use in Sound Forge. AM is NOT intended to be used as a real-time plugin. It is far to 'hungry' to be used this way. We let it be used because there are cases where it will work if latencies are not an issue.

Peter
PeterVred wrote on 3/17/2003, 3:52 PM
thanx for all your replies. i get it now.
i have tried AM via an efx bus and it DID work.
previously i couldn't get efx busses to work with much of anything,
but now all is better.
:)
Pete