Why do I have to Apply Trimming twice?

Author
jkoseattle
Max Output Level: -79 dBFS
  • Total Posts : 556
  • Joined: 2004/10/21 16:29:48
  • Status: offline
2017/11/15 17:08:22 (permalink)

Why do I have to Apply Trimming twice?

I have a long clip with a big blank section in the middle. I decide I want to split this into two clips. (They are a single clip because it was recorded in a single take, but it's really two separate things.) So I Alt-Click in the middle to split it into two clips. When I do this, each of these clips now has a tiny corner chopped out of it which I don't know what it's for. Then I need to remove the blank space in each clip, so I right click on them and select Apply Trimming. The first time I do this, what happens is that little chopped out corner disappears, but no actual trimming has taken place. Then I have to Apply Trimming a second time to get the actual blank space to disappear. What's going on here?

Sonar Version: Platinum  
Audio Interface: M-Audio Delta
Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
Soft Synths: EastWest PLAY Symphonic Orchestra
MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
Check out my work here
#1

4 Replies Related Threads

    chuckebaby
    Max Output Level: 0 dBFS
    • Total Posts : 13146
    • Joined: 2011/01/04 14:55:28
    • Status: offline
    Re: Why do I have to Apply Trimming twice? 2017/11/15 17:22:56 (permalink)
    Apply trimming is for removing slip edit data.
    All you need to do is:
    1- Delete the middle portion
    2- Select both clips
    3- Apply trimming.
     
    This removes slip edit data. I just tried it here and it works as expected. That's what apply trimming does, it removes Slip edit data. It doesn't trim the edge of the clip unless you tell it where you want it trimmed.
     
     

    Windows 8.1 X64 Sonar Platinum x64
    Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
    Focusrite Saffire 18I8 - Mackie Control
       
    #2
    jkoseattle
    Max Output Level: -79 dBFS
    • Total Posts : 556
    • Joined: 2004/10/21 16:29:48
    • Status: offline
    Re: Why do I have to Apply Trimming twice? 2017/11/15 23:47:01 (permalink)
    I see. I never use slip editing.
     
    Is there a way to cause Sonar to automatically combine, split and trim clips based on the contents? I do most of my work in PRV, but then when I need to look at the project in Track View, I've got a hundred tiny clips overlapping each other or else I'll have long clips with huge amounts of silence in them, or both. Basically, the clip boundaries bear no resemblance to the actual music in the project I realize I could open take lanes to help with the overlapping clips, but then I lose a lot of vertical space. And many of those take lane clips could still have empty space in them. Truth is, I don't care much about clips at all. But if they better represented the actual note info, they could be useful when I want to see which instruments are playing when, which can be a lot more difficult in PRV with all the overlapping note info.
     
    I'd like to be able to select a region and say "If there's a break of x bars or more, split into separate clips, otherwise combine into a single clip and trim everything." Then my Track View is going to be nice and neat and will accurately reflect what I actually have in the piece. 
     
    I'm dating myself here, but in very early versions of Cakewalk, like early-mid 90's, before there even was such a thing as clips, it would simply show a big dot if there was any midi info in a given bar on a given track. Of course, you couldn't drag these dots around or operate on them as a group they way you can with clips, so they were much more limited, but what they DID do was what I'm talking about here. You could easily and accurately see where you did and did not have events in every track. 
     
    Switching to Notes instead of Clips in Track View isn't much better, because there's no intelligence behind vertical positioning of events, and I have to resort of Fit Content on every track one at a time, and if I'm using keyswitches, that content gets mercilessly squished to a few teeny pixels anyway. And those tiny lines are the only feedback I have as to whether there's midi datea in there, often really hard to see.
     
    Anyone know of any way I can solve this problem without my current workaround of constantly bouncing and trimming clips for no other purpose than so that I can see what's really going on?

    Sonar Version: Platinum  
    Audio Interface: M-Audio Delta
    Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
    Soft Synths: EastWest PLAY Symphonic Orchestra
    MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
    Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
    Check out my work here
    #3
    ...wicked
    Max Output Level: -1.5 dBFS
    • Total Posts : 7360
    • Joined: 2003/12/18 01:00:56
    • Location: Seattle
    • Status: offline
    Re: Why do I have to Apply Trimming twice? 2017/11/16 00:46:56 (permalink)
    In my experience, Apply Trimming the first times removes the slip data, but will still leave "Dead air". Apply Trimming a second time removes the dead air.
     
    I have it key-bound so tapping it twice isn't as tedious.

    ===========
    The Fog People
    ===========

    Intel i7-4790 
    16GB RAM
    ASUS Z97 
    Roland OctaCapture
    Win10/64   

    SONAR Platinum 64-bit    
    billions VSTs, some of which work    
    #4
    chuckebaby
    Max Output Level: 0 dBFS
    • Total Posts : 13146
    • Joined: 2011/01/04 14:55:28
    • Status: offline
    Re: Why do I have to Apply Trimming twice? 2017/11/16 11:49:14 (permalink)
    I would personally use the "Bounce to clips function".
    Its almost the same thing as apply trimming but it can also heal clips. The down fall of Bounce to clips is you can only do one clip at a time if you want to create separate clips on the same track. If you select multiple clips on the same track and use Bounce to clips, they(their gaps) will be healed.
     
    I would like to introduce an interesting perceptive though. Before slicing all your midi clips up in to pieces,
    I would highly suggest making a back up of your midi clips (in one whole clip).
    If something were to ever happen to your Sonar project (weather it become corrupt, wont open, keeps crashing).
    You have no way to recover those midi files/clips. In other words, all that work you did...its gone.
    If you save 20 little clips that go on one track, its a nightmare to re assemble them on one track at a later date.
    Its much easier to have one whole track to import to a new project.

    Windows 8.1 X64 Sonar Platinum x64
    Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
    Focusrite Saffire 18I8 - Mackie Control
       
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1