On 12/17/2014 01:04 AM, Lukas W. wrote:
> Only if a QObject has a parent Qt automatically deletes all children
> on parent deconstruction.
Yes, our widgets are initialized with the parent widget (ie. the
dialog/window) as parent, so the widgets get destroyed whenever the
parent window is destroyed
2014-12-16 23:47 GMT+01:00 I'm Umcaruje :
> AFAIR, grejppi managed to make a fully functional VST dll of his bytes LV2
> synth, with only the VeSTige headers. It did not have a GUI though, but it
> worked in proprietary DAW's like Reaper and FL studio with no problems.
But why use VST at all then?
Only if a QObject has a parent Qt automatically deletes all children on
parent deconstruction.
2014-12-16 23:52 GMT+01:00 Vesa :
>
> On 12/17/2014 12:49 AM, Dave French wrote:
> > I decided to learn how to use Valgrind on code i knew, so decided a
> > good place to start was to analyse my Eq plugi
On 12/17/2014 12:49 AM, Dave French wrote:
> I decided to learn how to use Valgrind on code i knew, so decided a
> good place to start was to analyse my Eq plugin as that is fresh in my
> mind. Im learning quick :) and can see this to be very useful. Think i
> may be turning into "Dave the bug hunt
AFAIR, grejppi managed to make a fully functional VST dll of his bytes LV2
synth, with only the VeSTige headers. It did not have a GUI though, but it
worked in proprietary DAW's like Reaper and FL studio with no problems.
-Uroš|Umcaruje
On 16 December 2014 at 21:43, Vesa wrote:
>
> On 12/16/2014
The three bugs confirmed *fixed* for Win 64.
- Memory leak with Sample track
- LB302 audio cutoff on preset preview
- LB302 preset preview crashes LMMS
--
View this message in context:
http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Let-s-release-1-1-tp10316p11212.html
Sent from the lm
So, sample track bug is fixed as well as the outstanding LB302 bugs (LB302
preview crash, LB302 preview cut off).
I've begun the build process for RC11. If the build works and uploads
properly, the win32/win64 builds should soon appear here (about 30 minute)
https://github.com/LMMS/lmms/releases/
On 12/16/2014 07:50 PM, Tres Finocchiaro wrote:
> Wishful thinking, but if we get Ian's source code and cross-compile
> the DLL using Mingw (or Winegcc or Mono) and clean-room VST headers (I
> believe we have some of these in our code, right?) could we offer to
> the world the first GPL 2.0 VST?
T
Will have a look. It gives me a reason to learn something.
On 16 Dec 2014 20:35, "Vesa" wrote:
> On 12/16/2014 07:32 PM, Dave French wrote:
> > Today was my first time of using Valgrind to detect memory leaks. Its
> > awsome, and Im planning on spending a bit of time getting to know it.
> > As a
On 12/16/2014 07:32 PM, Dave French wrote:
> Today was my first time of using Valgrind to detect memory leaks. Its
> awsome, and Im planning on spending a bit of time getting to know it.
> As a command line tool the output is very verbose, but I ran it in Qt
> Creator, and it made viewing the log s
>
> > That would be smart, Tres, but I wrote it in Flowstone...
What language?
> Also, you might want to look at this.
> https://github.com/LMMS/lmms/issues/1436
I was talking about a GPL VST (if that's even possible) so I think it's a
bit different from your bug report. :)
-Tres
- tres.fi
That would be smart, Tres, but I wrote it in Flowstone...
Also, you might want to look at this.
https://github.com/LMMS/lmms/issues/1436
Any developer who is willing to help make this simple synth, just contact
me and I will guide the C++ replication.
On Tue, Dec 16, 2014 at 10:50 AM, Tres Finocc
Wishful thinking, but if we get Ian's source code and cross-compile the DLL
using Mingw (or Winegcc or Mono) and clean-room VST headers (I believe we
have some of these in our code, right?) could we offer to the world the
first GPL 2.0 VST?
Reason I mention this is as we approach a more consistent
Today was my first time of using Valgrind to detect memory leaks. Its
awsome, and Im planning on spending a bit of time getting to know it. As a
command line tool the output is very verbose, but I ran it in Qt Creator,
and it made viewing the log so simple. I have a feeling this will be a very
usef
I were just assuming that it would be better that diizy looked at the code
since he were going to fix the LB302 and if someone changes the fix code
now without looking in depth in LB302... Also assuming diizy did go in
depth and know LB302 better than anyone else.
On Tue, Dec 16, 2014 at 6:18 AM,
>
> > :/ if @1450 ( https://github.com/LMMS/lmms/issues/1450 ) is for 'real' then
> that /is/ a showstopper
Unless its been around for years, then it's not related to the 1.1
release. Please add some more test results to this bug report so we know
how to proceed. :)
- tres.finocchi...@gmail.co
>
> Well from the top of my head, I'd say you, Vesa and Lukas-W would make
> great mentors. :D But this is entirely voluntary. Anyone can apply as a
> mentor. :-)
I agree that Lukas and Vesa would be great candidates, but they would need
to come forward and elect themselves for this.
I am not a
On 16 December 2014 at 18:49, Tres Finocchiaro
wrote:
>> > If we'd want to participate then some senior developers who are
>> > over-seeing the whole project should take lead in this and who'd be willing
>> > to represent our community.
>
>
> Thanks kindly for the information.
>
> As far as the pr
>
> > Well as an organisation we'd need to apply in the program. And
> Org application process starts from February 09 at 19:00 UTC. So we
> have about 1 month and 3 weeks to prepare our proposal. :-) And this page
> has the complete instructions and FAQs.
> >
> http://www.google-melange.com/gsoc/d
On 16 December 2014 at 10:46, Tres Finocchiaro
wrote:
>> > Are we going to apply in GSoC 2015?
>
> Sure if you want. I don't think you'll get any major objections in doing so
> and we always need the help. If you do, please make sure to communicate
> with the dev team properly.
>
> We actually h
It seems so...
Well, I think that sample track will be fixed when they'll be updated,
so we may leave it if the problem is big. But it might actually be a
simple code mistake.
Did a video about it.
Il 16/12/2014 12:45, musikbear ha scritto:
> :/ if @1450 ( https://github.com/LMMS/lmms/issues/1
:/ if @1450 ( https://github.com/LMMS/lmms/issues/1450 ) is for 'real'
then that /is/ a showstopper
--
View this message in context:
http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Let-s-release-1-1-tp10316p11196.html
Sent from the lmms-devel mailing list archive at Nabble.com.
-
22 matches
Mail list logo
