John T
So, going back to the OP, it seems there are three new functions here. There might be more, but that's all I can see in the video. And they are: direct control of the DAW pan pot, direct control of the DAW fader, and ability to insert a send.
 
Just my opinion, but that doesn't seem all that decisive to me. You can already control level and pan in Console One on any DAW it works with, albeit in a sort of jury-rigged way. But the practical difference when mixing is minimal-to-none.
 
Ability to insert a send is reasonably nice, I suppose, but I do wonder if it's a significant time-saver.
 
Not knocking it; good work to Softube for continuing to enhance Console One, and good work to Presonus for being quick off the mark supporting such features. But for me personally, I'm not going "holy smokes, it's a whole new 

The three things you list are trivially done with control surface integration. Again I don't know the whole story and we'll talk to softube to find out what exactly "integration" means. We generally don't do custom stuff for third party hardware unless it benefits more than one class of hardware or were in direct partnership.
We have a great relationship with softube so well find out more.

I'll say this about the insert send thing; I've got a button that does exactly that on the V700. Brings up a dialogue and then you use a knob to scroll through all the possible destinations, which I assume is how Console One would have to do it.
 
Takes way, way longer than using the mouse. I haven't pressed it in literally years. Honestly, this is not a hot control surface feature.

Dreamstation
I'll agree that my second post was short, but not necessarily nasty, and yes... I should probably have written out the points rather than link to the video, but again... not necessarily a crime.  However, I don't think it's such a terrible post that it deserved your abusive response... but apparently that wasn't directed at me.  Yet, how was I to know that?

FWIW it's "forum shorthand" that unless indicated through a quote, a response refers to the previous post. But as you said, you don't spend a lot of time here so it's understandable you wouldn't know that, and I also apologize for any lack of clarity in being specific who the troll was (I did think banning the person who posted immediately before my response spoke for itself, but obviously that was not the case).
 
The reason you weren't banned for being an alt was because even though your thread followed the troll's standard script of "I'm leaving leaving SONAR for Studio One because..." and had other similarities, your post didn't have the same "vibe." I truly appreciate your subsequent follow-up, and accept what you say at face value.
 
FWIW the irony is that if SONAR didn't exist, I'd probably be using Studio One Pro. I don't have a problem with SOP; I use it for album assembly and have done videos for, and consulted to, PreSonus. If an additional layer of integration with a specific control surface is so important to you that you would change DAWs, then you should change DAWs. I switched to SONAR back in 2000 specifically because it provided, and still provides, unique functionalities that are crucial to the work I do, so I understand that what may seem like a relatively minor issue to some users would be seen as a major issue by others.
 
 
 
 

Resonant SerpentIn order to run Softube plugs in Windows 10, you have to use the Windows 8 compatibility mode

Why is this?

There is a bug in PACE that causes an instant crash if the plugin is run in a host that reports that it is Windows 10 compatible. For this release we actually had to make a work around to change SONAR's manifest to NOT report Win 10 compat because of this very issue, otherwise all Softube plugins would crash unless run in compatibility mode. I reported this to Softube and they said its a known bug in PACE that they will be resolving soon.
 

Noel Borthwick [Cakewalk]
There is a bug in PACE that causes an instant crash if the plugin is run in a host that reports that it is Windows 10 compatible. For this release we actually had to make a work around to change SONAR's manifest to NOT report Win 10 compat because of this very issue, otherwise all Softube plugins would crash unless run in compatibility mode. I reported this to Softube and they said its a known bug in PACE that they will be resolving soon.
 

Brilliant - thanks, Noel.

Agreed...I wonder how many "my DAW doesn't work with Windows 10" comments in other forums relate to PACE issues and not the DAWs themselves?
 
[Oh, and Dreamstation - I realized that scook deleted the post to which I replied. If you didn't see that post, then I totally understand why you didn't know what I was referring to.]
 
 

Quick FYI, the mobile version of the forum does not show profile info, sig's, or "banned." At first I thought the post may have been deleted till I pulled up the full version.

Mobile version doesn't show "hot" or "answered" either.
 
Edit - I guess a post was actually deleted from the thread, hence the confusion.

Noel Borthwick [Cakewalk]
There is a bug in PACE that causes an instant crash if the plugin is run in a host that reports that it is Windows 10 compatible. For this release we actually had to make a work around to change SONAR's manifest to NOT report Win 10 compat because of this very issue, otherwise all Softube plugins would crash unless run in compatibility mode. I reported this to Softube and they said its a known bug in PACE that they will be resolving soon.
 

Is this fun or what.
 
 

Indeed. That's my big objection to iLok. In principle, I'm fine with it, but over the years, PACE's implementation has been mostly amateur-hour, leavened by occasional brief periods of adequacy. There's really no excuse.