2017-04-16 0:54 GMT+02:00 Tim <[email protected]>:
>
>
> On 2017-04-15 04:00 PM, Robert Jonsson wrote:
>
> Hey guys,
>
>
> 2017-04-14 9:37 GMT+02:00 Dan MacDonald <[email protected]>:
>
>> Yes!
>>
>> If you don't release soon, the changelog will be so big it might take
>> out SF.net. In fact, it might be easier to list whats not changed
>> since the last release.
>>
>
> Muhaha. Well wouldn't that be a fun way of doing it ;)
>
> Ha ha. Yeah that ChangeLog is such an epic tome that
> were gonna have to compress it soon !
>
>
>
>
>>
>> I also find it quite funny how you refer to Robert as Spamatica. I
>> know thats one of his nick/stagenames but it has never quite sat right
>> with me when I read it.
>>
>> As you were!
>>
>> On Fri, Apr 14, 2017 at 12:53 AM, Tim <[email protected]> wrote:
>> > Hi, wondering if you all are OK with rolling another MusE
>> > release from git master, either RC3 or... even final 3.0?
>>
>
> RC3 if I get a say.
>
> No problem. My thoughts as well.
>
> >
>
>> > Any problems I should fix?
>> > Quick tweaks? Look n' feel?
>>
>
> Yeah I'm trying to compile a list as I go, I'm doing some recording
> currently but they are a bit mutually exclusive, testing the program and
> getting something recorded.. so I'm trying to recall what I've had trouble
> with and retesting.
> So far I got these:
> - can't use keyboard navigation in mixer as the pan widget gets the focus
>
> The keys have changed. Sorry, I had to do that.
> They are all listed in the ChangeLog. Should all be working, I hope.
>
Ah! Seems to work fine :) We need some documentation, or more videos :D
>
> - outline on selected mixerstrip is barely visible, the color should be
> stronger and put in the color list in Appearance setings
>
> Yeah I know, it's hard to see. Thinking of ways to improve that.
>
> These are my babies and I don't think they are showstoppers in anyway, I
> hardly use them myself ;)
>
> - Monitor support
> I had some problems with this before, basically too many clicks to get a
> track up and running to record. I think you mentioned doing something about
> it in one of the last checkins but I can't figure out a way to get live
> monitoring without a lot of clicking. Did you make any changes here?
>
> Yup. You have a choice now. Settings, or right click a strip, and
> you can select 'monitor on record arm'.
> I believe that will make it just as before, right? Hit record arm
> and away you go?
>
Didn't get to check this out, if it's like that then it's fine with me.
>
> - Non distinctive Solo/Proxy Solo
> I like these new icons but it turns out these icons are too similar, I
> turned on solo on a few tracks (and the dependent tracks were marked as
> proxy solo) but then the colors were so similar that I didn't know which
> was which so it took me a while to get everything unsoloed ;)
> Maybe make the proxy solo gray scale?
>
> Ah. Yes. Well, I did make a small change last update:
> The icons in the arranger are now more distinguishable.
> (I removed the 'unused' blue portions.)
> However, in the mixer, the icons need to have an appreciable
> 'footprint' so the user knows where to click, since I removed
> any 'outlines', frames, or button boxes.
> So I had to leave the two 'blue' portions of that icon there
> in the mixer only.
>
> I sure do hope y'all dig the meaning of that icon:
> It is supposed to look like two 'spotlights', one is the solo
> spotlight, and the other is the proxy solo spotlight.
> I thought it was quite a clever way to represent four possible
> soloing states. Something a simple 'letter' could not do.
>
> Keep in mind these are SVG icons, so detailed pixel-oriented
> scalable bitmaps are not that easy to do, so I kept them simple,
> and I think that's maybe a good thing here, simpler better.
> On the plus side, the icons are super easy to change as they
> use drawing 'objects' not pixels. I have included their
> LibreOffice project files in the MusE project tree as well.
>
Alright. Yeah, they look neat and I like the spotlight idiom, might be they
are easier to understand now. I'll check it out.
>
> - VST chunk support does not work with airwave (win vst bridge)
> I'm not really sure where the problem is but I'm trying to get Addictive
> drums to save state and it doesn't work. I tried Carla and I think I got it
> to restore the state correctly (it was terribly crashy). back in the day I
> had problems with Addictive and storing state also and it was chunk support
> that was missing in dssi-vst, so this is my first guess.
>
> I struggled to find a native VST synth that utilizes chunk support but I'm
> not sure I found one. I did find that the Discovery synth restores it's
> state only from the first bank, if I switch bank it won't load the correct
> sound.. but it's not clear if this is the same issue, maybe it's just a
> demo limitation.
>
>
>
> Hm, I tried airwave but got lost in the configuration and had to move on.
>
The ui for adding plugins is a bit wierd but once you understand what it
wants it's easy.
You select a specific *.dll and the target folder you want it to bind to
e.g. ~/.vst. A specific *.so file will be created in the target folder with
bootstrap code so it acts as a native vst plugin.
There are some synths that just aren't up to the standard of windows
versions so I'll keep looking at trying to solve this.
Addicitve Drums is one such plugin type, though there has been some great
advances in native drum plugins lately, they aren't on the same level yet.
> If this is something that WAS working in MusE and is now broken, let me
> know.
>
No, I don't think this is something that broke so it's definitely not
stopping a new release.
> >
>> > I need to practice rolling a release, I have never done it.
>> > Spamatica wrote some fine instructions on how to do it.
>>
>
> If I did that's good, I don't recall :D
> There are some hoops to jump through but most of it is straightforward.
> If you want to get your head around it do try to make an RC3 release, not
> so high profile, if it fails for some reasons we just make an RC4. No
> distros will pick up an RC release so I think we can play around a bit.
>
> Sometimes they do, sometimes app releases are so sparse that distros
> resort to using the latest development branches.
>
I guess, but I don't think anyone bundles our current RCs so I'd say it's
safe to assume they'll wait for a proper release.
Regards,
Robert
>
>
> Tim.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Lmuse-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lmuse-developer
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
