Re: wip/soundfont (and wip/ branches)

2016-10-18 Thread Stefan Westerfeld
Hi! On Thu, Sep 29, 2016 at 02:54:27PM +0200, Tim Janik wrote: > On 21.09.2016 21:08, Stefan Westerfeld wrote: > >> If you want me to guess, it could be related to bse_object_new now > >> hardcoding the C++ object types that are paired with a GType object. > > > > > Fixed, by replacing

Re: wip/soundfont (and wip/ branches)

2016-09-29 Thread Tim Janik
On 21.09.2016 21:08, Stefan Westerfeld wrote: >> If you want me to guess, it could be related to bse_object_new now >> hardcoding the C++ object types that are paired with a GType object. >> But you're right it needs further investigation. > > Fixed, by replacing g_object_new with

Re: wip/soundfont (and wip/ branches)

2016-09-21 Thread Tim Janik
On 21.09.2016 12:49, Stefan Westerfeld wrote: >>> However if you start BEAST, go to SoundFont repository and click load >>> and load a sound font, this is what happens: >>> >>> beast-0.10.1: bseobject.cc:167: void bse_object_init(BseObject*): >>> Assertion `in_bse_object_new' failed. >>>

Re: wip/soundfont (and wip/ branches)

2016-09-21 Thread Stefan Westerfeld
Hi! On Tue, Sep 20, 2016 at 07:09:52PM +0200, Tim Janik wrote: > On 20.09.2016 15:48, Stefan Westerfeld wrote: > > I squashed the whole SoundFont stuff into one commit, making it easier to > > merge > > for me. It contains > > > > - my original submission > > - everything from your

Re: wip/soundfont (and wip/ branches)

2016-09-20 Thread Tim Janik
On 20.09.2016 15:48, Stefan Westerfeld wrote: > I squashed the whole SoundFont stuff into one commit, making it easier to > merge > for me. It contains > > - my original submission > - everything from your wip/soundfont > > and was rebased to the BEAST master branch, and fixed to the degree