2018-01-06 23:33 GMT+01:00 Tim <[email protected]>:
>
>
> On 01/06/2018 04:21 PM, Robert Jonsson wrote:
>
>> Hi Tim,
>>
>> I'm finalizing the 3.0 packaging, thought I would share the current list
>> of issues I have experienced during the last weeks recordings (the ones I
>> remembered to write down that is)
>>
>> From the old list:
>> - Add measure does not take automation into account.
>>
>> New ones I've noted:
>> - Unmuting a track during playback sometimes causes wierd sound offset
>> issues
>>
>
> Didn't notice that. Is that with wave tracks or midi?
Not sure, audio I think, usually I'm deeply into something when it happens
and quickly try to get it working again, I'll report back with more info
next it happens.
>
> - Notes on the first tick in a loop is not played
>>
>
> Hm, maybe my fault, will check.
>
> - At one point I lost audio to master after unsoloing a track, seems not
>> repeatable though.
>> - Shortcuts for putting drum events with lower velocity seems not
>> working... or I don't remember how to use it.
>>
>
> Check them tooltips on the LVx columns for the key combos.
> Various combinations of control, meta and alt do it. Tests OK here.
>
> - Ctrl+C sometimes does not work for copying a part in the arranger, menu
>> alternative works
>> - Automation edit: db cue when editing is not the same as display db
>> - Creating midi-track used to default to last created synth
>>
>
> Hm, don't think it ever did. Someone brought that up a few years back,
> and I replied that we don't know which device the user might want
> the track to output on so we can only assume the default device
> which is going to be one of the hardware devices.
> I figured, half the people might want the synth, the other half an
> actual hardware device. How can we arbitrarily decide?
>
> Although, I suppose it might be rather obvious if there is a synth
> track available that the user would likely want that one, eh?
> I concede, that is how I want it and I find myself slightly annoyed
> sometimes that it doesn't as well, he he...
>
Hehe, well I can make a setting out of it.
1. always set to the default deveice
2. set it to the last created device.
I use a lot of soft synths so it's nearly always I want the last one.
> But there is a catch! What if there is more than one synth track?
> How do we decide which to default to? The first one in the track list?
As I said I would pick the last one, but it might just be my work flow?
Also what does this from the changelog mean? - New! Synthesizer tracks can
>> change their port from the track list.
>> It is indeed possible to click on the port column and get a list of all
>> ports including synths, I don't see the use of it though and there are some
>> serious drawbacks. If you select some other synth the other synth instance
>> is lost and can't be recovered.
>>
>
> Huh? That should be working just fine. You can now select which port
> the synth is assigned to, and it should not cause another synth to
> disappear. Are you saying the other synth track completely disappears?
> I just re-tested and all seems fine here. There is no loss of synth
> or sound when selecting among different synth or hardware ports or
> empty ports several times.
>
> The reason you see all existing devices listed is for the same reason
> you see them in a midi track's version of this popup: So that you can
> see who is currently on each port and you can choose one of them and
> override what is already there.
> Naturally, if you override what is already there, the existing entry
> is set to port <none> because we just took over that port.
> This is the same thing that happens when you do that in the midi
> configuration dialog.
>
> Try again? Maybe you just need to get used to it?
> It's a sound idea, and /is/ useful because now you don't have to go
> to the midi configuration dialog just to change what port a synth is
> assigned to.
A bit too tired to digest, I'll have to retest. Probably you are right, it
works but it threw me for a loop.
Also it's no longer possible to double click on the port to get the Native
>> gui, instead it brings up the config dialog, seems this is intentional? I
>> like to bring up the native gui this way so I can make a setting for it if
>> you want it this way :)
>>
>
> Oh! Not intentional, just happened 'cause I pop up the ports menu now.
> (If you carefully double-click while the menu is open, it actually
> opens the synth gui.)
> Hm, no way to get around this one? I need that menu to open when
> clicked. However I was thinking of merging some of the menus together
> because it all seems a bit clumsy - left click this column, right click
> that column... Should be all in one menu?
>
> Also got a crash or two but all in all it's very stable.
>>
>
> - Self report: Selecting from a synth's 'Presets' list in the
> right-click popup menu of a track list item's 'Port' column
> doesn't change anything, while doing the same from a midi strip's
> 'Patch' entry box does work.
>
Regards,
Robert
------------------------------------------------------------------------------
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
