I still want a new audio engine that runs tightly and is always sample accurate. If that isn't fixed, no amount of icing will ever make up for that.

UnderTow

brundlefly

UnderTow


I still want a new audio engine that runs tightly and is always sample accurate. If that isn't fixed, no amount of icing will ever make up for that.

UnderTow

Is there an existing thread on this issue so we can avoid rehashing everything here?. I'm not aware of any confirmed problem with SONAR's audio engine in this regard.
 
EDIT: Unless you're referring to all the looping-related issues...? 

Yes the looping issues and slight gaps when performing certain edit actions. The general lack of tightness of the audio engine (compared to competing products). I find the newfangled matrix view utterly useless as things don't run perfectly sync. (On any system I have tested it on. Not just one box).

Anyway, I am not expecting a debate on this. The people that have issues with it know. The peoples that don't have issues with this (for whatever reason), of course will not be concerned.  It is on my wish list and fully accept it might not be on other people's wish list. :)

UnderTow

beejeh


Ok, yes I agree about the 3 db increase, but ONLY on the bus called master, i'd expect the other buses to remain in stereo at their normal levels i.e. Sonar should only sum the left and right channels of the bus called master if I change it's interleave to mono. If I set the main mix on my hardware mixer to mono, it does not set all my subgroups to mono so why should Sonar behave the way it does ?

Sonar is working correctly for me when I change my Master Bus' interleave to mono. 
 
Do you have your Busses/Tracks grouped?
 
 

Jose7822

beejeh


Ok, yes I agree about the 3 db increase, but ONLY on the bus called master, i'd expect the other buses to remain in stereo at their normal levels i.e. Sonar should only sum the left and right channels of the bus called master if I change it's interleave to mono. If I set the main mix on my hardware mixer to mono, it does not set all my subgroups to mono so why should Sonar behave the way it does ?

Sonar is working correctly for me when I change my Master Bus' interleave to mono. 
 
Do you have your Busses/Tracks grouped?

Jose, I checked this yesterday, and got the same result as beejeh: Setting the Master to Mono interleave caused all buses and tracks to change to mono output (both in the meters, and audibly with tracks going direct to different outputs - not through the Master), though the interleave buttons continue to show they are stereo.

brundlefly

MIDI Source "NONE" that is actually "NONE" - this has been just plain stupid from way back when. If I want OMNI I will select OMNI - NONE should mean NONE! This has NEVER made any sense to me on any level.

This is a function of having "Always Echo Current MIDI Track" enabled in Global Options. SONAR can't Always Echo, if the input is NONE, so it defaults back to OMNI. Turn off Always Echo, and you will be able to set MIDI inputs to NONE.

Okay - thanks for clearing that up.
But I still say that is combining 2 different issues/functions and it goes against what I would consider common logic, at least in a practical/functional way in day-to-day use.

I'd STILL like NONE to be NONE *AND* to be able to "Always Echo Current MIDI Track".
I'm enough of an adult to know that if I have a track set to NONE that I won't be routing any MIDI.
I use a main controller keyboard and lots of modules, so the current method requires extra reaching across the room to click on things that seriously interrupts my workflow and can make adding a new track while a hardware sequencer is running actually 'break' things and require me to stop, rewind, click a few times, restart... I've been putting up with it for years, but it's truly annoying.

But thanks for explaining the unexplainable/previously unexplained.
I swear I've looked thorough the documentation dozens of times and just chalked it up to a bug or peculiarity of my specific system [as I had with the MIDI crash bug that used to plague me and turned out to be a rare bug].


I just thought of another annoyance that may be another 'feature' that I just don't grok:
The metronome keeps switching its audio outputs on me.
It will literally change itself without me doing anything other than arming a track for recording.
I can check the metronome settings, arm a track, check them again and it's changed to a different audio output.
I suspect this is another bug that is not too common [I have an E-MU 1820 PCI interface].
If this is a 'feature' then I don't get it.

Cakewalk SEEMS To take an interest in these threads [though implementing all requested features would take years] it can only help in the long run to see what people are looking for as a product evolves.

I can check the metronome settings, arm a track, check them again and it's changed to a different audio output. I suspect this is another bug that is not too common [I have an E-MU 1820 PCI interface].

That's interesting. I have an 1820m, and used to experience this. The Metronome output would switch from the Metronome bus to going direct to Main Outs. But IIRC, it only happened when I would temporarily change MIDI PPQ on the Clock tab so I could scan the event list and see what the timing looked like (a little easier to see at 120 than at 960). I haven't had that happen for a long time, though, and can't reproduce it now. Maybe it was fixed somewhere along the line - are you running 8.5.3 x64?

o.k. i thought of one thing besides the giant master meter:

on the midi piano roll, it has awesome timing control already.
you just type the beat and the number of ppq's.

but the pitch is very clunky.  it only gives you the half-steps.

it would be awesome to do +/- 100 cents on any note in that right-click panel

that would be phenomenal.

but i'm still sticking to my original story that the predominant theme
should be to stabilize any known functioning issues, and not just
add more stuff before the old stuff gets fully fixed.

i think the midi improvement i suggested would be a great help
without likely introducing more functioning problems.

rotaholic


Not sure if this has been mentioned but being able to pan/narrow stereo tracks.

That's what Channel Tools is for, though I would love to have something similar to what Vienna Ensemble Pro has for panning.
 
It would ROCK!  But Channel Tools does the same and more.
 
 
HTH

Use "Fit to Improvisation" under the Process menu.  It does something similar to what you describe.

HTH

Jose7822

brundlefly

Jose7822

beejeh


Ok, yes I agree about the 3 db increase, but ONLY on the bus called master, i'd expect the other buses to remain in stereo at their normal levels i.e. Sonar should only sum the left and right channels of the bus called master if I change it's interleave to mono. If I set the main mix on my hardware mixer to mono, it does not set all my subgroups to mono so why should Sonar behave the way it does ?

Sonar is working correctly for me when I change my Master Bus' interleave to mono. 

Do you have your Busses/Tracks grouped?

Jose, I checked this yesterday, and got the same result as beejeh: Setting the Master to Mono interleave caused all buses and tracks to change to mono output (both in the meters, and audibly with tracks going direct to different outputs - not through the Master), though the interleave buttons continue to show they are stereo.

 
OK, there it is. 
 
I had to open a project with stereo tracks, but now I see the problem.
 
Reported!
 
 

From the Read Me

Enabling Mono on a Bus/Main Will Affect Upstream Meters

If you make a bus or main out mono by toggling its Mono/Stereo switch, any “upstream” meters—that is, meters on any tracks or buses that are assigned to the mono bus/main out--from the bus/main out will also display as mono.
 
Note: this only affects the meter display, not any audio that is bounced or exported.
 
HTH

Tom

Saintom


From the Read Me

Enabling Mono on a Bus/Main Will Affect Upstream Meters

If you make a bus or main out mono by toggling its Mono/Stereo switch, any “upstream” meters—that is, meters on any tracks or buses that are assigned to the mono bus/main out--from the bus/main out will also display as mono.

Note: this only affects the meter display, not any audio that is bounced or exported.

HTH

Tom

Thanks Tom!
 
This is why I couldn't detect the "problem" at first, since the audio was being process correctly when in Mono, until I was pointed to look at the meters.  Still, I considered it a bug since it didn't make sense for the "upstream" meters to display in mono.  But now I see this is the intended behaviour, for some reason.  Do you know if this behavior can be changed?
 
Thanks again.
 
 

Jose7822

Saintom


From the Read Me

Enabling Mono on a Bus/Main Will Affect Upstream Meters

If you make a bus or main out mono by toggling its Mono/Stereo switch, any “upstream” meters—that is, meters on any tracks or buses that are assigned to the mono bus/main out--from the bus/main out will also display as mono.

Note: this only affects the meter display, not any audio that is bounced or exported.

HTH

Tom

Thanks Tom!
 
This is why I couldn't detect the "problem" at first, since the audio was being process correctly when in Mono, until I was pointed to look at the meters.  Still, I considered it a bug since it didn't make sense for the "upstream" meters to display in mono.  But now I see this is the intended behaviour, for some reason.  Do you know if this behavior can be changed?
 
Thanks again.

I was just searching for something else, and stumbled on this old thread in which I never saw the replies.


I just wanted to point out that when I tested this, I found (and mentioned) that even tracks not routed to the Mono bus were metering as mono. I also reported that the output of these other tracks/buses was audibly mono, contrary to the claim in the readme that it's just a metering phenomenon. I'll have to double-check this when I get a chance.