oscwilde

Not directly. You can copy data (project bundles only - AFAIK) via the Files app to/from the iPad internal storage. AirDrop/iCloud or directly connecting the Mac/iPad achieve the same result. iPadOS is locked down/sandboxed, so this limits what can be exchanged across platforms (at present). Hopefully this changes in future.

This thread indicates that VEP works on Sonoma with Logic 10.8.x:

Why not pack the unused stuff into a folder and drag it to the bottom of the track list, then rename the folder "For Later"?

Time handles? https://support.apple.com/en-au/guide/logicpro/lgcp4a739b4b/10.8/mac/13.5 You also have a number of other time stretching / manipulation options thru use of QuickSampler, Sample Alchemy, or audio FX (Remix FX, Multi FX, etc.)...if the MIDI part is a softsynth, external MIDI device, or printed to audio.

Yes, it's possible the bypass automation is the cause of an audio glitch. If this is the case, is there an alternative plug-in that can be used? You could experiment by manually bypassing the plug at other playback positions/disabling the automation, etc. to see if it changes things.

Ahhhh....OK....was wondering what happened in the video. Anything visible in the Mixer (with All active)?

It can send data, but the faders send sysex, rather than MIDI CC data. Has your friend considered a straight 88-note controller keyboard? Arturia Keylabs, Roland A-series, Native Instruments KK, Akai MPK88, etc? In the 73/76 range, I can only think of the StudioLogic and Numa boards that have weighted actions. Most keyboards in this size are more home-oriented, so lack hammer action keybeds and/or front panel controls. Away from the new keyboard angle....is the idea of a controller that sits on top of the VR730 a viable consideration? There are lots of tiny controllers (fader/knob boxes...rather than mini keyboards - although these can also be a good option) that might provide the desired "knobby or fader control" features for MS. Korg Nano units, Novation Launch Control, etc. You could also use an iPad for this - but I'd imagine your friend would want something tactile/use by feel alone during live performance - rather than something they need to look at to use.

Ask in /read thru the uber thread and also check out Dave's article:

Alchemy has multiple sound engines, as you've undoubtedly discovered. It also has a zillion parameters....and you're correct that a few of them "appear" (or actually) cover the same ground/impact the output in the same way. The behaviour of particular parameters changes when different sound engines are in use. When it comes to (user) sample handling - the import method is the key to this. You can import WAV, AIFF, and Sampler sound files as additive, spectral, a combination of additive and spectral, granular, or sampler elements (sound engines). If you're importing in Sampler mode only, you're not gonna find much going on. If you import as additive and spectral or granular, things "might" become more apparent - depending on the audio material. Once you've imported something - also import the SAME loop to an audio track and change the project tempo - then mute the audio track. Use this region as a point of comparison (unmute/play it) when messing with the audio in Alchemy. Alchemy. When doing the above....don't use an Apple Loop as these contain tempo information.

Cool. Glad it worked for you. The difference between folder/summing stacks is covered here: https://support.apple.com/en-au/guide/logicpro/lgcp9bc4b63d/mac The workaround you mentioned is another option that can be convenient when working with a region or two or several/all regions on a given track that you want to move to another. Personally, I'd just re-route the output in this situation, but - as you're discovering - Logic often provides a few ways to arrive at a destination. Each method has it pros/cons, but at the end of the day it comes down to working preference/the way your head works. Most of the "old-timers" here tend to go for the fastest/least labour-intensive method where multiple options to achieve the goal are available.

Is the user guide description unclear or you've tried it and it didn't seem to do anything? If the latter, the impact of the parameter is most apparent on rhythmic material like a drum or melodic loop. It interacts with the Speed control above it, and also the chosen loop mode. Another factor that affects all of the above is the project tempo when the audio is initially imported (and the analysis mode(s) chosen). It's a difficult parameter to describe (as it interacts with/is reliant on other parameters and the "type" of audio material being analyzed, sped up/down, looped, etc.) Probably the best way to have a "lightbulb moment" is by importing different kinds of audio material and messing around.

Yep...me too.

Do you use an external sequencer (beatstep, etc.) or drum machine....or software alongside/with Logic? I want to know why Logic is cycling at bar 61 and not bar 64, per your cycle region.

In addition to @wonshu's excellent suggestion you might consider using folders/track stacks. Packing a bunch of tracks into a folder will make things "neat" onscreen....and if you need to make edits or think I "do" need that 21st drum track, you can open the folder and all of the existing regions will be where you remember them being. Once you're done with your changes - close the folder. The other plus with working this way is that you can copy, mute, or apply things like automation at the folder level - affecting all regions/tracks inside it...so you could fade out all drums, for example, with a single volume automation lane - rather than automating 20 tracks individually.

Or use a folder/track stack and automate this....