2017-12-20 3:11 GMT+01:00 Tim <[email protected]>:
>
>
> On 12/19/2017 04:08 PM, Robert Jonsson wrote:
>
>> Stereo input is now supported by the RtAudio backend so it's starting to
>> be actually useable =)
>> The buffer and samplerate settings in the configuration are also wired to
>> the RtAudio backend now. There's also a new selector for selecting between
>> Pulse,Alsa,OSS and RtAudio based jack. Though I would consider Pulse to be
>> the only supported.
>>
>> I think that's all the work I will put into features for now. Hopefully
>> will move towards more recording and testing in the coming days.
>>
>
> It's... alive!
> Awesome.
>
\o/
>
> Taking a peek at the code, I realized that you may need some help
> adding routing capabilities. It could be a big job since it involves
> adding a completely new route type.
Yeah I found that was beyond my capabilities and settled on a more
hardwired level of functionality.
Two outputs and two inputs, that can't be changed.
Now I didn't test it beyond seeing that sound goes in and comes out so I'm
hoping it holds together.
> That involves checking every
> place in the code that uses routes. (This is why I try to use
> switch(type) statements everywhere instead of if(type...) so that
> the compiler will automatically point out any neglected 'cases'.)
>
> However, I have been meaning to add a new type of route myself but have
> dreaded the work that might be involved but now may be a good chance.
> The new type route is...
>
> Control routes.
>
> The ability to route any audio control signal such as plugin controls.
> That means being able to finally use plugin control output signals.
> Think side-chaining, DIY building-block compressor chains etc.
>
Would be awesome!
One problem I think is that you can't just connect controls and go.
> I figure there has to be some sort of middle-ware in between which
> allows adjustment of the connected values' amplitudes and offsets.
> Unless... the destination port's plugin already /has/ such adjustments,
> which we could never be guaranteed.
>
Alright, cool.
For the purpose of getting feature completeness to this backend it's a good
thing, but if the current stub works sufficiently for 2in/2out, I think we
can wait til after 3.0 though.
>
> T.
>
>
>> Reminds me, I loaded an old song after your big checkin, Tim, and I
>> noticed one of the synths were wrongly transposed, any related changes that
>> could interfere?
>>
>
The notes were 4-5 steps too high I think, when I listened, I didn't look
at the pianoroll so I don't know if it was reflected there.
I will do more testing during the holidays.
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
