1.7 Virtual Outs In DAW Not Working

Here's my setup. Windows 8, MPC Studio, 8 Output ASIO Interface, running Sonar X2. Typically when I run a vst synth plug-in through separate virtual outs, I can route the signal through an audio track in Sonar X2 and throw my vst fx plug-ins on the track and do my automation. When i try that with MPC 1.7, I can see the 32 virtual outs in Sonar, but nothing is coming out accept for 1/2 stereo. In fact, the meters are showing a steady inaudible hum on channels 3-32 that I've never seen any other plug-in do before.

I realize the whole mixer thing has changed everything (MIDI instead of audio), but this a deal breaker for me. Perhaps I'm doing something wrong so I'm willing to listen to suggestions.

Basically I drop my kick on pad A1, Hat on A2, Snare on A3. Go into the program mixer in MPC and route each pad to a separate audio track respectively. So A1 is on 1/2, A2 is on 3/4, A3 is on 5/6. I get no output through any of those channels, only 1 and 2. I tried exporting a sequence as MIDI data and putting each pad on separate MIDI tracks in Sonar. Still nothing. Please don't tell me to export the audio and then drop it into Sonar, that is not my workflow. Pro software should not be designed like that.

So am I just retarded. I'm pretty damn good in knowing my way around the studio and can usually troubleshoot on my own, but this has me stumped. I feel like it's something in the workflow I'm not doing right. Maybe I'm missing something with the new mixer? Is Sonar X2 just messing me up (believe me I wish I was on bad ass Mac with Logic running), but Sonar has never done me wrong in the past.

Please help. On another note. I'm not trying to Naysay, I know all the hard work that everyone has done on this. It's been a battle for everyone to get to this point and it's great to see strides being made. I just want this thing to work the way it should.

Thanks in advance

Same issue here using Nuendo 6 + Mac 10.8.5. All of my pads routings to dedicated virtual outputs have been reset to "Program"...

Spent my entire day to:
1) uninstall 1.7
2) re-install 1.6
3) make screen captures of my outputs settings in 1.6 for every project (yes, did that...)
4) re-install 1.7
5) from screen captures, set manually each virtual output for each pads for every project (yes, did that too...)

Works like a charm. 1.7 is a great release I wanted to use right now, I preferred not to wait for 1.7.1 to correct this bug.

I love my Renaissance, it's a great instrument and Akai team is doing a great job to improve it. But most of improvements are for Standalone users, DAW users are left on the side.

Inside DAW, one big improvement would be to use Ren as controller, software as sound module and DAW as sequencer. That means bypassing Rens sequencer.

I have no issues with Ren and Albeton 9, i am able to slave Albeton to Ren and Slave Ren to Albeton using midi and Audio.

I am running OSX

I'm in the middle of a project so have only done a quick test. Loaded a 1.6 project and routed about 5 pads to individual tracks. The virtual outputs worked as they should. I'm using Logic Pro X as the host.

I'll check in more detail later today, but I don't have Sonar so I can't check specifics.

Thanks for the replys. Just to clarify I'm trying to do this with a brand new project in 1.7. Nothing from 1.6 or any previous versions. I don't believe the virtual outs were even an option in 1.6 with sonar (I only had 1/2 main outs showing up in 1.6, at least in 1.7 I have 32, they just aren't working). So am I to understand that this a known bug with certain DAWS in 1.7? I read somewhere in the 1.7 manual, (I think it was setting up MMC control) where they mention setup for every major DAW except Sonar. Seems like they're not really supporting Sonar, So I'm not surprised that logic and ableton users are easily getting virtual outs to work. Guess I'll just have to wait and see if 1.7.1 can fix this.

I have also had success using them by setting up a brand new 1.7 project as well. Just fyi...

No problem setting virtual outputs in a new 1.7 project.

Issue was 1.6 projects including virtual outputs per pads not updated properly with 1.7. All virtual outputs were reset to "Program".

I'll make a video tonight after work...appreciate the help guys.

Here's the video. Not sure if this will help but I'm getting desperate.

https://www.youtube.com/watch?v=zUEpPPE ... =youtu.bee]

Life4M wrote:Here's the video. Not sure if this will help but I'm getting desperate.

https://www.youtube.com/watch?v=zUEpPPE ... =youtu.bee]

It's private

Sorry about that...try now

https://www.youtube.com/watch?v=zUEpPPE ... =youtu.bee

I use Sonar so interested to see whats going on... Will see if I can steal some time away from wife for testing this weekend. (its her bday and we travelling to coast and back so time will be limited)

Taking my mpc and laptop tho!

MPCTNT that would be greatly appreciated...at least than I can narrow it down to a problem with the software update or my setup. Let me know what version of sonar your using too. Thanks!

Double checked my configuration, midi working but having trouble with audio tracks while tracking out, seems to work off and on, plan to look at it in depth today, hopefully report my findings.

Setup Mac book pro, albeton 9 and 1.7 Ren.

I am using in stand alone mode not as plugin.

Life4M wrote:MPCTNT that would be greatly appreciated...at least than I can narrow it down to a problem with the software update or my setup. Let me know what version of sonar your using too. Thanks!

Wife took all the time she had coming this weekend. I left work early Friday and spent the rest of the day out with her, got up early Sat, drove to coast,w here we stayed until Yesterday. Just got settled in late and here it's Monday again.

I use SonarX3.