TheOrginalGrumpster
Max Output Level: -90 dBFS
- Total Posts : 46
- Joined: 2010/10/27 11:42:31
- Location: My Blue Heaven
- Status: offline
Clip Properties problem
Long time Sonar user trying to get to grips with X1. In Sonar 8.5, I could set a midi clips start time by right clicking on the clip, selecting Properties and setting the start time, simple. In X1, I found the Clip Properties on the Track Inspector, and tried to set the start time there but the start time leaps a huge amount every time I try to change it. Most likely I have missed something simple somewhere, I read the help file and I am following the procedure listed, but still these apparently random jumps are happening still. So can anyone tell me how to set\change a Clip Start Time ? Thanks for viewing my post, and for any assistance you can offer.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Clip Properties problem
2011/01/11 02:04:22
(permalink)
Seems to be working okay here. I select a MIDI clip that's at 1:01:000, and enter "3" for the Atart time in Clip Properties, and it moves to 3:01:000. I enter 3:02, and it moves to the next quarter. I change the tick value to 480, and it moves another eighth. Then I zoom in on the start time, and use the "spinners" to change the value by ticks, and the clip moves by ticks as it should. Sorry, but I can't think what you might be doing wrong. Hope there's something in what I wrote that helps. EDIT: Afterthought: Maybe you've got the time format set to SMPTE, and what you think should be measures are hours?
post edited by brundlefly - 2011/01/11 02:05:48
|
TheOrginalGrumpster
Max Output Level: -90 dBFS
- Total Posts : 46
- Joined: 2010/10/27 11:42:31
- Location: My Blue Heaven
- Status: offline
Re:Clip Properties problem
2011/01/11 09:15:27
(permalink)
Brundlefly, Thanks for the reply. The clip I was trying to move had been part of a larger clip split into smaller sections. It turns out if the split clips are Bounced to Clips the Clip Start Time works fine, but if it is not bounced to clip, it seems to treat the clip as if it was the original length, and moves the start accordingly. You can see it here: http://www.youtube.com/watch?v=F9Q7n-nKoxE Can anyone confirm this the default behaviour in X1 ?
|
Bristol_Jonesey
Max Output Level: 0 dBFS
- Total Posts : 16775
- Joined: 2007/10/08 15:41:17
- Location: Bristol, UK
- Status: offline
Re:Clip Properties problem
2011/01/11 10:03:43
(permalink)
I think that's because when you initially split a clip, or slip-edit the start/ends, all you've done is actually hide the original data - it's still there but you can't see it, as that particular type of edit is non-destructive. Bouncing to clip is by its very nature destructive, so afterwards each clip is, if you like, its own entity. Someone correct me if I'm wrong pelase.
CbB, Platinum, 64 bit throughoutCustom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Clip Properties problem
2011/01/11 11:12:34
(permalink)
Bristol_Jonesey I think that's because when you initially split a clip, or slip-edit the start/ends, all you've done is actually hide the original data - it's still there but you can't see it, as that particular type of edit is non-destructive. Bouncing to clip is by its very nature destructive, so afterwards each clip is, if you like, its own entity. Someone correct me if I'm wrong pelase. You're right that splitting and slip editing can be non-destructive (if you have that option enabled for MIDI clips, which I tend not to), and bouncing is destructive, but non-destructively edited clip boundaries should still follow snap rules. However, in X1, it seems that non-destructively edited clip boundaries always Move By, even when snap is set to Move To. I need to investigate this some more to confirm this, but that's my initial take. In the mean time, I recommend just copying the track, and using destructive editing on it. Even without this new (?) bug, I've always found non-destructive MIDI editing to produce strange and not-so-wonderful results in some cases.
post edited by brundlefly - 2011/01/11 12:16:27
|
TheOrginalGrumpster
Max Output Level: -90 dBFS
- Total Posts : 46
- Joined: 2010/10/27 11:42:31
- Location: My Blue Heaven
- Status: offline
Re:Clip Properties problem
2011/01/11 12:01:25
(permalink)
In the mean time, I recommend just copying the track, and using destructive editing on it. Yup, thats what i have been doing since noticing this though I don't think the behaviour is the same in S8, thats why it initially threw me. Thanks for taking the time to help out guys.
post edited by TheOrginalGrumpster - 2011/01/11 16:39:49
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:Clip Properties problem
2011/01/11 12:23:08
(permalink)
I fooled around with this some more, and get very inconsistent results. Sometimes it works great, sometimes it does Move By, instead of Move To, and sometimes it starts snapping the clip end to the grid or to the boundary of another clip, even though snap to Landmarks is disabled. I guess this is all part of the assorted issues that have been reported with Snap to Grid that we can only hope will be cleared up in X1b.
|