vladasyn

All you need to do is assign the input, assign the output, and turn on MIDI echo. Repeat that for as many synths and controllers that you want to play across as many tracks as you want. You can either use the same controller to play multiple synths or assign multiple controllers to play multiple synths, the choice is yours. Add in channels for even more possibilities.

 
My experience is that only *SELECTED* track is audible. There is such a thing as "ACTIVE" track. You can select more than one track but you can not have more than one active track, therefor obly one keyboard can be played at the same time, unless you know how to make it work.

Just to clear out a small detail: in sonar, focusing a track is not the same as selecting a track. Selecting is when you click on the number of the track and you see a blue square around the number. Focusing is when you click anywhere else on the track and it becomes highlighted in a lighter shade of grey.
 
Now, to hear live midi notes from your keyboard, a midi track needs to have the Input Echo button enabled. When a MIDI track is focused, the Auto Input Echo function is activated. If you move your focus to another track, now this other midi track has the Auto Input Echo on, and not the previous one. To have multiple live midi tracks going at once, you simply have to manually enable Input Echo on each midi track.

vladasyn

All you need to do is assign the input, assign the output, and turn on MIDI echo. Repeat that for as many synths and controllers that you want to play across as many tracks as you want. You can either use the same controller to play multiple synths or assign multiple controllers to play multiple synths, the choice is yours. Add in channels for even more possibilities.

 
My experience is that only *SELECTED* track is audible. There is such a thing as "ACTIVE" track. You can select more than one track but you can not have more than one active track, therefor obly one keyboard can be played at the same time, unless you know how to make it work.

That's where input echo comes in. You need to click on it on the non-focus track to hear the synths. It was all explained in the video which is why l linked you to it.

Yes, I remember your XP system woes, Vlad. I was one of the fellows telling you that X2 was not designed for XP and that your system did not meet the sys requirements of the program. In that thread, of course I, as well as others, were more to happy to help you out to solve your issues despite the initial freak outs. As I recall over the next week or so you had solved a lot of your issues by following the suggestions of the forum members and bakers and were happy (after more freak outs throughout the process).
 
So what does that tell you? To me that would say perhaps if you are having problems or concerns you should come check out the forum occasionally and CALMLY ask your questions and you will more than likely get some quality answers that will solve many of these little problems you seem to run into. I'm actually only around a lot these past couple days because of the new release. When I first got Sonar I was here constantly to learn about stuff but for the past while I barely log in... BUT I still read check out the forum every day or so to see what's up or if I run into a problem I post a thread asking a question. More often than not I get my problem solved.
 
It really does not take a lot of time and the benefits are WELL worth it (seriously just check out the forum for ten minutes every day or so). This is exactly what the forum is here for. I know you have updated your system and your system should be working fine but you say you are still experiencing some crashes. Well if you just popped in and asked some questions (without freaking out) we could probably get that sucker working like a dream. If you are having a hard time figuring out how to do something in Sonar you are in the masters den of Sonar nuts of ALL styles of music. You could post in the Sonar or Techniques forum and get ten different ways to do something.
 
Lookit... I know you're an alright person. I'd probably have a beer with ya if we met at a gig but you are really giving yourself a handicap by not using the forum. I also know there is a language barrier (french?) so that makes your frustrations come across even more agressive which makes it harder to get help too.
 
So, as a fellow Sonarite and musician... just take it easy, if you have a problem post a question (calmly) and if you don't understand the answer ask for some clarification. Everyone here is cool and willing to help. Look at all the advice you got in this thread. Look at all the advice you've gotten in past threads. All you have to do is ask. No need to freak out.
 
Right?
 
Cheers.

I am totally familiar with Input Eco, and yet- only active/ focused track is playable. I will test it again some time and respond, but I had issue with it in the past. Also- what is the difference between eco and that other version of that button?
 

X3 (or any previous version of SONAR) has ended it's cycle. There will be no more updates to it. The same is true after 12 months on the new SONAR. You will no longer receive updates. NOTHING has changed, and so if you accept how any previous version  of SONAR was sold and maintained then you accept the EXACT same terms for the new SONAR.

 
As I pointed out earlier, I am convinced and will likely buy full $150 version. However, I still do not like tha fact that X3's life cycle is ended. Can you think of at least one issue that was not fixed? Then how could it be ended without fixing it? In any industry- if you buy something, it means it works with no issues and if there documented issues, a company who sold it should fix it till it fixed. If there is a bug, it simply should be fixed for free and not in the next paid version of the same software. To me New Sonar is the same X3 with ok- few new features most of us could live without, and we asked to pay again, when we just paid last year and it still has issues that were not fixed. If I had X2 version that had step sequencer and it does not work in X3, I expect it to be fixed for free, not in the new version one day- I already paid for it to work.  
 
Now there is a thin line between fixes and new features. Many may feel that new features are "must haves" for fully functional production suit. If there was Undo/Redo button and it was taken away and I am waiting for it- it is waiting for the fix, new feature or old feature return? Just saying- had to throw it there. If there was no "count in" for metronome function and then in X4 they said, "We came up with new feature- it is count in for metronome". Would it be a fix or new feature?

Beepster, you mean, asking without "this ridiculous thing is not working again and never will I cant stand it why won't it do what it supposed to when I need to work? type of comments?" Ok- here is one: why is my computer "sees" USB controller, while Sonar sees it every other time? Why is it that some time I open a project, start playing and have no MIDI activity, and another time it works fine? It is Novation Lunchpad- I contacted Novation- they mailed me new USB cable. When I unplug it, computer says, "Tam tam tam..." so it knows it was connected. But Sonar does not. When I plug it back, Sonar says, "Wow! Found new MIDI device. Would you like to connect it?" "No sh**, Sherlock!" Been trying to make it work for last 15 minutes. So I have to put up with this drama day after day after day. And then I come and they say, "Another $150, please" and I say, "What you mean- you still did not fix my MIDI! So- forgive me for being frustrated. And yes, I can make this thing crash. Wanna bet? It was never X2 on XP problem till X2 came. My Sonar P4, P5, 6, 7, 8 all were crashing always on 3. 6 Mhz processor and Cheetah SCSI 15,000 rpm hard drives. It never ever was flawless. When you want a crash report?  

As has been stated and posted many times over the past couple days this model makes it so that instead of one big release being dumped onto the market which means all the unknown bugs have to be detected and reported at once by the customers by having things introduce in smaller bits it means if there is a problem it will be a SMALL problem and Cake will be able to fix it quickly. If it is screwing you up really badly you call easily rollback to the previous versio (from the previous month or whatever) from the Command Center.
 
Seriously... it is MAYBE something small being broken that you can easily reverse and then the Bakers can easily fix quickly versus the old way of having a HUGE program with pottentially LOTS of bugs all over the program that need to be detected, reported and fixed all at once.
 
If something is released at the VERY end of your membership and you do not resubscribe then if it is a major problem for you you can revert back to the last working version (which would be a month or two backwards... not a full year) and be okay until you decide to join up again. You lose much less than you would have previously... but that is all very unlikely anyway... AND the bakers said if a bug is REALLY bad they would work something out on a case by case basis for lapsed memberships.
 
It should, in theory, be a lot better and it has been discussed repeatedly.
 
No freakouts necessary.

As has been stated and posted many times over the past couple days this model makes it so that instead of one big release being dumped onto the market which means all the unknown bugs have to be detected and reported at once by the customers by having things introduce in smaller bits it means if there is a problem it will be a SMALL problem and Cake will be able to fix it quickly.

 
That is my exact point. I like it to be tested and fixed before they sale it, not after.

vladasyn
Beepster, you mean, asking without "this ridiculous thing is not working again and never will I cant stand it why won't it do what it supposed to when I need to work? type of comments?" Ok- here is one: why is my computer "sees" USB controller, while Sonar sees it every other time? Why is it that some time I open a project, start playing and have no MIDI activity, and another time it works fine? It is Novation Lunchpad- I contacted Novation- they mailed me new USB cable. When I unplug it, computer says, "Tam tam tam..." so it knows it was connected. But Sonar does not. When I plug it back, Sonar says, "Wow! Found new MIDI device. Would you like to connect it?" "No sh**, Sherlock!" Been trying to make it work for last 15 minutes. So I have to put up with this drama day after day after day. And then I come and they say, "Another $150, please" and I say, "What you mean- you still did not fix my MIDI! So- forgive me for being frustrated. And yes, I can make this thing crash. Wanna bet? My Sonar P4, P5, 6, 7, 8 all were crashing always on 3. 6 Mhz processor and Cheetah SCSI 15,000 rpm hard drives. It never ever was flawless. When you want a crash report?  

Okay, that is multiple questions and if you posted a thread asking about each question you would get the help you needed to sort it out...
 
BUT I remember offering some advice about the MIDI connection issue... what? Almost two years ago to you about it?
 
DO NOT PLUG IN OR TURN ON YOUR MIDI DEVICES WHILE SONAR IS RUNNING!!!
 
Sometimes it works, sometimes it doesn't. If I need to use a MIDI device that is not currently connected and turned on I turn off Sonar (and save beforehand if need be) THEN turn on/connect my controllers and THEN turn on Sonar. I know you have a cmplex studio and you do not want to do that but seriously it takes maybe 5-10 seconds to save what you are doing, close Sonar, turn on whatever it is you want to use and THEN reopen Sonar.
 
Unfortunately we are not living in the Star Trek universe yet and there is a limitation to what our technology can do so we have to kind of do what needs to be done evern if it is annoying or seems dumb.
 
We also talked about using the SAME MIDI PORT that you installed a device on so you do not confuse Windows by moving your devices to different ports.
 
There are also a ton of other things that were discussed in that thread and the following threads you posted.
 
There may be new problems but if you do not follow proper procedure or take basic advice (which did seem to work out for you last time) then we cannot troubleshoot any new problems.
 
So... you are having a lot of problems in your studio. Instead of dumping a million problems into one thread that has nothing to do with those problems write down your problems one by one. Post a thread for each in the appropriate forum and then wait for an answer and provide more details when they are asked of you.
 
Trust me... you will get a HUGE amount of your issues resolved.
 
Salud.

vladasyn

As has been stated and posted many times over the past couple days this model makes it so that instead of one big release being dumped onto the market which means all the unknown bugs have to be detected and reported at once by the customers by having things introduce in smaller bits it means if there is a problem it will be a SMALL problem and Cake will be able to fix it quickly.

 
That is my exact point. I like it to be tested and fixed before they sale it, not after.

It is tested. It will be Alpha tested and Beta tested then released to the market. At which point the holes that were not detected and plugged during the previous two testing stages will be reported by the consumer at which point patches will be released. This is how it has always worked with almost any reputable software provider and how it has worked with Sonar in the past.
 
Do you think Cakewalk will release completely untested products on the market?

vladasyn 
That is my exact point. I like it to be tested and fixed before they sale it, not after.

It is simply not possible to test all permutations and combinations of computer hardware, computer software, and plug-ins prior to release. It is also not possible to test with things that don't exist yet but could cause a break in the future, like if a plug-in handles VST or outputs in a non-standard way. Also, bugs aren't universal. You could test a feature on 99 systems and it would work fine, but on the 100th, it wouldn't. Another problem is that if Cakewalk cannot reproduce a bug, they cannot fix it. Unfortunately, all of these reasons are why no software can ever be considered bug-free.