Home » The PARIS Forums » PARIS: Main » Heavenly Virgins!
| Heavenly Virgins! [message #97041] |
Tue, 18 March 2008 13:41  |
excelav
Messages: 2130
Registered: July 2005
Location: Metro Detroit
|
Senior Member |
|
|
is 3.0 on an older Athlon XP/WinXP system -w- 1GB RAM.
> I
>>was going to re-purpose the PC for something else but would take offers
> for
>>it too.
>>
>>-Brian
>>
>>
>>
>>Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>Hi all. I was going to save this post for a bit longer until I had more
>>info
>>>to share, but it seems particularly timely today.
>>>
>>>Sorry this is a bit long - the summary is at the end. But as I'm putting
>>out
>>>an appeal here, you should have full access to my "source code" :D
>>>
>>>As my previous posts have implied, I've been busy contacting people in
>>>various places about the possibilities of pushing PARIS forward. I've
>>>talked
>>>to many companies/developers. Some names might surprise you. There are
> very
>>>interesting avenues to pursue, and obstacles to overcome to get there.
>>>
>>>Development involving the PARIS app itself (eg EDS plugins or the
>>>FaderWorks
>>>PDC advances) looks to be in excellent hands courtesy of Mike Audet and
>>>Dimitrios and others. I'm focusing my own efforts elsewhere - I'm
>>>investigating what alternatives might exist for the PARIS hardware
>>>independent of the PARIS app. This involves investigating things like
>>>what
>>>driver options could be pursued; what alternative "front end" apps might
>>>feasibly be adapted to access the PARIS hardware; and how we might obtain
>>>the ability to import/migrate ppjs/pafs into another app to "future
>>>proof"
>>>our access to our "back catalogs".
>>>
>>>I can only promise I'm working hard in the background and have devoted
> many
>>>hours already to the effort. I can't make promises on behalf of others,
>>but
>>>I see the bulk of items on my list as more "to do" items than a "wish
>>>list",
>>>and if two minor goals I'm working towards happen then I'd rate at least
>>one
>>>of the developments (safeguarding our ppj/pafs) as both "fairly likely"
>>and
>>>"within a reasonably short timeframe".
>>>
>>>BTW, I have already rejected some promising solutions that involved
>>>asking
>>>the community for significant sums of money for development specific only
>>to
>>>PARIS. I've talked to genuinely interested developers, folks with great
>>>track records and real good will who have offered me every break in the
>>>book, but I don't propose taking the community down that road. I'm
>>>instead
>>>seeking developers who will help for their own reasons. Like this one:
> Mike
>>>Audet and I have independently estimated the PARIS userbase as some 400
>>>users worldwide (I have recorded over 40 within the last few months
>>>amongst
>>>the subset of PARIS users that post to the NG). Capturing a market of
>>>that
>>>size is not insignificant for a smaller developer looking to build their
>>>clientele - it can be worth them throwing some effort into investigating
>>>making those people happy (particularly if the developer has existing
>>>code
>>>that might merely need tweaking). And there are aspects of the PARIS
>>>community that might make it more interesting to certain developers than
>>raw
>>>numbers might dictate.
>>>
>>>>>>>
>>>
>>>Here's the immediate obstacle I want to ask the community about.
>>>
>>>Even the most interested developers can't do much for us if they don't
> have
>>>a PARIS rig - and in 2008 PARIS rigs aren't easy to run out and buy.
>>>Given
>>>our small size as a market, if we as a community are asking a developer
>>to
>>>do things for us, then telling them "go out and source and purchase a
>>>PARIS
>>>rig so you can help us out" isn't gonna fly. Neither is promising a
>>>developer you'll get them access to a rig to test on without being sure
>>you
>>>can deliver. If the community wants developers to work on PARIS, and
>>>those
>>>developers have to have a PARIS rig available in order to help us - then
>>>IMHO it's *in the community's best interest to provide one to them*.
>>>
>>>>>>>
>>>
>>>So this is a "feeler" post. IMHO the community needs a pre-assembled,
>>>"turnkey" (ie pre-installed on a computer) PARIS development rig, ready
>>to
>>>be shipped to developers that could do it the most good (if you've
>>>guessed
>>>that I have destinations in mind to offer this to already - well, you're
>>a
>>>good guesser :D).
>>>
>>>Ideally this rig would be a multi-card, multi-MEC system containing at
> least
>>>one of every existing PARIS component we can get our hands on so PARIS
> can
>>>be thoroughly tested in larger configurations. No more of this "sorry,
> we
>>>didn't have a full system to test" thing. But as a start we'll settle for
>>>whatever we can lay our hands on.
>>>
>>>In addition we'd need a PARIS community member who lives in the 48
>>>contiguous states (to keep shipping costs and delays low) to volunteer
> to
>>be
>>>the occasional "depot/shipping person". They'd be the person that
>>>received
>>>the donated components, tested them, assembled them into a rig, and sent
>>it
>>>to where it needed to go, and if needed (although if it finds a long-term
>>>home fast, that's good news for us) receive it back and ship it
>>>elsewhere.
>>>
>>>BTW, I'd do it myself in a heartbeat, but I'm in Canada - don't even ask
>>>what international shipping would add to the hassle and the cost and the
>>>delays. I've already had the first potential volunteer interest, and he's
>>a
>>>name you've all known a long time, but we're clear that there are some
>>>commitments I need to obtain from others before we can ask him for his.
>>>
>>>Incidentally, obviously I'm not proposing we stick that volunteer,
>>>whoever
>>>it winds up being, with picking up shipping/packing charges. I'd propose
>>>setting up something like a PayPal account for them in order to let the
>>>community chip in a few bucks apiece to cover any reasonable
>>>packing/shipping costs. I'd nag, too - these are trivial "beer money"
>>>costs
>>>for a community to absorb, rather than a lump for an individual.
>>>
>>>>>>>
>>>
>>>As mentioned, this is not an actual call for components yet - it's just
>>an
>>>"assessment" call to determine if folks would give concrete support to
> this
>>>idea. I'd put everyone fully in the picture on *where* I was proposing
> it
>>to
>>>go (and of course *why*) when I made the actual call for components.
>>>
>>>PARIS hardware prices have plummeted so far that the gear's hardly worth
>>>selling now - ($25 for a C16? Feh, the faders in it are probably worth
> more
>>>than that as salvage!), and there's the possibility of very exciting
>>>developments if everything worked out well.
>>>
>>>So if you're contemplating blowing PARIS gear out at absurd "it's
>>>gathering
>>>dust, make me an offer, just get it out of here" fire-sale prices anyway
>>- a
>>>component or two, or an old but functional PARIS-equipped PC, or even a
>>full
>>>rig - would you consider donating components to such a "development rig"
>>>effort instead?
>>>
>>>In addition, would there be any interest in making a small donation to
> a
>>>community fund to purchase any components we're missing after we see what
>>>the donation call brings in? 27 MECs won't help us if we only have a
>>>single
>>>EDS card.
>>>
>>>I've got no promises to give in exchange at this moment, except my own,
>>that
>>>I'm working on things. But this is what's needed to get 'em done. Let me
>>>know what you think.
>>>
>>>- Kerry Galloway
>>>
>>
>This is a multi-part message in MIME format.
------=_NextPart_000_0027_01C8BF26.6AE7AE90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Kerry,
I'm not loaded with extra hardware and I'm not totally into pushing
44.1 converters into the future either but I'd still make a donation to =
help
the overall cause.
Count me in. =20
Tom
"Edna" <edna@texomaonline.com> wrote in message news:483ad981@linux...
+1
"Gantt Kushner" <ganttmann@comcast.net> wrote in message=20
news:483aa591$1@linux...
>
> I don't know what Brian's looking to get for his system, but if =
enough of
> us were to contribute $10 or $15 to the cause we could probably =
make it
> happen. Could we set up a PayPal account to gather Paris =
development=20
> funds?
>
> Gantt
>
> "Brian Milton" <bcmilton@austin.rr.com> wrote:
>>
>>I'm not really in the right financial shape to donate a rig (Out of=20
>>work/Starting
>>a new business), but I am looking to part with my rig. If any Paris =
>>die-hards
>>want to buy my rig at a reasonable price and donate it for =
development let
>>me know. I was about to post it to the FS group. I'm looking =
through the
>>old posts now to figure out what it's worth.
>>
>>Here's what I've got in Austin,TX:
>>All of these are in Black
>>
>>MEC
>>442
>>(2) EDS
>>8in card
>>8out card
>>ADAT card
>>(2) C16
>>
>>It's running Paris 3.0 on an older Athlon XP/WinXP system -w- 1GB =
RAM.
> I
>>was going to re-purpose the PC for something else but would take =
offers
> for
>>it too.
>>
>>-Brian
>>
>>
>>
>>Kerry Galloway <kg@kerrygalloway.com> wrote:
>>>Hi all. I was going to save this post for a bit longer until I had =
more
>>info
>>>to share, but it seems particularly timely today.
>>>
>>>Sorry this is a bit long - the summary is at the end. But as I'm =
putting
>>out
>>>an appeal here, you should have full access to my "source code" :D
>>>
>>>As my previous posts have implied, I've been busy contacting people =
in
>>>various places about the possibilities of pushing PARIS forward. =
I've=20
>>>talked
>>>to many companies/developers. Some names might surprise you. There =
are
> very
>>>interesting avenues to pursue, and obstacles to overcome to get =
there.
>>>
>>>Development involving the PARIS app itself (eg EDS plugins or the=20
>>>FaderWorks
>>>PDC advances) looks to be in excellent hands courtesy of Mike Audet =
and
>>>Dimitrios and others. I'm focusing my own efforts elsewhere - I'm
>>>investigating what alternatives might exist for the PARIS hardware
>>>independent of the PARIS app. This involves investigating things =
like=20
>>>what
>>>driver options could be pursued; what alternative "front end" apps =
might
>>>feasibly be adapted to access the PARIS hardware; and how we might =
obtain
>>>the ability to import/migrate ppjs/pafs into another app to "future =
>>>proof"
>>>our access to our "back catalogs".
>>>
>>>I can only promise I'm working hard in the background and have =
devoted
> many
>>>hours already to the effort. I can't make promises on behalf of =
others,
>>but
>>>I see the bulk of items on my list as more "to do" items than a =
"wish=20
>>>list",
>>>and if two minor goals I'm working towards happen then I'd rate at =
least
>>one
>>>of the developments (safeguarding our ppj/pafs) as both "fairly =
likely"
>>and
>>>"within a reasonably short timeframe".
>>>
>>>BTW, I have already rejected some promising solutions that involved =
>>>asking
>>>the community for significant sums of money for development =
specific only
>>to
>>>PARIS. I've talked to genuinely interested developers, folks with =
great
>>>track records and real good will who have offered me every break in =
the
>>>book, but I don't propose taking the community down that road. I'm=20
>>>instead
>>>seeking developers who will help for their own reasons. Like this =
one:
> Mike
>>>Audet and I have independently estimated the PARIS userbase as some =
400
>>>users worldwide (I have recorded over 40 within the last few months =
>>>amongst
>>>the subset of PARIS users that post to the NG). Capturing a market =
of=20
>>>that
>>>size is not insignificant for a smaller developer looking to build =
their
>>>clientele - it can be worth them throwing some effort into =
investigating
>>>making those people happy (particularly if the developer has =
existing=20
>>>code
>>>that might merely need tweaking). And there are aspects of the =
PARIS
>>>community that might make it more interesting to certain developers =
than
>>raw
>>>numbers might dictate.
>>>
>>>>>>>
>>>
>>>Here's the immediate obstacle I want to ask the community about.
>>>
>>>Even the most interested developers can't do much for us if they =
don't
> have
>>>a PARIS rig - and in 2008 PARIS rigs aren't easy to run out and =
buy.=20
>>>Given
>>>our small size as a market, if we as a community are asking a =
developer
>>to
>>>do things for us, then telling them "go out and source and purchase =
a=20
>>>PARIS
>>>rig so you can help us out" isn't gonna fly. Neither is promising a
>>>developer you'll get them access to a rig to test on without being =
sure
>>you
>>>can deliver. If the community wants developers to work on PARIS, =
and=20
>>>those
>>>developers have to have a PARIS rig available in order to help us - =
then
>>>IMHO it's *in the community's best interest to provide one to =
them*.
>>>
>>>>>>>
>>>
>>>So this is a "feeler" post. IMHO the community needs a =
pre-assembled,
>>>"turnkey" (ie pre-installed on a computer) PARIS development rig, =
ready
>>to
>>>be shipped to developers that could do it the most good (if you've=20
>>>guessed
>>>that I have destinations in mind to offer this to already - well, =
you're
>>a
>>>good guesser :D).
>>>
>>>Ideally this rig would be a multi-card, multi-MEC system containing =
at
> least
>>>one of every existing PARIS component we can get our hands on so =
PARIS
> can
>>>be thoroughly tested in larger configurations. No more of this =
"sorry,
> we
>>>didn't have a full system to test" thing. But as a start we'll =
settle for
>>>whatever we can lay our hands on.
>>>
>>>In addition we'd need a PARIS community member who lives in the 48
>>>contiguous states (to keep shipping costs and delays low) to =
volunteer
> to
>>be
>>>the occasional "depot/shipping person". They'd be the person that=20
>>>received
>>>the donated components, tested them, assembled them into a rig, and =
sent
>>it
>>>to where it needed to go, and if needed (although if it finds a =
long-term
>>>home fast, that's good news for us) receive it back and ship it=20
>>>elsewhere.
>>>
>>>BTW, I'd do it myself in a heartbeat, but I'm in Canada - don't =
even ask
>>>what international shipping would add to the hassle and the cost =
and the
>>>delays. I've already had the first potential volunteer interest, =
and he's
>>a
>>>name you've all known a long time, but we're clear that there are =
some
>>>commitments I need to obtain from others before we can ask him for =
his.
>>>
>>>Incidentally, obviously I'm not proposing we stick that volunteer,=20
>>>whoever
>>>it winds up being, with picking up shipping/packing charges. I'd =
propose
>>>setting up something like a PayPal account for them in order to let =
the
>>>community chip in a few bucks apiece to cover any reasonable
>>>packing/shipping costs. I'd nag, too - these are trivial "beer =
money"=20
>>>costs
>>>for a community to absorb, rather than a lump for an individual.
>>>
>>>>>>>
>>>
>>>As mentioned, this is not an actual call for components yet - it's =
just
>>an
>>>"assessment" call to determine if folks would give concrete support =
to
> this
>>>idea. I'd put everyone fully in the picture on *where* I was =
proposing
> it
>>to
>>>go (and of course *why*) when I made the actual call for =
components.
>>>
>>>PARIS hardware prices have plummeted so far that the gear's hardly =
worth
>>>selling now - ($25 for a C16? Feh, the faders in it are probably =
worth
> more
>>>than that as salvage!), and there's the possibility of very =
exciting
>>>developments if everything worked out well.
>>>
>>>So if you're contemplating blowing PARIS gear out at absurd "it's=20
>>>gathering
>>>dust, make me an offer, just get it out of here" fire-sale prices =
anyway
>>- a
>>>component or two, or an old but functional PARIS-equipped PC, or =
even a
>>full
>>>rig - would you consider donating components to such a "development =
rig"
>>>effort instead?
>>>
>>>In addition, would there be any interest in making a small donation =
to
> a
>>>community fund to purchase any components we're missing after we =
see what
>>>the donation call brings in? 27 MECs won't help us if we only have =
a=20
>>>single
>>>EDS card.
>>>
>>>I've got no promises to give in exchange at this moment, except my =
own,
>>that
>>>I'm working on things. But this is what's needed to get 'em done. =
Let me
>>>know what you think.
>>>
>>>- Kerry Galloway
>>>
>>
>=20
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0027_01C8BF26.6AE7AE90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Kerry,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I'm not loaded with extra hardware =
and I'm not=20
totally into pushing</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>44.1 converters into the future either =
but I'd=20
still make a donation to help</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the overall cause.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Count me in. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Edna" <<A=20
href=3D"mailto:edna@texomaonline.com">edna@texomaonline.com</A>> =
wrote in=20
message <A=20
=
href=3D"news:483ad981@linux">news:483ad981@linux</A>...</DIV>+1<BR>"Gantt=
=20
Kushner" <<A=20
href=3D"mailto:ganttmann@comcast.net">ganttmann@comcast.net</A>> =
wrote in=20
message <BR><A=20
=
href=3D"news:483aa591$1@linux">news:483aa591$1@linux</A>...<BR>><BR>&g=
t; I=20
don't know what Brian's looking to get for his system, but if enough=20
of<BR>> us were to contribute $10 or $15 to the cause we could=20
probably make it<BR>> happen. Could we set up a PayPal =
account=20
to gather Paris development <BR>> funds?<BR>><BR>>=20
Gantt<BR>><BR>> "Brian Milton" <<A=20
href=3D"mailto:bcmilton@austin.rr.com">bcmilton@austin.rr.com</A>>=20
wrote:<BR>>><BR>>>I'm not really in the right financial =
shape to=20
donate a rig (Out of <BR>>>work/Starting<BR>>>a new =
business), but=20
I am looking to part with my rig. If any Paris=20
<BR>>>die-hards<BR>>>want to buy my rig at a reasonable =
price and=20
donate it for development let<BR>>>me know. I was about to =
post it=20
to the FS group. I'm looking through the<BR>>>old posts =
now to=20
figure out what it's worth.<BR>>><BR>>>Here's what I've =
got in=20
Austin,TX:<BR>>>All of these are in=20
Black<BR>>><BR>>>MEC<BR>>>442 <BR>>>(2)=20
EDS<BR>>>8in card<BR>>>8out card<BR>>>ADAT=20
card<BR>>>(2) C16<BR>>><BR>>>It's running Paris 3.0 =
on an=20
older Athlon XP/WinXP system -w- 1GB RAM.<BR>> I<BR>>>was =
going to=20
re-purpose the PC for something else but would take offers<BR>>=20
for<BR>>>it=20
=
too.<BR>>><BR>>>-Brian<BR>>> <BR>>><BR>>><BR=
>>>Kerry=20
Galloway <<A=20
href=3D"mailto:kg@kerrygalloway.com">kg@kerrygalloway.com</A>>=20
wrote:<BR>>>>Hi all. I was going to save this post for a bit =
longer=20
until I had more<BR>>>info<BR>>>>to share, but it seems =
particularly timely today.<BR>>>><BR>>>>Sorry this =
is a bit=20
long - the summary is at the end. But as I'm=20
putting<BR>>>out<BR>>>>an appeal here, you should have =
full=20
access to my "source code" :D<BR>>>><BR>>>>As my =
previous=20
posts have implied, I've been busy contacting people =
in<BR>>>>various=20
places about the possibilities of pushing PARIS forward. I've=20
<BR>>>>talked<BR>>>>to many companies/developers. =
Some names=20
might surprise you. There are<BR>> very<BR>>>>interesting =
avenues=20
to pursue, and obstacles to overcome to get=20
there.<BR>>>><BR>>>>Development involving the PARIS =
app=20
itself (eg EDS plugins or the =
<BR>>>>FaderWorks<BR>>>>PDC=20
advances) looks to be in excellent hands courtesy of Mike Audet=20
and<BR>>>>Dimitrios and others. I'm focusing my own efforts =
elsewhere=20
- I'm<BR>>>>investigating what alternatives might exist for =
the PARIS=20
hardware<BR>>>>independent of the PARIS app. This involves=20
investigating things like <BR>>>>what<BR>>>>driver =
options=20
could be pursued; what alternative "front end" apps=20
might<BR>>>>feasibly be adapted to access the PARIS hardware; =
and how=20
we might obtain<BR>>>>the ability to import/migrate ppjs/pafs =
into=20
another app to "future <BR>>>>proof"<BR>>>>our =
access to our=20
"back catalogs".<BR>>>><BR>>>>I can only promise I'm =
working=20
hard in the background and have devoted<BR>> =
many<BR>>>>hours=20
already to the effort. I can't make promises on behalf of=20
others,<BR>>>but<BR>>>>I see the bulk of items on my =
list as=20
more "to do" items than a "wish =
<BR>>>>list",<BR>>>>and if=20
two minor goals I'm working towards happen then I'd rate at=20
least<BR>>>one<BR>>>>of the developments (safeguarding =
our=20
ppj/pafs) as both "fairly =
likely"<BR>>>and<BR>>>> "within a=20
reasonably short timeframe".<BR>>>><BR>>>>BTW, I =
have=20
already rejected some promising solutions that involved=20
<BR>>>>asking<BR>>>>the community for significant =
sums of=20
money for development specific =
only<BR>>>to<BR>>>>PARIS. I've=20
talked to genuinely interested developers, folks with=20
great<BR>>>>track records and real good will who have offered =
me=20
every break in the<BR>>>>book, but I don't propose taking the =
community down that road. I'm =
<BR>>>>instead<BR>>>>seeking=20
developers who will help for their own reasons. Like this one:<BR>> =
Mike<BR>>>>Audet and I have independently estimated the PARIS =
userbase as some 400<BR>>>>users worldwide (I have recorded =
over 40=20
within the last few months <BR>>>>amongst<BR>>>>the =
subset=20
of PARIS users that post to the NG). Capturing a market of=20
<BR>>>>that<BR>>>>size is not insignificant for a =
smaller=20
developer looking to build their<BR>>>>clientele - it can be =
worth=20
them throwing some effort into investigating<BR>>>>making =
those=20
people happy (particularly if the developer has existing=20
<BR>>>>code<BR>>>>that might merely need tweaking). =
And=20
there are aspects of the PARIS<BR>>>>community that might =
make it=20
more interesting to certain developers=20
than<BR>>>raw<BR>>>>numbers might=20
=
dictate.<BR>>>><BR>>>>>>>> <BR>>>><=
BR>>>>Here's=20
the immediate obstacle I want to ask the community=20
about.<BR>>>><BR>>>>Even the most interested =
developers=20
can't do much for us if they don't<BR>> have<BR>>>>a PARIS =
rig -=20
and in 2008 PARIS rigs aren't easy to run out and buy.=20
<BR>>>>Given<BR>>>>our small size as a market, if we =
as a=20
community are asking a developer<BR>>>to<BR>>>>do =
things for=20
us, then telling them "go out and source and purchase a=20
<BR>>>>PARIS<BR>>>>rig so you can help us out" isn't =
gonna=20
fly. Neither is promising a<BR>>>>developer you'll get them =
access to=20
a rig to test on without being sure<BR>>>you<BR>>>>can =
deliver.=20
If the community wants developers to work on PARIS, and=20
<BR>>>>those<BR>>>>developers have to have a PARIS =
rig=20
available in order to help us - then<BR>>>>IMHO it's *in the=20
community's best interest to provide one to=20
=
them*.<BR>>>><BR>>>>>>>> <BR>>>><BR=
>>>>So=20
this is a "feeler" post. IMHO the community needs a=20
pre-assembled,<BR>>>>"turnkey" (ie pre-installed on a =
computer) PARIS=20
development rig, ready<BR>>>to<BR>>>>be shipped to =
developers=20
that could do it the most good (if you've=20
<BR>>>>guessed<BR>>>>that I have destinations in =
mind to=20
offer this to already - well, you're<BR>>>a<BR>>>>good =
guesser=20
:D).<BR>>>><BR>>>>Ideally this rig would be a =
multi-card,=20
multi-MEC system containing at<BR>> least<BR>>>>one of =
every=20
existing PARIS component we can get our hands on so PARIS<BR>>=20
can<BR>>>>be thoroughly tested in larger configurations. No =
more of=20
this "sorry,<BR>> we<BR>>>>didn't have a full system to =
test"=20
thing. But as a start we'll settle for<BR>>>>whatever we can =
lay our=20
hands on.<BR>>>><BR>>>>In addition we'd need a PARIS =
community member who lives in the 48<BR>>>>contiguous states =
(to keep=20
shipping costs and delays low) to volunteer<BR>>=20
to<BR>>>be<BR>>>>the occasional "depot/shipping =
person". They'd=20
be the person that <BR>>>>received<BR>>>>the donated =
components, tested them, assembled them into a rig, and=20
sent<BR>>>it<BR>>>>to where it needed to go, and if =
needed=20
(although if it finds a long-term<BR>>>>home fast, that's =
good news=20
for us) receive it back and ship it=20
<BR>>>>elsewhere.<BR>>>> <BR>>>>BTW, I'd do =
it=20
myself in a heartbeat, but I'm in Canada - don't even =
ask<BR>>>>what=20
international shipping would add to the hassle and the cost and=20
the<BR>>>>delays. I've already had the first potential =
volunteer=20
interest, and he's<BR>>>a<BR>>>>name you've all known a =
long=20
time, but we're clear that there are some<BR>>>>commitments I =
need to=20
obtain from others before we can ask him for=20
his.<BR>>>><BR>>>>Incidentally, obviously I'm not =
proposing=20
we stick that volunteer, <BR>>>>whoever<BR>>>>it =
winds up=20
being, with picking up shipping/packing charges. I'd=20
propose<BR>>>>setting up something like a PayPal account for =
them in=20
order to let the<BR>>>>community chip in a few bucks apiece =
to cover=20
any reasonable<BR>>>>packing/shipping costs. I'd nag, too - =
these are=20
trivial "beer money" <BR>>>>costs<BR>>>>for a =
community to=20
absorb, rather than a lump for an=20
=
individual.<BR>>>><BR>>>>>>>> <BR>>>&g=
t;<BR>>>>As=20
mentioned, this is not an actual call for components yet - it's=20
just<BR>>>an<BR>>>>"assessment " call to determine if =
folks=20
would give concrete support to<BR>> this<BR>>>>idea. I'd =
put=20
everyone fully in the picture on *where* I was proposing<BR>>=20
it<BR>>>to<BR>>>>go (and of course *why*) when I made =
the=20
actual call for components.<BR>>>><BR>>>>PARIS =
hardware=20
prices have plummeted so far that the gear's hardly=20
worth<BR>>>>selling now - ($25 for a C16? Feh, the faders in =
it are=20
probably worth<BR>> more<BR>>>>than that as salvage!), and =
there's=20
the possibility of very exciting<BR>>>>developments if =
everything=20
worked out well.<BR>>>><BR>>>>So if you're =
contemplating=20
blowing PARIS gear out at absurd "it's=20
<BR>>>>gathering<BR>>>>dust, make me an offer, just =
get it=20
out of here" fire-sale prices anyway<BR>>>- =
a<BR>>>>component=20
or two, or an old but functional PARIS-equipped PC, or even=20
a<BR>>>full<BR>>>>rig - would you consider donating =
components=20
to such a "development rig"<BR>>>>effort=20
instead?<BR>>>><BR>>>>In addition, would there be =
any=20
interest in making a small donation to<BR>> =
a<BR>>>>community fund=20
to purchase any components we're missing after we see =
what<BR>>>>the=20
donation call brings in? 27 MECs won't help us if we only have a=20
<BR>>>>single<BR>>>>EDS=20
card.<BR>>>><BR>>>>I've got no promises to give in =
exchange=20
at this moment, except my own,<BR>>>that<BR>>>>I'm =
working on=20
things. But this is what's needed to get 'em done. Let =
me<BR>>>>know=20
what you think.<BR>>>><BR>>>>- Kerry=20
Galloway<BR>>>><BR>>> <BR>> <BR><BR></BLOCKQUOTE>
<DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
and=20
you?<BR><A=20
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BODY ></HTML>
------=_NextPart_000_0027_01C8BF26.6AE7AE90--I don't see what your talking about. (Al Jackson's left hand)Is this the correct
clip?
Otis Redding "Try a little Tenderness"?
rod
"TCB" <nobody@ishere.com> wrote:
>
>Even rootsier but at least as good. Al Jackson with Booker T., Duck Dunn,
>Steve Cropper and some horns. There are a few shots if you look carefully
>at Jackson and he's playing military grip with his left hand and moving
that
>hand about four inches off the drum and the snares are like gunfire.
>
>http://www.youtube.com/watch?v=3UlQVhMAbwg
>
>I still wonder how the hell he did that. Maybe it's that elusive combination
>of 'talent,' 'technique,' and 'practice' I keep hearing about.
>
>The rest of the band is pretty good too. Oh, and the vox don't suck. Decent
>song now that I think about it.
>
>TCB
>
>"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote:
>>
>>Thanks Thad, that was pretty sweet!
>>Rod
>>"TCB" <nobody@ishere.com> wrote:
>>>
>>>I pretty much gave up on George Benson when he started to sing, but how
>>about
>>>this in the funky dept.
>>>
>>>http://www.youtube.com/watch?v=_FBnQvd_xzs
>>>
>>>TCB
>>>
>>>Bill L <bill@billlorentzen.com> wrote:
>>>>After watching a couple of those "shred" videos I needed a little taste
>>>
>>>>of The Man. Y'all better spray some Lysol up in here 'cause things is
>
>>>>'bout to get real funky:
>>>>
>>>>http://www.youtube.com/watch?v=voNjeUUcdSo
>>>>
>>>>And if that don't get it this will - ol' school style:
>>>>
>>>>http://www.youtube.com/watch?v=jKXXzJhhlhQ
>>>
>>
>It's only there for a few seconds, but you can look up pretty much any Booker
T live clip and get an idea.
"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote:
>
>I don't see what your talking about. (Al Jackson's left hand)Is this the
correct
>clip?
>Otis Redding "Try a little Tenderness"?
>rod
>"TCB" <nobody@ishere.com> wrote:
>>
>>Even rootsier but at least as good. Al Jackson with Booker T., Duck Dunn,
>>Steve Cropper and some horns. There are a few shots if you look carefully
>>at Jackson and he's playing military grip with his left hand and moving
>that
>>hand about four inches off the drum and the snares are like gunfire.
>>
>>http://www.youtube.com/watch?v=3UlQVhMAbwg
>>
>>I still wonder how the hell he did that. Maybe it's that elusive combination
>>of 'talent,' 'technique,' and 'practice' I keep hearing about.
>>
>>The rest of the band is pretty good too. Oh, and the vox don't suck. Decent
>>song now that I think about it.
>>
>>TCB
>>
>>"Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote:
>>>
>>>Thanks Thad, that was pretty sweet!
>>>Rod
>>>"TCB" <nobody@ishere.com> wrote:
>>>>
>>>>I pretty much gave up on George Benson when he started to sing, but how
>>>about
>>>>this in the funky dept.
>>>>
>>>>http://www.youtube.com/watch?v=_FBnQvd_xzs
>>>>
>>>>TCB
>>>>
>>>>Bill L <bill@billlorentzen.com> wrote:
>>>>>After watching a couple of those "shred" videos I needed a little taste
>>>>
>>>>>of The Man. Y'all better spray some Lysol up in here 'cause things is
>>
>>>>>'bout to get real funky:
>>>>>
>>>>>http://www.youtube.com/watch?v=voNjeUUcdSo
>>>>>
>>>>>And if that don't get it this will - ol' school style:
>>>>>
>>>>>http://www.youtube.com/watch?v=jKXXzJhhlhQ
>>>>
>>>
>>
>Don't forget the Mac users please.
DCWow, finally got around to getting these installed and I am very impressed--awesome
work Mike! Highly recommended!Agreed. I've been 'way' busy here, but I finally got to install/ listen Sat
night, and I must say I'm quite impressed with the quality of them.
AA
"John Macy" <nospanjohn@johnmacy.com> wrote in message
news:483b1119$1@linux...
>
> Wow, finally got around to getting these installed and I am very
> impressed--awesome
> work Mike! Highly recommended!Thanks, guys! I'm working on the gated verb right now.
I can't wait to do some recording with this stuff this summer. :)
All the best,
Mike
"Aaron Allen" <know-spam@not_here.dude> wrote:
>Agreed. I've been 'way' busy here, but I finally got to install/ listen
Sat
>night, and I must say I'm quite impressed with the quality of them.
>
>AA
>
>
>"John Macy" <nospanjohn@johnmacy.com> wrote in message
>news:483b1119$1@linux...
>>
>> Wow, finally got around to getting these installed and I am very
>> impressed--awesome
>> work Mike! Highly recommended!
>
>This is a multi-part message in MIME format.
------=_NextPart_000_000D_01C8BF6A.21CA16F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I can't wait to do some recording with this stuff this summer. :)
Screw that Mike, we need more plugins . . .=20
Ha!
Tripple thanks,
Tom
"Mike Audet" <mike@...> wrote in message news:483b2190$1@linux...
Thanks, guys! I'm working on the gated verb right now.
I can't wait to do some recording with this stuff this summer. :)
All the best,
Mike =20
"Aaron Allen" <know-spam@not_here.dude> wrote:
>Agreed. I've been 'way' busy here, but I finally got to install/ =
listen
Sat=20
>night, and I must say I'm quite impressed with the quality of them.
>
>AA
>
>
>"John Macy" <nospanjohn@johnmacy.com> wrote in message=20
>news:483b1119$1@linux...
>>
>> Wow, finally got around to getting these installed and I am very=20
>> impressed--awesome
>> work Mike! Highly recommended!=20
>
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_000D_01C8BF6A.21CA16F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>I can't wait to=20
do some recording with this stuff this summer. :)</FONT><BR></FONT><FONT =
face=3DArial size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Screw that Mike, we need more =
plugins . . .=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ha!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Tripple thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Mike Audet" <mike@...> wrote in message <A=20
=
href=3D"news:483b2190$1@linux">news:483b2190$1@linux</A>...</DIV><BR>Than=
ks,=20
guys! I'm working on the gated verb right now.<BR><BR>I can't =
wait to do=20
some recording with this stuff this summer. :)<BR><BR>All the=20
best,<BR><BR>Mike <BR><BR><BR>"Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=20
wrote:<BR>>Agreed. I've been 'way' busy here, but I finally got to =
install/=20
listen<BR>Sat <BR>>night, and I must say I'm quite impressed with =
the=20
quality of them.<BR>><BR>>AA<BR>><BR>> <BR>>"John Macy" =
<<A=20
=
href=3D"mailto:nospanjohn@johnmacy.com">nospanjohn@johnmacy.com</A>> =
wrote in=20
message <BR>>news:483b1119$1@linux...<BR>>><BR>>> Wow, =
finally=20
got around to getting these installed and I am very <BR>>>=20
impressed--awesome<BR>>> work Mike! Highly recommended!=20
<BR>><BR>><BR></BLOCKQUOTE>
<DIV><FONT size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
and=20
you?<BR><A=20
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BODY ></HTML>
------=_NextPart_000_000D_01C8BF6A.21CA16F0--I haven't forgotten, DC - but I'll give it to you straight - OS9 development
involves serious custom building for a small and swiftly dwindling niche.
Mike Audet is going to be pushing hard on porting the plugins for you guys
ASAP but these efforts of mine are about currently supported OSes only.
I'm really sorry to say that, too - I'm not only a fellow Mac user, I'm an
ex-fellow "PARIS on OS9" user - but getting developers interested in the
long-discontinued PARIS system already poses a sufficient set of challenges,
and getting them interested in creating a branch effort to support the small
minority of PARIS users who also use an OS as long discontinued as OS9 is,
I'm just not so hopeful about.
And please understand, virtually every PARIS user I know personally is or
was a PARIS on OS9 guy, including myself - I just can't see a road ahead
there today.
Now - on the other hand...
.... Would developments that involved OSX interest you? :)
- K
On 5/26/08 11:46 AM, in article 483b0590$1@linux, "DC"
<dc@spammersinhell.com> wrote:
>
> Don't forget the Mac users please.
>
> DC
>Heya Gantt... I'm glad the consensus seems to be that it's a good idea for
the community to own its own development rig - I see it as essential myself.
I'm of two minds on purchased vs donated myself.
Some arguments for *making a rig from donated components*:
- cheap: as mentioned, I'm seeking solutions that represent as insignificant
a financial impact for the community as possible
- Honestly, I don't particularly want to administer the financial side so
we'd need a volunteer for that ("PARIS Treasurer", so to speak :D), They'd
have to set up a PARIS PayPal account (or something similar) and keep track
of it.
Some arguments for *purchasing* a rig:
- simplicity: a "best case" scenario sees a developer sticking by us for a
while, and thus needing the rig for an extended period. With a purchased rig
there's no complication of trying to track people down to return components
to, long in the future.
- equally shared benefit, equally shared risk and responsibility (ie
shipping damage etc).
- choice: obviously we could buy precisely what we need
- speed: we could have a core rig as fast as we could raise the money for it
I'll leave it up to the community to decide. If someone wants to volunteer
to step up to the plate and create and administer a community fund for this,
that would rock.
- Kerry
On 5/26/08 4:57 AM, in article 483aa591$1@linux, "Gantt Kushner"
<ganttmann@comcast.net> wrote:
>
> I don't know what Brian's looking to get for his system, but if enough of
> us were to contribute $10 or $15 to the cause we could probably make it
> happen. Could we set up a PayPal account to gather Paris development funds?
>
> Gantt
>
> "Brian Milton" <bcmilton@austin.rr.com> wrote:
>>
>> I'm not really in the right financial shape to donate a rig (Out of
>> work/Starting
>> a new business), but I am looking to part with my rig. If any Paris
>> die-hards
>> want to buy my rig at a reasonable price and donate it for development let
>> me know. I was about to post it to the FS group. I'm looking through the
>> old posts now to figure out what it's worth.
>>
>> Here's what I've got in Austin,TX:
>> All of these are in Black
>>
>> MEC
>> 442
>> (2) EDS
>> 8in card
>> 8out card
>> ADAT card
>> (2) C16
>>
>> It's running Paris 3.0 on an older Athlon XP/WinXP system -w- 1GB RAM.
> I
>> was going to re-purpose the PC for something else but would take offers
> for
>> it too.
>>
>> -BrianKerry Galloway wrote:
> Now - on the other hand...
>
> ... Would developments that involved OSX interest you? :)
What the...really?
Cheers,
-Jamie
www.JamieKrutz.com
> - K
>
> On 5/26/08 11:46 AM, in article 483b0590$1@linux, "DC"
> <dc@spammersinhell.com> wrote:
>
>> Don't forget the Mac users please.
>>
>> DC
>>
>Hey Kerry! I would be interested in a Mac version also, but I see some big
hurdles though. The last Apple Macintosh that had standard PCI slots were
the G4 towers. 2.0GHz processor upgrades are available for the G4, but they
are about $600. There is the possibility of building a Hackintosh machine
with a PC MOBO with standard PCI slots, but would it work??? FYI, it's also
against Apple's licensing agreement. There is also the expansion chassis
route. So Kerry, what path are you thinking about?
I'm sure your way ahead of me on this, but I think Justin the creator of
Reaper should be contacted about development. Somebody asked him in the
past about including paf in Reaper. Maybe he'd take us on if we got enough
people to commit. Reaper is under constant development, and he is developing
a Mac version. The PC version is way more advanced than the Mac version
at this time. I also have to say that the PC version of Reaper is impressive
at only a 3.2 MB download, and the noncommercial license is only $50.00.
I think most of us could live with that kind of a price too.
I just wonder what Paris hardware will sound like with a different software.
I personally believe the golden sauce is a combination of both, maybe we'll
find out in the future.
As long as Paris sounds good and the audio standards are 24bit-16bit 44.1
and MP3, I see Paris as being worth developing. I'll be using other tools
as well, however I won't be selling off Paris just because some new slick
box comes out. I'm also not in to spending a bunch of money on boxes to
get another DAW to sound like Paris, so I'm keeping Paris.
I want to say thanks to you and Mike for carrying the torch. For you to
comeback and push this project is a great thing! It's incredible to think
that Mike just jumped in and is cranking out the plugins the way he is.
If we could get easy to use delay compensation, that would really help out
a lot.
Thanks again guys, and long live PARIS!
Kerry Galloway <kg@kerrygalloway.com> wrote:
>Heya Gantt... I'm glad the consensus seems to be that it's a good idea for
>the community to own its own development rig - I see it as essential myself.
>
>I'm of two minds on purchased vs donated myself.
>
>Some arguments for *making a rig from donated components*:
>
>- cheap: as mentioned, I'm seeking solutions that represent as insignificant
>a financial impact for the community as possible
>
>- Honestly, I don't particularly want to administer the financial side so
>we'd need a volunteer for that ("PARIS Treasurer", so to speak :D), They'd
>have to set up a PARIS PayPal account (or something similar) and keep track
>of it.
>
>Some arguments for *purchasing* a rig:
>
>- simplicity: a "best case" scenario sees a developer sticking by us for
a
>while, and thus needing the rig for an extended period. With a purchased
rig
>there's no complication of trying to track people down to return components
>to, long in the future.
>- equally shared benefit, equally shared risk and responsibility (ie
>shipping damage etc).
>- choice: obviously we could buy precisely what we need
>- speed: we could have a core rig as fast as we could raise the money for
it
>
>I'll leave it up to the community to decide. If someone wants to volunteer
>to step up to the plate and create and administer a community fund for this,
>that would rock.
>
>- Kerry
>
>On 5/26/08 4:57 AM, in article 483aa591$1@linux, "Gantt Kushner"
><ganttmann@comcast.net> wrote:
>
>>
>> I don't know what Brian's looking to get for his system, but if enough
of
>> us were to contribute $10 or $15 to the cause we could probably make
it
>> happen. Could we set up a PayPal account to gather Paris development
funds?
>>
>> Gantt
>>
>> "Brian Milton" <bcmilton@austin.rr.com> wrote:
>>>
>>> I'm not really in the right financial shape to donate a rig (Out of
>>> work/Starting
>>> a new business), but I am looking to part with my rig. If any Paris
>>> die-hards
>>> want to buy my rig at a reasonable price and donate it for development
let
>>> me know. I was about to post it to the FS group. I'm looking through
the
>>> old posts now to figure out what it's worth.
>>>
>>> Here's what I've got in Austin,TX:
>>> All of these are in Black
>>>
>>> MEC
>>> 442
>>> (2) EDS
>>> 8in card
>>> 8out card
>>> ADAT card
>>> (2) C16
>>>
>>> It's running Paris 3.0 on an older Athlon XP/WinXP system -w- 1GB RAM.
>> I
>>> was going to re-purpose the PC for something else but would take offers
>> for
>>> it too.
>>>
>>> -Brian
>I wish I could give more info, Jamie; I'll do so the instant I can.
All that exists right now are interesting possibilities; the amount of work
and resources needed to achieve them can't even be assessed until we get a
rig to the right people to take a look at.
But yes, some of those available possibilities do include tantalizing
glimpses of OSX. I'm still investigating.
- K
On 5/26/08 10:09 PM, in article 483b9a14$1@linux, "Jamie K"
<JamieN0-SPAM@JamieKrutzN0-SPAM.com> wrote:
>
> Kerry Galloway wrote:
>> Now - on the other hand...
>>
>> ... Would developments that involved OSX interest you? :)
>
> What the...really?
>
> Cheers,
> -Jamie
> www.JamieKrutz.com
>
>
>> - K
>>
>> On 5/26/08 11:46 AM, in article 483b0590$1@linux, "DC"
>> <dc@spammersinhell.com> wrote:
>>
>>> Don't forget the Mac users please.
>>>
>>> DC
>>>
>>Yess...
Martin H
On 27/05/08 2:39 PM, in article C460DE87.B074%kg@kerrygalloway.com, "Kerry
Galloway" <kg@kerrygalloway.com> wrote:
> I haven't forgotten, DC - but I'll give it to you straight - OS9 development
> involves serious custom building for a small and swiftly dwindling niche.
> Mike Audet is going to be pushing hard on porting the plugins for you guys
> ASAP but these efforts of mine are about currently supported OSes only.
>
> I'm really sorry to say that, too - I'm not only a fellow Mac user, I'm an
> ex-fellow "PARIS on OS9" user - but getting developers interested in the
> long-discontinued PARIS system already poses a sufficient set of challenges,
> and getting them interested in creating a branch effort to support the small
> minority of PARIS users who also use an OS as long discontinued as OS9 is,
> I'm just not so hopeful about.
>
> And please understand, virtually every PARIS user I know personally is or
> was a PARIS on OS9 guy, including myself - I just can't see a road ahead
> there today.
>
> Now - on the other hand...
>
> ... Would developments that involved OSX interest you? :)
>
>
> - K
>
> On 5/26/08 11:46 AM, in article 483b0590$1@linux, "DC"
> <dc@spammersinhell.com> wrote:
>
>>
>> Don't forget the Mac users please.
>>
>> DC
>>
>Big time
>
>Now - on the other hand...
>
>... Would developments that involved OSX interest you? :)
>
>- K
>
>On 5/26/08 11:46 AM, in article 483b0590$1@linux, "DC"
><dc@spammersinhell.com> wrote:
>
>>
>> Don't forget the Mac users please.
>>
>> DC
>>
>I know its not much but I have a spare IF2 for the cause and of course a few
$ to the "Paris Comunity Paypal account".
Rob_Ay
"Kerry Galloway" <kg@kerrygalloway.com> wrote in message
news:C45F0B7F.B044%kg@kerrygalloway.com...
> Hi all. I was going to save this post for a bit longer until I had more
> info
> to share, but it seems particularly timely today.
>
> Sorry this is a bit long - the summary is at the end. But as I'm putting
> out
> an appeal here, you should have full access to my "source code" :D
>
> As my previous posts have implied, I've been busy contacting people in
> various places about the possibilities of pushing PARIS forward. I've
> talked
> to many companies/developers. Some names might surprise you. There are
> very
> interesting avenues to pursue, and obstacles to overcome to get there.
>
> Development involving the PARIS app itself (eg EDS plugins or the
> FaderWorks
> PDC advances) looks to be in excellent hands courtesy of Mike Audet and
> Dimitrios and others. I'm focusing my own efforts elsewhere - I'm
> investigating what alternatives might exist for the PARIS hardware
> independent of the PARIS app. This involves investigating things like what
> driver options could be pursued; what alternative "front end" apps might
> feasibly be adapted to access the PARIS hardware; and how we might obtain
> the ability to import/migrate ppjs/pafs into another app to "future proof"
> our access to our "back catalogs".
>
> I can only promise I'm working hard in the background and have devoted
> many
> hours already to the effort. I can't make promises on behalf of others,
> but
> I see the bulk of items on my list as more "to do" items than a "wish
> list",
> and if two minor goals I'm working towards happen then I'd rate at least
> one
> of the developments (safeguarding our ppj/pafs) as both "fairly likely"
> and
> "within a reasonably short timeframe".
>
> BTW, I have already rejected some promising solutions that involved asking
> the community for significant sums of money for development specific only
> to
> PARIS. I've talked to genuinely interested developers, folks with great
> track records and real good will who have offered me every break in the
> book, but I don't propose taking the community down that road. I'm instead
> seeking developers who will help for their own reasons. Like this one:
> Mike
> Audet and I have independently estimated the PARIS userbase as some 400
> users worldwide (I have recorded over 40 within the last few months
> amongst
> the subset of PARIS users that post to the NG). Capturing a market of that
> size is not insignificant for a smaller developer looking to build their
> clientele - it can be worth them throwing some effort into investigating
> making those people happy (particularly if the developer has existing code
> that might merely need tweaking). And there are aspects of the PARIS
> community that might make it more interesting to certain developers than
> raw
> numbers might dictate.
>
>>>>>
>
> Here's the immediate obstacle I want to ask the community about.
>
> Even the most interested developers can't do much for us if they don't
> have
> a PARIS rig - and in 2008 PARIS rigs aren't easy to run out and buy. Given
> our small size as a market, if we as a community are asking a developer to
> do things for us, then telling them "go out and source and purchase a
> PARIS
> rig so you can help us out" isn't gonna fly. Neither is promising a
> developer you'll get them access to a rig to test on without being sure
> you
> can deliver. If the community wants developers to work on PARIS, and those
> developers have to have a PARIS rig available in order to help us - then
> IMHO it's *in the community's best interest to provide one to them*.
>
>>>>>
>
> So this is a "feeler" post. IMHO the community needs a pre-assembled,
> "turnkey" (ie pre-installed on a computer) PARIS development rig, ready to
> be shipped to developers that could do it the most good (if you've guessed
> that I have destinations in mind to offer this to already - well, you're a
> good guesser :D).
>
> Ideally this rig would be a multi-card, multi-MEC system containing at
> least
> one of every existing PARIS component we can get our hands on so PARIS can
> be thoroughly tested in larger configurations. No more of this "sorry, we
> didn't have a full system to test" thing. But as a start we'll settle for
> whatever we can lay our hands on.
>
> In addition we'd need a PARIS community member who lives in the 48
> contiguous states (to keep shipping costs and delays low) to volunteer to
> be
> the occasional "depot/shipping person". They'd be the person that received
> the donated components, tested them, assembled them into a rig, and sent
> it
> to where it needed to go, and if needed (although if it finds a long-term
> home fast, that's good news for us) receive it back and ship it elsewhere.
>
> BTW, I'd do it myself in a heartbeat, but I'm in Canada - don't even ask
> what international shipping would add to the hassle and the cost and the
> delays. I've already had the first potential volunteer interest, and he's
> a
> name you've all known a long time, but we're clear that there are some
> commitments I need to obtain from others before we can ask him for his.
>
> Incidentally, obviously I'm not proposing we stick that volunteer, whoever
> it winds up being, with picking up shipping/packing charges. I'd propose
> setting up something like a PayPal account for them in order to let the
> community chip in a few bucks apiece to cover any reasonable
> packing/shipping costs. I'd nag, too - these are trivial "beer money"
> costs
> for a community to absorb, rather than a lump for an individual.
>
>>>>>
>
> As mentioned, this is not an actual call for components yet - it's just an
> "assessment" call to determine if folks would give concrete support to
> this
> idea. I'd put everyone fully in the picture on *where* I was proposing it
> to
> go (and of course *why*) when I made the actual call for components.
>
> PARIS hardware prices have plummeted so far that the gear's hardly worth
> selling now - ($25 for a C16? Feh, the faders in it are probably worth
> more
> than that as salvage!), and there's the possibility of very exciting
> developments if everything worked out well.
>
> So if you're contemplating blowing PARIS gear out at absurd "it's
> gathering
> dust, make me an offer, just get it out of here" fire-sale prices anyway -
> a
> component or two, or an old but functional PARIS-equipped PC, or even a
> full
> rig - would you consider donating components to such a "development rig"
> effort instead?
>
> In addition, would there be any interest in making a small donation to a
> community fund to purchase any components we're missing after we see what
> the donation call brings in? 27 MECs won't help us if we only have a
> single
> EDS card.
>
> I've got no promises to give in exchange at this moment, except my own,
> that
> I'm working on things. But this is what's needed to get 'em done. Let me
> know what you think.
>
> - Kerry Galloway
>OSX? Oh absolutely...
DCHi DJ,
RME's driver reports the ASIO buffer and the AD/DA latency of any of it's in board converters.
You also have the added PDC of the host app getting factored in.
There is also added latency in the samples range of the multiple audio devices like any other digital hardware.
All you digital gear and AD/DA converters are adding to some extant to the over In to Out latency.
It is not possible for the sound card to know the exact AD/DA latency performance of all your converters.
They are the only company that I Know of that even lets there driver report their latency in detail to the ASIO host.
Most other hide the the info and only report the driver latency only.
You will see this allot on the the low end firewire devices.
The highest number of support called we get are on Tascam and Lynx.
90% of the time they are not because of user error, i.e., not setting up the clock right.
This is from people that use our systems and from people that just purchased the gear from use.
That said though one the best bang for the buck converter sound card combos is a RME AES32 PCI card and a Lynx Aurora 16.
No proprietary cabling and more reliable clocking and actual fully functional hardware monitoring.
The only other high I/O combo I've seen that very good quality AD/DA that isn't very high priced would be using a
RME MADI card with a SSL Alpha Link MADI box.
24 high quality analog AD/DA and 24 AES or ADAT connections for around $5000 including the sound card.
Chris
Deej wrote:
> "Mike Audet" <mike@..> wrote:
>> DJ, are the latency values round trip or based on input and output buffers?
>>
>>
>> I emailed RME the same questions, but I thought you might know.
>>
>> All the best,
>>
>> Mike
>
> Mike,
>
> I think thereis an extra 32k of round trip latency involved with the RME
> gear, so 64k buffers (a/k/a 1.5ms latency) is actually around 2.25ms. RME
> won't admit that there this voodoo going on so I'd be surprised if they answer
> you. AFAIK, the LynxTwo series of cards has the best low latency performance,
> or at least that's what I read on the various forums. chris Ludwig would
> probaly be a better authority on this than I.
>
> ;o)
>
>
--
Chris Ludwig
ADK Pro Audio
(859) 635-5762
www.adkproaudio.com
chrisl@adkproaudio.comHey Deej,
What MB / chip combo did you end up with? The 4400 here is starting to
give me some grief and I'm looking at a replacement.
David.
Deej wrote:
> "TCB" <nobody@ishere.com> wrote:
>> Hey Deej,
>>
>> Glad you're feeling better. I've developed a general curiosity about the
>> domestic oil/gas business in my new job. I don't envy you doing what you
>> do.
>>
>> Also nice to see native is getting good enough to be the real deal for you.
>> I've been talking about native for years, as you know, and in the long run
>> we'll _all_ be doing native. And I mean the Mutt Lang types as well. Moore's
>> law spares no one.
>>
>> My fave thing about the quality of native is that it's letting me put my
>> big bucks where it really matters, into a smaller number of choices pieces
>> of analog gear like mics and analog synths.
>>
>> TCB
>>
>
> Well.......I thought I was gonna have to eat some major crow today. I was
> configuring a basic template and all of a sudden the whole then started losing
> sync....and I mean, like..........totally FUBAR. I was finally able to trace
> it down to a couple of settings with the control panel in my AES32 card that
> needed to change. That one is digitally interfacing with all my outboard
> reverbs. I'm clocking/syncing 17 different interfaces here. All is well now
> though....and to think.....when I sold my Paris system, I did it thinking
> that I was going to "simplify" things.
>
> It is running soooooo nicely now........and everything just integrates so
> flawlessly and it's so friggin cool!!
>
> You can take the boy out of the madhouse, but you can't take the madhouse
> out of the boy.
>
> ;o)
>
>Chris Ludwig <chrisl@adkproaudio.com> wrote:
>Hi DJ,
>
>RME's driver reports the ASIO buffer and the AD/DA latency of any of it's
in board converters.
>You also have the added PDC of the host app getting factored in.
>There is also added latency in the samples range of the multiple audio devices
like
>any other digital hardware.
>All you digital gear and AD/DA converters are adding to some extant to the
over In to
>Out latency.
>It is not possible for the sound card to know the exact AD/DA latency performance
of
>all your converters.
>They are the only company that I Know of that even lets there driver report
their latency
>in detail to the ASIO host.
>Most other hide the the info and only report the driver latency only.
>You will see this allot on the the low end firewire devices.
>
>The highest number of support called we get are on Tascam and Lynx.
>90% of the time they are not because of user error, i.e., not setting up
the clock right.
>This is from people that use our systems and from people that just purchased
the gear
>from use.
>
>That said though one the best bang for the buck converter sound card combos
is a RME
>AES32 PCI card and a Lynx Aurora 16.
>No proprietary cabling and more reliable clocking and actual fully functional
hardware
>monitoring.
>
>The only other high I/O combo I've seen that very good quality AD/DA that
isn't very
>high priced would be using a
>RME MADI card with a SSL Alpha Link MADI box.
>24 high quality analog AD/DA and 24 AES or ADAT connections for around $5000
including
>the sound card.
>
>Chris
>
>
I guess your speaking to mainly PC solutions. Chris, since you speaking
of solid systems, what are your thoughts about the Apogee stuff? Have you
tested it?
>
>
>
>Deej wrote:
>> "Mike Audet" <mike@..> wrote:
>>> DJ, are the latency values round trip or based on input and output buffers?
>>>
>>>
>>> I emailed RME the same questions, but I thought you might know.
>>>
>>> All the best,
>>>
>>> Mike
>>
>> Mike,
>>
>> I think thereis an extra 32k of round trip latency involved with the RME
>> gear, so 64k buffers (a/k/a 1.5ms latency) is actually around 2.25ms.
RME
>> won't admit that there this voodoo going on so I'd be surprised if they
answer
>> you. AFAIK, the LynxTwo series of cards has the best low latency performance,
>> or at least that's what I read on the various forums. chris Ludwig would
>> probaly be a better authority on this than I.
>>
>> ;o)
>>
>>
>
>--
>Chris Ludwig
>
>ADK Pro Audio
>(859) 635-5762
>www.adkproaudio.com
>chrisl@adkproaudio.comOn Mon, 26 May 2008 21:39:19 -0700, Kerry Galloway
<kg@kerrygalloway.com> wrote:
>
>Now - on the other hand...
>
>... Would developments that involved OSX interest you? :)
>
Effin' A skippy it would.... I've been an OS9 guy since I started, and
recently, begrudgingly, decided to start building an XP box because of
the available gooderness.
However, if Mike can make OSX - flavored versions, and your dudes can
make Paris work under OSX, then I'm ready to score a G4 and stay in
the family.
I'd be pissed that I sold my dual-1GHz Quicksilver after I got my G5,
but that's life.
pabif you're not using the card and he can use it...
On Tue, 27 May 2008 23:06:30 -0500, Paul Braun
<cygnus_nospam@ctgonline.org> wrote:
>On Mon, 26 May 2008 21:39:19 -0700, Kerry Galloway
><kg@kerrygalloway.com> wrote:
>
>>
>>Now - on the other hand...
>>
>>... Would developments that involved OSX interest you? :)
>>
>
>Effin' A skippy it would.... I've been an OS9 guy since I started, and
>recently, begrudgingly, decided to start building an XP box because of
>the available gooderness.
>
>However, if Mike can make OSX - flavored versions, and your dudes can
>make Paris work under OSX, then I'm ready to score a G4 and stay in
>the family.
>
>I'd be pissed that I sold my dual-1GHz Quicksilver after I got my G5,
>but that's life.
>
>pabHI James,
I've had a chance to use a symphony system once so far. It was very nice.
The latency was no better or worse than another PCI/PCI-e audio interface I've used on a MAC. But that was when it was still 10.4.
Seems to be allot of reports of people having trouble lately with Apogee and 10.5.
But that could just as well be user error from some of the reports I see.
A RME MADI PCI-e card at 96k will get the same low latencies as the Apogee does at 96k.
At 44.1k the Apogee perform like the RME does at 44.1k which is in the 2/3 ms range.
It's Logic "integration" is I guess a bonus for people that don't want to option the mixer panel on the apple menu bar.
It is a great value if you already have a bunch of Apogee but if not then it is not at all a good deal. More proprietary than Digi practically.
RME MADI PCI-e cards work great on MAC with any of the major software programs I've used.
The SSL RME MADI card combo would still be a untouchable combo atm.
Both RME and SSL will be releasing more I/O options especially large I/O ones over the next 1 or 2 with MADI connectivity.
Chris
James McCloskey wrote:
> Chris Ludwig <chrisl@adkproaudio.com> wrote:
>> Hi DJ,
>>
>> RME's driver reports the ASIO buffer and the AD/DA latency of any of it's
> in board converters.
>> You also have the added PDC of the host app getting factored in.
>> There is also added latency in the samples range of the multiple audio devices
> like
>> any other digital hardware.
>> All you digital gear and AD/DA converters are adding to some extant to the
> over In to
>> Out latency.
>> It is not possible for the sound card to know the exact AD/DA latency performance
> of
>> all your converters.
>> They are the only company that I Know of that even lets there driver report
> their latency
>> in detail to the ASIO host.
>> Most other hide the the info and only report the driver latency only.
>> You will see this allot on the the low end firewire devices.
>>
>> The highest number of support called we get are on Tascam and Lynx.
>> 90% of the time they are not because of user error, i.e., not setting up
> the clock right.
>> This is from people that use our systems and from people that just purchased
> the gear
>>from use.
>> That said though one the best bang for the buck converter sound card combos
> is a RME
>> AES32 PCI card and a Lynx Aurora 16.
>> No proprietary cabling and more reliable clocking and actual fully functional
> hardware
>> monitoring.
>>
>> The only other high I/O combo I've seen that very good quality AD/DA that
> isn't very
>> high priced would be using a
>> RME MADI card with a SSL Alpha Link MADI box.
>> 24 high quality analog AD/DA and 24 AES or ADAT connections for around $5000
> including
>> the sound card.
>>
>> Chris
>>
>>
>
> I guess your speaking to mainly PC solutions. Chris, since you speaking
> of solid systems, what are your thoughts about the Apogee stuff? Have you
> tested it?
>
>
>>
>>
>> Deej wrote:
>>> "Mike Audet" <mike@..> wrote:
>>>> DJ, are the latency values round trip or based on input and output buffers?
>>>>
>>>>
>>>> I emailed RME the same questions, but I thought you might know.
>>>>
>>>> All the best,
>>>>
>>>> Mike
>>> Mike,
>>>
>>> I think thereis an extra 32k of round trip latency involved with the RME
>>> gear, so 64k buffers (a/k/a 1.5ms latency) is actually around 2.25ms.
> RME
>>> won't admit that there this voodoo going on so I'd be surprised if they
> answer
>>> you. AFAIK, the LynxTwo series of cards has the best low latency performance,
>>> or at least that's what I read on the various forums. chris Ludwig would
>>> probaly be a better authority on this than I.
>>>
>>> ;o)
>>>
>>>
>> --
>> Chris Ludwig
>>
>> ADK Pro Audio
>> (859) 635-5762
>> www.adkproaudio.com
>> chrisl@adkproaudio.com
>
--
Chris Ludwig
ADK Pro Audio
(859) 635-5762
www.adkproaudio.com
chrisl@adkproaudio.comThis is a multi-part message in MIME format.
------=_NextPart_000_0006_01C8C0D4.F2CEAD90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Go figure. Didn't work before. It did today. It is a different ADAT =
card than I had been
trying as a second card. One happens to be a blue one in slot 9 and the =
new one is
black in slot 8. 1x 8in in slot 1 and 1 x 8out in slot 2.
Maybe it's the sequence of installing them? Use the last slot first so =
Paris looks down the whole=20
line before moving on. Later install stuff before it to be recognized. =
Just a thought.
Tom
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0006_01C8C0D4.F2CEAD90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Go figure. Didn't work =
before. It did=20
today. </FONT><FONT face=3DArial size=3D2>It is a different ADAT =
card than I=20
had been</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>trying as a second card. One =
happens to=20
be a blue one in slot 9 and the new one is</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>black in slot 8. 1x 8in in slot 1 =
and 1 x=20
8out in slot 2.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Maybe it's the sequence of installing =
them? =20
Use the last slot first so Paris looks down the whole </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>line before moving on. Later =
install stuff=20
before it to be recognized. Just a thought.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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 size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
and=20
you?<BR><A=20
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BODY ></HTML>
------=_NextPart_000_0006_01C8C0D4.F2CEAD90--I love all your reverbs.
Thank you for the predelay plugin !
One thing is that it is too dsp heavy !
Only 6 instances per card !
EDS compressors can be had for 16 instances so maybe I can use one compressor
pugin for just the lookahead working as predelay...
I managed to make all your reverbs available as mono inserts !
I would really love to see a dry/wet mix knob as to be able to take a real
benefit from the insert usage of the reverbs.
This would be mostly needed for Drumplate.
This way you can use a mono version of the reverb at the insert and follow
the panning of the istrument anf freeing the auxes.
1. Is there a way to reduce dsp if the reveb plugins become mono ??
This could free some dsp and there are times ,like snare, where mono reverb
is preffered as to not occupy much stereo space from the mix. In this way
the dry/wet mix knob would be essential
2. A great room reverb is a must for Paris !
The room already there cannot compete with "your" new halls and plates !
I would love a great room reverb for an electric guitar.
3. Your drumplate can only be used twice per card as opposed to dp pro hall
which can have four of it !
Is there a way to optimize that perhaps ? Maybe the less predelay would
cure that ?
Thanks for what you are doing for us !!
I will contimue supporting.
Will send more very soon...
Regards,
DimitriosThis is a multi-part message in MIME format.
------=_NextPart_000_0034_01C8C0F0.A12E28A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I've heard that can play into it, and you'll want to put them in the =
last 2 slots because of how XP/Paris looks for the cards. But it's not a =
guarantee that it'll work, and hasn't in some cases I know of. =
Unfortunately, I'm one of the unlucky ones for that.=20
Glad you got the luck on your side!
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:483daf7d$1@linux...
Go figure. Didn't work before. It did today. It is a different ADAT =
card than I had been
trying as a second card. One happens to be a blue one in slot 9 and =
the new one is
black in slot 8. 1x 8in in slot 1 and 1 x 8out in slot 2.
Maybe it's the sequence of installing them? Use the last slot first =
so Paris looks down the whole=20
line before moving on. Later install stuff before it to be =
recognized. Just a thought.
Tom
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0034_01C8C0F0.A12E28A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I've heard that can play into it, and =
you'll want=20
to put them in the last 2 slots because of how XP/Paris looks for the =
cards. But=20
it's not a guarantee that it'll work, and hasn't in some cases I know =
of.=20
Unfortunately, I'm one of the unlucky ones for that. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Glad you got the luck on your=20
side!<BR>AA</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> wrote =
in message=20
<A href=3D"news:483daf7d$1@linux">news:483daf7d$1@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Go figure. Didn't work =
before. It did=20
today. </FONT><FONT face=3DArial size=3D2>It is a different ADAT =
card than I=20
had been</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>trying as a second =
card. One happens=20
to be a blue one in slot 9 and the new one is</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>black in slot 8. 1x 8in in slot =
1 and 1 x=20
8out in slot 2.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Maybe it's the sequence of installing =
them? =20
Use the last slot first so Paris looks down the whole </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>line before moving on. Later =
install stuff=20
before it to be recognized. Just a thought.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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 size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
and=20
you?<BR><A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BLOCKQUOTE ></BODY></HTML>
------=_NextPart_000_0034_01C8C0F0.A12E28A0--Hi Dimitrios,
Thanks so much for the feedback - and for letting me know that my email is
bouncing!
The predelay just uses a lot of ram, which translates to dsp usage. I could
release a predlay plugin that is shorter - maybe there's a happy medium to
be found.
I'll look into the room reverb. I just finished porting the dp/pro plate.
It has a major memory issue that cause agacent tracks to leak into it.
Then, once I fixed the leak, I realized that it is exactly the same as the
stock paris plate. :)
I've since started on the gated reverb. I'll take a look tonight to see
if there is a room I could tackle. The stock room does kind of suck.
I will do mono versions of the plugs, and that will help a bit with the dsp
usage. I'll add wet/dry knobs when we get that going.
Thanks again for posting your feedback. It's great to hear that they are
getting used.
Mike
"Dimitrios" <musurgNOSPAMio@otenetNOSPAM.gr> wrote:
>
>I love all your reverbs.
>Thank you for the predelay plugin !
>One thing is that it is too dsp heavy !
>Only 6 instances per card !
>EDS compressors can be had for 16 instances so maybe I can use one compressor
>pugin for just the lookahead working as predelay...
>I managed to make all your reverbs available as mono inserts !
>I would really love to see a dry/wet mix knob as to be able to take a real
>benefit from the insert usage of the reverbs.
>This would be mostly needed for Drumplate.
>This way you can use a mono version of the reverb at the insert and follow
>the panning of the istrument anf freeing the auxes.
>
>1. Is there a way to reduce dsp if the reveb plugins become mono ??
>This could free some dsp and there are times ,like snare, where mono reverb
>is preffered as to not occupy much stereo space from the mix. In this way
>the dry/wet mix knob would be essential
>
>2. A great room reverb is a must for Paris !
>The room already there cannot compete with "your" new halls and plates !
>I would love a great room reverb for an electric guitar.
>
>3. Your drumplate can only be used twice per card as opposed to dp pro hall
>which can have four of it !
>Is there a way to optimize that perhaps ? Maybe the less predelay would
>cure that ?
>
>Thanks for what you are doing for us !!
>I will contimue supporting.
>Will send more very soon...
>Regards,
>DimitriosThis is a multi-part message in MIME format.
------=_NextPart_000_001F_01C8C103.B2A57670
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey Aaron,
Ya, I wasn't lucky for the last three installs in two comps in getting =
two ADATs
to show up with XP. Not sure what changed except:
#1 No Default project in use.
#2 No external WC.
#3 Slot 9 holding ADAT card 1 for multiple boots before installing
ADAT card 2 in slot 8.
I've had my days of bad luck that's for sure. It's about time something
worked easily. Now I'm waiting for a completely new box from Mr. Ludwig
that will make this a non deal.
We'll see,
Tom
"Aaron Allen" <know-spam@not_here.dude> wrote in message =
news:483ded01@linux...
I've heard that can play into it, and you'll want to put them in the =
last 2 slots because of how XP/Paris looks for the cards. But it's not a =
guarantee that it'll work, and hasn't in some cases I know of. =
Unfortunately, I'm one of the unlucky ones for that.=20
Glad you got the luck on your side!
AA
"Tom Bruhl" <arpegio@comcast.net> wrote in message =
news:483daf7d$1@linux...
Go figure. Didn't work before. It did today. It is a different =
ADAT card than I had been
trying as a second card. One happens to be a blue one in slot 9 and =
the new one is
black in slot 8. 1x 8in in slot 1 and 1 x 8out in slot 2.
Maybe it's the sequence of installing them? Use the last slot first =
so Paris looks down the whole=20
line before moving on. Later install stuff before it to be =
recognized. Just a thought.
Tom
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_001F_01C8C103.B2A57670
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hey Aaron,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Ya, I wasn't lucky for the last three =
installs in=20
two comps in getting two ADATs</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>to show up with XP. Not =
sure what=20
changed except:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>#1 No Default project in =
use.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>#2 No external WC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>#3 Slot 9 holding ADAT card 1 for =
multiple boots=20
before installing</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> ADAT card 2 in slot=20
8.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I've had my days of bad luck that's for =
sure. =20
It's about time something</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>worked easily. Now I'm waiting =
for a=20
completely new box from Mr. Ludwig</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that will make this a non =
deal.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We'll see,</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>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Aaron Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>> =
wrote in=20
message <A =
href=3D"news:483ded01@linux">news:483ded01@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>I've heard that can play into it, and =
you'll want=20
to put them in the last 2 slots because of how XP/Paris looks for the =
cards.=20
But it's not a guarantee that it'll work, and hasn't in some cases I =
know of.=20
Unfortunately, I'm one of the unlucky ones for that. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Glad you got the luck on your=20
side!<BR>AA</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Tom Bruhl" <<A=20
href=3D"mailto:arpegio@comcast.net">arpegio@comcast.net</A>> =
wrote in=20
message <A =
href=3D"news:483daf7d$1@linux">news:483daf7d$1@linux</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Go figure. Didn't work =
before. It=20
did today. </FONT><FONT face=3DArial size=3D2>It is a =
different ADAT card=20
than I had been</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>trying as a second =
card. One happens=20
to be a blue one in slot 9 and the new one is</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>black in slot 8. 1x 8in in =
slot 1 and 1 x=20
8out in slot 2.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Maybe it's the sequence of =
installing=20
them? Use the last slot first so Paris looks down the whole=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>line before moving on. Later =
install=20
stuff before it to be recognized. Just a thought.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></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 size=3D2><BR><BR>I choose Polesoft Lockspam to fight =
spam, and=20
you?<BR><A=20
=
href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
..html</A> </FONT></DIV></BLOCKQUOTE ></BLOCKQUOTE></BODY>=
</HTML>
------=_NextPart_000_001F_01C8C103.B2A57670--Dimitrios,
The answer to all your questions regarding dsp utilization lies in using
a multi card setup wisely.
Chuck
"Dimitrios" <musurgNOSPAMio@otenetNOSPAM.gr> wrote:
>
>I love all your reverbs.
>Thank you for the predelay plugin !
>One thing is that it is too dsp heavy !
>Only 6 instances per card !
>EDS compressors can be had for 16 instances so maybe I can use one compressor
>pugin for just the lookahead working as predelay...
>I managed to make all your reverbs available as mono inserts !
>I would really love to see a dry/wet mix knob as to be able to take a real
>benefit from the insert usage of the reverbs.
>This would be mostly needed for Drumplate.
>This way you can use a mono version of the reverb at the insert and follow
>the panning of the istrument anf freeing the auxes.
>
>1. Is there a way to reduce dsp if the reveb plugins become mono ??
>This could free some dsp and there are times ,like snare, where mono reverb
>is preffered as to not occupy much stereo space from the mix. In this way
>the dry/wet mix knob would be essential
>
>2. A great room reverb is a must for Paris !
>The room already there cannot compete with "your" new halls and plates !
>I would love a great room reverb for an electric guitar.
>
>3. Your drumplate can only be used twice per card as opposed to dp pro hall
>which can have four of it !
>Is there a way to optimize that perhaps ? Maybe the less predelay would
>cure that ?
>
>Thanks for what you are doing for us !!
>I will contimue supporting.
>Will send more very soon...
>Regards,
>DimitriosHi everyone, I have a Q regarding sync. The weird part is that this may be
normal, I'm not sure. When I press play in Paris, Cubase starts rolling but
always slows down, then speeds up and then after about 15 seconds, seems to
stabilise. Is this normal using ADAT sync?
Here is the setup:
(Computer 1)Paris Adat sync out via 9pin serial cable into (Computer2 )Scope
syncplate 9pin Serial running Cubase SX3. In Cubase, I am using the ASIO
Audio device setting, sample rate is set the same in Paris and Scope. I
setup a midi click in Cubase via my old D4 and its very un-stable at first
as mentioned above. When I try the audio click in cubase, it sounds solid
but I can still see the timeline jump ahead and then slow down. When I try
midioverLan to sync, it works perfect but is not sample accurate over time
as is ADAT sync, correct? Is this normal? Does the DAKOTA, have this issue
syncing Cubase to Paris via ADAT?
Thanks in advance
Regards
RobertMy Dakota has no problem syncing Cubase 2 to Paris...can't speak for version
3
"Rob A" <mani1147athotmaildotcom> wrote in message news:483e1c37@linux...
> Hi everyone, I have a Q regarding sync. The weird part is that this may be
> normal, I'm not sure. When I press play in Paris, Cubase starts rolling
> but always slows down, then speeds up and then after about 15 seconds,
> seems to stabilise. Is this normal using ADAT sync?
> Here is the setup:
> (Computer 1)Paris Adat sync out via 9pin serial cable into
> (Computer2 )Scope syncplate 9pin Serial running Cubase SX3. In Cubase, I
> am using the ASIO Audio device setting, sample rate is set the same in
> Paris and Scope. I setup a midi click in Cubase via my old D4 and its very
> un-stable at first as mentioned above. When I try the audio click in
> cubase, it sounds solid but I can still see the timeline jump ahead and
> then slow down. When I try midioverLan to sync, it works perfect but is
> not sample accurate over time as is ADAT sync, correct? Is this normal?
> Does the DAKOTA, have this issue syncing Cubase to Paris via ADAT?
>
> Thanks in advance
> Regards
> Robert
>
>Thanks Don, are you using the "ASIO Audio device " in Cubase sync options?
"Don Nafe" <dnafe@rogers.com> wrote in message news:483e859f@linux...
> My Dakota has no problem syncing Cubase 2 to Paris...can't speak for
> version 3
>
>
> "Rob A" <mani1147athotmaildotcom> wrote in message news:483e1c37@linux...
>> Hi everyone, I have a Q regarding sync. The weird part is that this may
>> be normal, I'm not sure. When I press play in Paris, Cubase starts
>> rolling but always slows down, then speeds up and then after about 15
>> seconds, seems to stabilise. Is this normal using ADAT sync?
>> Here is the setup:
>> (Computer 1)Paris Adat sync out via 9pin serial cable into
>> (Computer2 )Scope syncplate 9pin Serial running Cubase SX3. In Cubase, I
>> am using the ASIO Audio device setting, sample rate is set the same in
>> Paris and Scope. I setup a midi click in Cubase via my old D4 and its
>> very un-stable at first as mentioned above. When I try the audio click in
>> cubase, it sounds solid but I can still see the timeline jump ahead and
>> then slow down. When I try midioverLan to sync, it works perfect but is
>> not sample accurate over time as is ADAT sync, correct? Is this normal?
>> Does the DAKOTA, have this issue syncing Cubase to Paris via ADAT?
>>
>> Thanks in advance
>> Regards
>> Robert
>>
>>
>
>Dear Tom,
I am glad you found a way to have two adat cards on same mec.
I have achived that on two mecs using the 4 snd 6 slots.
I have concluded that the last mec on the chain perhaps cannot have two adat
cards.
So the culprint must be that adat cards should be installed far away from
the other cards and always last.
Regards,
Dimitrios
"Tom Bruhl" <arpegio@comcast.net> wrote:
>
>
>Go figure. Didn't work before. It did today. It is a different ADAT =
>card than I had been
>trying as a second card. One happens to be a blue one in slot 9 and the
=
>new one is
>black in slot 8. 1x 8in in slot 1 and 1 x 8out in slot 2.
>
>Maybe it's the sequence of installing them? Use the last slot first so
=
>Paris looks down the whole=20
>line before moving on. Later install stuff before it to be recognized.
=
>Just a thought.
>
>Tom
>
>
>
>
>I choose Polesoft Lockspam to fight spam, and you?
>http://www.polesoft.com/refer.html
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3DContent-Type content=3D"text/html; =
>charset=3Diso-8859-1">
><META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Go figure. Didn't work =
>before. It did=20
>today. </FONT><FONT face=3DArial size=3D2>It is a different ADAT =
>card than I=20
>had been</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>trying as a second card. One =
>happens to=20
>be a blue one in slot 9 and the new one is</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>black in slot 8. 1x 8in in slot 1 =
>and 1 x=20
>8out in slot 2.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>Maybe it's the sequence of installing =
>them? =20
>Use the last slot first so Paris looks down the whole </FONT></DIV>
><DIV><FONT face=3DArial size=3D2>line before moving on. Later =
>install stuff=20
>before it to be recognized. Just a thought.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></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 size=3D2><BR><BR>I choose Polesoft Lockspam to fight spam, =
>and=20
>you?<BR><A=20
>href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer=
>.html</A> </FONT></DIV></BODY></HTML>
>
>Dear Rob,
Have you loaded inside scope sfp environement Syncplate source ?
I assume you have a syncplate addon card and thats why you have connected
Paris adat sync to syncplate's adat sync in, right ?
Now by openeing the Syncpale source under tools you have to select the same
MTC settings i.e 25 frames etc...
Then you have to use the ASIO2 dest64 module and there connect the Clk1 with
syncplate's clk out.
Have you done all these ?
Midi is NOT needed.
Regards,
Dimitrios
"Rob A" <mani1147athotmaildotcom> wrote:
>Hi everyone, I have a Q regarding sync. The weird part is that this may
be
>normal, I'm not sure. When I press play in Paris, Cubase starts rolling
but
>always slows down, then speeds up and then after about 15 seconds, seems
to
>stabilise. Is this normal using ADAT sync?
>Here is the setup:
>(Computer 1)Paris Adat sync out via 9pin serial cable into (Computer2 )Scope
>syncplate 9pin Serial running Cubase SX3. In Cubase, I am using the ASIO
>Audio device setting, sample rate is set the same in Paris and Scope. I
>setup a midi click in Cubase via my old D4 and its very un-stable at first
>as mentioned above. When I try the audio click in cubase, it sounds solid
>but I can still see the timeline jump ahead and then slow down. When I try
>midioverLan to sync, it works perfect but is not sample accurate over time
>as is ADAT sync, correct? Is this normal? Does the DAKOTA, have this issue
>syncing Cubase to Paris via ADAT?
>
>Thanks in advance
>Regards
>Robert
>
>Latest Dakota drivers and Cubase 3 works perfectly here.
Kim
"Don Nafe" <dnafe@rogers.com> wrote:
>My Dakota has no problem syncing Cubase 2 to Paris...can't speak for version
>3
>
>
>"Rob A" <mani1147athotmaildotcom> wrote in message news:483e1c37@linux...
>> Hi everyone, I have a Q regarding sync. The weird part is that this may
be
>> normal, I'm not sure. When I press play in Paris, Cubase starts rolling
>> but always slows down, then speeds up and then after about 15 seconds,
>> seems to stabilise. Is this normal using ADAT sync?
>> Here is the setup:
>> (Computer 1)Paris Adat sync out via 9pin serial cable into
>> (Computer2 )Scope syncplate 9pin Serial running Cubase SX3. In Cubase,
I
>> am using the ASIO Audio device setting, sample rate is set the same in
>> Paris and Scope. I setup a midi click in Cubase via my old D4 and its
very
>> un-stable at first as mentioned above. When I try the audio click in
>> cubase, it sounds solid but I can still see the timeline jump ahead and
>> then slow down. When I try midioverLan to sync, it works perfect but is
>> not sample accurate over time as is ADAT sync, correct? Is this normal?
>> Does the DAKOTA, have this issue syncing Cubase to Paris via ADAT?
>>
>> Thanks in advance
>> Regards
>> Robert
>>
>>
>
>I subscribed to the Stewart Macdonald (StewMac) newsletter recently.
They are a guitar parts and repair tools dealer. The newsletter goes
over repair/setup tricks, and I have learned a lot about guitars from
reading it. I wouldn't try most of the stuff they show, like how to make
frets fit properly on a fret job, but I always learn something
interesting about guitars. For instance I never knew fret wire has
little barbs in the part that goes into the finger board that hold it in
place.
http://www.stewmac.com/ in the upper left there is a spot to enter your
email to receive the newsletter.Hi Di, yes I have the syncplate source in my scope patchbay and I have the
same frame rate in Paris, and in syncplate setting but I was using the "
ASIO2 DEST" module and not the "ASIO2 DEST64" Do you think this would
cause it? Will try tonight when I get home.
"Dimitrios" <musxxx@otexxx.gr> wrote in message news:483e9094$1@linux...
>
> Dear Rob,
> Have you loaded inside scope sfp environement Syncplate source ?
> I assume you have a syncplate addon card and thats why you have connected
> Paris adat sync to syncplate's adat sync in, right ?
Correct
> Now by openeing the Syncpale source under tools you have to select the
> same
> MTC settings i.e 25 frames etc...
Correct
> Then you have to use the ASIO2 dest64 module and there connect the Clk1
> with
> syncplate's clk out.
This is where I was using the "ASIO2 dest" module.
> Have you done all these ?
> Midi is NOT needed.
> Regards,
> Dimitrios
>
> "Rob A" <mani1147athotmaildotcom> wrote:
>>Hi everyone, I have a Q regarding sync. The weird part is that this may
> be
>>normal, I'm not sure. When I press play in Paris, Cubase starts rolling
> but
>>always slows down, then speeds up and then after about 15 seconds, seems
> to
>>stabilise. Is this normal using ADAT sync?
>>Here is the setup:
>>(Computer 1)Paris Adat sync out via 9pin serial cable into
>>(Computer2 )Scope
>
>>syncplate 9pin Serial running Cubase SX3. In Cubase, I am using the ASIO
>
>>Audio device setting, sample rate is set the same in Paris and Scope. I
>
>>setup a midi click in Cubase via my old D4 and its very un-stable at first
>
>>as mentioned above. When I try the audio click in cubase, it sounds solid
>
>>but I can still see the timeline jump ahead and then slow down. When I try
>
>>midioverLan to sync, it works perfect but is not sample accurate over time
>
>>as is ADAT sync, correct? Is this normal? Does the DAKOTA, have this issue
>
>>syncing Cubase to Paris via ADAT?
>>
>>Thanks in advance
>>Regards
>>Robert
>>
>>
>Hi Di, i tried the ASIO2 dest64 module in scope and get the same results. I
included an mp3 of the click track. Man this is puzzling. I thought maybe
this was normal coming from the old ADAT days where it took a few seconds to
get everything locked-up properly but you guys running adat sync aren't
experiencing this at all rite?
Regards,
Rob
"Dimitrios" <musxxx@otexxx.gr> wrote in message news:483e9094$1@linux...
>
> Dear Rob,
> Have you loaded inside scope sfp environement Syncplate source ?
> I assume you have a syncplate addon card and thats why you have connected
> Paris adat sync to syncplate's adat sync in, right ?
> Now by openeing the Syncpale source under tools you have to select the
> same
> MTC settings i.e 25 frames etc...
> Then you have to use the ASIO2 dest64 module and there connect the Clk1
> with
> syncplate's clk out.
> Have you done all these ?
> Midi is NOT needed.
> Regards,
> Dimitrios
>
> "Rob A" <mani1147athotmaildotcom> wrote:
>>Hi everyone, I have a Q regarding sync. The weird part is that this may
> be
>>normal, I'm not sure. When I press play in Paris, Cubase starts rolling
> but
>>always slows down, then speeds up and then after about 15 seconds, seems
> to
>>stabilise. Is this normal using ADAT sync?
>>Here is the setup:
>>(Computer 1)Paris Adat sync out via 9pin serial cable into
>>(Computer2 )Scope
>
>>syncplate 9pin Serial running Cubase SX3. In Cubase, I am using the ASIO
>
>>Audio device setting, sample rate is set the same in Paris and Scope. I
>
>>setup a midi click in Cubase via my old D4 and its very un-stable at first
>
>>as mentioned above. When I try the audio click in cubase, it sounds solid
>
>>but I can still see the timeline jump ahead and then slow down. When I try
>
>>midioverLan to sync, it works perfect but is not sample accurate over time
>
>>as is ADAT sync, correct? Is this normal? Does the DAKOTA, have this issue
>
>>syncing Cubase to Paris via ADAT?
>>
>>Thanks in advance
>>Regards
>>Robert
>>
>>
>
thanks !!EK Sound <ask_me@nospam.net> wrote:
>A SPDIF bounce would put Word Clock into the fray... A disc bounce would
>use the Paris internal clock and not make use of any external clock. If
>you had a really high quality clock source, it may make a noticeable
>difference with a SPDIF bounce.
>
>David.
>
>Cujo wrote:
>> Hmm, now I am curious, does anyone else hear a diff?
>> Is the SPDIF file more open and clear?
>>
>>
>> "Rod Lincoln" <rlincoln@nospam.kc.rr.com> wrote:
>>> Ted, If I remember right, rendered files were never in dispute, as Brian
>> T
>>> did a 10th generation render and it still canceled out. What was in dispute
>>> was disk bounce in 3.0 versues spdif bounce in 3.0. Sakis held the position
>>> that disk bounce in 3.0 was not as accurate as spdif bounce.
>>> Rod
>>> "Ted Gerber" <tedgerber@rogers.com> wrote:
>>>> I just recently started rendering files with native plugins
>>>> after testing the rendered against the edited original and
>>>> flipping the phase (copy channel settings to the new track
>>>> with the rendered file etc etc) I've been happy with the
>>>> result. Any prior nudging for latency (with UAD for
>>>> instance) is accounted for in the newly rendered file and it
>>>> saves time and horsepower. I hadn't used PARIS for a few years
>>>> until last summer, and remembered the debate between Sakis and
>>>> others over whether rendered files - with or without plugins -
>>>> were as accurate as bounced files. So far so good.
>>>>
>>>> Ted
>>>>
>>As I have listened (not with any great detail mind you) I have not noticed
a difference from the rendered files. I was a bit apprehensive as I have
always taked the "real time" approach to printing stems. Obviously, from
a time consumption stand point it can't be beat.
Tyrone
EK Sound <ask_me@nospam.net> wrote:
>A SPDIF bounce would put Word Clock into the fray... A disc bounce would
>use the Paris internal clock and not make use of any external clock. If
>you had a really high quality clock source, it may make a noticeable
>difference with a SPDIF bounce.
>
>David.
>
>Cujo wrote:
>> Hmm, now I am curious, does anyone else hear a diff?
>> Is the SPDIF file more open and clear?
>>
>>
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Fri May 22 11:22:31 PDT 2026
Total time taken to generate the page: 0.12620 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
