Okay, so I was enjoying getting to play my YRG in Sonar, but there are projects I'm working on, so I decided to see about easing the YRG into one of my projects. But before I did anything, I grabbed my digital camera and took a pic of the screen, so I could recall the setup that
worked if need be. I decided to call up the new project while leaving the file open I'd configured successfully for the YRG. This worked fine, sort of. I had two files open and was able to play the YRG, but it had switched to a soft synth I didn't want to use for this project (I had loaded two soft synths into the test project and gotten both to work, and was able to switch back and forth between the two without a problem), so I switched views and tried to activate the other synth. Before I brought up this new file, all I had to do was click on one of the output panels for the synth I wanted to use. This time when I clicked on the other synth's output panel, all my YRG sounds disappeared. So I shut down the new project file, so that now all I had open was the test file for the YRG -- which was previously working and
nothing had changed. No sound this time. But the VU meters respond as if there should be. If I click on the track, I get VU displacement for the track, and if I click on one of the output panels, I get VU displacement in it. I hadn't changed a thing. All I had done was bring another file into the mix, played the file and played my YRG some along with it, then shut down the file so I could make some changes in the test file. But that's all it took to send me back to square one.
I played around with settings and such for a good half hour before deciding to return here. A few of the setting changes I tried were changing ASIO OUT at the track's synth pane to "Master," and then make sure "Master" was set with the ASIO outs, same as it always was. In fact, this was the default setting for the second synth I loaded into the mix -- Cakewalk TTS-1. That is, when I loaded in TTS-1, it automatically configured one of its two panes' 'out' to "Master." Didn't make any difference, though. I played around some with the "C" and "O" and "P" selections, but it didn't make any difference.
Here is the snapshot I took of the Sonar setup that worked before it didn't work. This is a fairly large file. I saved it to a large file so you could read the smallish words in the console panes. Because they are gray colored I also bumped up the contrast a LOT and added quite a bit of the unsharp masking sharpness routine to the photo to make it as easy as possible to read the words and abbreviations. Cakewalk's forum software scrunches the image down to a reasonable size for viewing here. But if you right click on it and select "View Image" it will display the image only at a larger size. With my browser, I can click on the image yet again to view it full size. Hopefully you'll be able to read the text then.
I'll tell you what, if I can't figure out why this is such a big frigging problem with Sonar -- and after reading your responses that you are having no problems, even though it doesn't make a whole lot of sense to me, I will be forced to consider this YRG defective and return it to GC for a refund. I've got more important things to do with my time than screw around with what may likely be a defective piece of kit. And if it is, it really chaps my butt that GC would put a known defective item back on the shelf. It had been previously opened and used when I bought it, but I stood right there in the store and tried it out for a good half hour before I took it home, just to be sure. Heh. The one thing I couldn't check was how trouble free it would be with my software.