Jump to content

WolfWein

Member
  • Posts

    16
  • Joined

  • Last visited

Personal Information

  • Occupation
    music
  • Location
    USA
  • Mac
    2021 mbp 16"

WolfWein's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Reacting Well Rare
  • Week One Done

Recent Badges

3

Reputation

  1. Polanoid - why insist that people should not be able to record midi on Aux tracks and that it was just a hack? a) against what you claim, the Musical Typing kbd works fine on them; as does step input. b) why then did the developers add the Articulation Set menu? and a setting for default notation display? c) why do other AUX tracks when added as a track to the tracks window not have these features? d) as I understand it, the Rec Enable button on instrument tracks is only needed when wanting to record multiple tracks at once. I never needed that. I select a track = make it live/active - start recording. no need to touch the Rec button. and the same behavior worked on such AUXes. some hack, eh? Rather, it has been an excellent and clever implementation of a way to set up and work with multi-out VIs. The short of it is: it's a great way to have midi data and audio processing on the same channel. Saves hugely on track count, makes editing midi and the resulting audio changes faster and makes organizing sessions much easier. Can you accept that as being valid workflow considerations? And rebuilding templates with hundreds of tracks, intricate routing to implement (hopefully only temporarily needed) workarounds is no fun and to be avoided if at all possible. Recording midi on AUX was a feature that previously worked and is now broken. It was not announced as one of the changes (afaik) and therefore happened unintentionally and therefore is validly categorized as a bug.
  2. same here. Sadly this forces me to revert back to 10.7.7. bug report sent to Apple.
  3. I have a nonoKontrol 2 and nanoKontrol Studio. Both work fine with 10.4.5. It initially didn't show up but when I un-replugged it while LPX was running, it worked and has since.
  4. EDIT. just saw that volovicg already hinted at this. apologies. disregard. did you check the No Reset parameter in the track inspector? and/or in preferences - Midi - Reset Messages - uncheck Control 1 ?
  5. Fat Tony, very helpful indeed. Thank you for posting this.
  6. I see the same bug here. It only happens when I open old(er) projects. Creating a new project with multi out VIs - save-reopen works fine. I tried the same by creating a project in LPX 10.2.1 - open in 10.2.3 - still works. Opening any of my templates that were created in earlier versions than 10.2.1 (sadly I don't know which version I used) shows the bug. sadly this makes the update unusable for me as well. bug report sent to Apple P.S. this is clearly not a Kontakt bug, but a Logic 10.2.3 bug. I suggest renaming the thread if that's possible - makes it easier for others to find the thread.
  7. genius! disabling Snap + holding SHIFT gets rid of magnetism and disabling "Limit dragging to one direction" gets rid of it completely. I would have never made that connection. Is this documented and I missed it? I know this Prefs option is documented; but that this makes the midi notes magnetic I couldn't find - and I stubbornly remain that this is a bug. trouble is, I find the "limit dragging..." option quite useful and have it on by default. Guess I'll keep it on and use the SHFT key a lot. And now I can write a more complete bug report perplexingly, even with Snap active + "limit dragging..." active, moving regions in the arrange window works as expected; except for the unnecessary magnetism there too: CTRL get's rid of magnetism (or so it seems, not 100% sure) and moves regions in medium resolution; CTRL+SHFT moves regions in ticks. anyways, thanks for pointing this out!
  8. thanks for confirming. "magnetic midi" is a good description for it
  9. One of the most annoying things for me in LPX is the initial resistance midi notes have to being moved in Piano Roll - they seem to be glued to their original position and then suddenly jump by ~25-200 ticks depending in zoom level. CTRL-moving doesn't work any more; meaning the resolution doesn't change. CTRL-SHIFT moving does work and does not have the inertia, but is often to fine a resolution for quick, natural sounding adjustments. This behavior seems to have slightly changed in 10.2. Now when I grab a note with CTRL-SHFT, move it a bit, then let go of SHIFT, the old (meaning LP9) medium resolution moving seems to be back and there's no magnetism towards the original position. Beautiful! afaik, this is an undocumented change. but I am unsure how consistent it is - seems to only work in new songs and they lose that superpower sometimes. Could you try this out on your systems and report the results you get?
  10. confirming the bug. On my setup it only happens when I drag the velocity handle in midi draw. It does not happen when I adjust velocities with the volume tool - which I assigned to my right click - which is why I have not encountered the bug before. adn this would also be my albeit limited) workaround.
  11. I see. thx for finding and sharing! oh, the times we live in... We can't even tell folk anymore, putting on an air of superiority and belittling tone: RTFM!
  12. Eric, this is awesome! thanks. I was missing that function. How did you find this? I can not find the relevant info in the manual.
  13. same here as well. This was one of the first annoyances I encountered when trying out LPX - well before 10.0.7. seems to be related to Preferences/General/Editing - Limit dragging to one direction in: Piano Roll and Score. when I have this checked, the unwanted snapping behavior occurs, no matter how the Snap menu is set. a related bug (or new feature??) is that it is no longer possible to move notes by ticks when holding down CTRL-SHIFT when not fully zoomed in. that was possible in LP9 and it was great. it still works with regions in the Arrange (Main Window)
  14. Eric, are you hinting at a PDC bug involving this setup? I was just puzzled by this and created a new thread describing how I reproduced the behavior: viewtopic.php?f=1&t=106618 Is this a known bug that I have (blissfully) missed so far?
  15. I'm experiencing 2 scenarios where PDC is not working correctly. Please try the quick tests I post below. On my system, the behavior is reproducible 100% of the time. Please help me find out if these are LPX bugs or just something wrong on my setup. specs: 10.8.5, LPX 10.0.6, PDC set to All; Low Latency Mode is off (of course) scenario 1: Plugin Delay Compensation breaks when side chaining from a multi-out instrument's Aux channel. to reproduce: create new project - add 1 audio track - add a groove (drums, bass) with good timing, a blue Apple loop works - insert Compressor (optional: set Threshold to 0.0db) add Software Instrument track - insert multi out Ultrabeat - add 1 output channel (= Aux 1) - on main out, add send to Bus 1; on out 3-4 ( Aux 1 channel), add send to Bus 2. insert Adaptive Limiter (a high latency plugin) to both Ultrabeat Channels (add a Linear Phase EQ to hear things even more clearly) back to audio track - compressor - set side chain input to Bus 1 - PDC is fine. set SC input to Bus 2: PDC is off which can be heard be the audio no longer matching the click. this issue only happens with PDC set to "all". when set to "Audio and Software Instrument Tracks", PDC wroks correctly. Of course I need it set to "all" for mixing. This leads me to believe there is a bug with PDC on BUSes. scenario 2: PDC issue on Multi Out Vi's AUX channels: in the song above - in UltraBeat assign the snare to output 3-4. add a simple rhythm like a few quarter notes to each UltraBeat channel remove both Adaptive Limiters - solo each UB track - timing is correct. add Adaptive Limiter to Aux 1 (=UB out 3-4) - timing is still correct on both tracks add Adaptive Limiter to UB main out - timing is off on Aux1 (and on main out when doing the test with Kontakt 5) this is independent of the sends created before the same happens with EXS24 and Kontakt 5 (after which I stopped testing). the same scenarios work without flaw in LP9. it looks to me that: Plugin Delay Compensation breaks when side chaining from a multi-out instrument's Aux channel and Plugin Delay Compensation breaks for Multi Out Instruments' AUX channels, when plugins are added to the Instruments main out (out 1-2)
×
×
  • Create New...