Although the documentation seems pretty straightforward, I cannot change Streichfett patches with Sonar X3. The Waldorf User Manual shows the message as cc pp, where cc is the channel and pp is the patch number (0-11).  That's the standard program change message, right?  And that's how Sonar changes patches, right? Anyway, it's not working for me.  Has anyone had success here?  Thanks!

I don't have that particular synth, but I do have others by Waldorf. They can be a bit... unpredicatable at times, and operation and the manual aren't necessarily always in step with each other.

Try this.

The Striechfett, according the the manual, is supposed to send MIDI program change when programmes are changed on the unit. Set up a MIDI track with the synth as input, arm the track, switch off input monitoring to avoid MIDI feedback and start recording. Then step through the program change functions on the synth itself, loading each program slot one after the other.

With any luck the program change messages sent by the synth will be recorded in the MIDI track and viewable in the event viewer. If they are that may well give you the data the synth needs to receive to activate program changes. If Sonar doesn't seem able to send the data using the usual method, split up the recorded MIDI so each clip contains the data to trigger a program change, save each clip as a file and just paste them into MIDI tracks where you need the program changes.

Thanks!  Just tried your suggestion. 
 
Here's the sole event in this new composition, triggered by pressing the Streichfett's rightmost memory button, with the bank selector set to "C."  All is as expected. Event viewer shows:
 
[Track,HMSF,MBT,CH]; Kind =Patch; Data = Normal, 11.
 
I've looked at the files that SONAR writes when saving as .mid's, and Streichfett program changes appear to be transmitted the same way (no guarantee, of course; I wish there were an easier and more reliable way of monitoring/tweaking raw MIDI here).
 
I must be doing something wrong with the Streichfett.  But thanks for your suggestion!  I will report back if I find a solution.
 
 

You could set the synth to some other patch and then play the recording you just made to see if the patch changes back on the synth. One thing to check, by the way, is that the channel setting of your track in Sonar matches the channel configured on your synth. The channel number shown in your patch-change recording shows the channel the synth is set to. Also by the way, the patch change message is 'Cc pp', where 'C' is literally hex 'C', 'c' represents a channel number 0-15 (aka 1-16, or hex 0-F) and 'pp' is the patch number. Doesn't matter because Sonar doesn't really show you the hex.

No, I've tried all that -- no dice.  (I stopped programming a year ago, but can't seem to escape debug mode -- and what a way to start the New Year!)
 
Anyway, I just emailed Waldorf support; if they answer, I'll pass their response along.
 
Sorry for not capitalizing the "C" (hex 13).  I look at the hex in Visual Studio or Sharp .Net (the latter, recommended for the open source, Windows crowd, BTW).

You might find Waldorf take a few days to respond - Germany tends to be in festive mode from Christmas Eve through to 12th night (January 6th).

Meanwhile I'm about to return a brand new Pulse 2 that's stuck on patch 1, responds to none of its matrix controls other than the volume knob, sends no MIDI out at all, appears to respond to nothing but note on/off and the mod wheel, while Windows doesn't even recognise it as a MIDI device. My MacBook does detect it, but can do nothing with it other than reinstall the operating system. Which seems to install exactly as it should but makes no difference.

I've had a love/hate relationship with Waldorf for years. Trouble is that when their kit works it sounds like nothing else and is horribly addictive, but thoroughly debugging things just isn't the Waldorf way. :-/

Sorry to read about your Pulse 2 troubles.  It's infuriating how this sort of thing gets in the way of what you really want to do: make music.  All the hours, head-scratching, false leads... if you're lucky, someone will finally pipe in and say, "hold down memory buttons 4 and 27, connect the usb cable, put the pitch bend wheel at 119, release memory button 4, unplug the usb cable, release memory button 27, plug in the usb cable and -- voila!"  Pretty intuitive, of course.
 
A correction to my post of yesterday: "C" is hex talk for 12, not 13.  Jeez!