Greetings,

Auburn Sounds has released his second product fully made in D. It is intended to solve the following audio mixing problems:
- "I need to put more stereo in this track" and
- "regular panning doesn't sound that good on headphones".

https://www.auburnsounds.com/products/Panagement.html
https://www.youtube.com/watch?v=YytzPk09cQk

On the dplug side (https://github.com/p0nce/dplug/) rendering got optimized further, Audio Unit v2 was added and LDC became the compiler of choice for all releases. I couldn't been happier about LDC development.

On this note: if LDC ever supports iPhone and dplug implement Audio Unit v3, this might open up the iPhone market for audio effects since AU are sellable on the AppStore directly.

Unloading of shared libraries on OS X continues to be a problem though, it would be nice if it worked in 64-bit.

Last piece of news: I also started freelancing by accident (automating signaletics, in D too). So if you need a D programmer drop me an email!

On 27/06/16 13:02, Guillaume Piolat wrote:

> Unloading of shared libraries on OS X continues to be a problem though,
> it would be nice if it worked in 64-bit.

I know the current situation is not ideal, but does it cause any problems?

-- 
/Jacob Carlborg

On Monday, 27 June 2016 at 18:59:35 UTC, Jacob Carlborg wrote:
> On 27/06/16 13:02, Guillaume Piolat wrote:
>
>> Unloading of shared libraries on OS X continues to be a problem though,
>> it would be nice if it worked in 64-bit.
>
> I know the current situation is not ideal, but does it cause any problems?

My wording was a bit strong.

As you may remember, the workaround involved "leaking" the dynlib.

On OS X I keep having a lingering crash which is a bit random, happens with multiple instantiation/closing of a dynlib. It is a bit hard to reproduce and I failed to remove it. It follows an hysteresis pattern, when it's here it reproduces reliably, then disappear. With LDC-b2 I thought it was gone (was codegen I thought), but seems still here somehow.

I'm not sure at all if it's related at all to dynlib unloading (wild guess probability: 50%).

On 27/06/16 21:22, Guillaume Piolat wrote:

> My wording was a bit strong.
>
> As you may remember, the workaround involved "leaking" the dynlib.
>
> On OS X I keep having a lingering crash which is a bit random, happens
> with multiple instantiation/closing of a dynlib. It is a bit hard to
> reproduce and I failed to remove it. It follows an hysteresis pattern,
> when it's here it reproduces reliably, then disappear. With LDC-b2 I
> thought it was gone (was codegen I thought), but seems still here somehow.
>
> I'm not sure at all if it's related at all to dynlib unloading (wild
> guess probability: 50%).

Ok, I see. We need to add proper support of dynamic libraries on OS X.

-- 
/Jacob Carlborg

On Monday, 27 June 2016 at 11:02:33 UTC, Guillaume Piolat wrote:
> Unloading of shared libraries on OS X continues to be a problem though, it would be nice if it worked in 64-bit.

Sorry I haven't had much time to work on this lately. I'm not sure how soon I will have time. If anyone else wanted to champion this effort, we could discuss passing the torch and trying to make use of the work I've done thus far. I still plan to do it at some point, but I don't want to stand in anyone's way if there is an urgent need for it.

    Bit

On Friday, 1 July 2016 at 06:07:13 UTC, bitwise wrote:
> On Monday, 27 June 2016 at 11:02:33 UTC, Guillaume Piolat wrote:
>> Unloading of shared libraries on OS X continues to be a problem though, it would be nice if it worked in 64-bit.
>
> Sorry I haven't had much time to work on this lately. I'm not sure how soon I will have time. If anyone else wanted to champion this effort, we could discuss passing the torch and trying to make use of the work I've done thus far. I still plan to do it at some point, but I don't want to stand in anyone's way if there is an urgent need for it.
>
>     Bit

Stefan Koch/UplinkCoder told me he could be interested.
TBH I would only need this bug fixed in LDC. https://github.com/ldc-developers/ldc/issues/1071
I've added $200 to the associated bounty, if that even matters.

On 01/07/16 08:07, bitwise wrote:

> Sorry I haven't had much time to work on this lately. I'm not sure how
> soon I will have time. If anyone else wanted to champion this effort, we
> could discuss passing the torch and trying to make use of the work I've
> done thus far. I still plan to do it at some point, but I don't want to
> stand in anyone's way if there is an urgent need for it.

The native TLS support is merged, so that's one issue out of the way at least.

-- 
/Jacob Carlborg