kson: A bigger FX bin on busses. I'm tired of that tiny box when there's so much real estate on busses.

+1000. How come you can't stretch it by mouse :-(.

4       I think Celemony will be the most likely one to make Melodyne work better in Sonar and that Roland is probably working on V Vocal now -at least I am hoping they ARE! Hint Hint Wink Wink Nudge Nudge!
     As I read thru these posts, I realized I fully expect CW/Sonar - Roland and TONS of other people are very busy making all kinds of stuff, that I cannot wait to buy and use!  
    I have this sense of trust about it all. Since I am not used to X1d yet, at all, I  cannot be frustrated or limited by any limitations or lack of features, yet!
I do really appreciate all of your thoughts, musings and grumblings, etc.
Michael

I also have no stake in this...but am completely for VST 3 implentation (pretty obvious
from my posts)

That being said, those who vote 2 missed the post from Melodyne that stated

Melodyne REQUIRES the VST3 api to be integrated.  I even posted:

All you Melodyne Integration guys READ THIS TWICE.

SO,

My vote for just ONE would be 4.

But in order 4, 1, which allows for 2, 3, and 5 Improved Notation and Staff View - Colors would be nice, but
doesn't affect my work in any way...

gapless audio for sure is #1 more live usage considerations like helping us to use scene switches live. Instead of just move to next and previous marker how about move to marker x as an option? notation at least integrate a third party program option as a plug in so we can substitute the notation view with a third party choice. EWQL le Eventide reverb le

5. Staff view improvements

djwayne


6= Colorization options

+1 to this and I would like an integrated Audio Editor Window.

#5 - Staff View improvements (and I'm not talking about Sonar X3, more like the X2a)

[Clarification] - not asking for re-write in X2.003, just fix what has been broken since ver 7, and add Benstat's Sonar Plus stuff.

I would be willing to wait until X3 for functionality on par with Cube / PT / Log  

Melodyne 2.x is distributed as VST2.4 and VST3 and Rewire Slave
Current "integration" into Sonar is possible via VST2.4 and Rewire.

ARA is an extension to the VST2.4 AND VST3 interface. ARA is not "integration of melodyne", but extending the possibilities of plugins in general.

Both host and a plugin have to be able to "talk ARA". Currently, on the plugin side, only melodyne talks ARA, on the host side, only Presonus S1v2 talks ARA, and only within the "VST3 room".

The known "track based immediate offline editing of audio material melodyne style" is, what people usually mean when they talk about melodyne integration.

Therefor, Sonar has to be extended to talk ARA in general (then, when talking ARA in the VST2 room, Melodyne, and any other ARA aware plugin, could already be used ARA style. It's not necessary to build a new VST3 room within Sonar for Melodyne integration.

1. bugfixes/stability 2. gapless audio 3. vst3 -1. i do not want any bundled plugs - i'd much rather have quality before quantity

TabSel


Melodyne 2.x is distributed as VST2.4 and VST3 and Rewire Slave
Current "integration" into Sonar is possible via VST2.4 and Rewire.

ARA is an extension to the VST2.4 AND VST3 interface. ARA is not "integration of melodyne", but extending the possibilities of plugins in general.

Both host and a plugin have to be able to "talk ARA". Currently, on the plugin side, only melodyne talks ARA, on the host side, only Presonus S1v2 talks ARA, and only within the "VST3 room".

The known "track based immediate offline editing of audio material melodyne style" is, what people usually mean when they talk about melodyne integration.

Therefor, Sonar has to be extended to talk ARA in general (then, when talking ARA in the VST2 room, Melodyne, and any other ARA aware plugin, could already be used ARA style. It's not necessary to build a new VST3 room within Sonar for Melodyne integration.

Hey...I didnt say it...