mettelus

No transport looping for this. The 2-bar section mentioned in the OP can be dragged from the track into the Matrix View and set to loop, synced to the transport. That "track" will then be driven by the Matrix View, while the rest of the project will still be driven by the transport. The Matrix View is a looper that outputs to a project track.

I am not familiar with Boost 11, but as mentioned above, a compressor can be used for the same functionality (technically, some define a "limiter" as a compressor with greater than a 10:1 compression ratio). A high threshold (-1 to 0 so you do not see it functioning as a compressor (no active gain reduction)) and steep ratio (10:1 or better) should suffice. When tracks digitally clip, small red boxes will appear at the top of the VU meter for that track (and on busses as well); very similar to the red boxes in this picture at the top of the right track/buss. They need to be reset manually after a clipping/feedback event (and will be reset by default when a project opens). Do you see which track the clipping is occuring on? If you have a VST on a buss, the tracks feeding it may in fact not be clipping, but the buss itself can be, so check both tracks and busses (may be easiest in the Console View - ALT-2). Shift-D is the keyboard shortcut to maximize the multidock so you can easily see the full view... D toggles the multidock viewable/non-viewable. This should help you narrow it down to which VSTs are in play causing it.

I would recommend trying the Matrix View. Unlike a groove clip, you do not need to specify length of it (where the last groove clip will be the end), but merely start/stop it and it will continue to loop cells indefinitely for you. You can leave it looping till the cows come home, and for this reason is also a good tool for jamming with. Here is an older tutorial video for the Matrix View that is still relevant (a few controls have changed).

Safety point first... throw a limiter on your master buss with a high threshold and the highest ratio it has (brickwall if you have one). This is not to process audio musically (i.e., it should not be processing your music), but to catch audio spikes/feedback and protect your hearing and equipment. It could be a VST, and if the feedback is long enough to try this, hit "E" (Global FX bypass) and see if that kills the feedback immediately. I am curious how it is resolving itself though; possibly a response from CbB telling it that it is out of bounds (*if* it is a VST).

Larry covered pretty much everything already. I have a 1st gen Saffire, which also uses MixControl and a couple other thoughts came to mind. First, a couple more references. Since I tend to misplace hard-copy manuals, the pdf for the 6i6 is here. The video I usually give to folks is from Graham at TheRecordingRevolution.com and is here (a little shorter, and mix focused). In MixControl, a couple additional things: Inst vs. Line (pre-amp inputs 1&2), Hi Gain vs. Lo Gain (Line inputs 3&4) - Using Inputs 3&4 on the back of the Scarlett (used for Line inputs), be sure to set the input levels appropriately in the MixControl Router section. For the cassette deck, you will probably want these set to "Hi Gain" which is the default. I am not familiar with the SC-8850, and that may be "Lo Gain." If using the pre-amps (Inputs 1&2 on the front), be sure to set the Router inputs to "Line" if using either of these, and "Inst" for the mic. As Larry mentioned, be sure all gains are set to zero on all equipment before making/breaking connections or powering on equipment. In MixControl, you can also stereo link the even/odd inputs (the interleave/infinity symbol below the faders in MixControl). When working with Inputs 3/4 from a unit, this will give a stereo output. They are hard-panned left and right by default respectively. On some older cassettes, the right track can be lower volume, so leaving them split and recording them as mono channels into CbB, leveling them, then bouncing to a stereo track may be better. You may also find it easier to record the cassette into CbB first (as a separate step to recording instruments/vocals), then using the faders inside CbB to control playback levels via the "DAW output" sent to the Scarlett. On my unit, actually opening MixControl makes routing into a DAW smoother (even if MixControl is not "actively" used). I typically power on my unit, open MixControl, verify it "locks" on the MixControl GUI, then open a DAW. Again, I have not used the Scarlett, but the Input settings (#1 above) are in the Router section of my MixControl at the bottom.

Technically I am also first gen (my Saffire had no second gen), and never had an issue with MixControl routing. Granted, it does take a bit of a walkthrough to first learn (some videos are good on this), but most routings are static (DAW, inputs, outputs, etc.). To that end, my advice would be to take advantage of the "Save as" function. You can save only one routing setup into the hardware itself, but can save any number to the connected PC. 95% of the time I use *my* default routing, but for multiple outs, loopback, etc. I have those stored on the PC, so switching is a simple matter of loading the one desired. Also... those Mix tabs at the top are for up to 16 routing setups, which may be sufficient unto itself.

This statement summarizes the crux of many issues. "Unfinished features" comprise a much bigger list, and historically the old forum (especially under Gibson) became inundated with work arounds (e.g., "You can achieve that via this convoluted method, so it is already there!") rather than acknowledgement (e.g., "Oh, good point, we can definitely do that better!") and following through on it. This constantly came across as "I have given you a work around, so will forget you ever said anything." That mindset and its implied statement do not coincide with sales, usage, or promotion of a product; and Gibson epitomized this. The former "Feature Request" forum was filled with a plethora of good and detailed ideas, but was locked, and subsequently slid out of public view. I used to review them off and on and think of "what could have been." It amounted to a lot of heart-felt time and effort by users wasted. The "200+ hours" from the article in the OP strikes home for me as well. Granted, he tried to delve into everything he could, but new users are often beset with a similar time investment. Practical guides for new users is important, especially where common tasks are readily exposed with underlying functionality polished. [Side comment, potentially related] One thing I find concerning is that this new forum seems to be populated predominantly with members from the old. I *assume* this is open to everyone (perhaps in error), so find it odd that more new members are not present.