Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out /collections Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand These are the shifts in mindset that unlocked my career.Ĭurious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers □ The Senior Engineer Mindset ebook can help □ /senior-mindset. Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. Real insights into the career and skills of a modern software engineer. Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best. Get promoted, earn a bigger salary, work for top companies Learn more But with today's broadband speeds, GIFs have become perfectly viable.Īlthough you might still want to use Photoshop to convert real videos into good GIFs. Sure, it sucks that video on the web and in presentation is still not a very well solved problem and takes more fumbling around than necessary. No worrying about sound or converting the recorded video into GIF form. ![]() No fumbling around with selecting regions and hidden control windows. The app will automatically save an animated GIF file when you're done recording. You open the app, put it over the content you want to record, click a button and away you go. My favourite part of using LICEcap is that it's simple. It also came in handy for the talk I gave about d3.js a few weeks ago where I wanted to show people animated graphs, but didn't want to keep jumping in and out of the presentation and fumbling around with a thousand windows. If you want to simply embed some moving parts into your blogpost - GIF.įor example, I used LICEcap to make those gifs of Super Mario playing with himself for Week 2 of the 52papers challenge. It won't help you create the next Railscasts or Coursera, but if you want to make something move in your slides when giving a talk, you need a GIF. The best example of doing one thing and doing it well. Kudos to everyone who makes educational screencasts to help people learn programming.īut LICEcap really is the best screen recorder I've ever used. Typing under pressure from a screen recorder is really hard. Reaper.LICEcap - best screen capture tool I've ever used Reaper.Undo_EndBlock2(0, "Resize MIDI Item(s)", -1) Reaper.MarkTrackItemsDirty(reaper.GetMediaItem_Track(item), item) Reaper.MIDI_SetItemExtents(item, reaper.TimeMap2_timeToQN(0, startOfMeasure), reaper.TimeMap2_timeToQN(0, endOfMeasure)) Local endOfMeasure = reaper.TimeMap2_beatsToTime(0, endCml, endMeasures) Local startOfMeasure = reaper.TimeMap2_beatsToTime(0, 0, startMeasures) Local endBeats, endMeasures, endCml = reaper.TimeMap2_timeToBeats(0, pos + len) Local _, startMeasures = reaper.TimeMap2_timeToBeats(0, pos) Local len = reaper.GetMediaItemInfo_Value(item, "D_LENGTH") Local pos = reaper.GetMediaItemInfo_Value(item, "D_POSITION") Local item = reaper.GetSelectedMediaItem(0, i) ![]() Local selectedItems = reaper.CountSelectedMediaItems(0) I would want the item to be trimmed to the end of bar 3 rather than expanded to the end of bar 4.Ĭode: - sockmonkey72_a Same with the end You finish playing before the end of bar 3 but continue recording over the beginning of bar 4. For me, the beginning of the item should be "trimmed" to the start of bar 3, not expanded to the beginning of bar 2. Say you start recording before bar 3 but you don't actually play a note till the 2nd beat of bar 3. If this isn't useful to some, then maybe an option?Įdit: Having thought about my discourse with Vitalker below, I now think "trim" is also relevant for both start and end of the item. It would be a great timesaver when wanting to loop newly recorded midi items, IMHO, as I spend a lot of my time, post recording, triggering an action to expand the item. This currently happens with retrospective record so I think it would be consistent for it to happen in normal record. ![]() As the title suggests, I think it would be helpful if, after recording midi, the media item start and end were expanded (trimmed?) to the nearest bar on the grid.
0 Comments
Leave a Reply. |