BobF

abacab
How about a Mackie control app for Windows that you could just run from a touchscreen as 2nd monitor?  Sort of like a control pad app for iPad, but completely integrated with Windows and Sonar?
 
No hardware development investment required, just some creative software engineering.  And a virtual MIDI cable.

Maybe http://ctrlr.org/ will get you a step or two in that direction.

Unfortunately not.... Creating Mackie like controls in it is almost impossible (I have tried). It is very nice project, rather powerful, but for different task.

azslow3

abacab
How about a Mackie control app for Windows that you could just run from a touchscreen as 2nd monitor?  Sort of like a control pad app for iPad, but completely integrated with Windows and Sonar?
 
No hardware development investment required, just some creative software engineering.  And a virtual MIDI cable.

For some reason that does not exist... I guess no market. I have found only one App in that direction. Logically, who is going to use windows tablet for the purpose? Cheap tablets can also run Andoroid, expensive can run Sonar.

But no Windows tablet required!
 
For example, you can add a touchscreen to your existing desktop (or laptop) DAW for $200-300!
 
https://www.newegg.com/To...ors/SubCategory/ID-514

abacab

azslow3

abacab
How about a Mackie control app for Windows that you could just run from a touchscreen as 2nd monitor?  Sort of like a control pad app for iPad, but completely integrated with Windows and Sonar?
 
No hardware development investment required, just some creative software engineering.  And a virtual MIDI cable.

For some reason that does not exist... I guess no market. I have found only one App in that direction. Logically, who is going to use windows tablet for the purpose? Cheap tablets can also run Andoroid, expensive can run Sonar.

But no Windows tablet required!
 
For example, you can add a touchscreen to your existing desktop (or laptop) DAW for $200-300!
 
https://www.newegg.com/To...ors/SubCategory/ID-514

But what benefits an extra display with Mackie Controll is going to bring to the operations? Mackie control can only do "mixing" task, just moving Console View to this extra monitor will give that (and a bit more) possibilities.
 
If mobility is an advantage, for $100-$300 it is possible to get a tablet with TouchDAW/Lemur/TouchOSC.
 
Finally for a bit more there is X-Touch (Compact).

azslow3
 
But what benefits an extra display with Mackie Controll is going to bring to the operations? Mackie control can only do "mixing" task, just moving Console View to this extra monitor will give that (and a bit more) possibilities.

Maybe using "Mackie Control" as an example was too limited in scope.  If there was an API available from Cakewalk that could be accessed in Sonar, maybe another app could control more than mixing.  So rather than saying Sonar needs more flexibility in supporting hardware, why not just open up an API that 3rd party software devs could tap into.
 
My main point is that making control software compatible with DAW software might be a better option than trying to make more hardware control compatible with DAW software.

abacab

azslow3
But what benefits an extra display with Mackie Controll is going to bring to the operations? Mackie control can only do "mixing" task, just moving Console View to this extra monitor will give that (and a bit more) possibilities.

Maybe using "Mackie Control" as an example was too limited in scope.  If there was an API available from Cakewalk that could be accessed in Sonar, maybe another app could control more than mixing.  So rather than saying Sonar needs more flexibility in supporting hardware, why not just open up an API that 3rd party software devs could tap into.

Cakewalk has Open Source API SDK. It does not cover editing (unfortunately), but it does cover a lot.
I have used that SDK and created AZ Controller, which in turn support OSC (some improvements are still pending, but it is already quite usable with Apps such TouchOSC and Lemur).
 

My main point is that making control software compatible with DAW software might be a better option than trying to make more hardware control compatible with DAW software.

The procedure is EXACTLY the same. Software "controls" generate the same set of commands as corresponding hardware control, the whole logic is in the software on the DAW side (Control Surface plug-ins in Sonar, Python scripts in Ableton, etc.).

tlw

Ham N Egz
Go to GS/KVR/etc and read the negative posts about Sonar AND our forums

Go there and read posts about anything and you come away wondering if anything works at all or any maker of anything ever utters a true word. Analogue synths and guitar gear frequently gets slated for being "digital" when it's no such thing, and the old whatever it is is you can't buy any more is always praised by someone as so much better than the current version of the same thing. Even if the current one is exactly the same as the old one.

The signal to noise ratio can be very low at times.

 
There's a thread there now...
"Do all DAWs suck?"
 
The OP mentions that Sonar's "latency" gets worse over time.
Well... latency only has two sources.

• audio interface
• latent plugins inserted in the project

That particular complaint has to be pilot error.

KVR forum can be well described by old Russian joke:
Agenda for the Women's Committee meeting:
1. There's nothing good to wear (again)
2. All the men are bastards
3. Miscellaneous

Jim Roseberry
There's a thread there now...
"Do all DAWs suck?"
 
The OP mentions that Sonar's "latency" gets worse over time.
Well... latency only has two sources.

• audio interface
• latent plugins inserted in the project

That particular complaint has to be pilot error.

It could also possibly be caused by a software bug, in the PDC code for example

Not that I've noticed it myself

pwalpwal

Jim Roseberry
There's a thread there now...
"Do all DAWs suck?"
 
The OP mentions that Sonar's "latency" gets worse over time.
Well... latency only has two sources.

• audio interface
• latent plugins inserted in the project

That particular complaint has to be pilot error.

It could also possibly be caused by a software bug, in the PDC code for example

Not that I've noticed it myself

Yes, a bug in the PDC code could affect latency.
But... the OP in that thread was essentially saying Sonar's latency has gotten worse over time.
That's not the case... or everyone would be experiencing it.
My guess is that the OP started using latent plugins... and is blaming additional latency on the host.
 

Jim Roseberry

pwalpwal

Jim Roseberry
There's a thread there now...
"Do all DAWs suck?"

The OP mentions that Sonar's "latency" gets worse over time.
Well... latency only has two sources.

• audio interface
• latent plugins inserted in the project

That particular complaint has to be pilot error.

It could also possibly be caused by a software bug, in the PDC code for example

Not that I've noticed it myself

Yes, a bug in the PDC code could affect latency.
But... the OP in that thread was essentially saying Sonar's latency has gotten worse over time.
That's not the case... or everyone would be experiencing it.
My guess is that the OP started using latent plugins... and is blaming additional latency on the host.
 

I should go and read the thread :-)