Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Pre-Release Discussion

Reply
 
Thread Tools Display Modes
Old 02-07-2012, 04:32 PM   #1
jas
Human being with feelings
 
jas's Avatar
 
Join Date: Oct 2008
Location: a zonzo
Posts: 473
Default v4.16pre12 - February 7 2012

v4.16pre12 - February 7 2012
+ JS: support MIDI buses, set ext_midi_bus=1 in @init, then midi_bus is used for bus indices
+ JS: updated midi_logger to show bus
+ VST: MIDI bus I/O mapping
+ AU: MIDI bus input mapping
+ Live FX multiprocessing: slight performance improvements when using large track counts
# record input menu formatting updates
# Windows: added some missing ReleaseDC(NULL)s
+ Walter: fixed some overlay redraw issues
jas is offline   Reply With Quote
Old 02-07-2012, 04:42 PM   #2
zappadave
Human being with feelings
 
zappadave's Avatar
 
Join Date: Jan 2008
Posts: 1,257
Default

Wait for 1 midi Bus........and 16 turn up at once.
Nice.
__________________
Music is the best
เพลง ที่ดีที่สุดคือ
zappadave is offline   Reply With Quote
Old 02-07-2012, 04:47 PM   #3
gwok
Human being with feelings
 
gwok's Avatar
 
Join Date: Jun 2010
Location: canada
Posts: 3,396
Default

Quote:
Originally Posted by jas View Post
v4.16pre12 - February 7 2012

+ VST: MIDI bus I/O mapping
+ AU: MIDI bus input mapping
working like a charm! thanks a bunch!!!!
gwok is offline   Reply With Quote
Old 02-07-2012, 06:14 PM   #4
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Yay, we can play with MIDI buses in JS.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-07-2012, 06:15 PM   #5
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
Default

Good stuff devs!

Any news on getting MIDI and audio feedback detection separated so we can run vsts on the parent and sub outs on the childs? that would be very useful!
musicbynumbers is offline   Reply With Quote
Old 02-07-2012, 06:35 PM   #6
gofer
-blänk-
 
gofer's Avatar
 
Join Date: Jun 2008
Posts: 11,359
Default

Is it possible to code a channel-to-bus mapping matrix? I mean to route a given channel on one bus to the same channel on another bus (leaving the other channels on the original bus)? If yes, someone please do .

Or maybe I overlook a way it can be done already?
gofer is offline   Reply With Quote
Old 02-07-2012, 06:46 PM   #7
Marah Mag
Human being with feelings
 
Marah Mag's Avatar
 
Join Date: Sep 2008
Location: Here
Posts: 3,000
Default

Posted this in the thread for pre11, meant to [post it here.]

I have found consistently reproduceable problems with ReaTune as a take FX.

This is what happens in the current pre when gluing an item with a reatune instance. Note that there have been NO corrections actually made - simply enabling manual correction causes the null area to appear. More examples at link below.



I originally posted about this here:

http://forum.cockos.com/showthread.p...d=1#post900619
Marah Mag is offline   Reply With Quote
Old 02-07-2012, 07:54 PM   #8
nicholas
Scribe
 
nicholas's Avatar
 
Join Date: Jan 2007
Location: Van Diemen's Land
Posts: 12,167
Default

Quote:
Originally Posted by jas View Post
+ VST: MIDI bus I/O mapping
+ AU: MIDI bus input mapping
Can someone give me some help here, for the purposes of documentation?

I've figured out the bus/channel thing on MIDI sends/receives between tracks (I think!), but not on individual VSTi -

Thanks!
__________________
Learning Manuals and Reaper Books
REAPER Unleashed - ReaMix - REAPER User Guide
http://www.lulu.com/spotlight/glazfolk
nicholas is online now   Reply With Quote
Old 02-07-2012, 09:59 PM   #9
gwok
Human being with feelings
 
gwok's Avatar
 
Join Date: Jun 2010
Location: canada
Posts: 3,396
Default

Quote:
Originally Posted by nicholas View Post
Can someone give me some help here, for the purposes of documentation?

I've figured out the bus/channel thing on MIDI sends/receives between tracks (I think!), but not on individual VSTi -

Thanks!
here. you just have to right click on the "2 out">midi input' on the vst to choose it's input bus

Last edited by gwok; 06-28-2012 at 12:36 AM.
gwok is offline   Reply With Quote
Old 02-07-2012, 10:09 PM   #10
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by musicbynumbers View Post
Good stuff devs!

Any news on getting MIDI and audio feedback detection separated so we can run vsts on the parent and sub outs on the childs? that would be very useful!
Probably will never happen -- what would be more likely is pre-fx send support (MIDI vs audio is not the issue, causality is), but that is not in the near future.
Justin is offline   Reply With Quote
Old 02-07-2012, 10:15 PM   #11
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by Marah Mag View Post
Posted this in the thread for pre11, meant to [post it here.]

I have found consistently reproduceable problems with ReaTune as a take FX.

This is what happens in the current pre when gluing an item with a reatune instance. Note that there have been NO corrections actually made - simply enabling manual correction causes the null area to appear. More examples at link below.

I originally posted about this here:

http://forum.cockos.com/showthread.p...d=1#post900619
Edit: managed to duplicate this, looking into it.

Last edited by Justin; 02-07-2012 at 10:21 PM.
Justin is offline   Reply With Quote
Old 02-07-2012, 10:50 PM   #12
Marah Mag
Human being with feelings
 
Marah Mag's Avatar
 
Join Date: Sep 2008
Location: Here
Posts: 3,000
Default

Quote:
Originally Posted by Justin View Post
Edit: managed to duplicate this, looking into it.
Cool. Thanks Justin.

Your mentioning the live input led me to look more closely...

My default preset for ReaTune is set for non-live input, so all my testing has been under that mode (this had slipped my mind till you mentioned it.)

If I Reset to factory default (Live input) there is no problem.

If I then manually change to Non-live, there is again no issue.

But if then switch to my Non-live preset, the problem returns.

Further, if after loading the preset, I manually switch to Non-live, the problem again appears, but the nulling pattern is different.

This suggests there's something odd in the preset??


Last edited by Marah Mag; 04-19-2012 at 11:50 AM.
Marah Mag is offline   Reply With Quote
Old 02-07-2012, 10:52 PM   #13
Marah Mag
Human being with feelings
 
Marah Mag's Avatar
 
Join Date: Sep 2008
Location: Here
Posts: 3,000
Default

ps there's a link to a test proj here

http://forum.cockos.com/showpost.php...81&postcount=9
Marah Mag is offline   Reply With Quote
Old 02-08-2012, 12:40 AM   #14
nicholas
Scribe
 
nicholas's Avatar
 
Join Date: Jan 2007
Location: Van Diemen's Land
Posts: 12,167
Default

Quote:
Originally Posted by gwok View Post
here. you just have to right click on the "2 out">midi input' on the vst to choose it's input bus
Thanks ... a perfect example!
__________________
Learning Manuals and Reaper Books
REAPER Unleashed - ReaMix - REAPER User Guide
http://www.lulu.com/spotlight/glazfolk
nicholas is online now   Reply With Quote
Old 02-08-2012, 02:10 AM   #15
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
Default

Quote:
Originally Posted by Justin View Post
Probably will never happen -- what would be more likely is pre-fx send support (MIDI vs audio is not the issue, causality is), but that is not in the near future.
Can you expand a bit more on this? Will pre-fx sends help us have MIDI sent to the FX and audio output from the FX on the same track?
EvilDragon is offline   Reply With Quote
Old 02-08-2012, 02:29 AM   #16
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
Default

Quote:
Originally Posted by Justin View Post
Probably will never happen -- what would be more likely is pre-fx send support (MIDI vs audio is not the issue, causality is), but that is not in the near future.
Thanks for replying Justin but I'm hoping you misunderstood me! it sounds like you might have done because I can't see how causality comes into it with the routing I described especially since you can enable feedback routing and create the setup I described with absolutely no feedback.

(But you loose PDC)

I can't do a diagram as I'm not near reaper for another week but perhaps evildragron can do one to explain It better.
musicbynumbers is offline   Reply With Quote
Old 02-08-2012, 02:40 AM   #17
Phisk
Human being with feelings
 
Join Date: Jul 2007
Posts: 276
Default

What does "live fx processing" mean? ("+ Live FX multiprocessing: slight performance improvements when using large track counts")

processing of fx used on armed tracks?
Phisk is offline   Reply With Quote
Old 02-08-2012, 02:41 AM   #18
matthias.matthias
Human being with feelings
 
Join Date: Jun 2010
Posts: 194
Default

Quote:
Originally Posted by Justin View Post
Probably will never happen -- what would be more likely is pre-fx send support (MIDI vs audio is not the issue, causality is), but that is not in the near future.
Not really what I wanted to hear , but thanks anyway for giving us feedback.

For me this would have been an important feature. The current implementation really limits the routing flexibility when working with multi-out VSTis.
matthias.matthias is offline   Reply With Quote
Old 02-08-2012, 02:45 AM   #19
IXix
Human being with feelings
 
Join Date: Jan 2007
Location: mcr:uk
Posts: 3,889
Default

Quote:
v4.16pre12 - February 7 2012
+ JS: support MIDI buses, set ext_midi_bus=1 in @init, then midi_bus is used for bus indices
+ JS: updated midi_logger to show bus
+ VST: MIDI bus I/O mapping
+ AU: MIDI bus input mapping
Erm, cool, I think. I don't understand this MIDI bus malarky though. What's it good for, other than rewire?
IXix is offline   Reply With Quote
Old 02-08-2012, 02:46 AM   #20
matthias.matthias
Human being with feelings
 
Join Date: Jun 2010
Posts: 194
Default

Quote:
Originally Posted by EvilDragon View Post
Can you expand a bit more on this? Will pre-fx sends help us have MIDI sent to the FX and audio output from the FX on the same track?
Hi Justin, it'd be great if you could tell us a bit more about this idea in regard to multi-out vstis. Thanks a lot.
matthias.matthias is offline   Reply With Quote
Old 02-08-2012, 02:57 AM   #21
Reaktor:[Dave]
Human being with feelings
 
Reaktor:[Dave]'s Avatar
 
Join Date: Jun 2010
Location: Berlin
Posts: 563
Default

Quote:
Originally Posted by Justin View Post
Probably will never happen -- what would be more likely is pre-fx send support (MIDI vs audio is not the issue, causality is), but that is not in the near future.
Justin, I'd like to know a bit more detail about it. Would it work like this?:
And what do you think of this workaround?:
Quote:
Originally Posted by Coises View Post
Suppose we had a built-in SendReceive effect that could be inserted in an effects chain like any other effect.

The SendReceive effect would allow you to select a target track (to which to send and from which to receive), and it would have separate send and receive controls similar to those that currently exist for track sends and receives (MIDI none/all/channel to all/channel, Audio none/mono/stereo source to target with fader and pan).

Instead of the send being either pre-fx, post-fx or post-fader, it would always occur at the point in the fx chain where SendReceive was inserted. Likewise, the return would always occur just after the send (instead of pre-fx, which is where all returns go now). The return should still have a pre-fx/post-fx/post-fader selection, but this would relate to the target track. MIDI and audio pass-through should also be available and optional. [...]
As this is and has been an importan matter for lots of us for quite a long time now, could REAPER get one of these suggestions in the near future, please?

Quote:
Originally Posted by jas View Post
+ VST: MIDI bus I/O mapping
Kontakt uses four MIDI in ports, supporting 16 MIDI channels each. Can we use REAPER MIDI busses to address the remaining three input ports, finally?!
Reaktor:[Dave] is offline   Reply With Quote
Old 02-08-2012, 03:12 AM   #22
gofer
-blänk-
 
gofer's Avatar
 
Join Date: Jun 2008
Posts: 11,359
Default

Quote:
Originally Posted by Reaktor:[Dave] View Post
Kontakt uses four MIDI in ports, supporting 16 MIDI channels each. Can we use REAPER MIDI busses to address the remaining three input ports, finally?!
Only the standalone Kontakt does afaik. The VSTi has a single port only. You can address all standalone Kontakt ports the usual way with hardware outputs from Reaper to virtual MIDI ports.
gofer is offline   Reply With Quote
Old 02-08-2012, 03:15 AM   #23
typewriter
Human being with feelings
 
Join Date: Jun 2007
Posts: 528
Default

As far as I know more than 1 midi port per VSTi is only supported by VST3 plugins.
typewriter is offline   Reply With Quote
Old 02-08-2012, 04:16 AM   #24
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by matthias.matthias View Post
Not really what I wanted to hear , but thanks anyway for giving us feedback.

For me this would have been an important feature. The current implementation really limits the routing flexibility when working with multi-out VSTis.


MIDI and audio on the same track on a multiout VSTi
No feedback enabled
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 02-08-2012, 04:38 AM   #25
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
Default

That's a workaround instead of a feature that should already be in there.
EvilDragon is offline   Reply With Quote
Old 02-08-2012, 04:52 AM   #26
Jeffos
Mortal
 
Jeffos's Avatar
 
Join Date: Dec 2008
Location: France
Posts: 1,969
Default

Quote:
Originally Posted by jas View Post
v4.16pre12 - February 7 2012
+ JS: support MIDI buses, set ext_midi_bus=1 in @init, then midi_bus is used for bus indices
+ JS: updated midi_logger to show bus
+ VST: MIDI bus I/O mapping
+ AU: MIDI bus input mapping
kick ass!
Quote:
Originally Posted by IXix View Post
Erm, cool, I think. I don't understand this MIDI bus malarky though. What's it good for, other than rewire?
The MIDI path is sequential in FX chains. It remains so but we now have a workaround to do some sort of "parallel MIDI processing" (by remapping busses at the input and/or at the output of FXs, a bit like with audio channels).
As far as I understand it is only fully possible for VST: no output remapping for AU and no input/output remapping for JS in the FX Chain window (*but* I think we can do it in the code: receiving as said in the changelog + we can probably do the sysex encapslation ourselves via midisyx() and probably send to multiple busses which is not possible in the GUI ).
[EDIT] bullshit ^^ I just tried: receiving & sending is managed the same way. To send the same MIDI message on 2 busses it is as simple as:
Code:
midi_bus=12;
midisend(ts,msg1,msg23);
midi_bus=13;
midisend(ts,msg1,msg23);
I wonder if the max MIDI bitrate (31250 bits/sec) still apply *in* fx chain though?

Last edited by Jeffos; 02-08-2012 at 07:33 AM. Reason: bullshit + english
Jeffos is offline   Reply With Quote
Old 02-08-2012, 05:29 AM   #27
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by EvilDragon View Post
Can you expand a bit more on this? Will pre-fx sends help us have MIDI sent to the FX and audio output from the FX on the same track?
+1.
Quote:
Originally Posted by Jeffos View Post
[...]
I wonder if the max MIDI bitrate (31250 bits/sec) still apply *in* fx chain though?
(lol, the days when we spoke of "baud"...)

That should really only apply to actual hardware MIDI I/O, not for virtual MIDI ports or anywhere inside the host.

Is REAPER currently limiting MIDI bandwidth in any way, inside-the-box ?
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-08-2012, 06:18 AM   #28
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by EvilDragon View Post
That's a workaround instead of a feature that should already be in there.


Not entirely sure how completely native way of doing exactly what you want is a workaround hahahaha
Run out of thinsg to complain about have we ?
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 02-08-2012, 07:06 AM   #29
Jeffos
Mortal
 
Jeffos's Avatar
 
Join Date: Dec 2008
Location: France
Posts: 1,969
Default

Just tested. For JS, I can say it is indeed limited to 256 events per block but the strange thing is that it does not depend on the audio buffer size.. so nothing to see with MIDI HW max bitrate.. I don't understand..
Anyway, whatever is the reason, that limits the new possibilites.

Bug: replace, merge & disable MIDI outputs do not work (and I did not get fooled by MIDI logger which displays everything)

Weird: if the "legacy path" is now Bus 1, why do we have "out of bus" MIDI channels displayed in routing windows and not only Bus1(ch1-16) to Bus16(ch1-16) now?

consistency: about MIDI *input*, the "Map to input channel" feature should also be upgraded into "Map to input bus/channel" no?

Last edited by Jeffos; 02-08-2012 at 07:48 AM. Reason: map to bus/channel
Jeffos is offline   Reply With Quote
Old 02-08-2012, 07:27 AM   #30
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
Default

Gpunk_w, it looks like a few of us are talking about a different thing to you.

This is so you can EASILY have foldered multi-out vsts with the child tracks acting as the outs and the Parent folder acting as the MIDI track so you can easily hide away the mix channels like a few other daws now allow.

If it worked like this we could potentially have all new multi-out vsts create themselves like this and have it kept intuitive.

Also, How does the routing plugin handle plugin delay compensation
musicbynumbers is offline   Reply With Quote
Old 02-08-2012, 07:34 AM   #31
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Well you can do something similar, but it isn't worth trying to explain how (Better off waiting for native support)
PDC i suspect should be handled normally
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 02-08-2012, 07:39 AM   #32
Reaktor:[Dave]
Human being with feelings
 
Reaktor:[Dave]'s Avatar
 
Join Date: Jun 2010
Location: Berlin
Posts: 563
Default

Quote:
Originally Posted by gpunk_w View Post


Not entirely sure how completely native way of doing exactly what you want is a workaround hahahaha
Run out of thinsg to complain about have we ?
But you don't have to write and insert a new JS effect speciffically for each track each time you add a new instrument there, do you?
Reaktor:[Dave] is offline   Reply With Quote
Old 02-08-2012, 08:03 AM   #33
tarnationsauce2
Human being with feelings
 
tarnationsauce2's Avatar
 
Join Date: Dec 2009
Location: Oregon, USA
Posts: 155
Default

I found a bug that seems random but can wreak a lot of havoc. I have a large project with 14000+ clips and a lot of groups. It seems when New groups are created it will randomly include groups/clips not intended. So when I time stretch/delete/slip edit etc it will ruin previous edits at a random part of the project. Driving myself nuts over here trying to fix it.
tarnationsauce2 is offline   Reply With Quote
Old 02-08-2012, 09:01 AM   #34
gridlove
Human being with feelings
 
gridlove's Avatar
 
Join Date: Sep 2010
Location: Chesterfield, UK
Posts: 248
Default

Quote:
Originally Posted by gpunk_w View Post
What kind of voodoo is this?
I did something similar but with midi feedback enabled, sadly it introduced some latency here and there so was not reliable for me.

By the looks of it we can have midi/audio on the same track with multi out vsti?

Have you scripted the send/receive js plugin yourself gpunk?
gridlove is offline   Reply With Quote
Old 02-08-2012, 09:03 AM   #35
DuX
Human being with feelings
 
DuX's Avatar
 
Join Date: Jan 2007
Location: Underworld
Posts: 1,188
Default

What Musicbynumbers suggested would be wonderful! I've been wanting the multi out VSTis issue and that "feedback" setting resolved, so I could send MIDI from different tracks without having enabled "feedback" for years. MIDI and Audio should be a bit more separated IMO.

There's also one more issue that comes with the same "package": when you route channels 1 and 2 of the multiout VSTi to a different track, it should disappear from the output of the track that VSTi is on, just like other channels do, but 1 and 2 seem like "hardcoded" to go out no matter what you do. [pulling hair would maybe help?] It's simply confusing, as when you route something somewhere, you don't expect it to get mirrored, but routed - disappears from source and goes to the destination. That way we won't have to remember to disable "master/parent send" on the main VSTi track every time you're working with Kontakt or Battery, and these are my main workhorses. Lots of routing...

I suppose this is much harder to implement than it looks, so that's why they haven't done it so far.

Cheers!
__________________
Goodnight, thank you, and may your God go with you.

Last edited by DuX; 02-08-2012 at 09:11 AM.
DuX is offline   Reply With Quote
Old 02-08-2012, 12:46 PM   #36
gwok
Human being with feelings
 
gwok's Avatar
 
Join Date: Jun 2010
Location: canada
Posts: 3,396
Default

Quote:
Originally Posted by gofer View Post
Is it possible to code a channel-to-bus mapping matrix? I mean to route a given channel on one bus to the same channel on another bus (leaving the other channels on the original bus)? If yes, someone please do .

Or maybe I overlook a way it can be done already?
if your routing from one track to another using a send\receive than yes, i believe so

inserts don't currently support channels, only busses.

On that topic, IF channels were supported on inserts midi inputs' (as they are on busses), this might have some nice advantages. One great thing about supporting channels per bus on VST\Au input, is that one could then utilize FIPM, or multichannel midi items, that would then be routed to specific inserts. IOW, you wouldn't need an extra track to send midi to specific inserts, just set your midi info to a specific channel, on the SAME TRACK!

anyway that's just an idea, and would be an added bonus. Just being able to get to specific inserts on a chain is a HUGE help, and though the forum weather may have blown past this issue quickly, this is definatly worthy of a good round of woots

g
gwok is offline   Reply With Quote
Old 02-08-2012, 01:33 PM   #37
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by Reaktor:[Dave] View Post
But you don't have to write and insert a new JS effect speciffically for each track each time you add a new instrument there, do you?
Not sure what you mean here
Currently the way this works now is this,
1 You put the send plugin after the multiout
2 you put receives on each track you want an output to go to

Currently there are 8 receives available (16 channels) i thought this to be better than add a receive and then choose in a drop down on the receive which channel it was receiving (Just fond it way faster to set up)

This is not what people wanted though i guess, so i doubt it is useful
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 02-08-2012, 01:33 PM   #38
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by Jeffos View Post
Just tested. For JS, I can say it is indeed limited to 256 events per block but the strange thing is that it does not depend on the audio buffer size.. so nothing to see with MIDI HW max bitrate.. I don't understand..
Anyway, whatever is the reason, that limits the new possibilites.
It shouldn't be, there are no real limits on the number of midi events or amount of data that can be moved around internally...
Justin is offline   Reply With Quote
Old 02-08-2012, 01:41 PM   #39
Win Conway
Human being with feelings
 
Join Date: Dec 2010
Posts: 3,826
Default

Quote:
Originally Posted by gridlove View Post
Have you scripted the send/receive js plugin yourself gpunk?
I just modded Losers js
__________________
Stop posting huge images, smaller images or thumbnail, it's not rocket science!
Win Conway is offline   Reply With Quote
Old 02-08-2012, 02:03 PM   #40
plamuk
Human being with feelings
 
Join Date: Feb 2007
Posts: 3,221
Default

thank you so much for the per vst midi busses.
you just saved me some money. i was going to buy plogue bidule just so i could create 2 midi streams from a single input. a very overcomplicated workaround. not anymore!
plamuk is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 11:18 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.