| OT. New BBQ! [message #60320] |
Wed, 16 November 2005 15:27  |
Kim
Messages: 1246
Registered: October 2005
|
Senior Member |
|
|
in message
news:43a3524a$1@linux...
> Going off memory here, but I think you can go into MSCONFIG and reload
just
> those drivers through that panel from the Win98se CD. How escapes me at
the
> moment - lot's going on here - but I bet microsoft.com will have those
> answers in the Knowledge Base.
> http://support.microsoft.com
>
> AA
>
> "Jeff hoover" <jkhoover@excite.com> wrote in message
> news:43a32145$1@linux...
&
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: OT. New BBQ! [message #60750 is a reply to message #60364] |
Tue, 29 November 2005 22:38  |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
3D3D20
> > > message <A =3D3D
> > =3D
>
=
>>href=3D3D3D"news:43a5b0b4$1@linux">news:43a5b0b4$1@linux</A>...</DIV>Ar=
e=3D3D=3D
> >20
> > > you sure you have the two 'correct' EDS cards chosen for =
your =3D
> >system?
> > =3D3D
> > >I=3D3D20
> > > <BR>know that it gets sketchy pinning down which one, but on =
my =3D
> >system
> > =3D3D
> > >I have=3D3D20
> > > to <BR>use card A and C and skip putting a MEC on card B or =
wierd
> =3D
> >=3D3D
> > >stuff like=3D3D20
> > > this <BR>happens (another hidden Paris 'feature'). The other =
=3D
> >thing to
> > =3D3D
> > >check is=3D3D20
> > > that <BR>you have a good wordclock BNC cable running from =
MEC #1
> =3D
> >to =3D3D
> > >MEC=3D3D20
> > > #2.<BR><BR>AA<BR><BR><BR>"Deadmeat" <<A=3D3D20
> > > =3D3D
> > =3D
>
=
>>href=3D3D3D"mailto:scott@postmodernblues.com">scott@postmodernblues.com=
</A=3D
> >>&g=3D3D
> > >t;=3D3D20
> > > wrote in message <BR><A=3D3D20
> > > =3D3D
> > =3D
>
=
>>href=3D3D3D"news:43a59445$1@linux">news:43a59445$1@linux</A>...<BR>><BR=
>&g=3D
> >=3D3D
> > >t; Hi=3D3D20
> > > all -<BR>> Been messing with V3 for a bit and noticed a =
real=3D3D20
> > > problem.<BR>> Testing on a 3-card system, 2 MECs installed =
(on A
> =3D
> >=3D3D
> > >and=3D3D20
> > > B<BR>> cards), 2 ADAT and one Sync on MEC A, 1 8-input on =
=3D
> >MEC=3D3D20
> > > B.<BR>><BR>> Can record fine with MIX A, MEC A. Getting no =
sound
> =3D
> >=3D3D
> > >at=3D3D20
> > > all<BR>> on any inputs for MEC B, Mix B. Tried to load V2.2, =
=3D
> >and=3D3D20
> > > all<BR>> is fine - can record on MEC B inputs all day long. =
=3D
> >When=3D3D20
> > > using<BR>> V3, see input lights on module, but have no =
meters =3D
> >in=3D3D20
> > > mixer<BR>> and no sound - MEC B syncing to WC fine - plays =
=3D
> >sound=3D3D20
> > > accross<BR>> all submixes just fine from projects recorded =
=3D
> >on=3D3D20
> > > V2.<BR>><BR>> Any Thoughts? =
<BR><BR></BLOCKQUOTE></BODY></HTML>
> > >
> > >
> >
> >
> ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> ><HTML><HEAD>
> ><META http-equiv=3D3DContent-Type content=3D3D"text/html; =3D
> >charset=3D3Diso-8859-1">
> ><META content=3D3D"MSHTML 6.00.2800.1106" name=3D3DGENERATOR>
> ><STYLE></STYLE>
> ></HEAD>
> ><BODY bgColor=3D3D#ffffff>
> ><DIV><FONT face=3D3DArial size=3D3D2>That's a fact. With 3 x MECs, =
it's =3D
> >always the MEC=3D20
> >on card #2 that ends up locking to the external clock last. the =
most =3D
> >reliable=3D20
> >way to get my Frankenstein monster config working is to turn on my =
=3D
> >outboard=3D20
> >modules that are interfacing digitally with Parism then turn =
on=3D20
> >the external clock, then turn on the MECs, then boot the computer, =
=3D
> >then=3D20
> >boot Paris, let it sit for about 30 - 45 seconds until everything =
=3D
> >stabilizes,=3D20
> >then boot up my Cubase SX DAW. Any deviation from this will usually =
=3D
> >cause a=3D20
> >digital train wreck of the whole cotton pickin' thing.</FONT></DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> ><DIV><FONT face=3D3DArial size=3D3D2>;o)</FONT></DIV>
> ><DIV> </DIV>
> ><DIV> </DIV>
> ><DIV> </DIV>
> ><DIV>"Tom Bruhl" <<A=3D20
> >href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in =3D
> >message=3D20
> ><A href=3D3D"news:43a762d3@linux">news:43a762d3@linux</A>...</DIV>
> ><BLOCKQUOTE dir=3D3Dltr=3D20
> >style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
=3D
> >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> > <DIV><FONT face=3D3DArial size=3D3D2>Both versions of Paris =
forced this =3D
> >outer cards=3D20
> > for Mec attachement.</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>I almost traded it all in =
because it
> =3D
> >took me a=3D20
> > year to find the answer.</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>EMU didn't even know. I was =
=3D
> >pissed. =3D20
> > But now I'm happy.</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>You should be =
too.</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>Moving the Mec around isn't =
that big
> =3D
> >of a deal=3D20
> > really. I don't think it</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>will screw anything major =
up. =3D
> >No ADAT cards=3D20
> > in there right?</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2>Tom</FONT></DIV>
> > <DIV><FONT face=3D3DArial size=3D3D2></FONT> </DIV>
> > <BLOCKQUOTE=3D20
> > style=3D3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: =
5px; =3D
> >BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> > <DIV>"Deadmeat" <<A=3D20
> > =3D
>
=
>href=3D3D"mailto:scott@postmodernblues.com">scott@postmodernblues.com</A=
>&g=3D
> >t;=3D20
> > wrote in message <A=3D20
> > =3D
>
=
>href=3D3D"news:43a6d87f$1@linux">news:43a6d87f$1@linux</A>...</DIV><BR>W=
ell=3D
> >,=3D20
> > like I said, the system works as is (MECs on A and B)<BR>with =
the =3D
> >older 2.2=3D20
> > software, and has been running like that<BR>for a couple of =
years -
> =3D
> >all=3D20
> > inputs and outputs producing<BR>sound without problems. So, I =
know =3D
> >my clock=3D20
> > is good, the<BR>cards are good, the MECs and interfaces are =
good.
I=3D20
> > just<BR>brought up V2.2 to double check, and recorded =
using=3D20
> > the<BR>interfaces that don't work with 3.0, so it's =
definatley<BR>a
> =3D
> >3.0=3D20
> > issue.<BR><BR>When you had to have your MECs on A and C (or E),
was=3D20
> > that<BR>with Version 2.2 and 3.0, or just with 3.0? I could =
try=3D20
> > moving<BR>the MEC to C and see if that fixes it, but I dread
making=3D20
> > any<BR>changes at all to a functional (under 2.2) PARIS=3D20
> > system......<BR><BR><BR>"Tom Bruhl" <<A=3D20
> > =
href=3D3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>>=3D20
> > wrote:<BR>><BR>><BR>>Dead,<BR>>What Aaron says is =3D
> >true. =3D20
> > When my system was three cards with two Mecs<BR>>I had card A =
and =3D
> >C=3D20
> > attached to the Mecs. Now with five cards it's A =3D
> >and<BR>=3D3D<BR>>E.=3D20
> > =3D3D20<BR>>My ASUS boards like the first and last card when =
using =3D
> >two=3D20
> > Mecs.<BR>>Tom<BR>> "Aaron Allen" <<A=3D20
> > =
href=3D3D"mailto:nospam@not_here.dude">nospam@not_here.dude</A>> =3D
> >wrote in=3D20
> > message =3D3D<BR>>news:43a5b0b4$1@linux...<BR>> Are you =3D
> >sure you=3D20
> > have the two 'correct' EDS cards chosen for your =
=3D3D<BR>>system?=3D20
> > I=3D3D20<BR>> know that it gets sketchy pinning down which =3D
> >one, but on=3D20
> > my system I =3D3D<BR>>have to=3D3D20<BR>> use card A and C =3D
> >and skip=3D20
> > putting a MEC on card B or wierd stuff=3D20
> > like<BR>=3D3D<BR>>this=3D3D20<BR>> happens (another hidden =3D
> >Paris=3D20
> > 'feature'). The other thing to check =3D
> >is<BR>=3D3D<BR>>that=3D3D20<BR>> =3D20
> > you have a good wordclock BNC cable running from MEC #1 to =
MEC=3D20
> > #2.<BR>><BR>> AA<BR>><BR>><BR>> =3D
> >"Deadmeat" <<A=3D20
> > =3D
>
=
>href=3D3D"mailto:scott@postmodernblues.com">scott@postmodernblues.com</A=
>&g=3D
> >t;=3D20
> > wrote in message=3D3D20<BR>> <A=3D20
> > =3D
> >href=3D3D"news:43a59445$1@linux">news:43a59445$1@linux</A>...<BR>> =
=3D
> >=3D20
> > ><BR>> > Hi all -<BR>> > Been messing =3D
> >with V3 for=3D20
> > a bit and noticed a real problem.<BR>> > Testing on a =3D
> >3-card=3D20
> > system, 2 MECs installed (on A and B<BR>> > cards), 2 =3D
> >ADAT and=3D20
>
|
|
|
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
