Saturday, November 19, 2011

v0.5.7

A little, but long due, update :
  • Bypass/mute now flushes the audio buffers (preventing delays from playing the remaining buffers when turned back on)
  • Suppressed a click noise on mute/unmute
  • Audio devices configuration can be opened when the device is in use (Audio streams are suspended if needed. For Asio interfaces : you may have to update the device list afterward to rebuild new buffers)
  • Added a button in the toolbar to always open the selected plugin gui
  • Dragging a bank file (fxp or fxb) on a container will load the corresponding plugin (you'll have to load the plugin one time to add it to the database)

17 comments:

  1. Thanks man. Keep it going!

    ReplyDelete
  2. thanks a lot for the update. is there any place where i can check the future roadmap for this amazing app? if there isnt such info... could you please tell what you plan still to do ? the way i see it (except for the stability issues)it is already a very complete live plugin chainer :)

    ReplyDelete
  3. There's no roadmap as i'm learning in the process, i can't tell what's feasible and what is not. It's just a matter of time, trial and errors, and that's why it is "experimental".
    For now, the midi support needs some improvements : a filter of some sort, maybe a clock sync... And the error handling could be improved too, it's kind of hard to tell what's going on when something bad happens.
    There's a lot of things to fix and improve, but I almost have the app I needed, so the rest will be based on suggestions and bug reports I suppose.
    Thanks for the support :)

    ReplyDelete
  4. great update, thanks! i'm completely used to VstBoard and have substituted my Alesis Micron with a Behringer UMA25s and a netbook running VstBoard. :D

    what would be awesome to find in some future update is a possibility to route different MIDI channels to different instruments, so that one could switch between a sampler and synthesizer by changing the MIDI channel.

    ReplyDelete
  5. " so that one could switch between a sampler and synthesizer by changing the MIDI channel."

    This might be useful for other tasks, but cant you do that by changing the vstboard program \ preset ?

    ReplyDelete
  6. I would like to run this in ubuntu, are there any dependencies that would make this difficult/impossible?

    ReplyDelete
  7. I ran some tests on linux a while ago, it seems to be feasible since Qt and portaudio are cross-platform. I managed to run the main application, but it needs to support other plugin formats, I don't know what's available on linux

    ReplyDelete
  8. Hi Raphael! Big thanks for your software! Can you make VST programs (presets) and banks support loading in the next release?

    Regards, Eduard

    ReplyDelete
  9. Hey! Thanks -both of you !
    You can drag&drop fxb and fxp files on your plugins if that's what you're looking for. Or you can directly drop a bank file on a panel to load the associated plugin. Hope this help...

    ReplyDelete
    Replies
    1. Hi Raphael! Thanks for your quick reply! But what you are talking about doesn't work of mine. :(

      Delete
  10. Want some coffee? A massage perhaps?

    ReplyDelete
  11. Hello developer VSTBOARD ! You are Already my idol !
    I wanted to report a problem I found with all your versions of this fantastic PLUGIN ..

    Within Cubase is not possible to "WRITE" automation directly from the UI of Vst Used ..

    I wanted to ask if you do this kind of change in the next version ..

    unfortunately for me is a big problem not being able to "WRITE" automation directly from the UI of Plugin interested (GlissEQ, BlueCat, etc. ..)

    I am Italian and I do not speak English very well, but I hope i made it clear.

    Thank you!

    ReplyDelete
    Replies
    1. Hi, and thanks :) Unfortunately you're right about that, there's no automation output on the plugins hosted by vstboard. So you can't send to your host what you touch on the plugin's UI. IIRC, I had some infinite loops with some misbehaving plugins and decided to "temporarily" remove the output pins to prevent them to crash everything. I never took the time to find a proper way to do that and, I'm sorry to say, I don't plan to work on vstboard any time soon (well, you never know... but nah, I don't really feel like it, even after all this time...)
      sorry for the annoyance ^^

      Delete
    2. Thanks for your reply..!! then I hope that one day you will resume over the project !!! ;o)

      Delete