Jump to content

elnn

Member
  • Posts

    42
  • Joined

  • Last visited

elnn's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Dedicated Rare

Recent Badges

2

Reputation

  1. ah, so I guess it's best to just have 10.7.7 at hand, use 10.7.8 and if you get the pop up, pop back up into 10.7.7 and deal with it accordingly.
  2. But it removes the regions, so it's important to go through projects that have this problem and redo these regions. I myself don't remember which projects they were on, sadly. I hope it indeed doesn't happen again.
  3. The behaviour is just as described. Thanks for introducing with fellow sufferers. I'll join them there.
  4. Are you completely sure you had it in 10.7.4? I'll join the club. Logic 10.7.7 on OSX 12.6 on M1 Pro 2021 through system audio driver. I just returned from other DAWs for Region Folders, which I now use extensively. In addition to multiple tracks to the same channel strip. Additional behaviour: when ?-region is elicited, it might make other, non-foldered regions disappear from view and playback completely. You make a few changes here and there and these regions reappear.
  5. Anyone have this problem? I've just started using region folders extensively. Now oftentimes, other regions, those not foldered, stop working. They don't play and show a question mark in their info bar. I'd appreciate tips as to how to evade this.
  6. Thanks you very much, the both of you. It does seem quite a good system. After all, the score does not represent a performance, but the structure.
  7. I've decided to try out the score editor to make it easier to perform my pieces. Here's a problem that I have. The pictures should make it pretty self-explanatory, there's a number of problems: piano roll is quantised, first beat in 1/12, the next in 1/16, the rest in 1/12. score interprets in as three groups counted in 4th triplets (1/6), no 16th arpeggiation in the second beat, just a block chord instead. Also, the second note is interpreted as starting on beat 1. And for some reason, it thinks the D is repeated on beat 3. Score style is Piano 1/3+4. If I set it to piano, the first beat is interpreted fine, but no 16ths still. I tried to rewrite the bar in the score editor with no luck. How do I make it listen to me?
  8. Hi. We can draw automation steps with pen tool. How do I determine the size of a step? It seems fixed on divisions of 4 and corresponds somehow to zoom level, but I can't draw triplet-sized steps, which is what I want to do.
  9. Same with Alchemy. Poly mode even. Only at 97% gate length does it retrigger the next note (if it is on the same row). It also doesn't play the first note of a sequence. Even with no modulation. BUT ES1, ES2 work OK. I filed it as a bug, not sure I did it correctly though : D
  10. It's the same region in Tracks area and Loops grid. You can hear that when it plays from Tracks area, it's straight 8th note rhythm, while there are pauses almost every second note when played in Loops grid: these are notes with 100 % gate length (and the synth is set to legato mode)
  11. I checked it with Alchemy and Fxpansion's Cypher, so yea, it's an u-he thing. Thanks for responding.
  12. Seems to be a problem with gate length. A following note is always retriggered with 100% gate length in Tracks area, but is inconsistent in Loops grid. The same problem persists when converted to MIDI Region.
  13. Hi. MIDI automation steps come in late in relation to note on message. Plugin MIDI slew is 0. You can work around this by changing start offset of that row, but the percentage required is quite large – at least -11 % or more This makes step sequencer completely unsuitable for MIDI modulation. Anyone else experiencing this? Anyone knows how to fix it? Reducing I/O buffer helps a bit, but doesn't fix it entirely and is not a proper solution, because CPU, obviously Here's a video of it, automating MIDI mapped AmpEnv attack. Using U-he Repro-1
  14. I just delete all points before playing in midi cc again. No way to do smaller adjustments though, sadly. You can also make two tracks for the same instrument and use one for notes and another for midi cc data, as Dave says. Then you could use replace for only midi cc data. And after you are happy with the take, just join them together. It's not difficult to separate them, too, if you played them in together – just copy the region to that second track and delete all the notes in one and automation points in the first one. Might be quicker to use Transform tool if there's lots of midi data, but if it's just the Modwheel, selecting and deleting is quite quick
×
×
  • Create New...