AnsweredChanges driving me nuts!!!

Author
Puggles
Max Output Level: -90 dBFS
  • Total Posts : 28
  • Joined: 2016/04/03 00:49:25
  • Status: offline
2016/12/02 23:18:18 (permalink)

Changes driving me nuts!!!

What happened to the editing process!?  I recorded a guitar take that is kind of difficult for me, so I could copy and paste it and blend it seamlessly.  Normally, not a problem, but something changed in Sonar and I don't know what it is.
 
When I take one clip and try to line it up with another clip to blend them together, I see the crossfade (which if fine) but I also get these "cuts" that happen by themselves.  These "cuts" are in the space of the crossfade of both clips in question. (This doesn't matter which/how many clips there are, it applies to everything of this process).
 
If I don't blend/line up the two separate clips in the right spot (say, I have to click and drag a bit to the right) then there are --new cuts-- where the two clips came together, besides the two original clips that I'm trying to blend together.  It creates new "cuts" for some reason and it's really irritating.
 
I'll try to provide a screenshot.

 
 
See where the "recor" text is at?  Editing never used to be like that in previous Sonar's.  I swear Sonar becomes more and more difficult to use as the new releases come out,  Editing was the absolute best in X1.
 
Why can't I just click and move the clip to where it's needed without all the trivial garbage hurdles getting in my way of what I want to do!?  Sonar never used to be like this.
 
In the middle track, there are only supposed to be TWO clips that I should be able to click on, but this "issue" has created a THIRD.  Why?  It's just getting in my way, I don't need that, why was it created?
#1
mudgel
Max Output Level: 0 dBFS
  • Total Posts : 12010
  • Joined: 2004/08/13 00:56:05
  • Location: Linton Victoria (Near Ballarat)
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 01:19:32 (permalink)
5 years since Sonar X1 is quite a long time. They've been many changes. I'd suggest catching up by reading the manual or be prepared for lots more change catching you up. That's just the way it is with software.

Mike V. (MUDGEL)

STUDIO: Win 10 Pro x64, SPlat & CbB x64,
PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz.
Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2.
Monitors: Adam A7X, JBL 10” Sub.
Audio I/O & DSP Server: DIGIGRID IOS & IOX.
Screen: Raven MTi + 43" HD 4K TV Monitor.
Keyboard Controller: Native Instruments Komplete Kontrol S88.
#2
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 01:27:46 (permalink)
I agree with the OP,, Things keep changing and some days you just want to switch to a DAW that never changes so you can get some work done. The wave editing in Sonar is so bad I always tool copy into Wave lab. It hasn't changed how things work since I first used it in 2002. 
 

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#3
Deon_C
Max Output Level: -90 dBFS
  • Total Posts : 20
  • Joined: 2010/12/20 21:10:05
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 02:10:24 (permalink) ☄ Helpfulby RSMCGUITAR 2016/12/03 03:16:36
As far as i am aware, it does not create any new splits at all.
Its just a visual identifier of where the clips are overlaping, so you can see at a glance where one clip starts and the other ends. You can also manualy drag the crossfades in this region and alter the slope shape and position.

The only other reason there might be more than the clips intended is if there is something going on with the take lanes. If you expand that it might show you whats really going on.
#4
RSMCGUITAR
Max Output Level: -64 dBFS
  • Total Posts : 1318
  • Joined: 2014/12/27 02:33:15
  • Location: Toronto
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 03:17:38 (permalink)
The "cut" you are referring to is just the end of the clip on the left? Are you hearing something at that point?
#5
dwardzala
Max Output Level: -61 dBFS
  • Total Posts : 1470
  • Joined: 2008/05/26 19:18:33
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 06:29:23 (permalink)
And when you are happy with the edit, you can bounce to clip and it will make it all one clip.  The appearance of that new clip (which is really just a visual indicator of where the two clips are overlapping) will be gone.

Dave
Main Studio- Core i5 @2.67GHz, 16Gb Ram, (2) 500Gb HDs, (1) 360 Gb HD
MotU Ultralite AVB, Axiom 49 Midi Controller, Akai MPD18 Midi Controller
Win10 x64 Home
Sonar 2017.06 Platinum (and X3e, X2c, X1d)
 
Mobile Studio - Sager NP8677 (i7-6700HQ @2.67MHz, 16G Ram, 250G SSD, 1T HD)
M-Box Mini v. 2
Win 10 x64 Home
Sonar 2016.10 Platinum
 
Check out my original music:
https://soundcloud.com/d-wardzala/sets/d-wardzala-original-music
 
 
#6
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 15:11:46 (permalink) ☼ Best Answerby Puggles 2016/12/03 18:30:28
You'd need to show lanes to reveal exactly what's going on. But it does appear to me that you have more than just a simple crossfade between two clips in a single-lane track. Weird things can happen if you mix editing in lanes with the comping tool and editing in the parent track. Specifically, there is a bug that if you increase the overlap of a comping-generated crossfade in a lane, the original cross-fade segment will become a separate clip and the clip in the 'landing zone' of the dragged clip will get cropped out of the way rather than simply increasing the cross-fade area as you would expect (and as would happen if you did the same edit in the parent track with lanes not showing).
 
 

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#7
Anderton
Max Output Level: 0 dBFS
  • Total Posts : 14070
  • Joined: 2003/11/06 14:02:03
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 18:26:30 (permalink)
Puggles
Why can't I just click and move the clip to where it's needed without all the trivial garbage hurdles getting in my way of what I want to do!?  Sonar never used to be like this.



I think Brundlefly has the answer, it relates to the Comping changes that were introduced in X3.

The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
#8
Puggles
Max Output Level: -90 dBFS
  • Total Posts : 28
  • Joined: 2016/04/03 00:49:25
  • Status: offline
Re: Changes driving me nuts!!! 2016/12/03 18:31:45 (permalink)
brundlefly
You'd need to show lanes to reveal exactly what's going on. But it does appear to me that you have more than just a simple crossfade between two clips in a single-lane track. Weird things can happen if you mix editing in lanes with the comping tool and editing in the parent track. Specifically, there is a bug that if you increase the overlap of a comping-generated crossfade in a lane, the original cross-fade segment will become a separate clip and the clip in the 'landing zone' of the dragged clip will get cropped out of the way rather than simply increasing the cross-fade area as you would expect (and as would happen if you did the same edit in the parent track with lanes not showing).
 
 


Yes, I believe this sounds the most correct.  I really wish there was an option to get rid of this event happening.
I should be able to just click and drag and have the crossfades shrink or expand from there based on where I move the clips in question.
 
Also, when I do edit two clips together I have trouble seeing "behind" the overlapping clips.  Like if I wanted to scoot/trim the beginnings or the end of the clips to get rid of anything before or after the actual music in the clip.  I thought x-ray was responsible for this, but adjusting it doesn't seem to change anything.
#9
Jump to:
© 2025 APG vNext Commercial Version 5.1