t;/BLOCKQUOTE> I choose Polesoft Lockspam to fight spam, = and=20 you? <A=20 href=3D"http://www.polesoft.com/refer.html">http://www.polesoft.com/refer= ..html ------=_NextPart_000_0025_01C89BED.C88BAAD0--i mean that no one has the paris source code to develop the app to it's fullestHi Dimitrios, This is huge!!! I did buy faderworks to support the cause. I'll have to get this update. Great stuff!!! Mike "Dimitrios" <musurgio@otenet.gr> wrote: > > > >The author promised me a new upgrade for Faderworks tailored to us Paris users >!!! >This the page where you put all your plugins names and known latencies so >every time you put a plugin on your audio track you just push the om button >and all other Paris audio tracks get alligned !! >What else could we ask from a third party plugin developer ?? >He first made a PDC for us when I kindly asked him so and then he makes this >update to make it even better for all of us Paris users ( am I alone ??) >For all thos that have not bought Faderworks please do so to show our gratitute >because he will make our work with Paris so much easier ! >DeeJ come on back we are waiting for you, jump on Paris again ! >Regards, >Dimitrios >No Mac OS9 version! boo hoo! DCThis is the Alpha
Re: Something I'm discovering about native
version. In a few days I will the full beta version to test... I truly believe that faderworks is a godsend plugin for Paris. Not to overcome the 32 groups it has where you can solo mute and change volume for ecrtain audio tracks across all submixes ! Cheers, Dimitrios "Mike Audet" <mike@..> wrote: > >Hi Dimitrios, > >This is huge!!! I did buy faderworks to support the cause. I'll have to >get this update. > >Great stuff!!! > >Mike > >"Dimitrios" <musurgio@otenet.gr> wrote: >> >> >> >>The author promised me a new upgrade for Faderworks tailored to us Paris >users >>!!! >>This the page where you put all your plugins names and known latencies so >>every time you put a plugin on your audio track you just push the om button >>and all other Paris audio tracks get alligned !! >>What else could we ask from a third party plugin developer ?? >>He first made a PDC for us when I kindly asked him so and then he makes >this >>update to make it even better for all of us Paris users ( am I alone ??) >>For all thos that have not bought Faderworks please do so to show our gratitute >>because he will make our work with Paris so much easier ! >>DeeJ come on back we are waiting for you, jump on Paris again ! >>Regards, >>Dimitrios >> >This is a multi-part message in MIME format. ------=_NextPart_000_0037_01C89BF6.9FC977E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am patiently waiting . . .=20 "Dimitrios" <musurgio@otenet.gr> wrote in message = news:47ffd102$1@linux... This is the Alpha version. In a few days I will the full beta version to test... I truly believe that faderworks is a godsend plugin for Paris. Not to overcome the 32 groups it has where you can solo mute and = change volume for ecrtain aud
io tracks across all submixes ! Cheers, Dimitrios "Mike Audet" <mike@..> wrote: > >Hi Dimitrios, > >This is huge!!! I did buy faderworks to support the cause. I'll = have to >get this update. > >G
reat stuff!!! > >Mike > >"Dimitrios" <musurgio@otenet.gr> wrote: >> >> >> >>The author promised me a new upgrade for Faderworks tailored to us = Paris >users >>!!! >>This the page where you put all your plugins names and known = latencies so >>every time you put a plugin on your audio track you just push the om = button >>and all other Paris audio tracks get alligned !! >>What else could we ask from a third party plugin developer ?? >>He first made a PDC for us when I kindly asked him so and then he = makes >this >>update to make it even better for all of us Paris users ( am I alone = ??) >>For all thos that have not bought Faderworks please do so to show = our gratitute >>because he will make our work with Paris so much easier ! >>DeeJ come on back we are waiting for you, jump on Paris again ! >>Regards, >>Dimitrios >> > I choose Polesoft Lockspam to fight spam, and you? http://www.polesoft.com/refer.html ------=_NextPart_000_0037_01C89BF6.9FC977E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am patiently waiting . . . = <BLOCKQUOTE=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> "Dimitrios" <<A=20 href=3D"mailto:musurgio@otenet.gr">musurgio@otenet.gr> wrote in = message=20 news:47ffd102$1@linux... This= is=20 the Alpha version. In a few days I will the full beta version to=20 test... I truly believe that faderworks is a godsend plugin for=20 Paris. Not to overcome the 32 groups it has where you can solo mute = and=20 change volume for ecrtain audio tracks across all submixes=20 ! Cheers, Dimitrios "Mike Audet" <mike@..>=20 wrote: > >Hi Dimitrios, > >This is = huge!!! I did=20 buy faderworks to support the cause. I'll have to >get = this=20 update. > >Great=20 stuff!!! > >Mike >
/> will be investigating the ins-and-outs of posting whole sections from the actual manual inline so they can be woven in with practical observations. The technologies behind this thing are incredible; there are so many things you can do with this data once you've got it entered, it's amazing. Sortable plugin databases so you can find all compressors or all delays and choose one by feature or applicability (hey, don't laugh; you may not think you need this now, but look at how fast Mike Audet is developing new ones now he's hitting his stride!); key commands databased so you can pull up all the editing modifiers in a hurry - I have hopes that as this grows it can become a "leave open in the background" quick reference/help file. It's als
o going to be a place to collect some of the history and "back-story" of the platform, its developers and designers. I want to take a second here and express my gratitude to some particular people for their support, enthusiasm and cooperation in advance of rollout; Aaron Allen, Chuck Duffy, "Hiddensounds" Kim, Steve "artguy", Mike Arnao and Mike Audet. For their invaluable work as PARIS' "de facto" maintainers of the Archives, Steve "artguy" (whose last name I now commit to spelling correctly), John Bercik and Doug Wellington - and Kim for hist maintenance of the NG, essentially the "collective memory" of the community - and last but not least those many whose contributed insights form the backbone of the Wiki. An extremely quick tutorial is available linked to the front page, followed by detailed documentation afterwards. You aren't going to believe how easy - and even fun - it is when you get the hang of it. But there's a test area called the SandBox where you can mess around without hurting anything. Okidoki. More to come, but I'll shut up now. Kim's kindly made the "theproject" NG available for Wiki business, s
, I'll secure it, but until then, welcome one and all!". So > registration is automatic, nobody "approves it". > > Plans for this Wiki are fairly ambitious, but I'd hope realistic and > sustainable. For example - amongst other developments, Aaron Allen and > Chuck > Duffy have graciously given their consent for the Wiki to serve the Brian > Tankersley video, which (pending confirmation from BT), I'd like to see > broken into chapters and inserted in the relevant topics. I'd do this > pretty much ASAP pending hearing back from BT (anyone got a current > contact > email, shoot it to me privately). > > In addition, it's "skinnable" so the plain vanilla interface will go away > at > some point (when I get time) and be replaced by a slicker custom "look". I > will be investigating the ins-and-outs of posting whole sections from the > actual manual inline so they can be woven in with practical observations. > The technologies behind this thing are incredible; there are so many > things > you can do with this data once you've got it entered, it's amazing. > Sortable > plugin databases so you can find all compressors or all delays and choose > one by feature or applicability (hey, don't laugh; you may not think you > need this now, but look at how fast Mike Audet is developing new ones now > he's hitting his stride!); key commands databased so you can pull up all > the > editing modifiers in a hurry - I have hopes that as this grows it can > become > a "leave open in the background" quick reference/help file. It's also > going > to be a place to collect some of the history and "back-story" of the > platform, its developers and designers. > > I want to take a second here and express my gratitude to some particular > people for their support, enthusiasm and cooperation in advance of > rollout; > Aaron Allen, Chuck Duffy, "Hiddensounds" Kim, Steve "artguy", Mike Arnao > and > Mike Audet. > > For their invaluable work as PARIS' "de facto" maintainers of the > Archives, > Steve "artguy" (whose last name I now commit to spelling correctly), John > Bercik and Doug Wellington - and Kim for hist maintenance of the NG, > essentially the "collective memory" of the community - and last but not > least those many whose contributed insights form the backbone of the Wiki. > > An extremely quick tutorial is available linked to the front page, > followed > by detailed documentation afterwards. You aren't going to believe how > easy - > and even fun - it is when you get the hang of it. But there's a test area > called the SandBox where you can mess around without hurting anything. > > Okidoki. More to come, but I'll shut up now. Kim's kindly made the > "theproject" NG available for Wiki business, so if you want to talk > technical specifics, ie formatting, skins, concept, data organization, > that'd be a great place to keep it grouped and threaded together. > > > <<<<< > > > And now, the Wiki. I hope you enjoy it. (watch out for bad line wraps in > the > URLs) > > Home page - > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=HomeP age > > Some pages are more fleshed in than others: > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=BugsT roubleshooting > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Sessi onTracking > > > Some are "getting there": > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Windo wPatchBay > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Acces sWin > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Paris NoNos > > > Sample plugin page: > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=NoLim it > > > And remember - if you see bad info there, or something missing - don't > complain, log in and fix it! If I missed your contribution - sorry! Log in > and fix it! If I... well, you get the picture. > > Welcome, and enjoy. > > - Kerry > > >Guess it's time to complile a list of known latencies for plugins...maybe the new Wiki site might be a good place to put these thoughts "Dimitrios" <musurgio@otenet.gr> wrote in message news:47ffad71$1@linux... > > The author promised me a new upgrade for Faderworks tailored to us Paris > users > !!! > This the page where you put all your plugins names and known latencies so > every time you put a plugin on your audio track you just push the om > button > and all other Paris audio tracks get alligned !! > What else could we ask from a third party plugin developer ?? > He first made a PDC for us when I kindly asked him so and then he makes > this > update to make it even better for all of us Paris users ( am I alone ??) > For all thos that have not bought Faderworks please do so to show our > gratitute > because he will make our work with Paris so much easier ! > DeeJ come on back we are waiting for you, jump on Paris again ! > Regards, > Dimitrios >Another thought - as Mike's plugs have no presets maybe we can start compiling presets by using snapshots of his plugs. Again any thoughts "Kerry Galloway" <kg@kerrygalloway.com> wrote in message news:C4252755.2C37%kg@kerrygalloway.com... > Greetings all! > > Technology sure changes fast. A piece of technology became available to me > a > while back that finally allowed me to build what I used to just dream > about. > > Namely - there is now a PARISWiki where PARIS aficionados can compile all > existing data concerning PARIS. I've started the ball rolling by beginning > the process of converting and compiling the varied and valuable > information > found amongst the various official and unofficial FAQs. > > You might want to read the rest of the email before you click, but the > site > is linked at the bottom if you're not a "manuals" type. > > For those unfamiliar with the term - a "Wiki" is a collaborative, > community-driven encyclopedia. You don't complain to someone when you spot > something wrong or incomplete or missing - you *fix it yourself*. To do > this > is trivially easy - once you're registered and logged in, double-click > directly on the page you're reading and an editor opens. You can begin > entering/editing text right there. If you want to create a new page, you > just type a "CamelCase" word as you're editing (any word with an initial > cap > and another capital within it, like AppMessage) and when you "store" the > page the cunning macros behind the Wiki turn it into a hyperlink with > dashes > under it. Click on this and a new page with that name is created and saved > (before you do that, you might want to look at the page index to make sure > you aren't creating a duplicate). Yeah - you read that right - essentially > creating a hyperlink to a non-existing page, and then clicking on it, > actually creates the page. > > Now some important info. > > This site is *free*. By *free*, I mean - I am donating the time to build > and > maintain it; donating the bandwidth and server space to serve it; there > are > no "gotchas", no "enter your credit card", no "donate" buttuns and no ads; > I > will never sell, trade, share or knowingly make your email addresses > available to others. In short, this is a "labour of love". Unless the > bandwidth goes absolutely insane, I can't see ever needing to "pass the > hat" > for donations; if that ever happened (I doubt it, I have up to three > terabytes of bandwidth on the account it's served on) I'd talk it through > with the community before doing that in case someone in the community > simply > wanted to serve it elsewhere. Failing those sort of unforeseen and > unlikely > circumstances, I am happy to continue serving this for at least the next > eighteen months. If things go well, I have no problem keeping it going for > as long after that as I can foresee (ask me if you want to mirror it > elsewhere - assuming you don't want to mirror it on some white supremacist > hate site I'll almost certainly say yes, but let's make it a real mirror > and > not a copy so multiple sites don't develop different content). > > What I *would* ask for in return, however is participation. If I wanted my > own Private PARIS Manual, I could have done it on my own hard drive easily > without the hassle of maintaining it on a site. This Wiki is meant to be a > community service - and it is also intended to be nearly entirely > community-driven. As long as the community continues to participate, not > merely by reading but by *contributing information*, I'll continue to do > my > part by running the back office. I hope that seems fair. > > Aside from that, the conditions of use are largely common sense (I think > everyone's smart enough not to kill it instantly by posting illegal or > offensive material; arguments stay offsite; let's keep it focused; etc) > and > are printed on the front page. Registration is automatic (ie open to any > PARIS user, past or present, no matter how casual a user) and takes all of > about thirty seconds. > > A further note on registration - it's open for all. The technology exists > to > take it private, to require admin approval for who registers, etc etc; it > can be made very secure. However I'd like to start by assuming "if I need > to > secure it, I'll secure it, but until then, welcome one and all!". So > registration is automatic, nobody "approves it". > > Plans for this Wiki are fairly ambitious, but I'd hope realistic and > sustainable. For example - amongst other developments, Aaron Allen and > Chuck > Duffy have graciously given their consent for the Wiki to serve the Brian > Tankersley video, which (pending confirmation from BT), I'd like to see > broken into chapters and inserted in the relevant topics. I'd do this > pretty much ASAP pending hearing back from BT (anyone got a current > contact > email, shoot it to me privately). > > In addition, it's "skinnable" so the plain vanilla interface will go away > at > some point (when I get time) and be replaced by a slicker custom "look". I > will be investigating the ins-and-outs of posting whole sections from the > actual manual inline so they can be woven in with practical observations. > The technologies behind this thing are incredible; there are so many > things > you can do with this data once you've got it entered, it's amazing. > Sortable > plugin databases so you can find all compressors or all delays and choose > one by feature or applicability (hey, don't laugh; you may not think you > need this now, but look at how fast Mike Audet is developing new ones now > he's hitting his stride!); key commands databased so you can pull up all > the > editing modifiers in a hurry - I have hopes that as this grows it can > become > a "leave open in the background" quick reference/help file. It's also > going > to be a place to collect some of the history and "back-story" of the > platform, its developers and designers. > > I want to take a second here and express my gratitude to some particular > people for their support, enthusiasm and cooperation in advance of > rollout; > Aaron Allen, Chuck Duffy, "Hiddensounds" Kim, Steve "artguy", Mike Arnao > and > Mike Audet. > > For their invaluable work as PARIS' "de facto" maintainers of the > Archives, > Steve "artguy" (whose last name I now commit to spelling correctly), John > Bercik and Doug Wellington - and Kim for hist maintenance of the NG, > essentially the "collective memory" of the community - and last but not > least those many whose contributed insights form the backbone of the Wiki. > > An extremely quick tutorial is available linked to the front page, > followed > by detailed documentation afterwards. You aren't going to believe how > easy - > and even fun - it is when you get the hang of it. But there's a test area > called the SandBox where you can mess around without hurting anything. > > Okidoki. More to come, but I'll shut up now. Kim's kindly made the > "theproject" NG available for Wiki business, so if you want to talk > technical specifics, ie formatting, skins, concept, data organization, > that'd be a great place to keep it grouped and threaded together. > > > <<<<< > > > And now, the Wiki. I hope you enjoy it. (watch out for bad line wraps in > the > URLs) > > Home page - > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=HomeP age > > Some pages are more fleshed in than others: > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=BugsT roubleshooting > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Sessi onTracking > > > Some are "getting there": > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Windo wPatchBay > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Acces sWin > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Paris NoNos > > > Sample plugin page: > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=NoLim it > > > And remember - if you see bad info there, or something missing - don't > complain, log in and fix it! If I missed your contribution - sorry! Log in > and fix it! If I... well, you get the picture. > > Welcome, and enjoy. > > - Kerry > > >You're right, these guys are a blessing for paris. For me though the features of paris are too long in the tooth. Things like 16 channel submixes I find really limiting and I could never go back from Cubase. I wish everyone the best and hope you make tons of great music. Edmund the ass clown needs to release the fucking source code and get over it with the stupid pace challenge shit. He's got balls of steel thinking he can make money off new licenses and give zero support. Then you guys could really push it to the final limit instead of leaving the hardware shackled. I bet some bright programmer could even totally rewrite paris or figure out a way to get cubase or reaper to interface with it making limits like the 16 channel groupings transparent. You never know. John john "James McCloskey" <excelsm@hotmail.com> wrote: > >Now Aaron, it says right on ID's web site,"New products coming soon... " > > >Sorry, I couldn't resist; ) > >Thanks to Mike A. and these guys, there are new Paris products in 2008! : > ) > >"Aaron Allen" <know-spam@not_here.dude> wrote: >>I wouldn't say 'no one', but it ain't likely to ever see the light of day. >> >>AA >> >>"John" <no@no.com> wrote in message news:47ffc937$1@linux... >>> >>> i mean that no one has the paris source code to develop the app to it's > >>> fullest >> >> >I've played around a little with the old version of Faderworks, and missed the posibility to manually punch in the overall latency. I sometimes use virtually submixes, and this feature will make it more easy to maintain a constant latency across both live and virtual submixes. Is it possible to implement this in the new version? Bjorn R "Dimitrios" <musurgio@otenet.gr> wrote in message news:47ffad71$1@linux... > > The author promised me a new upgrade for Faderworks tailored to us Paris users > !!! > This the page where you put all your plugins names and known latencies so > every time you put a plugin on your audio track you just push the om button > and all other Paris audio tracks get alligned !! > What else could we ask from a third party plugin developer ?? > He first made a PDC for us when I kindly asked him so and then he makes this > update to make it even better for all of us Paris users ( am I alone ??) > For all thos that have not bought Faderworks please do so to show our gratitute > because he will make our work with Paris so much easier ! > DeeJ come on back we are waiting for you, jump on Paris again ! > Regards, > Dimitrios >I.o.w. what I'm looking for is the possibility to set a fixed, global latency that overrules the automatic one. Bjorn R "BR" <nospam@nospam.com> wrote in message news:4800934a@linux... > I've played around a little with the old version of Faderworks, and missed > the posibility to manually punch in the overall latency. I sometimes use > virtually submixes, and this feature will make it more easy to maintain a > constant latency across both live and virtual submixes. Is it possible to > implement this in the new version? > > Bjorn R > > > "Dimitrios" <musurgio@otenet.gr> wrote in message news:47ffad71$1@linux... > > > > The author promised me a new upgrade for Faderworks tailored to us Paris > users > > !!! > > This the page where you put all your plugins names and known latencies so > > every time you put a plugin on your audio track you just push the om > button > > and all other Paris audio tracks get alligned !! > > What else could we ask from a third party plugin developer ?? > > He first made a PDC for us when I kindly asked him so and then he makes > this > > update to make it even better for all of us Paris users ( am I alone ??) > > For all thos that have not bought Faderworks please do so to show our > gratitute > > because he will make our work with Paris so much easier ! > > DeeJ come on back we are waiting for you, jump on Paris again ! > > Regards, > > Dimitrios > > > >I believe we got the answer here why Edmund need the source code for himself: http://www.intelligentdevices.com/ So, in a year or five, it seems "soon" things will be happen with a new Paris version;-) "John" <no@no.com> skrev i en meddelelse news:4800907b$1@linux... > > Yo
Re: Something I'm discovering about native (Thad)
u're right, these guys are a blessing for paris. For me though the > features > of paris are too long in the tooth. Things like 16 channel submixes I > find > really limiting and I could never go back from Cubase. I wish everyone > the > best and hope you make tons of great music. Edmund the ass clown needs to > release the fucking source code and get over it with the stupid pace > challenge > shit. > > He's got balls of steel thinking he can make money off new licenses and > give > zero support. > > Then you guys could really push it to the final limit instead of leaving > the hardware shackled. I bet some bright programmer could even totally > rewrite > paris or figure out a way to get cubase or reaper to interface with it > making > limits like the 16 channel groupings transparent. You never know. > > John > > john > > "James McCloskey" <excelsm@hotmail.com> wrote: >> >>Now Aaron, it says right on ID's web site,&quot
/> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Windo wPatchBay http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Acces sWin http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Paris NoNos Sample plugin page: http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=NoLim it And remember - if you see bad info there, or something missing - don't complain, log in and fix it! If I missed your contribution - sorry! Log in and fix it! If I... well, you get the picture. Welcome, and enjoy. - KerryI wouldn't say 'no one', but it ain't likely to ever see the light of day. AA "John" <no@no.com> wrote in message news:47ffc937$1@linux... > > i mean that no one has the paris source code to develop the app to it's > fullestBill L <bill@billlorentzen.com> wrote: >I guess the question still unanswered is how important is recording >tracks at hi res, or is 96k+ also unnecessary? Well EQ processing, even if under 20k, processes across the timeline, hence it may potentially be more accurate with more data. I don't know enough about the maths involved to be accurate in my guess though, so I couldn't say for sure either way. I certainly see potential there though for better results at the higher sample rate. 24bit and above was bordering on unnecessary in the first place for general purpose band recording. Even at 16 bits, if you sum the tracks at zero, you end up with another bit of resolution above the 16 every time you double the tracks. So 2 tracks = 17 bits. 4 Tracks needs 18 bits, and 8 tracks needs 19 bits to store the result unaltered without resolution loss. Of course if, say, your song starts with a solo acoustic guitar part, and you plan to apply gain (even through compression) then you'll start to get past the 16 bit resolution of the source track. Assuming your source track was recorded relatively hot though it's unlikely anybody listening in a normal environment will notice that you've dropped to 15 or 14 bit resolution for a short time, especially if you have a full resolution reverb applied. But we'd need somebody with a good understanding of eq plugin operation to answer the high sample rate question. Potentially the answer might well be different for different eq designs. Cheers, Kim. > >Kim wrote: >> "DC" <dc@spammersinhell.com> wrote: >>> Our test results indicate that all of these recordings >>> could be released on conventional CDs with no audible >>> difference. They would not, however, find such a reliable >>> conduit to the homes of those with the systems and listening >>> habits to appreciate them. The secret, for two-channel >>> recordings at least, seems to lie not in the high-bit recording >>> ----------------- >>> >>> Interesting huh? >>> >>> DC >> >> Very much so, especially considering they were using proper audiophile quality >> recordings which presumably would be more likely show up any issues. >> >> Very very interesting. Amazing that these tests weren't done years ago. >> >> Cheers, >> Kim.Now Aaron, it says right on ID's web site,"New products coming soon... " Sorry, I couldn't resist; ) Thanks to Mike A. and these guys, there are new Paris products in 2008! : ) "Aaron Allen" <know-spam@not_here.dude> wrote: >I wouldn't say 'no one', but it ain't likely to ever see the light of day. > >AA > >"John" <no@no.com> wrote in message news:47ffc937$1@linux... >> >> i mean that no one has the paris source code to develop the app to it's >> fullest > >james...relax. $399.00 for support, i'd read the manual first...if i
back from Apple >>>>>and just sold me his personal copy of Logic 8 cheap, I'm thinking he >knows >>>>>something. Next week is NAB. I wonder if they are going to combine >everything >>>>>in to one package??? >>>>> >>>>> >>>>> >>>>>"TCB" <nobody@ishere.com> wrote: >>>>>> >>>>>>James just wants to remind everyone how great Apple is. Keep moving >along, >>>>>>nothing to see here . . . >>>>>> >>>>>>TCB >>>>>> >>>>>>rick <parnell68@hotmail.com> wrote: >>>>>>>maybe i'm missing something but it looks to me to be video oriented. >>>>>>> >>>>>>> >>>>>>> >>>>>>>On 10 Apr 2008 01:17:58 +1000, "James McCloskey" >>>>>>><excelsm@hotmail.com> wrote: >>>>>>> >>>>>>>> >>>>>>>>"James McCloskey" <excelsm@hotmail.com> wrote: >>>>>>>>> >>>>>>>>>http://www.apple.com/finalcutserver/?sr=hotnews >>>>>>>>> >>>>>>>>>I have a feeling that there is going to be a new version of Logic >released >>>>>>>>>soon. Maybe a new version of FCP, something's up. >>>>>>> >>>>>> >>>> >>Outstanding double thumbs up! "Kerry Galloway" <kg@kerrygalloway.com> wrote in message news:C4252755.2C37%kg@kerrygalloway.com... > Greetings all! > > Technology sure changes fast. A piece of technology became available to me > a > while back that finally allowed me to build what I used to just dream > about. > > Namely - there is now a PARISWiki where PARIS aficionados can compile all > existing data concerning PARIS. I've started the ball rolling by beginning > the process of converting and compiling the varied and valuable > information > found amongst the various official and unofficial FAQs. > > You might want to read the rest of the email before you click, but the > site > is linked at the bottom if you're not a "manuals" type. > > For those unfamiliar with the term - a "Wiki" is a collaborative, > community-driven encyclopedia. You don't complain to someone when you spot > something wrong or incomplete or missing - you *fix it yourself*. To do > this > is trivially easy - once you're registered and logged in, double-click > directly on the page you're reading and an editor opens. You can begin > entering/editing text right there. If you want to create a new page, you > just type a "CamelCase" word as you're editing (any word with an initial > cap > and another capital within it, like AppMessage) and when you "store" the > page the cunning macros behind the Wiki turn it into a hyperlink with > dashes > under it. Click on this and a new page with that name is created and saved > (before you do that, you might want to look at the page index to make sure > you aren't creating a duplicate). Yeah - you read that right - essentially > creating a hyperlink to a non-existing page, and then clicking on it, > actually creates the page. > > Now some important info. > > This site is *free*. By *free*, I mean - I am donating the time to build > and > maintain it; donating the bandwidth and server space to serve it; there > are > no "gotchas", no "enter your credit card", no "donate" buttuns and no ads; > I > will never sell, trade, share or knowingly make your email addresses > available to others. In short, this is a "labour of love". Unless the > bandwidth goes absolutely insane, I can't see ever needing to "pass the > hat" > for donations; if that ever happened (I doubt it, I have up to three > terabytes of bandwidth on the account it's served on) I'd talk it through > with the community before doing that in case someone in the community > simply > wanted to serve it elsewhere. Failing those sort of unforeseen and > unlikely > circumstances, I am happy to continue serving this for at least the next > eighteen months. If things go well, I have no problem keeping it going for > as long after that as I can foresee (ask me if you want to mirror it > elsewhere - assuming you don't want to mirror it on some white supremacist > hate site I'll almost certainly say yes, but let's make it a real mirror > and > not a copy so multiple sites don't develop different content). > > What I *would* ask for in return, however is participation. If I wanted my > own Private PARIS Manual, I could have done it on my own hard drive easily > without the hassle of maintaining it on a site. This Wiki is meant to be a > community service - and it is also intended to be nearly entirely > community-driven. As long as the community continues to participate, not > merely by reading but by *contributing information*, I'll continue to do > my > part by running the back office. I hope that seems fair. > > Aside from that, the conditions of use are largely common sense (I think > everyone's smart enough not to kill it instantly by posting illegal or > offensive material; arguments stay offsite; let's keep it focused; etc) > and > are printed on the front page. Registration is automatic (ie open to any > PARIS user, past or present, no matter how casual a user) and takes all of > about thirty seconds. > > A further note on registration - it's open for all. The technology exists > to > take it private, to require admin approval for who registers, etc etc; it > can be made very secure. However I'd like to start by assuming "if I need > to > secure it
think you >> need this now, but look at how fast Mike Audet is developing new ones now >> he's hitting his stride!); key commands databased so you can pull up all >> the >> editing modifiers in a hurry - I have hopes that as this grows it can >> become >> a "leave open in the background" quick reference/help file. It's also >> going >> to be a place to collect some of the history and "back-story" of the >> platform, its developers and designers. >> >> I want to take a second here and express my gratitude to some particular >> people for their support, enthusiasm and cooperation in advance of >> rollout; >> Aaron Allen, Chuck Duffy, "Hiddensounds" Kim, Steve "artguy", Mike Arnao >> and >> Mike Audet. >> >> For their invaluable work as PARIS' "de facto" maintainers of the >> Archives, >> Steve "artguy" (whose last name I now commit to spelling correctly), John >> Bercik and Doug Wellington - and Kim for hist maintenance of the NG, >> essentially the "collective memory" of the community - and last but not >> least those many whose contributed insights form the backbone of the Wiki. >> >> An extremely quick tutorial is available linked to the front page, >> followed >> by detailed documentation afterwards. You aren't going to believe how >> easy - >> and even fun - it is when you get the hang of it. But there's a test area >> called the SandBox
RIS/wikka.php?wakka=Paris NoNos >> >> >> Sample plugin page: >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=NoLim it >> >> >> And remember - if you see bad info there, or something missing - don't >> complain, log in and fix it! If I missed your contribution - sorry! Log in >> and fix it! If I... well, you get the picture. >> >> Welcome, and enjoy. >> >> - Kerry >> >> >> > >> Guess it's time to complile a list of known latencies for plugins...maybe > the new Wiki site might be a good place to put these Yep. Classic type of material for the Wiki. Getting a page up on this with a look-up table (and what latencies translate to in clicks on the "nudge" buttons) will be coming ASAP. Contributions welcome! I want to handle things like this as a coherent project so it all winds up in the same place in an easy-to-access format. I'm thinking the best way is Excel spreadsheet; my wife just happens to be a database wizard and says she's happy to whip up modern, easy-to-use front ends for the website - all we need to do is the data entry. - Kerry On 4/12/08 3:08 AM, in article 48008cd9@linux, "Don Nafe" <dnafe@rogers.com> wrote: > Guess it's time to complile a list of known latencies for plugins...maybe > the new Wiki site might be a good place to put these > > thoughts > > "Dimitrios" <musurgio@otenet.gr> wrote in message news:47ffad71$1@linux... >> >> The author promised me a new upgrade for Faderworks tailored to us Paris >> users >> !!! >> This the page where you put all your plugins names and known latencies so >> every time you put a plugin on your audio track you just push the om >> button >> and all other Paris audio tracks get alligned !! >> What else could we ask from a third party plugin developer ?? >> He first made a PDC for us when I kindly asked him so and then he makes >> this >> update to make it even better for all of us Paris users ( am I alone ??) >> For all thos that have not bought Faderworks please do so to show our >> gratitute >> because he will make our work with Paris so much easier ! >> DeeJ come on back we are waiting for you, jump on Paris again ! >> Regards, >> Dimitrios >> > >Dimitrios, I'm wondering - I've never used FaderWorks, but seeing as plugin latencies are absolute and repeatable across systems - are there any plans to include a database of the commonly used plugins so Faderworks just recognizes them and sets their latencies automatically? Yes, I know it's lazy - and the current version doesn't seem to be much of a hassle at all. But you gotta admit, it'd be elegant. All that seems necessary is for the most commonly used plugins to be databased by Faderworks in advance rather than being manually entered and for the software to do what software does best (which is to go look stuff up and write it somewhere else). Or maybe I'm misunderstanding how it works, and it does this already? - Kerry On 4/11/08 11:26 AM, in article 47ffad71$1@linux, "Dimitrios" <musurgio@otenet.gr> wrote: > > The author promised me a new upgrade for Faderworks tailored to us Paris users > !!! > This the page where you put all your plugins names and known latencies so > every time you put a plugin on your audio track you just push the om button > and all other Paris audio tracks get alligned !! > What else could we ask from a third party plugin developer ?? > He first made a PDC for us when I kindly asked him so and then he makes this > update to make it even better for all of us Paris users ( am I alone ??) > For all thos that have not bought Faderworks please do so to show our > gratitute > because he will make our work with Paris so much easier ! > DeeJ come on back we are waiting for you, jump on Paris again ! > Regards, > Dimitriossoon ! hahaha, i think i'll pass on anything he comes out withthese guys are "writing" on buildings using lasers http://www.youtube.com/watch?v=sm5NoiLxOOAOk..Now, I'm on-board with fader works. I'll be back on Paris this summer..So, this update is a good one.. P.S. Maybe we could get those folks ove at Solid State Logic http://www.solid-state-logic.com/music/Pro-Convert/index.asp (EDL Convert) to write a session conversion for Paris. That way tjose of us who are on other DAWS, can open other formats and so on..?? It's worth a try.. "Dimitrios" <musurgio@otenet.gr> wrote: > > > >The author promised me a new upgrade for Faderworks tailored to us Paris users >!!! >This the page where you put all your plugins names and known latencies so >every time you put a plugin on your audio track you just push the om button >and all other Paris audio tracks get alligned !! >What else could we ask from a third party plugin developer ?? >He first made a PDC for us when I kindly asked him so and then he makes this >update to make it even better for all of us Paris users ( am I alone ??) >For all thos that have not bought Faderworks please do so to show our gratitute >because he will make our work with Paris so much easier ! >DeeJ come on back we are waiting for you, jump on Paris again ! >Regards, >Dimitrios >Hi Kerry, Thanks so much for doing this. I made a few minor changes to the wiki this afternoon. I'll do more as I can. You rock! Mike Kerry Galloway <kg@kerrygalloway.com> wrote: >Greetings all! > >Technology sure changes fast. A piece of technology became available to me a >while back that finally allowed me to build what I used to just dream about. > >Namely - there is now a PARISWiki where PARIS aficionados can compile all >existing data concerning PARIS. I've started the ball rolling by beginning >the process of converting and compiling the varied and valuable information >found amongst the various official and unofficial FAQs. > >You might want to read the rest of the email before you click, but the site >is linked at the bottom if you're not a "manuals" type. > >For those unfamiliar with the term - a "Wiki" is a collaborative, >community-driven encyclopedia. You don't complain to someone when you spot >something wrong or incomplete or missing - you *fix it yourself*. To do this >is trivially easy - once you're registered and logged in, double-click >directly on the page you're reading and an editor opens. You can begin >entering/editing text right there. If you want to create a new page, you >just type a "CamelCase" word as you're editing (any word with an initial cap >and another capital within it, like AppMessage) and when you "store" the >page the cunning macros behind the Wiki turn it into a hyperlink with dashes >under it. Click on this and a new page with that name is created and saved >(before you do that, you might want to look at the page index to make sure >you aren't creating a duplicate). Yeah - you read that right - essential
ly >creating a hyperlink to a non-existing page, and then clicking on it, >actually creates the page. > >Now some important info. > >This site is *free*. By *free*, I mean - I am donating the time to build and >maintain it; donating the bandwidth and server space to serve it; there are >no "gotchas", no "enter your credit card", no "donate" buttuns and no ads; I >will never sell, trade, share or knowingly make your email addresses >available to others. In short, this is a "labour of love". Unless the >bandwidth goes absolutely insane, I can't see ever needing to "pass the hat" >for donations; if that ever happened (I doubt it, I have up to three >terabytes of bandwidth on the account it's served on) I'd talk it through >with the community before doing that in case someone in the community simply >wanted to serve it elsewhere. Failing those sort of unforeseen and unlikely >circumstances, I am happy to continue serving this for at least the next >eighteen months. If things go well, I have no problem keeping it going for >as long after that as I can foresee (ask me if you want to mirror it >elsewhere - assuming you don't want to mirror it on some white supremacist >hate site I'll almost certainly say yes, but let's make it a real mirror and >not a copy so multiple sites don't develop different content). > >What I *would* ask for in return, however is participation. If I wanted my >own Private PARIS Manual, I could have done it on my own hard drive easily >without the hassle of maintaining it on a site. This Wiki is meant to be a >community service - and it is also intended to be nearly entirely >community-driven. As long as the community continues to participate, not >merely by reading but by *contributing information*, I'll continue to do my >part by running the back office. I hope that seems fair. > >Aside from that, the conditions of use are largely common sense (I think >everyone's smart enough not to kill it instantly by posting illegal or >offensive material; arguments stay offsite; let's keep it focused; etc) and >are printed on the front page. Registration is automatic (ie open to any >PARIS user, past or present, no matter how casual a user) and takes all of >about thirty seconds. > >A further note on registration - it's open for all. The technology exists to >take it private, to require admin approval for who registers, etc etc; it >can be made very secure. However I'd like to start by assuming "if I need to >secure it, I'll secure it, but until then, welcome one and all!". So >registration is automatic, nobody "approves it". > >Plans for this Wiki are fairly ambitious, but I'd hope realistic and >sustainable. For example - amongst other developments, Aaron Allen and Chuck >Duffy have graciously given their consent for the Wiki to serve the Brian >Tankersley video, which (pending confirmation from BT), I'd like to see >broken into chapters and inserted in the relevant topics. I'd do this >pretty much ASAP pending hearing back from BT (anyone got a current contact >email, shoot it to me privately). > >In addition, it's "skinnable" so the plain vanilla interface will go away at >some point (when I get time) and be replaced by a slicker custom "look". I >will be investigating the ins-and-outs of posting whole sections from the >actual manual inline so they can be woven in with practical observations. >The technologies behind this thing are incredible; there are so many things >you can do with this data once you've got it entered, it's amazing. Sortable >plugin databases so you can find all compressors or all delays and choose >one by feature or applicability (hey, don't laugh; you may not think you >need this now, but look at how fast Mike Audet is developing new ones now >he's hitting his stride!); key commands databased so you can pull up all the >editing modifiers in a hurry - I have hopes that as this grows it can become >a "leave open in the background" quick reference/help file. It's also going >to be a place to collect some of the history and "back-story" of the >platform, its developers and designers. > >I want to take a second here and express my gratitude to some particular >people for their support, enthusiasm and cooperation in advance of rollout; >Aaron Allen, Chuck Duffy, "Hiddensounds" Kim, Steve "artguy", Mike Arnao and >Mike Audet. > >For their invaluable work as PARIS' "de facto" maintainers of the Archives, >Steve "artguy" (whose last name I now commit to spelling correctly), John >Bercik and Doug Wellington - and Kim for hist maintenance of the NG, >essentially the "collective memory" of the community - and last but not >least those many whose contributed insights form the backbone of the Wiki. > >An extremely quick tutorial is available linked to the front page, followed >by detailed documentation afterwards. You aren't going to believe how easy - >and even fun - it is when you get the hang of it. But there's a test area >called the SandBox where you can mess around without hurting anything. > >Okidoki. More to come, but I'll shut up now. Kim's kindly made the >"theproject" NG available for Wiki business, so if you want to talk >technical specifics, ie formatting, skins, concept, data organization, >that'd be a great place to keep it grouped and threaded together. > > ><<<<< > > >And now, the Wiki. I hope you enjoy it. (watch out for bad line wraps in the >URLs) > >Home page - > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=HomeP age > >Some pages are more fleshed in than others: > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=BugsT roubleshooting > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Sessi onTracking > > >Some are "getting there": > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Windo wPatchBay > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Acces sWin > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Paris NoNos > > >Sample plugin page: > > http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=NoLim it > > >And remember - if you see bad info there, or something missing - don't >complain, log in and fix it! If I missed your contribution - sorry! Log in >and fix it! If I... well, you get the picture. > >Welcome, and enjoy. > >- Kerry > > >Kerry, The uthor refused to make a ral pdc because of some restrictions that vst plugins give. Anyway maybe you did not understand how Faderworks new version will work. Ok... So you have a bunch of plugins. You collect their latencies, someone , maybe me, will post the most used plugins with their latencies... Then you just make presets inside faderworks with name and latency. For instance Waves rvox 64 Waves rcomp 64 Drumagog 175 etc Then whenever you put say rvox on a paris audio track you just will scroll your column inside faderworks until you find the one named rvox nd just hit the on button ! Thats all !! All other faderworkds instances on all other paris audio tracks will get delayed by that latency ! Its a damn clever sustem. It even substracts latencies !! So if you have a overall 256 samples latency and you put a plugin on a new track that has 64 then the 256 overall does not change but the above track gets delayed by 256-64= 198 !!! He is damn clever guy ! Hope this helps, Regards, Dimitrios Kerry Galloway <kg@kerrygalloway.com> wrote: >Dimitrios, I'm wondering - I've never used FaderWorks, but seeing as plugin >latencies are absolute and repeatable across systems - are there any plans >to include a database of the commonly used plugins so Faderworks just >recognizes them and sets their latencies automatically? > >Yes, I know it's lazy - and the current version doesn't seem to be much of a >hassle at all. But you gotta admit, it'd be elegant. All that seems >nec
lk it through >> with the community before doing that in case someone in the community simply >> wanted to serve it elsewhere. Failing those sort of unforeseen and unlikely >> circumstances, I am happy to continue serving this for at least the next >> eighteen months. If things go well, I have no problem keeping it going for >> as long after that as I can foresee (ask me if you want to mirror it >> elsewhere - assuming you don't want to mirror it on some white supremacist >> hate site I'll almost certainly say yes, but let's make it a real mirror > and >> not a copy so multiple sites don't develop different content). >> >> What I *would* ask for in return, however is participation. If I wanted > my >> own Private PARIS Manual, I could have done it on my own hard drive easily >> without the hassle of maintaining it on a site. This Wiki is meant to be > a >> community service - and it is also intended to be nearly entirely >> community-driven. As long as the community continues to participate, not >> merely by reading but by *contributing information*, I'll continue to do > my >> part by running the back office. I hope that seems fair. >> >> Aside from that, the conditions of use are largely common sense (I think >> everyone's smart enough not to kill it instantly by posting illegal or >> offensive material; argument
;> >> Home page - >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=HomeP age >> >> Some pages are more fleshed in than others: >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=BugsT roubleshooting >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Sessi onTracking >> >> >> Some are "getting there": >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Windo wPatchBay >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Acces sWin >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=Paris NoNos >> >> >> Sample plugin page: >> >> http://www.kerrygalloway.com/WikiPARIS/wikka.php?wakka=NoLim it >> >> >> And remember - if you see bad info there, or something missing - don't >> complain, log in and fix it! If I missed your contribution - sorry! Log > in >> and fix it! If I... well, you get the picture. >> >> Welcome, and enjoy. >> >> - Kerry >> >> >> >This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C89D0E.59880AD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Faderworks new update !!! see how it looks !!!!!!!!!Hi Kerry, I'm thinking the GUI won't be aware of what's going on behind the = scenes. Is that what you're saying also? I'm also thinking that