I just tried importing a stereo wav file into a strip in track view and it worked as expected.
 

I worked with midi drums last night and I'm seeing that the drum map "mis-alignment in the PRV" issue is back again.  I haven't seen that for quite some time now.  The solution is the same, (close the PRV and then reopen), but it's much worse this time around. 
 
I'm going to test the Export Audio issue on this release, (see here for the post), and then roll back to 2017.01.
 
Paul

I decided to roll back. That took care of most of my issues. Not to rub it in, but in addition to what I previously mentioned, I was seeing things like the Now Time marker bleeding through the Console View and the Console Emulator in ProChannel not accepting input.

mmarton

MagicMike
I've had weird graphical glitches. Open a project I created with the new update, no 3rd party plugins and only a couple of prochan modules on the master, tracks in track view briefly appear whilst project is loading then after loading the whole of track view is empty. I have to scroll the scroll bar to the right of track view to make them appear.
Also other glitches within the same project - mic audio was showing when track was armed but nothing recorded. Had to restart Sonar to sort this out.
 

I have the disappearing track issue too, but that started with 2017.01

I'm rolling back. Editing a drum track, I'm zooming in on a kick drum transient so I can make a cut across all my drum tracks - as I zoom in the wav display disappears although the timeline says I'm still at that point. Make a split and it's not at the start of the kick drum transient.

Update on my post. Rolled back and still the same zoom glitch. Bounced audio to clip and it's behaving as expected now in both the previous and new version.

Hey, wait I got a new complaint.
 
On my daw, latest early release for FEB, last one before the official release.
I loaded up a new file. BASIC, one midi track, one analog and a master strip.
I right clicked on the analog track, selected import audio... was presented with
the explorer window where my last import came from and as soon as I moused down
on the file to import, SONAR locked with the go-round-circle and had to be killed but would
not fully kill until restart. I tried the whole process again and this time it worked. Giving credence to the notion that doing the same thing over and over expecting a differing result is the definition of a moron or idiot -- I forget. Too much of an idiot I suppose.
 
Nevertheless there is something amiss with import audio just not all the time. - which should be fun to fix.
 
Windows 10 32 bit.

Ok had my first issue with the update last night.  Well I have had issues with importing waves files.I re-did them and tested them in Sound Forge first this time.  Unfortunately, there were a lot of noise issues after I imported them.  I do this all the time so I know it can be done successfully...that is..er...until last night.
 
Any thoughts or suggestions on this issue.  It is a critical one for the way I work with Sonar Platinum.
 
No problems, however,   recording/mixing or using plugins.  All seems normal there.  The import feature is the only issue so far.

Can you create a recipe for Import audio not working with a specific file if possible? There have been zero changes to that area in a long while and certainly not in the 02 release. The issue in 02 is most likely coincidental that you noticed it.

I tested the Audio Export issue with 2017.02, (see my post above - apparently you can't quote your own posts anymore,...lol), and nothing's changed so I rolled back to 2017.01 and the Smart Tool issues are now in .01! 
 
In addition to that, I saw this interesting behavior.  After comping an audio track I selected all the clips and attempted to Bounce To Clip.  I got this message: An unknown error occurred during processing possibly caused by an invalid parameter".  I closed the DB and re-selected the clips and it worked as expected except that the resulting wave form showed "Busy" and just set there!  Sonar showed "running" in the Task Manger and I ended up having to shut Sonar down, and try again.  After several attempts, it worked. 
 
This happened for several tracks I had been comping and then I abruptly stopped getting the error message and I was able to edit and bounce for the rest of the session without issues, (other than the a fore mentioned Smart Tool problems).  Yes I re-booted several times.
 
Likely unrelated but my Audio Playback just stopped working last night.  Tried everything including shutting Sonar down and trying to play an audio file in Windows.  Nothing!  I had to turn off my interface and turn it back on again.  It only happened that one time.  Strange stuff has been happening.  Very frustrating!
 
Any thoughts?  Thanks.
 
Paul

I've been working with some pretty complex songs since the release and have noticed no negative issues so far. Positives though! The new Take Lane enhancement is a real time saver and a pleasure to use.