Home » The PARIS Forums » PARIS: Main » *******PARIS Compressor Released plus updates*******
| Re: *******PARIS Compressor Released plus updates******* [message #91174 is a reply to message #91165] |
Mon, 08 October 2007 18:19   |
Ted Gerber
Messages: 705
Registered: January 2009
|
Senior Member |
|
|
Hi Mike-
In light of this, what would you like me to do vis a vis directing funds?
Happy Thanksgiving
Ted
Feel free to call me @ 416.821.7084
"Mike Audet" <mike@...> wrote:
>
>No reference projects??!?!?!?!
>
>Chuck, thank you so much for all the work you did. I'm very, very aware
>that I'm blessed to have your work to look at and learn from. I'm having
>such a great time working on this stuff, and it really is a dream come true
>to be able to move PARIS forward.
>
>I've sent you a couple of emails, but I have a feeling that my messages
get
>killed by your spam filter. I would love to work on the precision limiter,
>and It would be a huge help to have the wires code to look at. One of the
>things I still have no clue about (among many) is how the routing works.
> I would really, really, love to add a side chain to a compressor, and I
>think that the wires code would be a huge help.
>
>Thanks again for everything!
>
>Mike
>
>PS - I don't know if you've seen my little site at ensoniq.ca, but you've
>got a very special thanks right at the top.
>
>
>
>"chuck duffy" <c@c.com> wrote:
>>
>>Mike,
>>
>>The Mac stuff is built under Code Warrior, not visual C++. It's a real
>nightmare,
>>and if you think it was hard to grok the Visual C++ side, think about doing
>>it with no reference projects. Yikes.
>>
>>Chuck
>>
>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
>>>
>>>I'm in and thanks Mike.
>>>cheers,
>>>Mike Mullin
>>>
>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
>>>>
>>>>Do we have four Mac users other than me whowould be willing to kick in
>>$20
>>>>each?
>>>>
>>>>Thanks Mike!
>>>>
>>>>Gantt
>>>>
>>>>"Mike Audet" <mike@...> wrote:
>>>>>
>>>>>I would really like to tackle the Mac stuff, but I don't have a Mac
running
>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2 cross
>platform
>>>>>edition just to compile the code. The cheapest I've seen it for is
around
>>>>>$80 plus shipping. If a Mac user wants to send me a copy or the $100
>>(I
>>>>>live in Canada and shipping is always stupid expensive), I'll get to
>work
>>>>>on it.
>>>>>But even then, I can't make any promises except to try.
>>>>>
>>>>>All the best,
>>>>>
>>>>>Mike
>>>>>
>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I will be
>>all
>>>>>
>>>>>>over this.
>>>>>>Did you by chance fix it so that the Mac mismap bug is gone for the
>Mac
>>>>>
>>>>>>users?
>>>>>>Question: can I run 'this' compressor also w/o causing problems on
the
>>>>
>>>>>>crunched version that shipped with the Paris rigs?
>>>>>>
>>>>>>AA
>>>>>>
>>>>>>
>>>>>>"Mike Audet" <mike@.....> wrote in message news:4705b550$1@linux...
>>>>>>>
>>>>>>> Hey all,
>>>>>>>
>>>>>>> I've got some new goodies!
>>>>>>>
>>>>>>> I've just released the "PARIS compressor". It's the original PARIS
>>>
>>>>>>> compressor
>>>>>>> algo before it was "crunched" to allow 16 compressors to fit on one
>>>EDS100
>>>>>>> card. I've added meters (of course) AND
>>>>>>>
>>>>>>> I fixed the sample rate bug in this and my previous two plugins!
>>>>>>>
>>>>>>> If you hadn't heard, almost all the PARIS effects assume 48k for
their
>>>>>
>>>>>>> calculations,
>>>>>>> even when they are working at 44.1K. Not these. They operate at
>the
>>>>>
>>>>>>> project
>>>>>>> sample rate. Can you hear a difference? You tell me!
>>>>>>>
>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
>>>>>>> once the DNS goes through, simply at ensoniq.ca.
>>>>>>>
>>>>>>> These plugins are released as "pay what you can" (ie - not free).
>
>>
>>>
>>>>I'm
>>>>>>> not a rich man, and I could use the help.
>>>>>>>
>>>>>>> As always, let me know what you think.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91196 is a reply to message #91165] |
Tue, 09 October 2007 13:26 |
chuck duffy
Messages: 453
Registered: July 2005
|
Senior Member |
|
|
Hi Mike. You are either getting spam filtered or using my old address. My
address is
c d u f f y @ i d e a c o r p o r a t i o n . c o m
for the past couple years
Wires: no problem sharing the code if I can find it. Unfortunately there
is no routing from effect to effect, across channels for inserts in the architecture,
so wires is a big hack. Basically what I do is steal 16 words of shared
memory at the top of an ESP2 and reserve it. Then for each output wire,
I send the audio a sample at a time up to one of the reserved words of memory.
For each input wire I retrieve the audio a sample at a time from that reserved
word. It's dirt simple, but suffers from a bad side effect. There is no
shared memory BETWEEN effects chips. So say that you set up an output wire,
and an effect and an input wire, and everything works great. But then you
add another effect, and the effects engine shuffles the algos around to different
ESP2 chips to get a better allocation. Your input wire can get allocated
to one chip, the output to another. Then things no worky. The fix is to
remove the input and output wire, then add them back, and in all likelyhood
they will end up on the same chip, but its a pain.
I have a great keyed gate and a sidechain I never released because wires
is not a reliable method, and there is no other way to route from channel
to channel among inserts.
I also can't release the precision limiter because that is the property of
one of the original ensoniq guys, and I have an ironclad agreement with him
that I cannot release it, unless its for sale , and he gets a cut.
The one thing I do think we should release is matts reverb, cause nobody
has heard from here in years.
Chuck
"Mike Audet" <mike@...> wrote:
>
>No reference projects??!?!?!?!
>
>Chuck, thank you so much for all the work you did. I'm very, very aware
>that I'm blessed to have your work to look at and learn from. I'm having
>such a great time working on this stuff, and it really is a dream come true
>to be able to move PARIS forward.
>
>I've sent you a couple of emails, but I have a feeling that my messages
get
>killed by your spam filter. I would love to work on the precision limiter,
>and It would be a huge help to have the wires code to look at. One of the
>things I still have no clue about (among many) is how the routing works.
> I would really, really, love to add a side chain to a compressor, and I
>think that the wires code would be a huge help.
>
>Thanks again for everything!
>
>Mike
>
>PS - I don't know if you've seen my little site at ensoniq.ca, but you've
>got a very special thanks right at the top.
>
>
>
>"chuck duffy" <c@c.com> wrote:
>>
>>Mike,
>>
>>The Mac stuff is built under Code Warrior, not visual C++. It's a real
>nightmare,
>>and if you think it was hard to grok the Visual C++ side, think about doing
>>it with no reference projects. Yikes.
>>
>>Chuck
>>
>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
>>>
>>>I'm in and thanks Mike.
>>>cheers,
>>>Mike Mullin
>>>
>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
>>>>
>>>>Do we have four Mac users other than me whowould be willing to kick in
>>$20
>>>>each?
>>>>
>>>>Thanks Mike!
>>>>
>>>>Gantt
>>>>
>>>>"Mike Audet" <mike@...> wrote:
>>>>>
>>>>>I would really like to tackle the Mac stuff, but I don't have a Mac
running
>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2 cross
>platform
>>>>>edition just to compile the code. The cheapest I've seen it for is
around
>>>>>$80 plus shipping. If a Mac user wants to send me a copy or the $100
>>(I
>>>>>live in Canada and shipping is always stupid expensive), I'll get to
>work
>>>>>on it.
>>>>>But even then, I can't make any promises except to try.
>>>>>
>>>>>All the best,
>>>>>
>>>>>Mike
>>>>>
>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I will be
>>all
>>>>>
>>>>>>over this.
>>>>>>Did you by chance fix it so that the Mac mismap bug is gone for the
>Mac
>>>>>
>>>>>>users?
>>>>>>Question: can I run 'this' compressor also w/o causing problems on
the
>>>>
>>>>>>crunched version that shipped with the Paris rigs?
>>>>>>
>>>>>>AA
>>>>>>
>>>>>>
>>>>>>"Mike Audet" <mike@.....> wrote in message news:4705b550$1@linux...
>>>>>>>
>>>>>>> Hey all,
>>>>>>>
>>>>>>> I've got some new goodies!
>>>>>>>
>>>>>>> I've just released the "PARIS compressor". It's the original PARIS
>>>
>>>>>>> compressor
>>>>>>> algo before it was "crunched" to allow 16 compressors to fit on one
>>>EDS100
>>>>>>> card. I've added meters (of course) AND
>>>>>>>
>>>>>>> I fixed the sample rate bug in this and my previous two plugins!
>>>>>>>
>>>>>>> If you hadn't heard, almost all the PARIS effects assume 48k for
their
>>>>>
>>>>>>> calculations,
>>>>>>> even when they are working at 44.1K. Not these. They operate at
>the
>>>>>
>>>>>>> project
>>>>>>> sample rate. Can you hear a difference? You tell me!
>>>>>>>
>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
>>>>>>> once the DNS goes through, simply at ensoniq.ca.
>>>>>>>
>>>>>>> These plugins are released as "pay what you can" (ie - not free).
>
>>
>>>
>>>>I'm
>>>>>>> not a rich man, and I could use the help.
>>>>>>>
>>>>>>> As always, let me know what you think.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91209 is a reply to message #91196] |
Tue, 09 October 2007 16:45 |
Mike Audet
Messages: 294
Registered: December 2008
|
Senior Member |
|
|
Hi Chuck,
I was writing to your old address. The worst part is that in my sent items,
I have an email that I sent to your new address that you responded to a couple
of years ago! So, I have no excuse.
I think I'm going to write a ducker that uses the left and right channels
of a stereo plugin. I did come across a function in boxTranslator that says
it connects the output of one plugin to an input of another, but it uses
"order" and "flags" parameters that aren't defined anywhere, and I can't
find an example of them being used, either.
Did you ever try compiling the Mac plugs under Visual Studio 4.2 cross platform?
The reason I thought that would be the way to go is that the driver requires
4.2, and the troll.h has a zillion entries for translating between Mac and
PC.
I've yet to get a debug version of a plugin to load in PARIS, too.
Thanks again for everything!
Mike
"chuck duffy" <c@c.com> wrote:
>
>Hi Mike. You are either getting spam filtered or using my old address.
My
>address is
>
>c d u f f y @ i d e a c o r p o r a t i o n . c o m
>
>for the past couple years
>
>Wires: no problem sharing the code if I can find it. Unfortunately there
>is no routing from effect to effect, across channels for inserts in the
architecture,
>so wires is a big hack. Basically what I do is steal 16 words of shared
>memory at the top of an ESP2 and reserve it. Then for each output wire,
>I send the audio a sample at a time up to one of the reserved words of memory.
> For each input wire I retrieve the audio a sample at a time from that reserved
>word. It's dirt simple, but suffers from a bad side effect. There is no
>shared memory BETWEEN effects chips. So say that you set up an output wire,
>and an effect and an input wire, and everything works great. But then you
>add another effect, and the effects engine shuffles the algos around to
different
>ESP2 chips to get a better allocation. Your input wire can get allocated
>to one chip, the output to another. Then things no worky. The fix is to
>remove the input and output wire, then add them back, and in all likelyhood
>they will end up on the same chip, but its a pain.
>
>I have a great keyed gate and a sidechain I never released because wires
>is not a reliable method, and there is no other way to route from channel
>to channel among inserts.
>
>I also can't release the precision limiter because that is the property
of
>one of the original ensoniq guys, and I have an ironclad agreement with
him
>that I cannot release it, unless its for sale , and he gets a cut.
>
>The one thing I do think we should release is matts reverb, cause nobody
>has heard from here in years.
>
>Chuck
>
>
>
>"Mike Audet" <mike@...> wrote:
>>
>>No reference projects??!?!?!?!
>>
>>Chuck, thank you so much for all the work you did. I'm very, very aware
>>that I'm blessed to have your work to look at and learn from. I'm having
>>such a great time working on this stuff, and it really is a dream come
true
>>to be able to move PARIS forward.
>>
>>I've sent you a couple of emails, but I have a feeling that my messages
>get
>>killed by your spam filter. I would love to work on the precision limiter,
>>and It would be a huge help to have the wires code to look at. One of the
>>things I still have no clue about (among many) is how the routing works.
>> I would really, really, love to add a side chain to a compressor, and
I
>>think that the wires code would be a huge help.
>>
>>Thanks again for everything!
>>
>>Mike
>>
>>PS - I don't know if you've seen my little site at ensoniq.ca, but you've
>>got a very special thanks right at the top.
>>
>>
>>
>>"chuck duffy" <c@c.com> wrote:
>>>
>>>Mike,
>>>
>>>The Mac stuff is built under Code Warrior, not visual C++. It's a real
>>nightmare,
>>>and if you think it was hard to grok the Visual C++ side, think about
doing
>>>it with no reference projects. Yikes.
>>>
>>>Chuck
>>>
>>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
>>>>
>>>>I'm in and thanks Mike.
>>>>cheers,
>>>>Mike Mullin
>>>>
>>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
>>>>>
>>>>>Do we have four Mac users other than me whowould be willing to kick
in
>>>$20
>>>>>each?
>>>>>
>>>>>Thanks Mike!
>>>>>
>>>>>Gantt
>>>>>
>>>>>"Mike Audet" <mike@...> wrote:
>>>>>>
>>>>>>I would really like to tackle the Mac stuff, but I don't have a Mac
>running
>>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2 cross
>>platform
>>>>>>edition just to compile the code. The cheapest I've seen it for is
>around
>>>>>>$80 plus shipping. If a Mac user wants to send me a copy or the $100
>>>(I
>>>>>>live in Canada and shipping is always stupid expensive), I'll get to
>>work
>>>>>>on it.
>>>>>>But even then, I can't make any promises except to try.
>>>>>>
>>>>>>All the best,
>>>>>>
>>>>>>Mike
>>>>>>
>>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
>>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I will
be
>>>all
>>>>>>
>>>>>>>over this.
>>>>>>>Did you by chance fix it so that the Mac mismap bug is gone for the
>>Mac
>>>>>>
>>>>>>>users?
>>>>>>>Question: can I run 'this' compressor also w/o causing problems on
>the
>>>>>
>>>>>>>crunched version that shipped with the Paris rigs?
>>>>>>>
>>>>>>>AA
>>>>>>>
>>>>>>>
>>>>>>>"Mike Audet" <mike@.....> wrote in message news:4705b550$1@linux...
>>>>>>>>
>>>>>>>> Hey all,
>>>>>>>>
>>>>>>>> I've got some new goodies!
>>>>>>>>
>>>>>>>> I've just released the "PARIS compressor". It's the original PARIS
>>>>
>>>>>>>> compressor
>>>>>>>> algo before it was "crunched" to allow 16 compressors to fit on
one
>>>>EDS100
>>>>>>>> card. I've added meters (of course) AND
>>>>>>>>
>>>>>>>> I fixed the sample rate bug in this and my previous two plugins!
>>>>>>>>
>>>>>>>> If you hadn't heard, almost all the PARIS effects assume 48k for
>their
>>>>>>
>>>>>>>> calculations,
>>>>>>>> even when they are working at 44.1K. Not these. They operate at
>>the
>>>>>>
>>>>>>>> project
>>>>>>>> sample rate. Can you hear a difference? You tell me!
>>>>>>>>
>>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
>>>>>>>> once the DNS goes through, simply at ensoniq.ca.
>>>>>>>>
>>>>>>>> These plugins are released as "pay what you can" (ie - not free).
>>
>>>
>>>>
>>>>>I'm
>>>>>>>> not a rich man, and I could use the help.
>>>>>>>>
>>>>>>>> As always, let me know what you think.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91210 is a reply to message #91209] |
Tue, 09 October 2007 17:06 |
chuck duffy
Messages: 453
Registered: July 2005
|
Senior Member |
|
|
>I did come across a function in boxTranslator that says
>it connects the output of one plugin to an input of another, >but it uses
> "order" and "flags" parameters that aren't defined anywhere, and I can't
>find an example of them being used, either.
You can chain output to input, and you can do it using only the box markup
code in the ini file. Basically it allows you to chain two or more plugs
together, output of one to input of another. This serves to form a 'composite'
plugin definition. But that's just the definition of the plug, not the instance.
There is no way to point the output of one instance of an insert plugin,
to the input of an instance of an insert on another channel. This was confirmed
by the guys who wrote the software and designed the hardware, that's where
I came up with the idea for wires.
>Did you ever try compiling the Mac plugs under Visual Studio 4.2 cross platform?
> The reason I thought that would be the way to go is that the driver requires
>4.2, and the troll.h has a zillion entries for translating between Mac and
>PC.
Well, the reason I went with CodeWarrior, is that that's what all the mac
plugs were built with by the Ensoniq guys.
>I've yet to get a debug version of a plugin to load in PARIS, too.
It's not possible, AFAIK. What is possible, and I used on a minute by minute
basis is the following:
Sprinkle debugprints throughout your code, then pick up the output with sysinternals
debugview, available at www.sysinternals.com
>Thanks again for everything!
>
>
>Mike
>
>
>
>"chuck duffy" <c@c.com> wrote:
>>
>>Hi Mike. You are either getting spam filtered or using my old address.
> My
>>address is
>>
>>c d u f f y @ i d e a c o r p o r a t i o n . c o m
>>
>>for the past couple years
>>
>>Wires: no problem sharing the code if I can find it. Unfortunately there
>>is no routing from effect to effect, across channels for inserts in the
>architecture,
>>so wires is a big hack. Basically what I do is steal 16 words of shared
>>memory at the top of an ESP2 and reserve it. Then for each output wire,
>>I send the audio a sample at a time up to one of the reserved words of
memory.
>> For each input wire I retrieve the audio a sample at a time from that
reserved
>>word. It's dirt simple, but suffers from a bad side effect. There is
no
>>shared memory BETWEEN effects chips. So say that you set up an output
wire,
>>and an effect and an input wire, and everything works great. But then
you
>>add another effect, and the effects engine shuffles the algos around to
>different
>>ESP2 chips to get a better allocation. Your input wire can get allocated
>>to one chip, the output to another. Then things no worky. The fix is
to
>>remove the input and output wire, then add them back, and in all likelyhood
>>they will end up on the same chip, but its a pain.
>>
>>I have a great keyed gate and a sidechain I never released because wires
>>is not a reliable method, and there is no other way to route from channel
>>to channel among inserts.
>>
>>I also can't release the precision limiter because that is the property
>of
>>one of the original ensoniq guys, and I have an ironclad agreement with
>him
>>that I cannot release it, unless its for sale , and he gets a cut.
>>
>>The one thing I do think we should release is matts reverb, cause nobody
>>has heard from here in years.
>>
>>Chuck
>>
>>
>>
>>"Mike Audet" <mike@...> wrote:
>>>
>>>No reference projects??!?!?!?!
>>>
>>>Chuck, thank you so much for all the work you did. I'm very, very aware
>>>that I'm blessed to have your work to look at and learn from. I'm having
>>>such a great time working on this stuff, and it really is a dream come
>true
>>>to be able to move PARIS forward.
>>>
>>>I've sent you a couple of emails, but I have a feeling that my messages
>>get
>>>killed by your spam filter. I would love to work on the precision limiter,
>>>and It would be a huge help to have the wires code to look at. One of
the
>>>things I still have no clue about (among many) is how the routing works.
>>> I would really, really, love to add a side chain to a compressor, and
>I
>>>think that the wires code would be a huge help.
>>>
>>>Thanks again for everything!
>>>
>>>Mike
>>>
>>>PS - I don't know if you've seen my little site at ensoniq.ca, but you've
>>>got a very special thanks right at the top.
>>>
>>>
>>>
>>>"chuck duffy" <c@c.com> wrote:
>>>>
>>>>Mike,
>>>>
>>>>The Mac stuff is built under Code Warrior, not visual C++. It's a real
>>>nightmare,
>>>>and if you think it was hard to grok the Visual C++ side, think about
>doing
>>>>it with no reference projects. Yikes.
>>>>
>>>>Chuck
>>>>
>>>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
>>>>>
>>>>>I'm in and thanks Mike.
>>>>>cheers,
>>>>>Mike Mullin
>>>>>
>>>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
>>>>>>
>>>>>>Do we have four Mac users other than me whowould be willing to kick
>in
>>>>$20
>>>>>>each?
>>>>>>
>>>>>>Thanks Mike!
>>>>>>
>>>>>>Gantt
>>>>>>
>>>>>>"Mike Audet" <mike@...> wrote:
>>>>>>>
>>>>>>>I would really like to tackle the Mac stuff, but I don't have a Mac
>>running
>>>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2 cross
>>>platform
>>>>>>>edition just to compile the code. The cheapest I've seen it for is
>>around
>>>>>>>$80 plus shipping. If a Mac user wants to send me a copy or the $100
>>>>(I
>>>>>>>live in Canada and shipping is always stupid expensive), I'll get
to
>>>work
>>>>>>>on it.
>>>>>>>But even then, I can't make any promises except to try.
>>>>>>>
>>>>>>>All the best,
>>>>>>>
>>>>>>>Mike
>>>>>>>
>>>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
>>>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I will
>be
>>>>all
>>>>>>>
>>>>>>>>over this.
>>>>>>>>Did you by chance fix it so that the Mac mismap bug is gone for the
>>>Mac
>>>>>>>
>>>>>>>>users?
>>>>>>>>Question: can I run 'this' compressor also w/o causing problems on
>>the
>>>>>>
>>>>>>>>crunched version that shipped with the Paris rigs?
>>>>>>>>
>>>>>>>>AA
>>>>>>>>
>>>>>>>>
>>>>>>>>"Mike Audet" <mike@.....> wrote in message news:4705b550$1@linux...
>>>>>>>>>
>>>>>>>>> Hey all,
>>>>>>>>>
>>>>>>>>> I've got some new goodies!
>>>>>>>>>
>>>>>>>>> I've just released the "PARIS compressor". It's the original PARIS
>>>>>
>>>>>>>>> compressor
>>>>>>>>> algo before it was "crunched" to allow 16 compressors to fit on
>one
>>>>>EDS100
>>>>>>>>> card. I've added meters (of course) AND
>>>>>>>>>
>>>>>>>>> I fixed the sample rate bug in this and my previous two plugins!
>>>>>>>>>
>>>>>>>>> If you hadn't heard, almost all the PARIS effects assume 48k for
>>their
>>>>>>>
>>>>>>>>> calculations,
>>>>>>>>> even when they are working at 44.1K. Not these. They operate
at
>>>the
>>>>>>>
>>>>>>>>> project
>>>>>>>>> sample rate. Can you hear a difference? You tell me!
>>>>>>>>>
>>>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
>>>>>>>>> once the DNS goes through, simply at ensoniq.ca.
>>>>>>>>>
>>>>>>>>> These plugins are released as "pay what you can" (ie - not free).
>>>
>>>>
>>>>>
>>>>>>I'm
>>>>>>>>> not a rich man, and I could use the help.
>>>>>>>>>
>>>>>>>>> As always, let me know what you think.
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
|
|
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91217 is a reply to message #91210] |
Tue, 09 October 2007 19:25 |
mike audet[1]
Messages: 129
Registered: February 2006
|
Senior Member |
|
|
Hi Chuck,
It must have been extremely cool picking the brains of the PARIS designers.
Was there a particular version of code warrior that they used for the mac
plugs? It would be great to get those out, too.
What do you think of my work so far?
All the best,
Mike
"chuck duffy" <c@c.com> wrote:
>
>>I did come across a function in boxTranslator that says
>>it connects the output of one plugin to an input of another, >but it uses
>> "order" and "flags" parameters that aren't defined anywhere, and I can't
>>find an example of them being used, either.
>
>You can chain output to input, and you can do it using only the box markup
>code in the ini file. Basically it allows you to chain two or more plugs
>together, output of one to input of another. This serves to form a 'composite'
>plugin definition. But that's just the definition of the plug, not the instance.
> There is no way to point the output of one instance of an insert plugin,
>to the input of an instance of an insert on another channel. This was confirmed
>by the guys who wrote the software and designed the hardware, that's where
>I came up with the idea for wires.
>
>>Did you ever try compiling the Mac plugs under Visual Studio 4.2 cross
platform?
>> The reason I thought that would be the way to go is that the driver requires
>>4.2, and the troll.h has a zillion entries for translating between Mac
and
>>PC.
>
>Well, the reason I went with CodeWarrior, is that that's what all the mac
>plugs were built with by the Ensoniq guys.
>
>>I've yet to get a debug version of a plugin to load in PARIS, too.
>
>It's not possible, AFAIK. What is possible, and I used on a minute by minute
>basis is the following:
>
>Sprinkle debugprints throughout your code, then pick up the output with
sysinternals
>debugview, available at www.sysinternals.com
>
>>Thanks again for everything!
>>
>>
>>Mike
>>
>>
>>
>>"chuck duffy" <c@c.com> wrote:
>>>
>>>Hi Mike. You are either getting spam filtered or using my old address.
>> My
>>>address is
>>>
>>>c d u f f y @ i d e a c o r p o r a t i o n . c o m
>>>
>>>for the past couple years
>>>
>>>Wires: no problem sharing the code if I can find it. Unfortunately there
>>>is no routing from effect to effect, across channels for inserts in the
>>architecture,
>>>so wires is a big hack. Basically what I do is steal 16 words of shared
>>>memory at the top of an ESP2 and reserve it. Then for each output wire,
>>>I send the audio a sample at a time up to one of the reserved words of
>memory.
>>> For each input wire I retrieve the audio a sample at a time from that
>reserved
>>>word. It's dirt simple, but suffers from a bad side effect. There is
>no
>>>shared memory BETWEEN effects chips. So say that you set up an output
>wire,
>>>and an effect and an input wire, and everything works great. But then
>you
>>>add another effect, and the effects engine shuffles the algos around to
>>different
>>>ESP2 chips to get a better allocation. Your input wire can get allocated
>>>to one chip, the output to another. Then things no worky. The fix is
>to
>>>remove the input and output wire, then add them back, and in all likelyhood
>>>they will end up on the same chip, but its a pain.
>>>
>>>I have a great keyed gate and a sidechain I never released because wires
>>>is not a reliable method, and there is no other way to route from channel
>>>to channel among inserts.
>>>
>>>I also can't release the precision limiter because that is the property
>>of
>>>one of the original ensoniq guys, and I have an ironclad agreement with
>>him
>>>that I cannot release it, unless its for sale , and he gets a cut.
>>>
>>>The one thing I do think we should release is matts reverb, cause nobody
>>>has heard from here in years.
>>>
>>>Chuck
>>>
>>>
>>>
>>>"Mike Audet" <mike@...> wrote:
>>>>
>>>>No reference projects??!?!?!?!
>>>>
>>>>Chuck, thank you so much for all the work you did. I'm very, very aware
>>>>that I'm blessed to have your work to look at and learn from. I'm having
>>>>such a great time working on this stuff, and it really is a dream come
>>true
>>>>to be able to move PARIS forward.
>>>>
>>>>I've sent you a couple of emails, but I have a feeling that my messages
>>>get
>>>>killed by your spam filter. I would love to work on the precision limiter,
>>>>and It would be a huge help to have the wires code to look at. One of
>the
>>>>things I still have no clue about (among many) is how the routing works.
>>>> I would really, really, love to add a side chain to a compressor, and
>>I
>>>>think that the wires code would be a huge help.
>>>>
>>>>Thanks again for everything!
>>>>
>>>>Mike
>>>>
>>>>PS - I don't know if you've seen my little site at ensoniq.ca, but you've
>>>>got a very special thanks right at the top.
>>>>
>>>>
>>>>
>>>>"chuck duffy" <c@c.com> wrote:
>>>>>
>>>>>Mike,
>>>>>
>>>>>The Mac stuff is built under Code Warrior, not visual C++. It's a real
>>>>nightmare,
>>>>>and if you think it was hard to grok the Visual C++ side, think about
>>doing
>>>>>it with no reference projects. Yikes.
>>>>>
>>>>>Chuck
>>>>>
>>>>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
>>>>>>
>>>>>>I'm in and thanks Mike.
>>>>>>cheers,
>>>>>>Mike Mullin
>>>>>>
>>>>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
>>>>>>>
>>>>>>>Do we have four Mac users other than me whowould be willing to kick
>>in
>>>>>$20
>>>>>>>each?
>>>>>>>
>>>>>>>Thanks Mike!
>>>>>>>
>>>>>>>Gantt
>>>>>>>
>>>>>>>"Mike Audet" <mike@...> wrote:
>>>>>>>>
>>>>>>>>I would really like to tackle the Mac stuff, but I don't have a Mac
>>>running
>>>>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2 cross
>>>>platform
>>>>>>>>edition just to compile the code. The cheapest I've seen it for
is
>>>around
>>>>>>>>$80 plus shipping. If a Mac user wants to send me a copy or the
$100
>>>>>(I
>>>>>>>>live in Canada and shipping is always stupid expensive), I'll get
>to
>>>>work
>>>>>>>>on it.
>>>>>>>>But even then, I can't make any promises except to try.
>>>>>>>>
>>>>>>>>All the best,
>>>>>>>>
>>>>>>>>Mike
>>>>>>>>
>>>>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
>>>>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I will
>>be
>>>>>all
>>>>>>>>
>>>>>>>>>over this.
>>>>>>>>>Did you by chance fix it so that the Mac mismap bug is gone for
the
>>>>Mac
>>>>>>>>
>>>>>>>>>users?
>>>>>>>>>Question: can I run 'this' compressor also w/o causing problems
on
>>>the
>>>>>>>
>>>>>>>>>crunched version that shipped with the Paris rigs?
>>>>>>>>>
>>>>>>>>>AA
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>"Mike Audet" <mike@.....> wrote in message news:4705b550$1@linux...
>>>>>>>>>>
>>>>>>>>>> Hey all,
>>>>>>>>>>
>>>>>>>>>> I've got some new goodies!
>>>>>>>>>>
>>>>>>>>>> I've just released the "PARIS compressor". It's the original
PARIS
>>>>>>
>>>>>>>>>> compressor
>>>>>>>>>> algo before it was "crunched" to allow 16 compressors to fit on
>>one
>>>>>>EDS100
>>>>>>>>>> card. I've added meters (of course) AND
>>>>>>>>>>
>>>>>>>>>> I fixed the sample rate bug in this and my previous two plugins!
>>>>>>>>>>
>>>>>>>>>> If you hadn't heard, almost all the PARIS effects assume 48k for
>>>their
>>>>>>>>
>>>>>>>>>> calculations,
>>>>>>>>>> even when they are working at 44.1K. Not these. They operate
>at
>>>>the
>>>>>>>>
>>>>>>>>>> project
>>>>>>>>>> sample rate. Can you hear a difference? You tell me!
>>>>>>>>>>
>>>>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
>>>>>>>>>> once the DNS goes through, simply at ensoniq.ca.
>>>>>>>>>>
>>>>>>>>>> These plugins are released as "pay what you can" (ie - not free).
>>>>
>>>>>
>>>>>>
>>>>>>>I'm
>>>>>>>>>> not a rich man, and I could use the help.
>>>>>>>>>>
>>>>>>>>>> As always, let me know what you think.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91228 is a reply to message #91217] |
Tue, 09 October 2007 23:50 |
Tom Bruhl
Messages: 1368
Registered: June 2007
|
Senior Member |
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0319_01C80AE8.4BAFEC10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey Mike,
I'm installing my mecs tomorrow. If all goes well I'll be trying the =
newest
versions of all your work. If they sound as good as they look I'll be a
happy camper! Your ideas (and Dimitrios') are making Paris breath a =
little
easier again. Every little bit helps. I have tons of mixes to get to =
and
will be using the comps and NoLimit quite a bit.
Great work!
Tom
"Mike Audet" <mike@....> wrote in message news:470c3826$1@linux...
Hi Chuck,
It must have been extremely cool picking the brains of the PARIS =
designers.
Was there a particular version of code warrior that they used for the =
mac
plugs? It would be great to get those out, too.
What do you think of my work so far?
All the best,
Mike
=20
"chuck duffy" <c@c.com> wrote:
>
>>I did come across a function in boxTranslator that says
>>it connects the output of one plugin to an input of another, >but it =
uses
>> "order" and "flags" parameters that aren't defined anywhere, and I =
can't
>>find an example of them being used, either.
>
>You can chain output to input, and you can do it using only the box =
markup
>code in the ini file. Basically it allows you to chain two or more =
plugs
>together, output of one to input of another. This serves to form a =
'composite'
>plugin definition. But that's just the definition of the plug, not =
the instance.
> There is no way to point the output of one instance of an insert =
plugin,
>to the input of an instance of an insert on another channel. This =
was confirmed
>by the guys who wrote the software and designed the hardware, that's =
where
>I came up with the idea for wires.
>
>>Did you ever try compiling the Mac plugs under Visual Studio 4.2 =
cross
platform?
>> The reason I thought that would be the way to go is that the driver =
requires
>>4.2, and the troll.h has a zillion entries for translating between =
Mac
and
>>PC.
>
>Well, the reason I went with CodeWarrior, is that that's what all the =
mac
>plugs were built with by the Ensoniq guys. =20
>
>>I've yet to get a debug version of a plugin to load in PARIS, too.
>
>It's not possible, AFAIK. What is possible, and I used on a minute by =
minute
>basis is the following:
>
>Sprinkle debugprints throughout your code, then pick up the output =
with
sysinternals
>debugview, available at www.sysinternals.com
>
>>Thanks again for everything!
>>
>>
>>Mike
>>
>>
>>
>>"chuck duffy" <c@c.com> wrote:
>>>
>>>Hi Mike. You are either getting spam filtered or using my old =
address.
>> My
>>>address is=20
>>>
>>>c d u f f y @ i d e a c o r p o r a t i o n . c o m
>>>
>>>for the past couple years
>>>
>>>Wires: no problem sharing the code if I can find it. Unfortunately =
there
>>>is no routing from effect to effect, across channels for inserts in =
the
>>architecture,
>>>so wires is a big hack. Basically what I do is steal 16 words of =
shared
>>>memory at the top of an ESP2 and reserve it. Then for each output =
wire,
>>>I send the audio a sample at a time up to one of the reserved words =
of
>memory.
>>> For each input wire I retrieve the audio a sample at a time from =
that
>reserved
>>>word. It's dirt simple, but suffers from a bad side effect. There =
is
>no
>>>shared memory BETWEEN effects chips. So say that you set up an =
output
>wire,
>>>and an effect and an input wire, and everything works great. But =
then
>you
>>>add another effect, and the effects engine shuffles the algos =
around to
>>different
>>>ESP2 chips to get a better allocation. Your input wire can get =
allocated
>>>to one chip, the output to another. Then things no worky. The fix =
is
>to
>>>remove the input and output wire, then add them back, and in all =
likelyhood
>>>they will end up on the same chip, but its a pain.
>>>
>>>I have a great keyed gate and a sidechain I never released because =
wires
>>>is not a reliable method, and there is no other way to route from =
channel
>>>to channel among inserts.
>>>
>>>I also can't release the precision limiter because that is the =
property
>>of
>>>one of the original ensoniq guys, and I have an ironclad agreement =
with
>>him
>>>that I cannot release it, unless its for sale , and he gets a cut.
>>>
>>>The one thing I do think we should release is matts reverb, cause =
nobody
>>>has heard from here in years.
>>>
>>>Chuck
>>>
>>>
>>>
>>>"Mike Audet" <mike@...> wrote:
>>>>
>>>>No reference projects??!?!?!?!
>>>>
>>>>Chuck, thank you so much for all the work you did. I'm very, very =
aware
>>>>that I'm blessed to have your work to look at and learn from. I'm =
having
>>>>such a great time working on this stuff, and it really is a dream =
come
>>true
>>>>to be able to move PARIS forward.
>>>>
>>>>I've sent you a couple of emails, but I have a feeling that my =
messages
>>>get
>>>>killed by your spam filter. I would love to work on the precision =
limiter,
>>>>and It would be a huge help to have the wires code to look at. One =
of
>the
>>>>things I still have no clue about (among many) is how the routing =
works.
>>>> I would really, really, love to add a side chain to a compressor, =
and
>>I
>>>>think that the wires code would be a huge help.
>>>>
>>>>Thanks again for everything!
>>>>
>>>>Mike
>>>>
>>>>PS - I don't know if you've seen my little site at ensoniq.ca, but =
you've
>>>>got a very special thanks right at the top.
>>>>
>>>>
>>>>
>>>>"chuck duffy" <c@c.com> wrote:
>>>>>
>>>>>Mike,
>>>>>
>>>>>The Mac stuff is built under Code Warrior, not visual C++. It's =
a real
>>>>nightmare,
>>>>>and if you think it was hard to grok the Visual C++ side, think =
about
>>doing
>>>>>it with no reference projects. Yikes.
>>>>>
>>>>>Chuck
>>>>>
>>>>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
>>>>>>
>>>>>>I'm in and thanks Mike.
>>>>>>cheers,
>>>>>>Mike Mullin
>>>>>>
>>>>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
>>>>>>>
>>>>>>>Do we have four Mac users other than me whowould be willing to =
kick
>>in
>>>>>$20
>>>>>>>each?
>>>>>>>
>>>>>>>Thanks Mike!
>>>>>>>
>>>>>>>Gantt
>>>>>>>
>>>>>>>"Mike Audet" <mike@...> wrote:
>>>>>>>>
>>>>>>>>I would really like to tackle the Mac stuff, but I don't have =
a Mac
>>>running
>>>>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2 =
cross
>>>>platform
>>>>>>>>edition just to compile the code. The cheapest I've seen it =
for
is
>>>around
>>>>>>>>$80 plus shipping. If a Mac user wants to send me a copy or =
the
$100
>>>>>(I
>>>>>>>>live in Canada and shipping is always stupid expensive), I'll =
get
>to
>>>>work
>>>>>>>>on it.
>>>>>>>>But even then, I can't make any promises except to try.
>>>>>>>>
>>>>>>>>All the best,
>>>>>>>>
>>>>>>>>Mike
>>>>>>>>
>>>>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
>>>>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I =
will
>>be
>>>>>all
>>>>>>>>
>>>>>>>>>over this.
>>>>>>>>>Did you by chance fix it so that the Mac mismap bug is gone =
for
the
>>>>Mac
>>>>>>>>
>>>>>>>>>users?
>>>>>>>>>Question: can I run 'this' compressor also w/o causing =
problems
on
>>>the
>>>>>>>
>>>>>>>>>crunched version that shipped with the Paris rigs?
>>>>>>>>>
>>>>>>>>>AA
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>"Mike Audet" <mike@.....> wrote in message =
news:4705b550$1@linux...
>>>>>>>>>>
>>>>>>>>>> Hey all,
>>>>>>>>>>
>>>>>>>>>> I've got some new goodies!
>>>>>>>>>>
>>>>>>>>>> I've just released the "PARIS compressor". It's the =
original
PARIS
>>>>>>
>>>>>>>>>> compressor
>>>>>>>>>> algo before it was "crunched" to allow 16 compressors to =
fit on
>>one
>>>>>>EDS100
>>>>>>>>>> card. I've added meters (of course) AND
>>>>>>>>>>
>>>>>>>>>> I fixed the sample rate bug in this and my previous two =
plugins!
>>>>>>>>>>
>>>>>>>>>> If you hadn't heard, almost all the PARIS effects assume =
48k for
>>>their
>>>>>>>>
>>>>>>>>>> calculations,
>>>>>>>>>> even when they are working at 44.1K. Not these. They =
operate
>at
>>>>the
>>>>>>>>
>>>>>>>>>> project
>>>>>>>>>> sample rate. Can you hear a difference? You tell me!
>>>>>>>>>>
>>>>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
>>>>>>>>>> once the DNS goes through, simply at ensoniq.ca.
>>>>>>>>>>
>>>>>>>>>> These plugins are released as "pay what you can" (ie - not =
free).
>>>>
>>>>>
>>>>>>
>>>>>>>I'm
>>>>>>>>>> not a rich man, and I could use the help.
>>>>>>>>>>
>>>>>>>>>> As always, let me know what you think.
>>>>>>>>>>=20
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
I choose Polesoft Lockspam to fight spam, and you?
http://www.polesoft.com/refer.html
------=_NextPart_000_0319_01C80AE8.4BAFEC10
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.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hey Mike,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I'm installing my mecs =
tomorrow. If all=20
goes well I'll be trying the newest</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>versions of all your work. If =
they sound as=20
good as they look I'll be a</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>happy camper! Your ideas (and =
Dimitrios') are=20
making Paris breath a little</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>easier again. Every little bit=20
helps. I have tons of mixes to get to and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>will be using the comps and NoLimit =
quite a=20
bit.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Great work!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Mike Audet" <mike@....> wrote in message <A=20
=
href=3D"news:470c3826$1@linux">news:470c3826$1@linux</A>...</DIV><BR>Hi=20
Chuck,<BR><BR>It must have been extremely cool picking the brains of =
the=20
PARIS designers.<BR> Was there a particular version of code =
warrior=20
that they used for the mac<BR>plugs? It would be great to get =
those out,=20
too.<BR><BR>What do you think of my work so far?<BR><BR>All the=20
best,<BR><BR>Mike<BR> <BR><BR>"chuck duffy" <<A=20
href=3D"mailto:c@c.com">c@c.com</A>> wrote:<BR>><BR>>>I =
did come=20
across a function in boxTranslator that says<BR>>>it connects =
the output=20
of one plugin to an input of another, >but it uses<BR>>> =
"order" and=20
"flags" parameters that aren't defined anywhere, and I =
can't<BR>>>find=20
an example of them being used, either.<BR>><BR>>You can chain =
output to=20
input, and you can do it using only the box markup<BR>>code in the =
ini=20
file. Basically it allows you to chain two or more=20
plugs<BR>>together, output of one to input of another. This =
serves to=20
form a 'composite'<BR>>plugin definition. But that's just the =
definition of=20
the plug, not the instance.<BR>> There is no way to point the =
output of one=20
instance of an insert plugin,<BR>>to the input of an instance of an =
insert=20
on another channel. This was confirmed<BR>>by the guys who =
wrote the=20
software and designed the hardware, that's where<BR>>I came up with =
the=20
idea for wires.<BR>><BR>>>Did you ever try compiling the Mac =
plugs=20
under Visual Studio 4.2 cross<BR>platform?<BR>>> The reason I =
thought=20
that would be the way to go is that the driver =
requires<BR>>>4.2, and=20
the troll.h has a zillion entries for translating between=20
Mac<BR>and<BR>>>PC.<BR>><BR>>Well, the reason I went with=20
CodeWarrior, is that that's what all the mac<BR>>plugs were built =
with by=20
the Ensoniq guys. <BR>><BR>>>I've yet to get a debug =
version of=20
a plugin to load in PARIS, too.<BR>><BR>>It's not possible, =
AFAIK. What=20
is possible, and I used on a minute by minute<BR>>basis is the=20
following:<BR>><BR>>Sprinkle debugprints throughout your code, =
then pick=20
up the output with<BR>sysinternals<BR>>debugview, available at <A=20
=
href=3D"http://www.sysinternals.com">www.sysinternals.com</A><BR>><BR>=
>>Thanks=20
again for=20
=
everything!<BR>>><BR>>><BR>>>Mike <BR>>><BR>>&g=
t;<BR>>><BR>>>"chuck=20
duffy" <<A href=3D"mailto:c@c.com">c@c.com</A>>=20
wrote:<BR>>>><BR>>>>Hi Mike. You are either =
getting=20
spam filtered or using my old address.<BR>>> =
My<BR>>>>address=20
is <BR>>>><BR>>>>c d u f f y @ i d e a c o r p o r a =
t i o n=20
. c o m<BR>>>><BR>>>>for the past couple=20
years<BR>>>><BR>>>>Wires: no problem sharing the =
code if I=20
can find it. Unfortunately there<BR>>>>is no routing =
from=20
effect to effect, across channels for inserts in=20
the<BR>>>architecture,<BR>>>>so wires is a big =
hack. =20
Basically what I do is steal 16 words of shared<BR>>>>memory =
at the=20
top of an ESP2 and reserve it. Then for each output=20
wire,<BR>>>>I send the audio a sample at a time up to one of =
the=20
reserved words of<BR>>memory.<BR>>>> For each input wire I =
retrieve the audio a sample at a time from=20
that<BR>>reserved<BR>>>>word. It's dirt simple, but =
suffers=20
from a bad side effect. There is<BR>>no<BR>>>>shared =
memory=20
BETWEEN effects chips. So say that you set up an=20
output<BR>>wire,<BR>>>>and an effect and an input wire, =
and=20
everything works great. But then<BR>>you<BR>>>>add =
another=20
effect, and the effects engine shuffles the algos around=20
to<BR>>>different<BR>>>>ESP2 chips to get a better=20
allocation. Your input wire can get allocated<BR>>>>to =
one=20
chip, the output to another. Then things no worky. The fix =
is<BR>>to<BR>>>>remove the input and output wire, then add =
them=20
back, and in all likelyhood<BR>>>>they will end up on the =
same chip,=20
but its a pain.<BR>>>><BR>>>>I have a great keyed =
gate and a=20
sidechain I never released because wires<BR>>>>is not a =
reliable=20
method, and there is no other way to route from =
channel<BR>>>>to=20
channel among inserts.<BR>>>><BR>>>>I also can't =
release the=20
precision limiter because that is the=20
property<BR>>>of<BR>>>>one of the original ensoniq =
guys, and I=20
have an ironclad agreement with<BR>>>him<BR>>>>that I =
cannot=20
release it, unless its for sale , and he gets a=20
cut.<BR>>>><BR>>>>The one thing I do think we should =
release=20
is matts reverb, cause nobody<BR>>>>has heard from here in=20
=
years.<BR>>>><BR>>>>Chuck <BR>>>><BR>>>&g=
t;<BR>>>><BR>>>> "Mike=20
Audet" <mike@...> =
wrote:<BR>>>>><BR>>>>>No=20
reference =
projects??!?!?!?!<BR>>>>><BR>>>>>Chuck,=20
thank you so much for all the work you did. I'm very, very=20
aware<BR>>>>>that I'm blessed to have your work to look at =
and=20
learn from. I'm having<BR>>>>>such a great time =
working on=20
this stuff, and it really is a dream=20
come<BR>>>true<BR>>>>>to be able to move PARIS=20
forward.<BR>>>>><BR>>>>>I've sent you a couple =
of=20
emails, but I have a feeling that my=20
messages<BR>>>>get<BR>>>>>killed by your spam=20
filter. I would love to work on the precision=20
limiter,<BR>>>>>and It would be a huge help to have the =
wires code=20
to look at. One of<BR>>the<BR>>>>>things I still have =
no clue=20
about (among many) is how the routing works.<BR>>>>> I =
would=20
really, really, love to add a side chain to a compressor,=20
and<BR>>>I<BR>>>>>think that the wires code would be =
a huge=20
help.<BR>>>>><BR>>>>>Thanks again for=20
=
everything!<BR>>>>><BR>>>>>Mike <BR>>>>&g=
t;<BR>>>>>PS=20
- I don't know if you've seen my little site at ensoniq.ca, but=20
you've<BR>>>>>got a very special thanks right at the=20
=
top.<BR>>>>><BR>>>>> <BR>>>>><BR>>&=
gt;>>"chuck=20
duffy" <<A href=3D"mailto:c@c.com">c@c.com</A>>=20
=
wrote:<BR>>>>>><BR>>>>>>Mike, <BR>>>&g=
t;>><BR>>>>>>The=20
Mac stuff is built under Code Warrior, not visual C++. It's a=20
real<BR>>>>>nightmare,<BR>>>>>>and if you =
think it=20
was hard to grok the Visual C++ side, think=20
about<BR>>>doing<BR>>>>>>it with no reference =
projects.=20
=
Yikes.<BR>>>>>><BR>>>>>>Chuck <BR>>>&g=
t;>><BR>>>>>> "Mike=20
Mullin" <<A=20
=
href=3D"mailto:lunarlordship@sympatico.ca">lunarlordship@sympatico.ca</A>=
>=20
wrote:<BR>>>>>>> <BR>>>>>>>I'm in =
and=20
thanks=20
=
Mike.<BR>>>>>>>cheers, <BR>>>>>>>Mike =
Mullin<BR>>>>>>> <BR>>>>>>>"Gantt =
Kushner"=20
<<A =
href=3D"mailto:ganttmann@comcast.net">ganttmann@comcast.net</A>>=20
=
wrote:<BR>>>>>>>> <BR>>>>>>>>Do =
we=20
have four Mac users other than me whowould be willing to=20
=
kick<BR>>>in<BR>>>>>>$20 <BR>>>>>>>=
>each?<BR>>>>>>>> <BR>>>>>>>>=
Thanks=20
=
Mike!<BR>>>>>>>> <BR> >>>>>>>Gant =
t<BR>>>>>>>> <BR>>>>>>>> "Mike=20
Audet" <mike@...>=20
=
wrote:<BR> >>>>>>>& ;gt; <BR>>>>>>>>=
;>I=20
would really like to tackle the Mac stuff, but I don't have a=20
Mac<BR>>>>running<BR> >>>>>>>& ;gt;PARIS =
and I'm=20
pretty sure that I need a copy of Visual C++ 4.2=20
=
cross<BR>>>>>platform<BR> >>>>>>>& ;gt;edit=
ion=20
just to compile the code. The cheapest I've seen it=20
for<BR>is<BR>>>>around<BR> >>>>>>>& ;gt;$80 =
plus=20
shipping. If a Mac user wants to send me a copy or=20
=
the<BR>$100<BR>>>>>>(I <BR> >>>>>>>& ;gt;=
live=20
in Canada and shipping is always stupid expensive), I'll=20
=
get<BR>>to<BR>>>>>work <BR> >>>>>>>& ;gt;=
on=20
it.<BR> >>>>>>>& ;gt;But even then, I can't make any =
promises except to=20
=
try.<BR> >>>>>>>& ;gt; <BR> >>>>>>>& ;=
gt;All=20
the=20
=
best,<BR> >>>>>>>& ;gt; <BR>>>>>>>>=
>Mike<BR> >>>>>>>& ;gt; <BR>>>>>>>&=
gt;>"Aaron=20
Allen" <<A=20
=
href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=20
wrote:<BR> >>>>>>>& ;gt;>Deeeewwwwwwwwwd..... As =
soon as=20
these 15-18 hr days cease, I=20
=
will<BR>>>be<BR>>>>>>all <BR>>>>>>>=
>><BR> >>>>>>>& ;gt;>over=20
this.<BR> >>>>>>>& ;gt;>Did you by chance fix it =
so that=20
the Mac mismap bug is gone=20
=
for<BR>the<BR>>>>>Mac<BR> >>>>>>>& ;gt; <BR>=
>>>>>>>& ;gt;>users? <BR>>>>>>>>=
;>>Question:=20
can I run 'this' compressor also w/o causing=20
=
problems<BR>on<BR>>>>the<BR>>>>>>>> <BR>>=
>>>>>>>& ;gt;crunched=20
version that shipped with the Paris=20
=
rigs?<BR> >>>>>>>& ;gt;> <BR>>>>>>>=
>>>AA<BR> >>>>>>>& ;gt;> <BR>>>>>=
;>>>>><BR> >>>>>>>& ;gt;> "Mike=20
Audet" <mike@.....> wrote in message <A=20
=
href=3D"news:4705b550$1@linux">news:4705b550$1@linux</A>...<BR>>>&g=
t;>>>>>>><BR > >>>>>>>& ;gt;>>=
;=20
Hey=20
=
all,<BR> >>>>>>>& ;gt;>> <BR>>>>>>&=
gt;>>>>=20
I've got some new=20
=
goodies!<BR> >>>>>>>& ;gt;>> <BR>>>>>&=
gt;>>>>>=20
I've just released the "PARIS compressor". It's the=20
=
original<BR>PARIS<BR>>>>>>> <BR>>>>>>>=
>>>>=20
compressor<BR> >>>>>>>& ;gt;>> algo before it =
was=20
"crunched" to allow 16 compressors to fit=20
=
on<BR>>>one<BR>>>>>>>EDS100 <BR>>>>>&g=
t;>>>>>=20
card. I've added meters (of course)=20
=
AND<BR> >>>>>>>& ;gt;>> <BR>>>>>>&g=
t;>>>>=20
I fixed the sample rate bug in this and my previous two=20
=
plugins!<BR> >>>>>>>& ;gt;>> <BR>>>>>&=
gt;>>>>>=20
If you hadn't heard, almost all the PARIS effects assume 48k=20
=
for<BR>>>>their<BR> >>>>>>>& ;gt; <BR>>>&=
gt;>>>>>>>= 20
calculations,<BR> >>>>>>>& ;gt;>> even when =
they are=20
working at 44.1K. Not these. They=20
=
operate<BR>>at<BR>>>>>the <BR> >>>>>>>& ;=
gt;<BR> >>>>>>>& ;gt;>>=20
project<BR> >>>>>>>& ;gt;>> sample rate. =
Can you=20
hear a difference? You tell=20
=
me!<BR> >>>>>>>& ;gt;>> <BR>>>>>>&g=
t;>>>>=20
you can download these at <A=20
=
href=3D"http://www.mikeaudet.com/ensoniq.ca">www.mikeaudet.com/ensoniq.ca=
</A>=20
or<BR> >>>>>>>& ;gt;>> once the DNS goes =
through,=20
simply at=20
=
ensoniq.ca.<BR> >>>>>>>& ;gt;>> <BR>>>>&g=
t;>>>>>>=20
These plugins are released as "pay what you can" (ie - not=20
=
free).<BR>>>>><BR>>>>>> <BR>>>>>>=
;><BR>>>>>>>>I'm <BR> >>>>>>>& ;=
gt;>>=20
not a rich man, and I could use the=20
=
help.<BR> >>>>>>>& ;gt;>> <BR>>>>>>=
>>>>>=20
As always, let me know what you=20
think.<BR> >>>>>>>& ;gt;>>=20
=
<BR> >>>>>>>& ;gt;> <BR> >>>>>>>& ;=
gt;><BR> >>>>>>>& ;gt; <BR>>>>>>>&g=
t;<BR>>>>>>><BR >>>>>><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_0319_01C80AE8.4BAFEC10--
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91229 is a reply to message #91228] |
Wed, 10 October 2007 03:11 |
mike audet[1]
Messages: 129
Registered: February 2006
|
Senior Member |
|
|
Thanks, Tom! I'm having a great time adding all the feature that I would
like.
Good luck with the MECs and the mixes. I look forward to hearing what you
think of the plugs. I think the new compressor sounds great. The stock
comp always seemed to sound thick, but it dulled the high end in an unpleasant
way. This one sounds thick and the high end remains intact.
I'm not sure how much fixing the sample rate bugs made a difference. It
would be fun to bounce some tracks with old and new versions to see if there
is an audible difference. Right now, I'm just too busy and having too much
fun building these things.
I got a ducker working last night. I just have to change the metering so
that it makes sense. If anyone is desperate for a ducker, let me know and
I'll post the current version.
All the best,
Mike
"Tom Bruhl" <arpegio@comcast.net> wrote:
>
>
>Hey Mike,
>I'm installing my mecs tomorrow. If all goes well I'll be trying the =
>newest
>versions of all your work. If they sound as good as they look I'll be a
>happy camper! Your ideas (and Dimitrios') are making Paris breath a =
>little
>easier again. Every little bit helps. I have tons of mixes to get to =
>and
>will be using the comps and NoLimit quite a bit.
>
>Great work!
>Tom
>
> "Mike Audet" <mike@....> wrote in message news:470c3826$1@linux...
>
> Hi Chuck,
>
> It must have been extremely cool picking the brains of the PARIS =
>designers.
> Was there a particular version of code warrior that they used for the
=
>mac
> plugs? It would be great to get those out, too.
>
> What do you think of my work so far?
>
> All the best,
>
> Mike
> =20
>
> "chuck duffy" <c@c.com> wrote:
> >
> >>I did come across a function in boxTranslator that says
> >>it connects the output of one plugin to an input of another, >but it
=
>uses
> >> "order" and "flags" parameters that aren't defined anywhere, and I
=
>can't
> >>find an example of them being used, either.
> >
> >You can chain output to input, and you can do it using only the box =
>markup
> >code in the ini file. Basically it allows you to chain two or more =
>plugs
> >together, output of one to input of another. This serves to form a =
>'composite'
> >plugin definition. But that's just the definition of the plug, not =
>the instance.
> > There is no way to point the output of one instance of an insert =
>plugin,
> >to the input of an instance of an insert on another channel. This =
>was confirmed
> >by the guys who wrote the software and designed the hardware, that's
=
>where
> >I came up with the idea for wires.
> >
> >>Did you ever try compiling the Mac plugs under Visual Studio 4.2 =
>cross
> platform?
> >> The reason I thought that would be the way to go is that the driver
=
>requires
> >>4.2, and the troll.h has a zillion entries for translating between =
>Mac
> and
> >>PC.
> >
> >Well, the reason I went with CodeWarrior, is that that's what all the
=
>mac
> >plugs were built with by the Ensoniq guys. =20
> >
> >>I've yet to get a debug version of a plugin to load in PARIS, too.
> >
> >It's not possible, AFAIK. What is possible, and I used on a minute by
=
>minute
> >basis is the following:
> >
> >Sprinkle debugprints throughout your code, then pick up the output =
>with
> sysinternals
> >debugview, available at www.sysinternals.com
> >
> >>Thanks again for everything!
> >>
> >>
> >>Mike
> >>
> >>
> >>
> >>"chuck duffy" <c@c.com> wrote:
> >>>
> >>>Hi Mike. You are either getting spam filtered or using my old =
>address.
> >> My
> >>>address is=20
> >>>
> >>>c d u f f y @ i d e a c o r p o r a t i o n . c o m
> >>>
> >>>for the past couple years
> >>>
> >>>Wires: no problem sharing the code if I can find it. Unfortunately
=
>there
> >>>is no routing from effect to effect, across channels for inserts in
=
>the
> >>architecture,
> >>>so wires is a big hack. Basically what I do is steal 16 words of =
>shared
> >>>memory at the top of an ESP2 and reserve it. Then for each output
=
>wire,
> >>>I send the audio a sample at a time up to one of the reserved words
=
>of
> >memory.
> >>> For each input wire I retrieve the audio a sample at a time from =
>that
> >reserved
> >>>word. It's dirt simple, but suffers from a bad side effect. There
=
>is
> >no
> >>>shared memory BETWEEN effects chips. So say that you set up an =
>output
> >wire,
> >>>and an effect and an input wire, and everything works great. But =
>then
> >you
> >>>add another effect, and the effects engine shuffles the algos =
>around to
> >>different
> >>>ESP2 chips to get a better allocation. Your input wire can get =
>allocated
> >>>to one chip, the output to another. Then things no worky. The fix
=
>is
> >to
> >>>remove the input and output wire, then add them back, and in all =
>likelyhood
> >>>they will end up on the same chip, but its a pain.
> >>>
> >>>I have a great keyed gate and a sidechain I never released because
=
>wires
> >>>is not a reliable method, and there is no other way to route from =
>channel
> >>>to channel among inserts.
> >>>
> >>>I also can't release the precision limiter because that is the =
>property
> >>of
> >>>one of the original ensoniq guys, and I have an ironclad agreement
=
>with
> >>him
> >>>that I cannot release it, unless its for sale , and he gets a cut.
> >>>
> >>>The one thing I do think we should release is matts reverb, cause =
>nobody
> >>>has heard from here in years.
> >>>
> >>>Chuck
> >>>
> >>>
> >>>
> >>>"Mike Audet" <mike@...> wrote:
> >>>>
> >>>>No reference projects??!?!?!?!
> >>>>
> >>>>Chuck, thank you so much for all the work you did. I'm very, very
=
>aware
> >>>>that I'm blessed to have your work to look at and learn from. I'm
=
>having
> >>>>such a great time working on this stuff, and it really is a dream
=
>come
> >>true
> >>>>to be able to move PARIS forward.
> >>>>
> >>>>I've sent you a couple of emails, but I have a feeling that my =
>messages
> >>>get
> >>>>killed by your spam filter. I would love to work on the precision
=
>limiter,
> >>>>and It would be a huge help to have the wires code to look at. One
=
>of
> >the
> >>>>things I still have no clue about (among many) is how the routing
=
>works.
> >>>> I would really, really, love to add a side chain to a compressor,
=
>and
> >>I
> >>>>think that the wires code would be a huge help.
> >>>>
> >>>>Thanks again for everything!
> >>>>
> >>>>Mike
> >>>>
> >>>>PS - I don't know if you've seen my little site at ensoniq.ca, but
=
>you've
> >>>>got a very special thanks right at the top.
> >>>>
> >>>>
> >>>>
> >>>>"chuck duffy" <c@c.com> wrote:
> >>>>>
> >>>>>Mike,
> >>>>>
> >>>>>The Mac stuff is built under Code Warrior, not visual C++. It's
=
>a real
> >>>>nightmare,
> >>>>>and if you think it was hard to grok the Visual C++ side, think =
>about
> >>doing
> >>>>>it with no reference projects. Yikes.
> >>>>>
> >>>>>Chuck
> >>>>>
> >>>>>"Mike Mullin" <lunarlordship@sympatico.ca> wrote:
> >>>>>>
> >>>>>>I'm in and thanks Mike.
> >>>>>>cheers,
> >>>>>>Mike Mullin
> >>>>>>
> >>>>>>"Gantt Kushner" <ganttmann@comcast.net> wrote:
> >>>>>>>
> >>>>>>>Do we have four Mac users other than me whowould be willing to
=
>kick
> >>in
> >>>>>$20
> >>>>>>>each?
> >>>>>>>
> >>>>>>>Thanks Mike!
> >>>>>>>
> >>>>>>>Gantt
> >>>>>>>
> >>>>>>>"Mike Audet" <mike@...> wrote:
> >>>>>>>>
> >>>>>>>>I would really like to tackle the Mac stuff, but I don't have
=
>a Mac
> >>>running
> >>>>>>>>PARIS and I'm pretty sure that I need a copy of Visual C++ 4.2
=
>cross
> >>>>platform
> >>>>>>>>edition just to compile the code. The cheapest I've seen it =
>for
> is
> >>>around
> >>>>>>>>$80 plus shipping. If a Mac user wants to send me a copy or =
>the
> $100
> >>>>>(I
> >>>>>>>>live in Canada and shipping is always stupid expensive), I'll
=
>get
> >to
> >>>>work
> >>>>>>>>on it.
> >>>>>>>>But even then, I can't make any promises except to try.
> >>>>>>>>
> >>>>>>>>All the best,
> >>>>>>>>
> >>>>>>>>Mike
> >>>>>>>>
> >>>>>>>>"Aaron Allen" <know-spam@not_here.dude> wrote:
> >>>>>>>>>Deeeewwwwwwwwwd..... As soon as these 15-18 hr days cease, I
=
>will
> >>be
> >>>>>all
> >>>>>>>>
> >>>>>>>>>over this.
> >>>>>>>>>Did you by chance fix it so that the Mac mismap bug is gone =
>for
> the
> >>>>Mac
> >>>>>>>>
> >>>>>>>>>users?
> >>>>>>>>>Question: can I run 'this' compressor also w/o causing =
>problems
> on
> >>>the
> >>>>>>>
> >>>>>>>>>crunched version that shipped with the Paris rigs?
> >>>>>>>>>
> >>>>>>>>>AA
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>"Mike Audet" <mike@.....> wrote in message =
>news:4705b550$1@linux...
> >>>>>>>>>>
> >>>>>>>>>> Hey all,
> >>>>>>>>>>
> >>>>>>>>>> I've got some new goodies!
> >>>>>>>>>>
> >>>>>>>>>> I've just released the "PARIS compressor". It's the =
>original
> PARIS
> >>>>>>
> >>>>>>>>>> compressor
> >>>>>>>>>> algo before it was "crunched" to allow 16 compressors to =
>fit on
> >>one
> >>>>>>EDS100
> >>>>>>>>>> card. I've added meters (of course) AND
> >>>>>>>>>>
> >>>>>>>>>> I fixed the sample rate bug in this and my previous two =
>plugins!
> >>>>>>>>>>
> >>>>>>>>>> If you hadn't heard, almost all the PARIS effects assume =
>48k for
> >>>their
> >>>>>>>>
> >>>>>>>>>> calculations,
> >>>>>>>>>> even when they are working at 44.1K. Not these. They =
>operate
> >at
> >>>>the
> >>>>>>>>
> >>>>>>>>>> project
> >>>>>>>>>> sample rate. Can you hear a difference? You tell me!
> >>>>>>>>>>
> >>>>>>>>>> you can download these at www.mikeaudet.com/ensoniq.ca or
> >>>>>>>>>> once the DNS goes through, simply at ensoniq.ca.
> >>>>>>>>>>
> >>>>>>>>>> These plugins are released as "pay what you can" (ie - not
=
>free).
> >>>>
> >>>>>
> >>>>>>
> >>>>>>>I'm
> >>>>>>>>>> not a rich man, and I could use the help.
> >>>>>>>>>>
> >>>>>>>>>> As always, let me know what you think.
> >>>>>>>>>>=20
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
>
>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.2800.1400" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial size=3D2>Hey Mike,</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>I'm installing my mecs =
>tomorrow. If all=20
>goes well I'll be trying the newest</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>versions of all your work. If =
>they sound as=20
>good as they look I'll be a</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>happy camper! Your ideas (and =
>Dimitrios') are=20
>making Paris breath a little</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>easier again. Every little bit=20
>helps. I have tons of mixes to get to and</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>will be using the comps and NoLimit =
>quite a=20
>bit.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>Great work!</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Tom</FONT></DIV>
><DIV><FONT face=3DArial size=3D2></FONT> </DIV>
><BLOCKQUOTE=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Mike Audet" <mike@....> wrote in message <A=20
> =
>href=3D"news:470c3826$1@linux">news:470c3826$1@linux</A>...</DIV><BR>Hi=20
> Chuck,<BR><BR>It must have been extremely cool picking the brains of =
>the=20
> PARIS designers.<BR> Was there a particular version of code =
>warrior=20
> that they used for the mac<BR>plugs? It would be great to get =
>those out,=20
> too.<BR><BR>What do you think of my work so far?<BR><BR>All the=20
> best,<BR><BR>Mike<BR> <BR><BR>"chuck duffy" <<A=20
> href=3D"mailto:c@c.com">c@c.com</A>> wrote:<BR>><BR>>>I =
>did come=20
> across a function in boxTranslator that says<BR>>>it connects =
>the output=20
> of one plugin to an input of another, >but it uses<BR>>> =
>"order" and=20
> "flags" parameters that aren't defined anywhere, and I =
>can't<BR>>>find=20
> an example of them being used, either.<BR>><BR>>You can chain =
>output to=20
> input, and you can do it using only the box markup<BR>>code in the =
>ini=20
> file. Basically it allows you to chain two or more=20
> plugs<BR>>together, output of one to input of another. This =
>serves to=20
> form a 'composite'<BR>>plugin definition. But that's just the =
>definition of=20
> the plug, not the instance.<BR>> There is no way to point the =
>output of one=20
> instance of an insert plugin,<BR>>to the input of an instance of an =
>insert=20
> on another channel. This was confirmed<BR>>by the guys who =
>wrote the=20
> software and designed the hardware, that's where<BR>>I came up with =
>the=20
> idea for wires.<BR>><BR>>>Did you ever try compiling the Mac =
>plugs=20
> under Visual Studio 4.2 cross<BR>platform?<BR>>> The reason I =
>thought=20
> that would be the way to go is that the driver =
>requires<BR>>>4.2, and=20
> the troll.h has a zillion entries for translating between=20
> Mac<BR>and<BR>>>PC.<BR>><BR>>Well, the reason I went with=20
> CodeWarrior, is that that's what all the mac<BR>>plugs were built =
>with by=20
> the Ensoniq guys. <BR>><BR>>>I've yet to get a debug =
>version of=20
> a plugin to load in PARIS, too.<BR>><BR>>It's not possible, =
>AFAIK. What=20
> is possible, and I used on a minute by minute<BR>>basis is the=20
> following:<BR>><BR>>Sprinkle debugprints throughout your code, =
>then pick=20
> up the output with<BR>sysinternals<BR>>debugview, available at <A=20
> =
>href=3D"http://www.sysinternals.com">www.sysinternals.com</A><BR>><BR>=
>>>Thanks=20
> again for=20
> =
>everything!<BR>>><BR>>><BR>>>Mike<BR>>><BR>>&g=
>t;<BR>>><BR>>>"chuck=20
> duffy" <<A href=3D"mailto:c@c.com">c@c.com</A>>=20
> wrote:<BR>>>><BR>>>>Hi Mike. You are either =
>getting=20
> spam filtered or using my old address.<BR>>> =
>My<BR>>>>address=20
> is <BR>>>><BR>>>>c d u f f y @ i d e a c o r p o r a =
>t i o n=20
> . c o m<BR>>>><BR>>>>for the past couple=20
> years<BR>>>><BR>>>>Wires: no problem sharing the =
>code if I=20
> can find it. Unfortunately there<BR>>>>is no routing =
>from=20
> effect to effect, across channels for inserts in=20
> the<BR>>>architecture,<BR>>>>so wires is a big =
>hack. =20
> Basically what I do is steal 16 words of shared<BR>>>>memory =
>at the=20
> top of an ESP2 and reserve it. Then for each output=20
> wire,<BR>>>>I send the audio a sample at a time up to one of =
>the=20
> reserved words of<BR>>memory.<BR>>>> For each input wire I =
>
> retrieve the audio a sample at a time from=20
> that<BR>>reserved<BR>>>>word. It's dirt simple, but =
>suffers=20
> from a bad side effect. There is<BR>>no<BR>>>>shared =
>memory=20
> BETWEEN effects chips. So say that you set up an=20
> output<BR>>wire,<BR>>>>and an effect and an input wire, =
>and=20
> everything works great. But then<BR>>you<BR>>>>add =
>another=20
> effect, and the effects engine shuffles the algos around=20
> to<BR>>>different<BR>>>>ESP2 chips to get a better=20
> allocation. Your input wire can get allocated<BR>>>>to =
>one=20
> chip, the output to another. Then things no worky. The fix =
>
> is<BR>>to<BR>>>>remove the input and output wire, then add =
>them=20
> back, and in all likelyhood<BR>>>>they will end up on the =
>same chip,=20
> but its a pain.<BR>>>><BR>>>>I have a great keyed =
>gate and a=20
> sidechain I never released because wires<BR>>>>is not a =
>reliable=20
> method, and there is no other way to route from =
>channel<BR>>>>to=20
> channel among inserts.<BR>>>><BR>>>>I also can't =
>release the=20
> precision limiter because that is the=20
> property<BR>>>of<BR>>>>one of the original ensoniq =
>guys, and I=20
> have an ironclad agreement with<BR>>>him<BR>>>>that I =
>cannot=20
> release it, unless its for sale , and he gets a=20
> cut.<BR>>>><BR>>>>The one thing I do think we should =
>release=20
> is matts reverb, cause nobody<BR>>>>has heard from here in=20
> =
>years.<BR>>>><BR>>>>Chuck<BR>>>><BR>>>&g=
>t;<BR>>>><BR>>>>"Mike=20
> Audet" <mike@...> =
>wrote:<BR>>>>><BR>>>>>No=20
> reference =
>projects??!?!?!?!<BR>>>>><BR>>>>>Chuck,=20
> thank you so much for all the work you did. I'm very, very=20
> aware<BR>>>>>that I'm blessed to have your work to look at =
>and=20
> learn from. I'm having<BR>>>>>such a great time =
>working on=20
> this stuff, and it really is a dream=20
> come<BR>>>true<BR>>>>>to be able to move PARIS=20
> forward.<BR>>>>><BR>>>>>I've sent you a couple =
>of=20
> emails, but I have a feeling that my=20
> messages<BR>>>>get<BR>>>>>killed by your spam=20
> filter. I would love to work on the precision=20
> limiter,<BR>>>>>and It would be a huge help to have the =
>wires code=20
> to look at. One of<BR>>the<BR>>>>>things I still have =
>no clue=20
> about (among many) is how the routing works.<BR>>>>> I =
>would=20
> really, really, love to add a side chain to a compressor,=20
> and<BR>>>I<BR>>>>>think that the wires code would be =
>a huge=20
> help.<BR>>>>><BR>>>>>Thanks again for=20
> =
>everything!<BR>>>>><BR>>>>>Mike<BR>>>>&g=
>t;<BR>>>>>PS=20
> - I don't know if you've seen my little site at ensoniq.ca, but=20
> you've<BR>>>>>got a very special thanks right at the=20
> =
>top.<BR>>>>><BR>>>>><BR>>>>><BR>>&=
>gt;>>"chuck=20
> duffy" <<A href=3D"mailto:c@c.com">c@c.com</A>>=20
> =
>wrote:<BR>>>>>><BR>>>>>>Mike,<BR>>>&g=
>t;>><BR>>>>>>The=20
> Mac stuff is built under Code Warrior, not visual C++. It's a=20
> real<BR>>>>>nightmare,<BR>>>>>>and if you =
>think it=20
> was hard to grok the Visual C++ side, think=20
> about<BR>>>doing<BR>>>>>>it with no reference =
>projects.=20
> =
>Yikes.<BR>>>>>><BR>>>>>>Chuck<BR>>>&g=
>t;>><BR>>>>>>"Mike=20
> Mullin" <<A=20
> =
>href=3D"mailto:lunarlordship@sympatico.ca">lunarlordship@sympatico.ca</A>=
>>=20
> wrote:<BR>>>>>>><BR>>>>>>>I'm in =
>and=20
> thanks=20
> =
>Mike.<BR>>>>>>>cheers,<BR>>>>>>>Mike =
>
> Mullin<BR>>>>>>><BR>>>>>>>"Gantt =
>Kushner"=20
> <<A =
>href=3D"mailto:ganttmann@comcast.net">ganttmann@comcast.net</A>>=20
> =
>wrote:<BR>>>>>>>><BR>>>>>>>>Do =
>we=20
> have four Mac users other than me whowould be willing to=20
> =
>kick<BR>>>in<BR>>>>>>$20<BR>>>>>>>=
>>each?<BR>>>>>>>><BR>>>>>>>>=
>Thanks=20
> =
>Mike!<BR>>>>>>>><BR>>>>>>>>Gant=
>t<BR>>>>>>>><BR>>>>>>>>"Mike=20
> Audet" <mike@...>=20
> =
>wrote:<BR>>>>>>>>><BR>>>>>>>>=
>;>I=20
> would really like to tackle the Mac stuff, but I don't have a=20
> Mac<BR>>>>running<BR>>>>>>>>>PARIS =
>and I'm=20
> pretty sure that I need a copy of Visual C++ 4.2=20
> =
>cross<BR>>>>>platform<BR>>>>>>>>>edit=
>ion=20
> just to compile the code. The cheapest I've seen it=20
> for<BR>is<BR>>>>around<BR>>>>>>>>>$80 =
>plus=20
> shipping. If a Mac user wants to send me a copy or=20
> =
>the<BR>$100<BR>>>>>>(I<BR>>>>>>>>>=
>live=20
> in Canada and shipping is always stupid expensive), I'll=20
> =
>get<BR>>to<BR>>>>>work<BR>>>>>>>>>=
>on=20
> it.<BR>>>>>>>>>But even then, I can't make any =
>
> promises except to=20
> =
>try.<BR>>>>>>>>><BR>>>>>>>>&=
>gt;All=20
> the=20
> =
>best,<BR>>>>>>>>><BR>>>>>>>>=
>>Mike<BR>>>>>>>>><BR>>>>>>>&=
>gt;>"Aaron=20
> Allen" <<A=20
> =
>href=3D"mailto:know-spam@not_here.dude">know-spam@not_here.dude</A>>=20
> wrote:<BR>>>>>>>>>>Deeeewwwwwwwwwd..... As =
>soon as=20
> these 15-18 hr days cease, I=20
> =
>will<BR>>>be<BR>>>>>>all<BR>>>>>>>=
>>><BR>>>>>>>>>>over=20
> this.<BR>>>>>>>>>>Did you by chance fix it =
>so that=20
> the Mac mismap bug is gone=20
> =
>for<BR>the<BR>>>>>Mac<BR>>>>>>>>><BR>=
>>>>>>>>>>users?<BR>>>>>>>>=
>;>>Question:=20
> can I run 'this' compressor also w/o causing=20
> =
>problems<BR>on<BR>>>>the<BR>>>>>>>><BR>>=
>>>>>>>>>crunched=20
> version that shipped with the Paris=20
> =
>rigs?<BR>>>>>>>>>><BR>>>>>>>=
>>>>AA<BR>>>>>>>>>><BR>>>>>=
>;>>>>><BR>>>>>>>>>>"Mike=20
> Audet" <mike@.....> wrote in message <A=20
> =
>href=3D"news:4705b550$1@linux">news:4705b550$1@linux</A>...<BR>>>&g=
>t;>>>>>>><BR>>>>>>>>>>>=
>;=20
> Hey=20
> =
>all,<BR>>>>>>>>>>><BR>>>>>>&=
>gt;>>>>=20
> I've got some new=20
> =
>goodies!<BR>>>>>>>>>>><BR>>>>>&=
>gt;>>>>>=20
> I've just released the "PARIS compressor". It's the=20
> =
>original<BR>PARIS<BR>>>>>>><BR>>>>>>>=
>>>>>=20
> compressor<BR>>>>>>>>>>> algo before it =
>was=20
> "crunched" to allow 16 compressors to fit=20
> =
>on<BR>>>one<BR>>>>>>>EDS100<BR>>>>>&g=
>t;>>>>>=20
> card. I've added meters (of course)=20
> =
>AND<BR>>>>>>>>>>><BR>>>>>>&g=
>t;>>>>=20
> I fixed the sample rate bug in this and my previous two=20
> =
>plugins!<BR>>>>>>>>>>><BR>>>>>&=
>gt;>>>>>=20
> If you hadn't heard, almost all the PARIS effects assume 48k=20
> =
>for<BR>>>>their<BR>>>>>>>>><BR>>>&=
>gt;>>>>>>>=20
> calculations,<BR>>>>>>>>>>> even when =
>they are=20
> working at 44.1K. Not these. They=20
> =
>operate<BR>>at<BR>>>>>the<BR>>>>>>>>&=
>gt;<BR>>>>>>>>>>>=20
> project<BR>>>>>>>>>>> sample rate. =
>Can you=20
> hear a difference? You tell=20
> =
>me!<BR>>>>>>>>>>><BR>>>>>>&g=
>t;>>>>=20
> you can download these at <A=20
> =
>href=3D"http://www.mikeaudet.com/ensoniq.ca">www.mikeaudet.com/ensoniq.ca=
></A>=20
> or<BR>>>>>>>>>>> once the DNS goes =
>through,=20
> simply at=20
> =
>ensoniq.ca.<BR>>>>>>>>>>><BR>>>>&g=
>t;>>>>>>=20
> These plugins are released as "pay what you can" (ie - not=20
> =
>free).<BR>>>>><BR>>>>>><BR>>>>>>=
>;><BR>>>>>>>>I'm<BR>>>>>>>>&=
>gt;>>=20
> not a rich man, and I could use the=20
> =
>help.<BR>>>>>>>>>>><BR>>>>>>=
>>>>>>=20
> As always, let me know what you=20
> think.<BR>>>>>>>>>>>=20
> =
><BR>>>>>>>>>><BR>>>>>>>>&=
>gt;><BR>>>>>>>>><BR>>>>>>>&g=
>t;<BR>>>>>>><BR>>>>>><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>
>
>
|
|
|
|
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91244 is a reply to message #91243] |
Wed, 10 October 2007 10:37 |
mike audet[1]
Messages: 129
Registered: February 2006
|
Senior Member |
|
|
Thanks for this, Chuck. At first, I was just throwing exceptions to see if
a block of code was being run. Then, I found your fprintf code, and built
in a running log of what was going on.
This sounds a lot better. :)
As for the reverb, I actually spent a couple of days trying to get it running,
but it was one of the first things I did, and I'm not sure if the problem
was that I didn't know what I was doing, or if the compiled object code was
broken. Do you have a copy of the dsp source for that one? The posted code
only had the compiled .o file.
Thanks again!
Mike
"chuck duffy" <c@c.com> wrote:
>
>For more info on
>
>dbgprint
>http://msdn2.microsoft.com/en-us/library/ms792790.aspx
>
>debugview
> http://www.microsoft.com/technet/sysinternals/Miscellaneous/ DebugView.mspx
>
>Sprinkling
>www.parishilton.com
>
>Chuck
>
>"Neil" <IOUOI@OIU.com> wrote:
>>
>>Paul Braun <cygnus_nospam@ctgonline.org> wrote:
>>>On 10 Oct 2007 10:06:42 +1000, "chuck duffy" <c@c.com> wrote:
>>>>
>>>>Sprinkle debugprints throughout your code, then pick up the output with
>>sysinternals
>>>>debugview, available at www.sysinternals.com
>>>>
>>>
>>>Dude! WTF did you just say???? And is that legal here in the USA???
>>
>>No kidding... last time I sprinkled debugprints anywhere it
>>cost me a $500 fine & a day in jail.
>>
>>:D
>>
>
|
|
|
|
| Re: *******PARIS Compressor Released plus updates******* [message #91251 is a reply to message #91244] |
Wed, 10 October 2007 16:00 |
chuck duffy
Messages: 453
Registered: July 2005
|
Senior Member |
|
|
I never had the code for the reverb, but I do have a working compiled version
including presets that were imported from the DP/PRO. I have to find it
of course.
Chuck
"Mike Audet" <mike@....> wrote:
>
>Thanks for this, Chuck. At first, I was just throwing exceptions to see
if
>a block of code was being run. Then, I found your fprintf code, and built
>in a running log of what was going on.
>
>This sounds a lot better. :)
>
>As for the reverb, I actually spent a couple of days trying to get it running,
>but it was one of the first things I did, and I'm not sure if the problem
>was that I didn't know what I was doing, or if the compiled object code
was
>broken. Do you have a copy of the dsp source for that one? The posted
code
>only had the compiled .o file.
>
>Thanks again!
>
>Mike
>
>
>"chuck duffy" <c@c.com> wrote:
>>
>>For more info on
>>
>>dbgprint
>>http://msdn2.microsoft.com/en-us/library/ms792790.aspx
>>
>>debugview
>> http://www.microsoft.com/technet/sysinternals/Miscellaneous/ DebugView.mspx
>>
>>Sprinkling
>>www.parishilton.com
>>
>>Chuck
>>
>>"Neil" <IOUOI@OIU.com> wrote:
>>>
>>>Paul Braun <cygnus_nospam@ctgonline.org> wrote:
>>>>On 10 Oct 2007 10:06:42 +1000, "chuck duffy" <c@c.com> wrote:
>>>>>
>>>>>Sprinkle debugprints throughout your code, then pick up the output with
>>>sysinternals
>>>>>debugview, available at www.sysinternals.com
>>>>>
>>>>
>>>>Dude! WTF did you just say???? And is that legal here in the USA???
>>>
>>>No kidding... last time I sprinkled debugprints anywhere it
>>>cost me a $500 fine & a day in jail.
>>>
>>>:D
>>>
>>
>
|
|
|
|
Goto Forum:
Current Time: Fri Nov 22 04:06:31 PST 2024
Total time taken to generate the page: 0.04262 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
