Hi Allen - That will depend on the drum kit (software instrument) you use. Most of the GB kits use the General MIDI drum map, so if you play A#1 (open hihat) followed by G#1 (hihat foot), the G#1 key will close the open hihat (like a drummer stepping on the hihat pedal). The F#1 key (closed hihat) will also close the A#1 open hihat. Some drum kits have more elaborate hihat mapping -- for example, some of the Drummer kits use the modwheel to open & close the hihats -- but the F#1/G#1/A#1 layout is the most common implementation.

Recording will always begin at the bar you position the cursor at. If a count-in is enabled it will back up and count you in for 1 or 2 bars before recording begins, just to give you a chance to hear what went before and get ready to come in on time and at speed. But the recording will not begin until the 1 or 2 bar count-in is done and the playhead reaches the bar you positioned it at before you hit record.

Part of the confusion here is that you're using some terminology loosely/incorrectly. - In 4/4 there is one whole note in each bar - In 4/4 there are 4 quarter-notes in each bar (4 quarter notes are the same length as 1 whole note) - Each quarter-note consists of 4 16th-notes (4 16th-notes are the same length as 1 quarter-note) - In 4/4 there are 16 16th-notes in each bar - The display of gridlines changes depends on how far you're zoomed in -- for example if you're zoomed out it may show only quarter-note gridlines but if you zoom in more it may show 16th-notes gridlines - The term "squares" has no meaning in musical terminology and is confusing In 4/4 the 3rd beat of any bar is the 3rd quarter-note in that bar. Again, this course should be helpful with the musical terminology and bar/beat designations: https://www.macprovideo.com/course/music-theory-109-music-theory-for-daw-musicians?afid=E470KLQ7r9

Yes, the Metronome will click one click for each quarter-note -- the downbeat (the 1) of each bar will have a higher-pitched click than the others. The 1234 button enables a countoff. A countoff is where GB will click for a bar (or two) when you press record before recording begins (the transport strats moving), to give the player a chance to get ready to come in on time and at the correct tempo.

Quantization works by moving notes to the nearest musical gridlines. The metronome clicks on the musical [quarter-note] gridlines, that's how you know if you're paying more or less in time with the musical grid. If you don't play along with the metronome, then how would you be able to play close enough in time to the musical grid for Quantization to work properly? Keep in mind that if you pencil in notes manually one at a time instead of playing them in in real-time then it doesn't matter -- the metronome is only needed for real-time playing/recording. https://www.macprovideo.com/course/music-theory-109-music-theory-for-daw-musicians?afid=E470KLQ7r9

Apple's Motion is a powerful application for making animations and visual effects for video and film. Iain Anderson's course "Motion: The Basics" covers the basics, and now his latest course "Motion: Creating Titles and 3D Effects" digs deeper into the creative possibilities of Motion. The course starts out by revealing how to create and animate titles and get exactly the desired results, how to save time with preset text behaviors, how to publish work for quick use in Final Cut Pro, and how to make titles compatible with multiple aspect ratios. Next up is a deep dive into the advanced world of creating 3D text, exploring different material, and learning to create custom text. Lighting, reflections, shadows and working with 3D cameras are all covered in depth. The course wraps up with an exploration of animating and replicating 3D objects. So for those who are ready to up their game, this new course is just the ticket to take Motion to the next level.

I would guess it depends on the video player -- most video players have a fullscreen button of some kind that will expand the video to use the entire screen. Beyond that, I can't be specific, I'm not an Android user..

It does sound like a corrupted item in the Library, or a corrupted database, could be the cause. A search turned up a couple of suggestions, and though I'm not a FCPX user myself these sound potentially helpful.. - The method you mentioned -- removing & adding files back in one by one -- might be worth trying. I'm an audio guy, and that's how we troubleshoot for a bad/incompatible plug-in. - Apparently there's a database file in the package called Flexolibrary -- some people suggested removing this file (I guess I'd zip it and back it up elsewhere first). Supposedly FCPX will rebuild it the next time. This sounds like the common troubleshooting strategy of blowing out/resetting a possibly corrupted Preference file, so it might be worth a try. I guess it's possible that a solution might require both of these methods..

Buffer Size for a DAW is usually found in the Preferences. Since this is a Cubase thread, you'd want to check Cubase's audio preferences for the current buffer setting, usually expressed in samples. The common options are 32, 64, 128, 256, 512, and 1024. As above, I'd suggest starting with 128 -- if your computer is modern/powerful you could try 64 or even 32. If your computer is older/weaker try 256 or 512. But keep in mind that a buffer setting higher than 256 may result in uncomfortable latency for live players trying to record audio or virtual instruments while monitoring the DAW audio in headphones. If that turns out to be the case, you can set a lower buffer for recording, and a higher one for mixing.

Even for a programmer who can read/interpret a crash report, it's not always possible to come up with a definitive answer without further details & additional troubleshooting. I'm most definitely not a programmer, but I would tend to guess that if you have no other indications of problems on your system, then it's less likely to be bad RAM -- a RAM issue would assumedly show up elsewhere as well, unless nothing else you do addresses that much RAM -- I'd think it'd be more likely to be an issue with FCP, Compressor, or the particular file. Has this kind of issue come up when you do the same thing with different FCP projects, or is it specific to this particular project? That's where I'd start troubleshooting (assuming you'e already done the usual full shutdown/restart, etc)..