Channel In/Out Assignment Confusion

[bnh]

Could you be more specific and more elaborate with your flow chart description in the FAQ .pdf file. I don't want to miss-read this section. So many things are called "channels" and "ports" by different developers. While "Ins and Outs" are easy to distinguish in the hardware world with cords and plugs, in the virtual word, "Ins and Out" are less clear. Terms like "channels" and "port" become almost interchangeable. Sonar is especially loose with the word "channel." In setting up a DAW system with EWSC as a plug-in, in some instances, connecting to the same "channel" is desired, while in other cases, it is to be avoided. It just helps just to have terms clearly defined and flow charts specific.

I know it's clear to you because you already understand it, but the conflict in terms is a killer on this side of the fence. For example, Sonar actually has a unique "channel" value visible only in their Staff View or Event List that is related to the interface between Sonar and EWSC. They call it "channel," but it is more akin to "voice channel" as used in Sibelius. It is one source where conflict can occur with EWSC.

If you could just spell it out, please, in detail, it would be appreciated. Don't let us guess at an inference for "connected to" or "same as." Yes, I understand what parentheses mean, and I can interpret that flow chart with changes in color code in several different ways. Please just spell it out.

Thank you.

[Sam Fischmann]

Hello,

A port and a channel are NOT the same thing.

A port is a physical (or virtual) MIDI port in the computer. If you have a card with MIDI plugs on it, each one is a MIDI port. Any MIDI port can send and receive information on 16 different channels.

When setting ins and outs, you usually set the port information will travel on, and the channel within that port.

If you're looking for something specific for SONAR:

Load up Symphonic Choirs as a VSTi. It will create two tracks; an instrument track, and a MIDI track. The MIDI track will have an area for you to load MIDI FX. Load WordBuilder as a MIDI effect, leaving all the options default.

-Sam

[bnh]

Thank you for the speedy reply.
If I understand correctly, we're to disregard the manual's reference for using EWSC as a DXi plug in in Sonar, and treat it as a VST plug in. I have been avoiding use of EWSC as a VST because I've seen reports of problesm with Sonar 4 and the VST adapter. I'm still using Sonar 3.1. Sonar has just released an update to their VST Adapter, a version 4.5, which they indicate is applicable to Sonar 3.1. Will this update and my Sonar 3.1 satisfy EWSC?

[Sam Fischmann]

Hello,

Unfortunately I only have the two latest versions, SONAR 4 and 5 to test with. It's worth giving the update a try, but I am not able to confirm the results on my end. If Cakewalk is keeping SONAR 3 up to date as far as VST support goes, then it should work just fine.

I believe the problem with SONAR 3 is that it doesn't work with the WordBuilder MIDI plugin. That will have to be done standalone, which requires a more complicated setup. If you find that it works wonderfully after your update, please let us know!

-Sam