AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 15:33:17
(permalink)
Anderton
azslow3
SilverBlueMedallion
John
To prevent the volume on the FM8 from being lowered goto the Event List View and insert a CC7 with level you want the FM8 to play at the very beginning. If for some reason you have other CC7s in the track and don't want them delete them. Once that has been done you can have reset controllers without problems.
and what if i am not starting playback at the very beginning?
This is not something one should have to do. Maybe it shouldn't be getting random CC 7 messages to begin with.
Sorry for repeating that, one more and for the last time from me:
Sonar IS NOT injecting any MIDI, and it IS NOT changing synth parameter. It is you, your equipment or your installation which does that fancy things. At least there was no single prove that is usual for other users.
Sonar has some inconvenient behavior with MIDI, which is the same for everyone. Just inconvenient, nothing serious.
Sonar has some small bugs in MIDI, confirmed by other. All of them are triggered in quite special situations only. They are not in the list of your complains.
Sonar does not support MIDI routing. Sonar does not really support MIDI FXes in VST format. That is in the future requests for long time, but that is not a bug. It is simple "not there yet". Using VST MIDI outputs is A WORKAROUND to somehow support VST MIDI FX. Far from perfect. Has several problems, including known and not mentioned by you. And it is known that using this workaround is a nightmare as soon as you change MIDI devices, re-route something, etc.
Sonar also can not prepare food. It is possible to insert tons of plug-ins and start playback, that will drive CPU to the limit, it will produce a lot of heat, so theoretically cooking something. But it is pointless to complain that does not work perfectly.
Sonar is DIRTY CHEAP for the value of third party software coming with it. If you sum even cheapest discount prices of AD2, Melodyne and all other included plug-ins, it is easy to prove you pay almost nothing for the DAW. It can not do EVERYTHING the way ANY PARTICULAR USER wants. There are other software packages, which provide other and sometimes better ways for particular workflows. They are also DIRTY CHEAP. Think about it other way: all your $$ spent for Sonar can at most cover ONE programmer for ONE day....
Azslow3, I truly appreciate that a) you know what you're talking about, and b) that you try to educate people whose minds are made up and not interested in facts. However, after my providing links showing that something SBM repeatedly calls a "bug" is a specific design decision (detailed in the Cakewalk blog concerning SONAR's VST3 implementation), and his refusal to educate himself about why that design decision was made, I have chosen to give up on him and instead, spend my time on people who benefit from the learning process rather than reject it.
And I can't believe he said "and what if i am not starting playback at the very beginning? This is not something one should have to do." Well one doesn't have to, but he clearly knows so little about SONAR's basics he's not aware of "Zero controllers when play stops" and "Controller searchback before play starts," let alone when or how to use them. Yet he wants us to believe he's incapable of user error.
People with a solipsistic mindset who demand constant attention and play victim get tiring. Perhaps we should take up a collection and buy him any software program he wants, with the stipulation that he participate only in that program's forum.
Anderton, the user is telling me to put a CC 7 control in the beginning of my track to ensure the volume is where I want it. Yes, I WILL need to start at the beginning of the track... that's the point! I shouldn't have to if Sonar's "NONE" wasn't actually acting as MIDI Omni for input! Don't you get it? Also did you see the steps here? http://forum.cakewalk.com/FindPost/3542477 How can you say this option is "working". you seriously are flat out saying now things are working as is, when they CLEARLY aren't. What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING! I can't actually believe after looking at my 4 steps you are still saying this is by design!! The checkmark actually DOES NOT DO ANYTHING!!! IT - IS - BROKEN! How is that by design? What you are saying makes no sense now.... just anything to make this not look like a Sonar issue. Unbelievable.
post edited by SilverBlueMedallion - 2017/01/08 18:47:31
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 15:58:07
(permalink)
☄ Helpfulby tlw 2017/01/08 16:26:13
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 16:01:15
(permalink)
gustabo
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in. besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 16:24:30
(permalink)
SilverBlueMedallion
gustabo
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.
besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track
That was me and I was trying to answer why when you start playback the volume is not what you want. The channel idea was trying to avoid errant MIDI affecting other synths. All you have to do to prevent synths from sending MIDI data out and is in the dialog I talked about uncheck that. I said noting about a widget in the track. I've been working with MIDI for twenty or more years. Before there was a Sonar. And these are not problems unless you make them problems.
|
MarioD
Max Output Level: -72 dBFS
- Total Posts : 901
- Joined: 2006/04/15 15:59:50
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 16:25:36
(permalink)
Go to preset/project/midi and make sure there is a check mark on patch/controller search back before play starts and when you start a playback later in the song Sonar will read all of the patch/controller settings prior to starting the playback.
Are you sure that erroneous MIDI data is making the changes or is the softsynth just starting at its own designated settings? I have run into that with Kontakt were I have to start a track with a CC7/11 or 2 or else Kontakt will use its designated volume setting. YMMV
The reason people say the vinyl sounds better is because the music was better. Sonar Platinum, Intel i7 –2600 CPU @ 3.2 GHz, 16 GB ram, 2x2TB internal drives and 1 1TB internal drive, Radeon HD 5570 video card, HP 25" monitor,
Roland Octa Capture, MOTU Midi Express 128, Win 10 Pro
www.soundcloud.com/Mario_Guitar
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 16:32:31
(permalink)
This is what I'm talking about.  Because it unchecked there will be no MIDI output from the synth.
|
tlw
Max Output Level: -49.5 dBFS
- Total Posts : 2567
- Joined: 2008/10/11 22:06:32
- Location: West Midlands, UK
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 16:42:59
(permalink)
Ye Gods.
Look, this really is very, very simple.
Before you launch any DAW you turn your audio interface on, yes? That's a rhetorical question by the way. If you don't then any project loaded will complain about it and the master bus and any other busses feeding hardware outputs won't be routed correctly.
MIDI hardware is treated the same way.
If, before you launch Sonar you switch your MIDI controller on so Sonar is seeing the MIDI environment the projects tell it to expect to see MOST OF YOUR "PROBLEMS" WILL GO AWAY.
If you used MIDI channels to route MIDI MOST OF YOUR "PROBLEMS" WILL GO AWAY. If you used some DAWs, e.g. Logic for one, you would have to do that. If you used hardware synths or MIDI controlled processors you would have to do that. Putting lots of stuff all on the same channel is asking for problems and massively complicates sorting out routing problems and mistakes. Using channels means you can be certain MIDI only controls what that particular MIDI should be controlling. Doing it your way is asking for problems.
It is not Sonar's fault that you don't switch your controller on or refuse to use channels to help keep MIDI routing as you want it and would rather vent here about what is neither a design problem nor a bug other than the omni/none naming issue. WHICH YOU CAN AVOID BY TURNING YOUR CONTROLLER ON OR USING MIDI CHANNELS before opening a project that expects it to be available.
And that's the first time I've ever shouted on this forum, but I'd hate to see someone being misled by your personal gripes.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board, ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre. Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 16:44:24
(permalink)
tlw
Ye Gods.
Look, this really is very, very simple.
Before you launch any DAW you turn your audio interface on, yes? That's a rhetorical question by the way. If you don't then any project loaded will complain about it and the master bus and any other busses feeding hardware outputs won't be routed correctly.
MIDI hardware is treated the same way.
If, before you launch Sonar you switch your MIDI controller on so Sonar is seeing the MIDI environment the projects tell it to expect to see MOST OF YOUR "PROBLEMS" WILL GO AWAY.
If you used MIDI channels to route MIDI MOST OF YOUR "PROBLEMS" WILL GO AWAY. If you used some DAWs, e.g. Logic for one, you would have to do that. If you used hardware synths or MIDI controlled processors you would have to do that. Putting lots of stuff all on the same channel is asking for problems and massively complicates sorting out routing problems and mistakes. Using channels means you can be certain MIDI only controls what that particular MIDI should be controlling. Doing it your way is asking for problems.
It is not Sonar's fault that you don't switch your controller on or refuse to use channels to help keep MIDI routing as you want it and would rather vent here about what is neither a design problem nor a bug other than the omni/none naming issue. WHICH YOU CAN AVOID BY TURNING YOUR CONTROLLER ON OR USING MIDI CHANNELS before opening a project that expects it to be available.
And that's the first time I've ever shouted on this forum, but I'd hate to see someone being misled by your personal gripes.
totally wrong, i dont need to plug in my interface if "NONE" actually meant "NONE". see: http://forum.cakewalk.com/FindPost/3542635
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:10:57
(permalink)
You're just trolling now. Blocking applied.
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:11:49
(permalink)
ampfixer
You're just trolling now. Blocking applied.
absolutely not trolling. this is a REAL issue inside Sonar. NONE=Omni LOL
|
ampfixer
Max Output Level: -20 dBFS
- Total Posts : 5508
- Joined: 2010/12/12 20:11:50
- Location: Ontario
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:12:15
(permalink)
Cool! now the whole thread is about folks describing how midi works. 
Regards, John I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps. WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig, Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:13:13
(permalink)
ampfixer
Cool! now the whole thread is about folks describing how midi works.
ah right, because "NONE" actually SHOULD mean "OMNI". got it.
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:37:37
(permalink)
SilverBlueMedallion
gustabo
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.
besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track
There is something called "Controller searchback before play starts".
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:39:17
(permalink)
gustabo
SilverBlueMedallion
gustabo
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.
besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track
There is something called "Controller searchback before play starts".
Oh ok, cool. I have that turned off, it was suggested from another issue I am having with presets not saving correctly. Cool feature.
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 17:41:14
(permalink)
|
mettelus
Max Output Level: -22 dBFS
- Total Posts : 5321
- Joined: 2005/08/05 03:19:25
- Location: Maryland, USA
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 18:02:30
(permalink)
☄ Helpfulby Nong 2017/03/06 06:41:11
Life is about time, priorities, and decisions. That is pretty much it. If a situation does not suit someone, either adapt to what is, overcome, or move on. If someone truly wants to do something, they will make it happen by using one of those vehicles to do so.
Unfortunately, I have met so many people who will spend 90% of their time finding reasons not to achieve that if they had spent it on doing, then they would have already gotten things done. I am more convinced that certain people default to this behavior.
A simple word of advice is to take in responses, read them for what they are, and decide accordingly. The time you save will benefit the rest of your life (i.e., use it on something meaningful).
ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 18:08:46
(permalink)
SilverBlueMedallion
hmmm actually according to this, it appears that function does not search back for any and all CC data, just
patch change, wheel, and pedal events. so i dont think thats it.
https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Playback.33.html
Your ignorance about what you want astounds me! What do you think pedal and wheel events are? They're CC info. Without testing it, you'll never know! (It's Cakewalk's fault for not seeing you coming, they should have listed every single CC# )
post edited by gustabo - 2017/01/08 18:31:07
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
abacab
Max Output Level: -30.5 dBFS
- Total Posts : 4464
- Joined: 2014/12/31 19:34:07
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 18:11:48
(permalink)
What was that quote by someone famous, about repeating the same action again and again, expecting a different outcome each time?
DAW: CbB; Sonar Platinum, and others ...
|
jsg
Max Output Level: -69 dBFS
- Total Posts : 1079
- Joined: 2003/11/20 04:54:18
- Location: San Francisco, California
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 18:48:11
(permalink)
☄ Helpfulby dcumpian 2017/01/09 08:18:18
Anderton, the user is telling me to put a CC 7 control in the beginning of my track to ensure the volume is where I want it. Yes, I WILL need to start at the beginning of the track... that's the point! I shouldn't have to if Sonar's "NONE" wasn't actually acting as MIDI Omni for input! Don't you get it?Also did you see the steps here? http://forum.cakewalk.com/FindPost/3542477 How can you say this option is "working". you seriously are flat out saying now things are working as is, when they CLEARLY aren't. What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!But I understand as a VP of Gibson, this thread could potentially sway new users away from a purchase, hence you have to make it look like there is no problem and its a user error. I can't actually believe after looking at my 4 steps you are still saying this is by design!! The checkmark actually DOES NOT DO ANYTHING!!! IT - IS - BROKEN!How is that by design? What you are saying makes no sense now.... just anything to make this not look like a Sonar issue. Unbelievable.It's standard procedure to place at the start of every track all the MIDI controllers at the default values you want them to be at. For example, here's a typical MIDI track starting at 1:00:01: Control 7 127 Control 11 127 Control 18 0 (this is the controller I used for attack time) Control 19 85 (I use this controller for release time) Control 22 (controls which cell (articulation) is called up for my VSL library Control 33 (controls the vertical dimension of cell choice (articulation) Control 44 (determines whether patches with built-in crescendo/decrescendo start as crescendo or decrescendo Control 55 (humanizes playback by introducing a controllable amount of pitch variation All these controls are at the top of every track. For softsynths, whatever controller I assign to a parameter I do the same thing: at the top of the track the default controller values are always there. If you don't start playback at the top of the track, MIDI searchback takes care of that by defaulting to the last controller value. I assume you are aware of MIDI searchback and how to activate it. A lot of people seem to be trying to help you, but either we're not getting what you're saying or you and Sonar are simply not a good match. Sonar's MIDI functions are excellent, in spite of the fact there are some bugs. Jerry www.jerrygerber.com
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 18:49:22
(permalink)
gustabo
SilverBlueMedallion
hmmm actually according to this, it appears that function does not search back for any and all CC data, just
patch change, wheel, and pedal events. so i dont think thats it.
https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Playback.33.html
Your ignorance about what you want astounds me!
What do you think pedal and wheel events are? They're CC info.
Without testing it, you'll never know!
(It's Cakewalk's fault for not seeing you coming, they should have listed every single CC# )
either way, I shouldn't have to put any CC 7 data in there if CC from other softsynths wasn't erroneously making changes to other softsynths.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 21:05:48
(permalink)
SilverBlueMedallion
What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!
I can't actually believe after looking at my 4 steps you are still saying this is by design!! The checkmark actually DOES NOT DO ANYTHING!!! IT - IS - BROKEN!
How is that by design? What you are saying makes no sense now.... just anything to make this not look like a Sonar issue. Unbelievable.
What's unbelievable is that you blame me because you don't understand what a default is, what overriding a default is, what creates defaults, what a specification is, don't pursue links I provide that back up what I say, and then cross-post in other threads making idiotic accusations but never update the errors you make with correct information. When I'm wrong, I have the decency to say so and give credit where credit is due because my concern is disseminating correct information. Apparently you have different priorities. At this point, I honestly don't know if you truly don't understand, or whether your're willfully ignorant. Please, turn the thread title from a threat to a promise.
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 21:17:47
(permalink)
Anderton
SilverBlueMedallion
What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!
I can't actually believe after looking at my 4 steps you are still saying this is by design!! The checkmark actually DOES NOT DO ANYTHING!!! IT - IS - BROKEN!
How is that by design? What you are saying makes no sense now.... just anything to make this not look like a Sonar issue. Unbelievable.
What's unbelievable is that you blame me because you don't understand what a default is, what overriding a default is, what creates defaults, what a specification is, don't pursue links I provide that back up what I say, and then cross-post in other threads making idiotic accusations but never update the errors you make with correct information.
When I'm wrong, I have the decency to say so and give credit where credit is due because my concern is disseminating correct information. Apparently you have different priorities.
At this point, I honestly don't know if you truly don't understand, or whether your're willfully ignorant.
Please, turn the thread title from a threat to a promise.
Here is what I know. The checkboxes in the SAME dialog box don't act the same. This is not the "norm" if you will. As I showed you in the video, if I select "Simple Instrument Track" or "Track Folder" or "All Stereo Outputs" - and then choose to never ask me again... those settings will always work when I insert a softsynth.... just not the "Enable MIDI Output". If you can't see how that seems like a poor design, I don't know what to tell you. One would expect that if "Enable MIDI Output" is disabled and then you choose "never ask me again", NO synth you insert would have it's MIDI output enabled! It's like SUPER-simple. INFACT the checkbox works when you choose to ask every time! Seems kinda wonky. Oh and what about this.... is this a bug? http://forum.cakewalk.com/FindPost/3542635
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 22:20:36
(permalink)
SilverBlueMedallion
Anderton
SilverBlueMedallion
What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!
I can't actually believe after looking at my 4 steps you are still saying this is by design!! The checkmark actually DOES NOT DO ANYTHING!!! IT - IS - BROKEN!
How is that by design? What you are saying makes no sense now.... just anything to make this not look like a Sonar issue. Unbelievable.
What's unbelievable is that you blame me because you don't understand what a default is, what overriding a default is, what creates defaults, what a specification is, don't pursue links I provide that back up what I say, and then cross-post in other threads making idiotic accusations but never update the errors you make with correct information.
When I'm wrong, I have the decency to say so and give credit where credit is due because my concern is disseminating correct information. Apparently you have different priorities.
At this point, I honestly don't know if you truly don't understand, or whether your're willfully ignorant.
Please, turn the thread title from a threat to a promise.
Here is what I know.
The checkboxes in the SAME dialog box don't act the same. This is not the "norm" if you will. As I showed you in the video, if I select "Simple Instrument Track" or "Track Folder" or "All Stereo Outputs" - and then choose to never ask me again... those settings will always work when I insert a softsynth.... just not the "Enable MIDI Output".
If you can't see how that seems like a poor design, I don't know what to tell you. One would expect that if "Enable MIDI Output" is disabled and then you choose "never ask me again", NO synth you insert would have it's MIDI output enabled! It's like SUPER-simple. INFACT the checkbox works when you choose to ask every time! Seems kinda wonky. Okay, now I know for sure: You're willfully ignorant. I provided a recipe that proves what you say in bold is wrong and I provided a link to back up what I said. Oh and what about this.... is this a bug?
Now I also know for sure you don't read my responses, because I already replied to that - which supports the perception that you have no interest in a dialog. Your only response to anything is ultimately "It doesn't work the way I want it to work." I can't let this go by without comment... But I understand as a VP of Gibson, this thread could potentially sway new users away from a purchase, hence you have to make it look like there is no problem and its a user error. If potential SONAR owners see this thread, they'll be very impressed with our patience. Then they'll check out the other forum threads, and think "Yeah, this is a pretty helpful bunch of people...well, except for a couple." I have been a VP at Gibson for almost 4 years. I switched to SONAR almost 17 years ago. I have been using DAWs since the first Pro Tools. You will find no difference in what I've said about SONAR before and after I was with Gibson, except that I do bite my tongue a bit more to avoid seeming too enthusiastic about new features (besides, plenty of people here do it anyway), and I'm more critical of the program because now I actually owe something to the users beyond just helping out. I think most people here know that I advocate for the needs of Cakewalk to the users, and for the needs of the users to Cakewalk. That advocacy is not always positive, in either direction. I have worked with Ableton, Steinberg (for whom I designed a plug-in), Avid, Magix, Sony, Native Instruments, Acoustica, PreSonus, Waves, and others whose names escape me right now. As a result I am proficient in all their programs. I don't complain about learning curves being difficult, I respect and admire that all these companies have made extremely deep and innovative programs for tiny niche markets. Even when I was consulting to them, they knew upfront that SONAR was my DAW of choice. But they were mature enough to realize that it's my DAW of choice because it fits my particular needs best. All software has bugs, workflow issues, legacy items in need of cleanup, sections that haven't been updated in years, etc. However, I don't have a sense of entitlement about it. I am very grateful for the fact that this industry has produced tools costing us a few hundred dollars that were worth a half a million not that long ago (and which required constant maintenance, by the way). I am thankful we have all these incredible tools at our disposal, warts and all. Despite your opinion that making a lot of noise and demanding attention will get results, you are wrong. It's not because of people like you that this rate of improvement occurs; it's because of the people at these companies and the people who actually learn and use the programs. I urge you to download trial versions of other programs. It's insane that you're not doing that now - you said you were going to leave Cakewalk, so you better start learning some other programs in order to make good on your thread title.
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 22:36:33
(permalink)
too many quotes within quotes, so let me just hit a few short points: #1:Anderton: "Okay, now I know for sure: You're willfully ignorant. I provided a recipe that proves what you say in bold is wrong and I provided a link to back up what I said. " Adam: The "Enable MIDI Output" option ONLY works if you have it set to ASK. Can we establish that as fact? If you have to have it ask every time, perhaps the option should be removed from the default options window, no? It could get very confusing.... as "simple instrument track", "track folder" and other parameters DO work even if you set it to never prompt. So the "Enable MIDI out" in the SAME dialog prompt NOT working (if you don't set it to ask every time) seems like it shouldn't be there, since it doesn't really do anything. I actually feel like you are missing my point, we can't be this far off. I trust you are an intelligent person, and trust me, I am too, despite what you think lol. I seriously think we are having a serious miscommunication. #2: (regarding: http://forum.cakewalk.com/FindPost/3542635) Anderton: Now I also know for sure you don't read my responses, because I already replied to that - which supports the perception that you have no interest in a dialog. Your only response to anything is ultimately "It doesn't work the way I want it to work." Adam: I haven't seen you once speak to this. The screenshot itself is showing 2 different things lol. When you choose "None", it actually says "Omni" below (see the 2 red arrows?) how can that be Anderton? It is either "None" or "Omni". And it works like "Omni" (All MIDI as a source) instead of "None". How can you say that choosing "None" as an input and having it work as "Omni" is not a bug? You know that in a private message with a Cakewalk engineer, I pointed this out as a problem and it was actually acknowledged as a problem, right? Yet you are saying things to the effect this is design? And as far as anything about you being a VP or anything personal... let me say this right now. Before this "tiff", I thought you were a cool dude. I remember a song you wrote for your daughter, it had to do with being so far away or something... really good stuff I recall. You have always helped me in the past and I have always thanked you for it. In no way did I come start this thread to fight with you or any of the CW members. It was just plain truth. A friend of mine was over when I lost the patches for a song of his, and I just decided, you know what.... "I think i might need a new DAW".... the list of problems kept growing, so... that was my title. Nothing but TRUTH. I have been testing DAWs, have a few installed, but I would love to just stay with Sonar. It is what I know for a long time now. I started to get angry when I felt all you were doing was trying to soften my post. I lost a lot of time spent on this project (yes stupid me, I didn't save patches), because I trusted "freeze synth, whatever... lesson learned... but just remember, my frustrations come out of real problems I had here, then softening the thread really just made me feel like you were doing it so it seems like a user problem and not a Sonar problem.
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/08 22:49:01
(permalink)
Anderton, I made a new short video, maybe I am failing to type properly what I mean, but I am very clear and to the point here. Maybe this is what I should have posted to begin with. I hope you see the problem(s) here. https://www.youtube.com/watch?v=M9z1Lr2P5rQ
Thank you, Adam
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/09 11:33:31
(permalink)
SilverBlueMedallion
gustabo
SilverBlueMedallion
gustabo
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.
besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track
There is something called "Controller searchback before play starts".
Oh ok, cool. I have that turned off, it was suggested from another issue I am having with presets not saving correctly. Cool feature.
I saw that post, the dude was helping you troubleshoot why your soft synths were consistently not remembering their settings. He never told you to leave it off, he said try it.
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/09 11:36:26
(permalink)
gustabo
SilverBlueMedallion
gustabo
SilverBlueMedallion
gustabo
SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!
Wrong.
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.
besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track
There is something called "Controller searchback before play starts".
Oh ok, cool. I have that turned off, it was suggested from another issue I am having with presets not saving correctly. Cool feature.
I saw that post, the dude was helping you troubleshoot why your soft synths were consistently not remembering their settings.
He never told you to leave it off, he said try it.
of course, but I am saying that isn't the issue here, that's all. i appreciate the efforts. Right now, these are the 2 things that I don't get: https://www.youtube.com/watch?v=M9z1Lr2P5rQ
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/09 11:36:57
(permalink)
SilverBlueMedallion
gustabo
SilverBlueMedallion
hmmm actually according to this, it appears that function does not search back for any and all CC data, just
patch change, wheel, and pedal events. so i dont think thats it.
https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Playback.33.html
Your ignorance about what you want astounds me!
What do you think pedal and wheel events are? They're CC info.
Without testing it, you'll never know!
(It's Cakewalk's fault for not seeing you coming, they should have listed every single CC# )
either way, I shouldn't have to put any CC 7 data in there if CC from other softsynths wasn't erroneously making changes to other softsynths.
I've had that happen on projects before with just one soft synth loaded. It wasn't a Sonar issue, it was a soft synth and/or patch issue, it was resetting itself without any cc7 data in the midi track. To overcome that, I would right click on the midi fader and click on "disable control".
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/
|
AdamGrossmanLG
Max Output Level: -62 dBFS
- Total Posts : 1436
- Joined: 2014/07/13 03:40:34
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/01/09 11:41:34
(permalink)
gustabo
SilverBlueMedallion
gustabo
SilverBlueMedallion
hmmm actually according to this, it appears that function does not search back for any and all CC data, just
patch change, wheel, and pedal events. so i dont think thats it.
https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Playback.33.html
Your ignorance about what you want astounds me!
What do you think pedal and wheel events are? They're CC info.
Without testing it, you'll never know!
(It's Cakewalk's fault for not seeing you coming, they should have listed every single CC# )
either way, I shouldn't have to put any CC 7 data in there if CC from other softsynths wasn't erroneously making changes to other softsynths.
I've had that happen on projects before with just one soft synth loaded. It wasn't a Sonar issue, it was a soft synth and/or patch issue, it was resetting itself without any cc7 data in the midi track. To overcome that, I would right click on the midi fader and click on "disable control".
fair enough. I am not saying there can't be some wonky VST issues... but check my video. Tell me if my 2 points dont make sense. Thank you. https://www.youtube.com/watch?v=M9z1Lr2P5rQ
|
OldNick
Max Output Level: -68 dBFS
- Total Posts : 1149
- Joined: 2005/12/14 20:35:17
- Location: Perth...W Australia, the sunset home
- Status: offline
Re: Poor MIDI Implementation Is Going To Cause Me To Leave Cakewalk
2017/03/07 05:21:20
(permalink)
BobF
If you want the Baker's attention, submit feature requests and/or problem reports as required.
Check the OP's OP. They have done just that.
Nick Aced : Zither Mush (I no longer have ANY idea what this means) Ancient Seeker of Artifacts Platinum 23.4.0, Win 7 64 bit
|