|
|
|
|
|
|
| Re: Your biggest reason for leaving Paris? [message #88527 is a reply to message #88428] |
Wed, 25 July 2007 05:20   |
Bill L
 Messages: 766 Registered: August 2006
|
Senior Member |
|
|
get="_blank">jjdpro@ameritech.net> wrote:
>
>Now, this is what I'm talking about. Two way integration. Tradidtional I/O
>routing and VST plugin via Firwire ala SSL Duende.. Nice list $499.00
>
>http://www.lexiconpro.com/ProductDetails.aspx?productID=146No 88.2 or 96k? What were they thinking?
Graham
LaMont wrote:
> Now, this is what I'm talking about. Two way integration. Tradidtional I/O
> routing and VST plugin via Firwire ala SSL Duende.. Nice list $499.00
>
> http://www.lexiconpro.com/ProductDetails.aspx?productID=146....of keeping the price down...
David.
Graham Duncan wrote:
> No 88.2 or 96k? What were they thinking?
>
> Graham
>
> LaMont wrote:
>
>> Now, this is what I'm talking about. Two way integration. Tradidtional
>> I/O
>> routing and VST plugin via Firwire ala SSL Duende.. Nice list $499.00
>>
>> http://www.lexiconpro.com/ProductDetails.aspx?productID=146Agreed, LaMont, it would fill a niche, but still just a niche. But hey, I
hope you guys wind up with it if that's what you want.
TCB
"LaMont" <jjdpro@ameritech.net> wrote:
>
>That's a powerful combo Thad(LIVE & SX), but an updated Paris for Mix and
>Recording Engineers is very much welcomed.
>
>Not everyone wanted not need all of the goodies in SX. When it comes time
>to mix the $$ jobs, Paris & Pro Tools are no#1 in my book. Notice that I
>did not say editing.. That dubious spot belongs to SX/Nuendo hands down..
>
>So, if an updated Paris did not have a midi sequencer, vsti hosting ....But
>HAD: Total Delay coompensation, even more flexible patchbay routing, and
>proper Asio2 plugin handling..Wow!!
>
>
>
>"TCB" <nobody@ishere.com> wrote:
>>
>>I'm a capitalist, and I have a hard time a product that has been essentially
>>dormant for five years could possibly compete with products that have been
>>out there in the marketplace fighting with each other. I'm happy to look
>>at anything to see if it's a better mousetrap, but I can't imagine I'll
>prefer
>>it to my Live/SX combo rig that I'm running now.
>>
>>TCB
>>
>>"LaMont" <jjdpro@ameritech.net> wrote:
>>>
>>>That's harsh.. I'd welcome something new from ID. Paris was still in it's
>>>infacy when they pulled the plug.
>>>
>>>I remember Edmund showing me a "working" version of Paris "Native" on
Mac
>>>OS back in 2000 NAMM. I mean it was working really good.
>>>
>>>So, to have a native VST version of Paris that spealize in Tracking, routing,
>>>mixing would be great. Forget about the midi sequencer, vsti's..
>>>
>>>Well??? If he had all that
|
|
|
|
| Re: Your biggest reason for leaving Paris? [message #88539 is a reply to message #88527] |
Wed, 25 July 2007 08:45   |
LaMont
Messages: 828 Registered: October 2005
|
Senior Member |
|
|
---=_NextPart_000_0064_01C80167.9FD736C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I had a SCSI that did that.. worked w/442, but wouldn't with a MEC. I =
think you probably hit it right on the head.=20
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fb4262@linux...
AA,
I did find one scsi cable that had a couple dead pins out of five =
cables.
It allowed the 442 to work though. ? . Maybe those pins aren't used
in the Paris pin out? I chucked it anyway. Could be the source =
of
all evil.
Tom
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46fa1183@linux...
Aaron,
Thanks, I won't know about the modules until some new Mecs get =
delivered here.
I think I have the four I need almost on their way from multiple =
sources.
It looks like a chip in the master section of the scsi scorched mec =
got hit bad. We're
looking for the chip now. The other mecs may have less of a =
problem. Maybe some DC=20
down the WC line? Just a guess. Everything was AC grounded and no =
polarity shift.
We learned there's all kinds of protection fuses in line on the =
master section. It seems 'they' weren't
fried but the expensive stuff right after them was. . .
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f9cf56@linux...
I'll also toss out an edumacated guess that only the interface =
portion got fried and all your MEC cards are likely to be ok... holla =
back on that man.=20
Sorry, no spare MEC's around here, in fact I'm going to be growing =
my rig again shortly with a few more EDS cards :)
Say Tom, have you called The Soniq about repairing yours... he =
offers warranty on his work yano :)
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f9621b@linux...
Most absolutely hardware. 3 Mecs down for the count.
No word on the 10 modules that were onboard during
the mishap.
Anyone have a spare mec they can part with?
Assamundo
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f4fa9a@linux...
I'll double check Aaron.
Continuity is my middle name.
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:46f4e6c0@linux...
Dude, if you have 3 toasted MEC's I think it VERY likely you =
had a bad cable that put the hurt on them all as you swapped around =
parts.=20
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:46f472e2@linux...
Intersted people,
I know 3 fried mecs is unlikely. It's not confirmed until =
Tuesday=20
when I'll check the two that might 'still work'. The =
hardware solution
is seeming to be the most logic
|
|
|
|
| Re: Your biggest reason for leaving Paris? [message #88549 is a reply to message #88539] |
Wed, 25 July 2007 21:33  |
Neil
Messages: 1645 Registered: April 2006
|
Senior Member |
|
|
cable at the Master Mec sometime during that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>next week. There =
was smoke in=20
the power supply area so I never tried that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Mec again. My =
other mec=20
was attached at that time. I now think it fried=20
something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>in their =
too.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am trying DJs and my =
hopefully=20
unfried mec at another studio on Tuesday to =
confirm</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that neither works. =
If I'm=20
wrong then we're back to software.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It ain't over till it's=20
over.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial =
size=3D2> </FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Neil" <<A =
href=3D"mailto:IOU@OIU.com">IOU@OIU.com</A>>=20
wrote in message <A=20
=
href=3D"news:46f46d03$1@linux">news:46f46d03$1@linux</A>...</DIV><BR>In=20
all seriousness - THREE bad MEC's??? What's the=20
real<BR>likelihood of that? Unless all 3 PSU's got hit =
hard with=20
a<BR>voltage spike or something weird like that, is it=20
really<BR>possible that ALL of his MECs went=20
bad?<BR><BR>Neil<BR><BR><BR><BR>"DJ" <animix _ at _ =
animas _=20
dot _ net>=20
wrote:<BR>><BR>><BR>>Tom,<BR>> <BR>>Do you =
think=20
the one I sent was bad ? It was working fine when I=20
pulled<BR>=3D<BR>>it from the =
rack.=3D20<BR>><BR>>I've=20
noticed a few posts recently regarding errors. Maybe no =
more=20
than =3D<BR>>usual, but it seemed like an unusually =
high number=20
to me over the last =3D<BR>>few weeks. Errors I'm not =
familiar=20
with. It will have been 10 years in =3D<BR>>November =
since=20
Paris shipped. I wonder if the lifespan of this=20
hardware<BR>=3D<BR>>is starting to fade. TG for =
TheSoniq, I=20
guess.<BR>><BR>>Deej<BR>><BR>> "Tom =
Bruhl"=20
<<A=20
=
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>>=20
wrote in message =
=3D<BR>>news:46f44c75$1@linux...<BR>> =20
3 bad mecs.<BR>><BR>> =
Hmmm?<BR>><BR>> =20
I'll know for a fact next Tuesday when =
there's<BR>> =20
time to test a couple on another=20
|
|
|
|