On 1/6/19 4:43 AM, Carl Eugen Hoyos wrote:
> 2019-01-03 6:19 GMT+01:00, David Bryant :
>> On 12/28/18 3:56 AM, Paul B Mahol wrote:
>>> On 12/24/18, Derek Buitenhuis wrote:
On 24/12/2018 17:47, David Bryant wrote:
> I want to do that, but am swamped at work right now, so it will probably
>
2019-01-03 6:19 GMT+01:00, David Bryant :
> On 12/28/18 3:56 AM, Paul B Mahol wrote:
>> On 12/24/18, Derek Buitenhuis wrote:
>>> On 24/12/2018 17:47, David Bryant wrote:
I want to do that, but am swamped at work right now, so it will probably
be a few months before I can get to that.
>>>
On Wed, Jan 02, 2019 at 09:19:30PM -0800, David Bryant wrote:
> On 12/28/18 3:56 AM, Paul B Mahol wrote:
> > On 12/24/18, Derek Buitenhuis wrote:
> >> On 24/12/2018 17:47, David Bryant wrote:
> >>> I want to do that, but am swamped at work right now, so it will probably
> >>> be a few months befor
On 12/28/18 3:56 AM, Paul B Mahol wrote:
> On 12/24/18, Derek Buitenhuis wrote:
>> On 24/12/2018 17:47, David Bryant wrote:
>>> I want to do that, but am swamped at work right now, so it will probably
>>> be a few months before I can get to that.
>>>
>>> In the meantime, I think this patch would b
On 12/24/18, Derek Buitenhuis wrote:
> On 24/12/2018 17:47, David Bryant wrote:
>> I want to do that, but am swamped at work right now, so it will probably
>> be a few months before I can get to that.
>>
>> In the meantime, I think this patch would be a safe stopgap (and prevent
>> the Kodi crash)
On 24/12/2018 17:47, David Bryant wrote:
> I want to do that, but am swamped at work right now, so it will probably be a
> few months before I can get to that.
>
> In the meantime, I think this patch would be a safe stopgap (and prevent the
> Kodi crash).
I think it's OK for the meantime (my op
On 12/24/18 12:21 AM, Paul B Mahol wrote:
> On 12/24/18, David Bryant wrote:
>> On 11/21/18 9:50 PM, David Bryant wrote:
>>> On 11/20/18 10:58 PM, Peter Ross wrote:
On Tue, Nov 20, 2018 at 09:23:03PM -0800, David Bryant wrote:
> Hi,
>
> Was made aware of this problem on Kodi:
On 12/24/18, David Bryant wrote:
> On 11/21/18 9:50 PM, David Bryant wrote:
>> On 11/20/18 10:58 PM, Peter Ross wrote:
>>> On Tue, Nov 20, 2018 at 09:23:03PM -0800, David Bryant wrote:
Hi,
Was made aware of this problem on Kodi:
https://github.com/xbmc/xbmc/issues/14771
>>
On 11/21/18 9:50 PM, David Bryant wrote:
> On 11/20/18 10:58 PM, Peter Ross wrote:
>> On Tue, Nov 20, 2018 at 09:23:03PM -0800, David Bryant wrote:
>>> Hi,
>>>
>>> Was made aware of this problem on Kodi:
>>>
>>> https://github.com/xbmc/xbmc/issues/14771
>>>
>>> I'm going to try to add full WavPack
On 11/20/18 10:58 PM, Peter Ross wrote:
> On Tue, Nov 20, 2018 at 09:23:03PM -0800, David Bryant wrote:
>> Hi,
>>
>> Was made aware of this problem on Kodi:
>>
>> https://github.com/xbmc/xbmc/issues/14771
>>
>> I'm going to try to add full WavPack DSD support, but thought in the
>> meantime it wou
On Tue, Nov 20, 2018 at 09:23:03PM -0800, David Bryant wrote:
> Hi,
>
> Was made aware of this problem on Kodi:
>
> https://github.com/xbmc/xbmc/issues/14771
>
> I'm going to try to add full WavPack DSD support, but thought in the meantime
> it would be a good idea to detect and error out early
Hi,
Was made aware of this problem on Kodi:
https://github.com/xbmc/xbmc/issues/14771
I'm going to try to add full WavPack DSD support, but thought in the meantime
it would be a good idea to detect and error out early.
Thanks!
David
>From c86aacdf98c3d34a3f8d63233e01c4a3ab55577e Mon Sep 17
12 matches
Mail list logo