Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

1,574 profile views

denoiser's Achievements

Advanced Member

Advanced Member (3/8)

  1. Hi, i had similar experience with Vienna ensemble pro, where VEP server was set to receive midi on 32 ports, each with 16 channels. When in sam i instantiated VEP client plugin, sam was only able to send midi to 16 midi channels on port 1. In Sam midi track has only option to select channel, and it assumes it's on port 1. For eg. this problem in Cubase was solved by introducing rack instruments, where every VSTI exposes its ports and channels (as i heard ). Anyway, guys from Vienna solved this by making small 'event' plugin (mainly for Logic users), which you place on midi track. As usual, on your midi track you choose midi out channel to VSTI, and in 'event' plugin you choose port. This routes incoming midi signal to VEP server to desired port. Unfortunately for Independence, this works only in VEP, but what i actually wanted to say is that developers should extend midi track's I/O option to include ports, not only channels on port 1. Greets d
  2. Hi, could you implement free, non license burdened 10 bit osc 2 way network midi protocol please?? Why not? Your midi implementation which cannot interpret/translate sysex to cc or anything usefull and vice versa dates 20 years from nowdays. Greets d
  3. Hi can samp. or seq. send custom midi/sysex messages on app/project start? Also, is there a way to program custom sysex upon some action? Thanks d
  4. Hi, does anyone has running setup with rise, and what is best/common/simple workflow with it ? For eg. sending multiple midi info (channels) to Kontakt (or your favourite VSTi) at once... are there any obsticles etc... Thanks d
  • Create New...