> The video can be seen here: https://youtu.be/S9SQcUxMJ8I Aha—I was picturing something completely different! :-) It looks like what you need to do is perform color corrections for the different hues each time the color wheel changes, and then automate those (gradual) color corrections. This is beyond my limited FCP experience (I'm really an audio guy) but it seems like that should be doable with Keyframing, as per the video below. Obviously the color corrections you'd have to make would be much more drastic that what he does in the example, but it seems like that approach could get the job done. Perhaps if Iain (the course author) notices this thread he might be able to weigh in with some more specific advice..

On the heels of his comprehensive Massive X course, Rishabh Rajan has now added this advanced Massive X course "Designing Massive Sounds", a deep dive into sound design techniques in Native Instruments' popular softsynth. Rishabh creates a wide variety of sounds, from electronic drums and basses to rich pads and leads, and even sound effects—the course is a must-have for aspiring Massive X programmers..

Seeing as it's strictly software I would assume downloadable, as with all their installers..

To bus two or more instrument channel strips in a patch together for group volume control you can create a new (stereo) Aux in the mixer panel, set its input to the next unused bus, and set the outputs of the instrument channels to that bus. (If there's a reverb or other send&return effect included in the patch and you want to control its level along with the level of the instruments, don't forget to route its output to the same Aux as well). If you also want to have a screen control (like a volume pedal) control that Aux level, (create one and) select it in the Workspace and assign it (in the Screen Control Inspector at the bottom) to that Aux > Volume. You could then assign an external controller like a MIDI volume/expression pedal (or a fader or even the modwheel) to that screen control, for live performance. (see the screenshot at bottom) Of course there are other ways to do it, like assigning the Volume faders of the multiple instrument channel strips to the same screen control (by adding additional mappings in the Screen Control Inspector), but the Aux approach seems to be closest to what you seem to be looking for. I don't know what your level of expertise is, but if these aspects of MainStage are unfamiliar, the video below covers the basics of screen control assignments & mapping..

Hi Ricivou - It could be an iOS version issue.. As far as I can determine at one point there was an update to the player that requires iOS 11 or later, so if you're on an older iOS version there may be a version mismatch (also as I understand it Apple at some point stopped updating iOS for the iPad Air 1st Gen beyond iOS 12, FWIW).. I don't have an iPad Air to check this out, so I'd suggest you contact our Support team directly, at this address: https://macprovideo.com/support Make sure to include the iOS version you're running. Support will contact you (via email) within 24 (business) hours, and obviously the tech wizards there have access to the most current information—they should be able to provide you with the best solution..

Student452134 wrote: > Here's what's TOTALLY not clear to me. Ideally I'd use DKD to get the right groove, and then split out the MIDI parts to different channels for my own processing. I see it's easy to transform the MIDI events in DKD to different tracks, but they're all on one channel, so individual processing is not possible. I could open up new channels and Option-drag the MIDI into those but then I don't get the nuanced producer's track setups. Or am I missing something? Help! " Hi - I loaded up a DKD Producer Kit, created a MIDI part, and used the command "Separate by Note Pitch" (right-click on MIDI Region->MIDI->"Separate by Note Pitch") to break out the MIDI Region to separate Regions—the top screenshot (below) shows the result. I then changed the names of the new tracks for clarity (bottom screenshot). This should allow individual MIDI processing (Q, etc) on the separate drum/cymbal Regions (via the Region Inspector), which, as far as I understand, is what you're looking for. (In this setup the individual drum/cymbal regions don't need to be on different MIDI channels to be able to process the MIDI in each independently.) The audio is still routed to the Producer Kit's separate Auxes for individual drum/cymbal AUDIO processing (EQ, comp, etc). It makes for a lot of extra track lanes in the Arrange (Tracks) area—obviously necessary for the separate drum/cymbal Regions—but all those Overhead track lanes are just duplicates of the original, so they don't show separately in the Mixer. I seems to me that breaking out the individual drum/cymbal MIDI into separate Regions this should way accomplish what you're looking to do..

Hi - Unfortunately, it sounds like that particular video file may be corrupted, but I can suggest a few troubleshooting steps to try to determine if it's an issue with the file or with the hardware/software.. First off, echoing Rounik's response to the original poster, how much RAM is installed (>8GB would be better), and what iMovie & OX versions are running—if it's a brand new MacBook did it come with Catalina (10.15)? Catalina users have reported all sorts of issues with audio and video applications (even with Apple software like Logic), so it could be growing pains.. Apple's troubleshooting checklist includes a number of standard steps, but you might want to try some of the tests below before doing any reinstalling (but definitely do a hard shutdown/restart first if you haven't already). As to a possible issue with the file itself.. - Try bringing the problem file into a new project for test playback—sometimes a file may be fine but the project gets corrupted.. - Can you record/playback additional videos without problems? IOW, is the problem specific to that one video file (more likely file corruption) or now that it's happened once does it occur in other video recordings (more likely a sw/hw issue)? - Can you see the rest of the video file (after the place it freezes) in the timeline? If you stop and cue up after that spot, does the video play ok from later in the file (suggests corruption at that spot in the file)? - If you can play the later video by manually skipping past the place it freezes, can you edit out that section and achieve smooth playback? - Is there any effect or transition at or near that spot (in any video or audio track)? If so, try removing them and see if the video plays smoothly through the problem spot - Can you share/export the file as a QT movie? If so, does it play through the problem spot (more likely an issue with iMovie) or does it freeze at that spot in the exported .mov file as well (more likely file corruption)? Apple's suggestions are also worth trying, particularly testing with a new library/project, testing in a new (temporary test) User space, and if all else fails, reinstalling iMovie. https://support.apple.com/en-us/HT206157 If nothing works, and if you can't duplicate the problem with any other video recordings, unfortunately that might point to file corruption. If that turns out to be the case hopefully you can salvage most of the video by editing/exporting the sections that do play properly and piecing together a version that excludes the problem area(s). Since I don't know what your level of expertise is, I'm including a link (above) to a basic iMovie course, in case you might want to consult it for help in editing/exporting video as part of your troubleshooting..

Student452134 wrote: > That's close, but what I want is for the tracks to actually be channels. This would allow me, for example, to separately eq top and bottom snare mics, or pan the overheads differently, or use a transient designer plug-in on the toms. The editing, in short, is not MIDI editing on tracks, but sound editing on channels... Hi again - But you can already do that with a standard Producer Kit, even if all the MIDI notes are in one Region (in the top lane of the Producer Kit Track Stack). All the drums in a DKD Producer Kit are split out to separate Aux channels in the Producer Kit Track Stack, where you can apply whatever audio processing you like individually to each drum—there's no need to separate the MIDI into individual Regions if you don't want/need to do any MIDI editing to the performance data. Are you sure you're loading up a multi-output Producer Kit? They're the ones with the + sign—you may have to load them from the Library pane (shortcut "Y"). You should be able to hit the small disclosure triangle on a Drummer/DKD Producer Kit track (see the screenshots above & below) to access the individual drum/cymbal channels for audio processing—those are all the channel strips following the Overheads channel strip in the Mixer & Tracks panes in the screenshot below. If it helps, the attached video (and the one following it) cover working with Producer Kits in Logic..

Sounds like a bug, though I couldn't find any other references to this particular behavior. Were the Clips themselves selected when you took this action? If so perhaps the limitation mentioned in the screenshot below (from the Ableton Live 10 MIDI Essentials course) would apply? I'm not a Live user so I can't try to test/duplicate it here. In general it would be a good idea to provide more information about a problem. For example, what computer & software/OS version are you running? The new macOS Catalina has many many problems with audio applications, and this could be an OS-related graphic glitch. Only Live 10.1.2 or higher is compatible. Other helpful information to include: - What kind of Clip(s)—MIDI or audio? - What version of Live (I'm assuming Live 10)? - Exactly what actions did you take? How did you select the tracks/clips, and did you perform any operations after making the multi-selection, or did the glitch occur immediately on selection? - What steps have you already taken to troubleshoot? As far as trying to recover.. - Did you close the session without saving? If so when you reopened it, were the names still asterisks? - As always, try a hard shutdown and restart - Try duplicating the session (Save As?) and see if it restores the proper names..? - Does Live create any auto-backups you can revert to to recover the Clip names? - If you have a clone or a (Mac) Time Machine backup of the saved session (or an earlier version) before the name change, revert to that and either proceed from that point or use it as a reference to manually rename the affected Clips To troubleshoot the cause (to avoid having it happen again).. - Duplicate/BU one or more sessions and try the same procedure on copies of the sessions, to see if it's a session specific glitch - If you can revert to an older version of the affected session, try the same procedure on a copy to see if it can be reproduced or if it was a one-time glitch - Maybe if you had selected more than 7 tracks/clips, on a session copy try selecting 7 or less and see if that works reliably—if it does, then try selecting more than 7 and see if that triggers the glitch Hopefully you'll be able to recover the names from a BU or in worst case manually rename the Clips and continue to work in the session.. :-)

Hi Vincent - While there is some overlap between Audition and RX7 in the area of audio processing & repair functions, Audition is more of a general-purpose audio program for recording & editing, while RX7 concentrates on advanced audio repair techniques, going much further in that area than general-purpose DAWs. It includes a number of cutting-edge tools specifically for dialog/VO processing, which I regularly use myself on the VOs for my courses, so I'm sure you'll find it useful.