Page 7 of 10

Re: What do we have? What do we need?

Posted: Fri Jan 06, 2017 7:05 pm
by skei
Luc wrote:That looks very interesting! Is it available somehow?
not yet.. but i will probably put together a new prototype/test version soon.. it's a bit buggy at the moment, plus there's some differences between the ladspa and vst formats i'm not sure how to handle properly.. i was planning to clean up some internal parts of my plugin framework before i continued..

Re: What do we have? What do we need?

Posted: Fri Jan 06, 2017 9:51 pm
by lykwydchykyn
Is there a good drum replacer plugin that I'm missing? Something that will trigger samples when a frequency range gets over a certain threshold?

Re: What do we have? What do we need?

Posted: Sat Jan 07, 2017 2:10 am
by glowrak guy
skei wrote:i use only (linux) vst plugins myself, so i recently made a basic ladspa -> vst wrapper.. haven't done much with it after i got it to work, but maybe i should continue working on it? and maybe try to expand it to support dssi (?) and lv2?
That would make all three formats easily available in Linux vst supporting products.
The future would be brighter for linux devs, knowing whatever software format they preferred,
or were most proficient with, their works would be easily available. Win Win!
dssi and lv2 have whysynth, hexter, amsynth, xsynth, wsynth, and fluidsynth,
with many dozens of nice effects to choose from etc

Re: What do we have? What do we need?

Posted: Sat Jan 07, 2017 10:39 am
by skei
ok, here's a test-version..
ladspa_wrapper_v0.0.0.zip (212kb)
http://pc.cd/WD8otalK
linux, 32/64-bit
only 64-bit version tested, in bitwig studio (1.3.13)
some discussion about licensing, etc:
see http://www.kvraudio.com/forum/viewtopic ... 3&t=473500
let me know about any problems, issues, bugs, comments, suggestions, etc..
various ideas and/or plans for this:

* automatic gui generation
* expand .cfg file to allow user-defined gui/skin
(size, knobs/sliders, background image, etc)
* better mono/stereo handling..
at the momnent, if the ladspa plugin has one audio input,
and one audio output, two instances are created,
one for each side..
* add .cfg stuff for various ways of handling ports
* error-checking, safe-guarding, stability, bug-fixing, etc..

maybe:

* support dssi plugins
* support lv2 plugins
* expand this into a modular environment of some sort,
using ladspa plugins as modules..
older/early test of gui (already heavily expanded)
https://www.youtube.com/watch?v=wSvu2oGoYlg

- tor-helge

Re: What do we have? What do we need?

Posted: Sat Jan 07, 2017 6:04 pm
by funkmuscle
lykwydchykyn wrote:Is there a good drum replacer plugin that I'm missing? Something that will trigger samples when a frequency range gets over a certain threshold?
LSP Plugins.

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 2:51 am
by glowrak guy
skei wrote:ok, here's a test-version..
ladspa_wrapper_v0.0.0.zip (212kb)
http://pc.cd/WD8otalK
linux, 32/64-bit
only 64-bit version tested, in bitwig studio (1.3.13)
some discussion about licensing, etc:
see http://www.kvraudio.com/forum/viewtopic ... 3&t=473500
let me know about any problems, issues, bugs, comments, suggestions, etc..
various ideas and/or plans for this:
Tried in Bitwig, and ladspa guitarix played nicely. I placed the wrapper plugin
after bitwg's Hardware Instrument plugin, for rompler use, and followed the amp
with U-he MFM2.

Thanks for making this. As time allows, adding features would I think get a lot of use,
maybe even inspire new apps, or renew interest in some that have been dormant for
whatever reason(s)
Cheers

(If your day job is coding, your boss is lucky to have you!)

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 4:10 am
by sysrqer
skei wrote:haven't done much with it after i got it to work, but maybe i should continue working on it? and maybe try to expand it to support dssi (?) and lv2?
Definitely, I'm a big fan of the code you have released so far (plugins) so I'm sure you would do a great job with this.
Maybe the best approach for something like this would be a wrapper which can convert all plugins types to all other types. It's probably easy for me to say as I don't program but, to me, one step towards less fragmentation would be a big leap.

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 8:51 am
by rghvdberg
a bit off topic :
In the (distant?) future when my main performance keyboard Roland Fantom X7 finally fails I'd like to switch to a pure plugin driven setup.

What do I need:
  • a good soundset of let's call it GM sounds (piano's, organs, brass, strings, basic synth patches). I guess this won't be much of a problem, NBO and NBB spring to my mind,
  • something to load these patches, I use a lot of splits/layers; I guess Carla would do this ?
  • arpeggiator
  • a looping sequencer with clicktrack:
    On my Fantom I make 'empty' sequences, just a 4 bar loop with a track dedicated to a click track.
    I use the pads on the Fantom to trigger 'patterns'; the triggering is synced so the pattern always starts on beat 1. Pattern can be set to loop, or one shot.
    I guess luppp or giada are good candidates.
  • my biggest worry; lightning fast switching/loading of setups. On the Fantom there's the 'Performance Mode', one can assign patches and sequences to buttons under the display. Press a button, bam! ready for next song, everything setup.
I noticed someone posted something about software for live play, but can't find it now :-/
>>EDIT<<
found it :Konfyt viewtopic.php?f=50&t=16586&p=77371&hili ... ard#p77371

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 9:51 am
by sadko4u
skei wrote:ok, here's a test-version..
ladspa_wrapper_v0.0.0.zip (212kb)
http://pc.cd/WD8otalK
linux, 32/64-bit
only 64-bit version tested, in bitwig studio (1.3.13)
some discussion about licensing, etc:
see http://www.kvraudio.com/forum/viewtopic ... 3&t=473500
let me know about any problems, issues, bugs, comments, suggestions, etc..
various ideas and/or plans for this:
It's good idea for that hosts that don't support LADSPA/LV2
skei wrote: * automatic gui generation
* expand .cfg file to allow user-defined gui/skin
(size, knobs/sliders, background image, etc)
* better mono/stereo handling..
at the momnent, if the ladspa plugin has one audio input,
and one audio output, two instances are created,
one for each side..
* add .cfg stuff for various ways of handling ports
* error-checking, safe-guarding, stability, bug-fixing, etc..
But I think this should be done a bit differently. It would be good to have VST generator: you want to wrap a plugin, you select a plugin that you want to wrap, then it generates wrapper code, compiles and becomes an .so.

maybe:
skei wrote: * support dssi plugins
I think, DSSI is dead. There is no need to support them.
skei wrote: * support lv2 plugins
* expand this into a modular environment of some sort,
using ladspa plugins as modules..
older/early test of gui (already heavily expanded)
https://www.youtube.com/watch?v=wSvu2oGoYlg

- tor-helge
Yes, but LV2 is very different to VST. Where VST has built-in functions, LV2 implements them quite different via extensions. That's why I think dynamically generate .so files would be (probably) better.

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 12:16 pm
by davephillips
sadko4u wrote:
skei wrote: * support dssi plugins
I think, DSSI is dead. There is no need to support them.
Developers seem to have no further interest in the format, but there are some amazingly good DSSI synthesizers that have yet to be converted to LV2 and/or VST, in particular WhySynth and Hexter from Sean Bolton. Skei's wrapper would be most welcome for those instruments.

Best,

dp

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 2:30 pm
by sadko4u
davephillips wrote: Developers seem to have no further interest in the format, but there are some amazingly good DSSI synthesizers that have yet to be converted to LV2 and/or VST, in particular WhySynth and Hexter from Sean Bolton. Skei's wrapper would be most welcome for those instruments.

Best,

dp
Yes, you're right. I think the best solution would be to port them to LV2+LinuxVST instead of support DSSI.

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 5:26 pm
by davephillips
re: the OP :

Since I can't/don't speak for "us" I can only address the post wrt my own situation.

What I have: Access to great gear up the wazoo.

What I need: More talent and more time.

Best,

dp

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 6:47 pm
by rghvdberg
davephillips wrote:re: the OP :

Since I can't/don't speak for "us" I can only address the post wrt my own situation.

What I have: Access to great gear up the wazoo.

What I need: More talent and more time.

Best,

dp
Hehe.

I'm surprised nobody replied with: love. All we need is love.

And some plugins.

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 8:17 pm
by GMaq
Again, I'm late to the party...

My biggest hurdle in the Linux world is the ability to visually draw MIDI note velocities in Ardour and Mixbus, especially for drum programming.. I know, I know it's all cleverly done with mouse scrolling but that's not visual. I am completely satisfied with Ardour and Mixbus and have produced a few complete albums with them and their Audio capabilities. But the lack of ability to draw note velocities keeps sending me back to Hydrogen which I really like but is becoming increasingly kludgy to use especially with multiple drum tracks. Ardour's MIDI editing has other great features and capabilities but every other sequencer I've done MIDI programming with over MANY years (Digital Orchestrator, CubaseVST, Reaper, EnergyXT) have had the very simple feature of drawing MIDI note velocity visually even with timeline-based editing, Call me crazy but I absolutely loved MIDI editing in EnergyXT :oops:

I've mentioned it several times on Ardour IRC and I'm pretty sure there is a dusty discarded Feature Request for it somewhere in Ardour's Mantis basement but it seems to be a very low priority... Anyone else missing this in Ardour and Mixbus?

Re: What do we have? What do we need?

Posted: Sun Jan 08, 2017 9:14 pm
by Luc
rghvdberg wrote:I'm surprised nobody replied with: love. All we need is love.
And some plugins.
Love is overrated, I'll take "time" any day.

And "talent" is subjective.