SONAR-Project5 Integration
We get a lot of requests to have the integration between SONAR and Project5 be tighter. We thought it might be good to address this issue and let you know where the Project5 team stands on this issue. First, we obviously all love SONAR, and think it is great. We understand how a lot of people would want to start a project in Project5 and then move on to SONAR for more massive editing and mixing tasks. However there are also a lot of people who are using Project5 exclusively and our plan is put all our resources into making Project5 the best piece of software it can be.
We want Project5 to integrate (play well) with other applications in general. We do not want to treat Project5 as an add-on to SONAR, but instead its own individual application. So the idea is that we want Project5 to work well with other applications, not just SONAR specifically. We are looking to add features that are more universal, in the sense that they make Project5 a better program. So for example, features like Project5 as a VSTi or MIDI export…those would benefit SONAR customers but would not be exclusive to them. Those are the kind of features we would be likely to add as opposed to some proprietary feature that only works between SONAR and Project5.
So in summary, we love SONAR, and we have a dedicated team that showers it with attention every day. Now it is time to show Project5 the love it deserves.
We want Project5 to integrate (play well) with other applications in general. We do not want to treat Project5 as an add-on to SONAR, but instead its own individual application. So the idea is that we want Project5 to work well with other applications, not just SONAR specifically. We are looking to add features that are more universal, in the sense that they make Project5 a better program. So for example, features like Project5 as a VSTi or MIDI export…those would benefit SONAR customers but would not be exclusive to them. Those are the kind of features we would be likely to add as opposed to some proprietary feature that only works between SONAR and Project5.
So in summary, we love SONAR, and we have a dedicated team that showers it with attention every day. Now it is time to show Project5 the love it deserves.
posted by Andrew at 2:48 PM
Subscribe
9 Comments:
Then, we could understand that Project5 will exist in VSTi/VSTfx format? :)
I was just throwing out an example...it is on our radar though...remember that we have only announced some of the new features, there will be another round.
Can you add a facility to export all tracks as a seperate wav file. These could then be imported into any sequencer for use.
To use P5 as a vsti in other hosts would be amazing. Please do it!!!
Will the Groove Matrix have more triggering options?
Also a very important option to me is that the Groove Matrix cells that are set to "play in time with song", actually get recorded to the track view as "play in time with song" and not as "trigger from start", like it is now.
I've noticed that posts on this subject on the Project5 forum did not get any replies from CakeWalk.
If there were any, I probably have overlooked them and I apologise.
VSTi support is absolutely a must. It is a feature that will focus on the flexibility of P5 which I think is something Cakewalk are keen to spotlight.
Why add all the features that Sonar has into P5 at this point. Simply give it a more simplified route to working with every VSTi host out there.
Adding VSTi support puts P5 ahead of even Live 6.
VSTi support has always been a big hitter with the hugely popular FL Studio crowd. Fl studio has had this feature for ages.
Energy XT is another massively popular app. Why? It is a full host but as with FL studio can operate as a VSTi.
Bakers...add VSTi functionality to P5 and broaden it's appeal overnight.
Rewire is not everyones favourite way to connect P5 and Sonar. VSTi usage is far simpler, quicker and easier on many levels.
Midi out is another very important feature. Live and Reason already have this P5 must try and keep up here. But offering P5 as a VSTi would nudge P5 ahead of Live6 and Reason3.
Once I get to a certain point in a project I no longer need to work in P5, I want to edit and add audio tracks in Sonar. Currently we can only export a stereo mix.
I believe the most efficient way to quickly integrate P5 is to allow the export of "stems", separate wav's for each track. Even better, allow them to be exported into a named Sonar project starting at track #.
The stems would obviously need to be time aligned so they would be filled with silence, where needed, so they all start at 0 time.
With P5 and Sonar being Cakewalk applications, one would think that tight integration between the two would be a given.
This seems to paint a picture that the P5 team wants to build an artificial barrier between the two products?
They're both Cakewalk products and tight integration should have been a founding concept as they both do different things and combined they would be a power house.
Rewire and one way drag n' drop is not what one expects from two products from the same manufacturer. This is a major dropping of the ball and crippling of the product.
We need the ability to "EASILY" move tracks MIDI/Audio between P5 and Sonar. The focus should start with Sonar and move out from there.
Just my 2 cents :)
AXE
I can appreciate that the Project 5 team want to make P5 independent and able to compete on its own merits.
But not integrating with Sonar above and beyond what is possible via ReWire and VSTi is not a good idea.
I use Live for composition and Sonar for completing projects. If P5 enabled a smooth end-to-end workflow it would be an impossible to ignore proposition.
Something as basic(!) as a file converter would suffice. Something that takes the project info in P5 and converts it (copies) to Sonar would be very welcome indeed.
Shame on Cakewalk for not developing a common project file standard in the first place!
Post a Comment
<< Home