C++ coder required

Richard Owlett wrote:
> On 1/25/2016 9:21 AM, Tom Gardner wrote:
>
>> As everybody here reads comp.risks, don't they (and
>> if not, why not), they will have seen
>> <http://www.rvs.uni-bielefeld.de/publications/Reports/KempLancasterPowerCuts201512V3.pdf>
>>
>> referenced in
>> <http://catless.ncl.ac.uk/Risks/29.22.html#subj1>
>>
>> The relevant bit is that when, not if, electric power
>> is out, buying necessities is /much/ easier with paper
>> money than with electronic money ;}
>>
>
> We old folks get to watch the morning news.
> Seems Sweden [IIRC} has plans to totally eliminate paper money.


A certain class of economist predicts extreme difficulties lie that
way. And why bother? Tax cheats? They're in the noise and
transactions that are cash outside the tax system generally don't
cause any harm anyway.

-- 
Les Cargill

angrydude wrote:
> On Monday, January 25, 2016 at 9:19:41 AM UTC-5, Les Cargill wrote:
>> Tim Wescott wrote:
>>> On Sat, 23 Jan 2016 04:08:07 -0600, zukan wrote:
>>>
>>>>> On Thursday, January 21, 2016 at 8:51:08 AM UTC-6, zukan
>>>>> wrote:
>>>>>>> On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
>>>>>> He preferred a share in the product as opposed to money as
>>>>>> he wanted
>>>> to
>>>>> be
>>>>>> involved in this particular project.
>>>>>
>>>>> There's your real problem. In fact, the first thing I would
>>>>> have asked
>>>> is:
>>>>> shared royalties? (and in reply to "No", "Then you're my
>>>>> competition ... and I take no prisoners.").
>>>>>
>>>>> A lot of programmers, I think, are wising up to the
>>>>> traditional contract-for-hire arrangement. You see: it's a
>>>>> lot of brain-busting
>>>> creativity to put
>>>>> into something that is -- in effect -- a form of authoring
>>>>> and writing (not engineering; yes, I'm talking to you, fellow
>>>>> DSP'ers!) and to have
>>>> the
>>>>> fruits of one's creativity go out to someone else with
>>>>> nothing to show
>>>> for it
>>>>> but some money, is way too much to lose.
>>>>>
>>>>> It's a lot like slicing off layers of your brain to give to
>>>>> someone else as a brain transplant donor.
>>>>>
>>>>> If you do the following you may get more takers: (1) ensure
>>>>> the actual coding be distributable and distributed open
>>>>> source, (2) contract only
>>>> for the
>>>>> fitting of the code to the application on hand (the widget)
>>>>> -- which qualifies as a service analogous to being an editor,
>>>>> rather than a form
>>>> of
>>>>> writing or engineering, (3) keep the original developers'
>>>>> names on the
>>>> code,
>>>>> copyrighting it in their names (but to be distributed under
>>>>> copyleft).
>>>>>
>>>>> Better yet, look for freely distributed DSP libraries that do
>>>>> VST, take them and adapt them to your projects.
>>>>>
>>>>> Either way, in the process, you'll also make your operation
>>>>> more Millennial-friendly in appearance, rather than something
>>>>> more reminiscent
>>>> of the
>>>>> Sears, McDonalds, Walmarts, Microsofts of the world and the
>>>>> previous
>>>> century.
>>>>
>>>> It's not like that at all. He wanted royalties, I prefer to pay
>>>> up front. He wanted to be a part of the company and not just
>>>> involved in one product.
>>>>
>>>> I work in the music industry as a writer. All of my 6 books in
>>>> print have been pirated, all of my sound libraries that I
>>>> earned royalties from for companies like Emu and Roland have
>>>> been pirated. I have yet to receive monies from a film score I
>>>> wrote and I have had all my site content duplicated on torrent
>>>> sites.
>>>>
>>>> The reality of our industry is that we have such little earning
>>>> power left, due to the lack of longevity of any product, that
>>>> we have tp collaborate with competitors and release products
>>>> regularly. That way we get about 1-3 months worth of revenue
>>>> before the content is available everywhere.
>>>>
>>>> This is the world we live in today.
>>>
>>> I'm probably going to get dumped on for saying this, but the
>>> whole notion of copyright really evolved in Europe in the 18th
>>> century, and while patent law in some form or another goes back
>>> to the ancient Greeks it had a lot more with who had royal favor
>>> than with who actually invented something.
>>>
>>
>> Yep. The term is common between "a monopoly on the sales &
>> manufacture of a device" and "a monopoly on trade in good <x>".
>> IOW, The Hudson's Bay Company had a royal patent on the North
>> American fur trade.
>>
>>> Personally I think that copyright law really only works in an
>>> environment where there is significant capital investment in
>>> reproducing a work, and where everyone values the notion of
>>> copyright.  That's why you didn't see it come about until after
>>> movable type was ubiquitous, and it's why -- I believe -- that
>>> it's going to follow moving type into obsolescence.
>>>
>>
>> Very interesting idea.
>>
>>> Copyrights were already starting to fray with the invention of
>>> the copier, cassette tape and VCR, but in the digital age they
>>> become so difficult to enforce that -- in my opinion -- the
>>> constraints placed on individuals to do so cause more damage to
>>> society than the good caused by keeping their integrity.
>>>
>>
>> And another way to look at it is that money may be slowly going
>> obsolete.
>>
>> The net effect of all this "free" might be expressed in
>> accelerating deflation.
>>
>>> The world has changed, and we need to find a way to fund creative
>>> efforts like book-writing and audio sampling, without putting
>>> everyone's digital devices in chains.
>>>
>>
>> This hasn't worked, so far. Kindle style books are the only thing
>> that works now, SFAIK. I only say that from a distance; they may
>> be pirated more than I know.
>>
>> -- Les Cargill
>
> "This hasn't worked, so far. Kindle style books are the only thing
> that works now, SFAIK. I only say that from a distance; they may be
> pirated more than I know."
>
> All useful books in demand are pirated, even those with only paper
> editions - someone turns all the pages and puts them on scanner..


That's kind of more excerpting than piracy. I'd done that
mainly when putting together materials legitimately considered
under Fair Use, or for books out of print ( before
Abe Books ).

There exists another plane of "economy" where referring to material
adds value.

If blogger X has 2M readers and reviews your book, a paltry 1%
conversion rate means 20,000 sales.


> Heck, Google does in on massive scale - it's called book digitation
> project or something like that - going to all libraioes, scanning all
> books then doing OCR Electronic books, kindle or whatever, are the
> easiest to pirate - once your have your software setup the labor is
> zero
>

Yeah, there's that. I'm not sure we have a coherent ... system
for dealing with this.

And meanwhile, I can't even get to Forbes.com any more without taking
some action. They're walled off.

-- 
Les Cargill

On Mon, 25 Jan 2016 11:59:07 -0600, Les Cargill wrote:

> Richard Owlett wrote:
>> On 1/25/2016 9:21 AM, Tom Gardner wrote:
>>
>>> As everybody here reads comp.risks, don't they (and if not, why not),
>>> they will have seen
>>> <http://www.rvs.uni-bielefeld.de/publications/Reports/
KempLancasterPowerCuts201512V3.pdf>
>>>
>>> referenced in <http://catless.ncl.ac.uk/Risks/29.22.html#subj1>
>>>
>>> The relevant bit is that when, not if, electric power is out, buying
>>> necessities is /much/ easier with paper money than with electronic
>>> money ;}
>>>
>>>
>> We old folks get to watch the morning news.
>> Seems Sweden [IIRC} has plans to totally eliminate paper money.
> 
> 
> A certain class of economist predicts extreme difficulties lie that way.
> And why bother? Tax cheats? They're in the noise and transactions that
> are cash outside the tax system generally don't cause any harm anyway.

I suspect that some de-facto system will arise that will amount to an 
underground cash economy.  The two scenarios that spring to mind 
immediately are bus tokens and out-of-country currency.

-- 
www.wescottdesign.com

Tim Wescott <seemywebsite@myfooter.really> Wrote in message:
> On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
> 
>> Hi
>> 
>> I am a complete novice when it comes to coding so I have a team that
>> helps me design vstis for the audio industry.
>> 
>> We have a coder but are not confident in his abilities as he doesn't
>> seem to understand maths and we tech heads talk in maths. He doesn't
>> seem to grasp schematics either and is not English so explaining simple
>> rudimentary functions can take ages.
>> 
>> We are tightly linked to Sound On Sound magazine and this vsti has been
>> in the making for 3 years as it incorporates advanced technologies.
>> 
>> We are looking for a coder to undertake either helping our coder with
>> DSP algorithms or to recode the whole project.
>> 
>> Please feel free to contact me directly at:
>> 
>> info_at_samplecraze.com
>> 
>> Many thanks.
>> 
>> Eddie Bazil Samplecraze
> 
> First: feel free to contact me by email, I may be interested.
> 
> Second: there's a lot of advantage to someone local, so you may not be 
> interested in me.
> 
> Third: With all due respect, this sounds like a failure in interviewing 
> and job specification.  If you're not pissed off by that comment, here 
> are some suggestions:
> 
> 1: Advertise for a software engineer, not a "coder".  A "coder" is a 
> person who cobbles code together.  An engineer is a person who does 
> structured design of the entire software set, and even (in embedded 
> projects) impacts the hardware design.  Do you want a rotting pile of 
> spaghetti code, or do you want software?
> 
 <snip>

Three motherfucking years to code up a VSTi?!

-- 


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

On Friday, January 29, 2016 at 11:28:16 AM UTC-5, bitrex wrote:
> Tim Wescott <seemywebsite@myfooter.really> Wrote in message:
> > On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
> > 
> >> Hi
> >> 
> >> I am a complete novice when it comes to coding so I have a team that
> >> helps me design vstis for the audio industry.
> >> 
> >> We have a coder but are not confident in his abilities as he doesn't
> >> seem to understand maths and we tech heads talk in maths. He doesn't
> >> seem to grasp schematics either and is not English so explaining simple
> >> rudimentary functions can take ages.
> >> 
> >> We are tightly linked to Sound On Sound magazine and this vsti has been
> >> in the making for 3 years as it incorporates advanced technologies.
> >> 
> >> We are looking for a coder to undertake either helping our coder with
> >> DSP algorithms or to recode the whole project.
> >> 
> >> Please feel free to contact me directly at:
> >> 
> >> info_at_samplecraze.com
> >> 
> >> Many thanks.
> >> 
> >> Eddie Bazil Samplecraze
> > 
> > First: feel free to contact me by email, I may be interested.
> > 
> > Second: there's a lot of advantage to someone local, so you may not be 
> > interested in me.
> > 
> > Third: With all due respect, this sounds like a failure in interviewing 
> > and job specification.  If you're not pissed off by that comment, here 
> > are some suggestions:
> > 
> > 1: Advertise for a software engineer, not a "coder".  A "coder" is a 
> > person who cobbles code together.  An engineer is a person who does 
> > structured design of the entire software set, and even (in embedded 
> > projects) impacts the hardware design.  Do you want a rotting pile of 
> > spaghetti code, or do you want software?
> > 
>  <snip>
> 
> Three motherfucking years to code up a VSTi?!
> 
> -- 
> 
> 
> ----Android NewsGroup Reader----
> http://usenet.sinaapp.com/

It's not about VST coding - VST coding is trivial. It's about underlying technology - DSP algorithms (and associated intellectual property)

If a new and useful DSP algorithm is publicly disclosed then it takes less than a year to develop optimized implementations for particular purposes and code them up in any language of choice
But it can take 50 years or longer until next sucker is born to discover and publicly disclose new and useful DSP algorithm for VST developers to code up ...