It's probably too difficult as the developers live all over the world, I
suspect. A Google Hangout might be a good idea for a meetup.
On Thu, Jan 9, 2014 at 4:10 PM, Nathan McCoy wrote:
> I was thinking for a while it would be nice to get an event setup where
> developers could get together and
Thanks Tobias! The move to github will be a real boost for new
development.
Great move!
Devin
On Thu, Jan 9, 2014 at 3:33 PM, Tobias Doerffel
wrote:
> Hi,
>
> thank you all for your helpful and diverse input! I also agree with most
> of what has been said. Even though I do have time to contr
Hi all,
I'm a programmer and I've contributed to LMMS in the past (multi-export
feature). I do think it is a bit more work to be a part of this project
because one must submit patches through the mailing list. I would really
like to see the source hosted on Github, as it makes it much easier to
Thanks Toby. I was just logging into my computer to take a look into this,
but you beat me to it.
Devin
On Sun, Nov 25, 2012 at 4:50 AM, Tobias Doerffel
wrote:
> Hi,
>
> I found and fixed the bug. The according commit just has been pushed
> to the git repository - everyone should update.
>
> Th
All,
Here is the patchset for my multiple track export feature. It works now
the way I originally envisioned.
For example, after I export tracks on my little song, I see this in the
directory I created:
devin@devin-studio:~/lmms/projects/fff$ ls
0_Defaultpreset.wav 3_Defaultpreset.wav 6_c
Would someone give me a quick overview of the BB track architecture?
I've been debugging for a few hours and can't quite make sense of it yet.
>From a song, you can get a list of tracks, and some of those tracks are of
type track::BBTrack.
At this point I'm conceptually after the tracks within t
o i tend to layer sounds, and this would be a bad if i didnt have the
> effects i wanted on layered sounds.
>
> but i repeat, if you added the feature instead of replacing/changing it
> from a mixer track export, that would be awesome.
>
> just my two cents
>
> 2012/10/29 Dev
);
- if (m_multi_export==true)
+ if (m_multiExport==true)
{
multi_render();
}
On Mon, Oct 29, 2012 at 3:19 AM, Tobias Doerffel
wrote:
> Hi,
>
> Thanks for your efforts!
>
> 2012/10/29 Devin Venable :
> > ...
> > + std::vector m_to_render_vec;
> > } ;
&g
Running out of time tonight, but going to submit working patch for
individual track export (for review).
(Note, I think the LMMS submitting a patch page should say to use "git diff
--cached" instead of "git diff" since right above you instruct the reader
to add the changed files to the staging are
In the multi-track export feature I'm working on, I run into a snag. The
algorithm is essentially this:
Get list of all enabled tracks
for each track
mute all but current one
call ProjectRenderer::startProcessing
restore original mute states
Since ProjectRender is a QThread, and since t
I've almost finished development of a multi-track rendering feature. Still
have a few details to complete, but in general it works. I've added an
"Export tracks..." menu item that dumps all tracks individually.
Keep bugging me to make sure I finish this and post the patch!
Devin
---
g submixes might work.
Devin
On Wed, Sep 19, 2012 at 4:44 PM, Raine M. Ekman wrote:
> Quoting Devin Venable :
>
> On Wed, Sep 19, 2012 at 11:17 AM, Raine M. Ekman wrote:
>>
>> Quoting Devin Venable :
>>> > So for dumping, I was thinking about an "export all
On Wed, Sep 19, 2012 at 11:17 AM, Raine M. Ekman wrote:
> Quoting Devin Venable :
> > So for dumping, I was thinking about an "export all instruments"
> features,
> > that just loops through the available instruments,
>
> My feeling, speaking from a user poi
I've just started looking over the code. I love LMMS, but wish I could
easily dump tracks into Ardour, or have some reliable sync with Ardour.
Jack sync (master or slave) would be great for syncing with an external
sequencer when you need something more powerful than what is built in.
So for dum
14 matches
Mail list logo
