Jump to content

eakwarren

Member
  • Posts

    63
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

eakwarren's Achievements

Contributor

Contributor (5/14)

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

Recent Badges

24

Reputation

  1. Perhaps use the voice separation tool to set what viola notes appear on the stave.
  2. Can confirm it is a bug. I reported it mid Feb. and Mike Audio emailed me for more info. Here's what I sent on Feb. 22:
  3. Another option is to open two Environment windows and drag across them to cable connections. I find this more intuitive at times than the list view (with its alphabetized list which often doesn't reflect my track order) when navigating large projects. Kapture 2024-02-22 at 12.26.27.mp4
  4. The manual describes: But I'm not entirely sure I'm following the description. It appears you set it in the plugin, but it only applies to all regions that don't have automation data of that kind. Uhhh, so set CC1 in the plugin, but it wouldn't apply since previous recordings would already have CC1 data... 😕
  5. Perhaps create a default region with points every bar or beat and set the track to Touch mode. After recording it will "reset" to the next automation point in the region. To quickly build the default points over time, after entering a couple default automation points, extend the region, select them with the Automation Select Tool, copy, move the playhead (> shortcut key), and paste. Repeat. Save the default region on a separate placeholder track or set the region on all tracks. You could also import that track/region into other projects.
  6. 2/7/24 v1.2 released Added support for multiple art types (controller, program, aftertouch, pitch bend, note off) Added support for Per Channel Strip MIDI Channels in art sets Added library code option to build pic URL from art set name Added sendosc universal binary Added support for large art sets (≤ 50 arts) Optimized Logic queries and processing Fixed bug when right panels open in Main Window
  7. In the Score window, select View > Colors > Show Voice Assignment. Then select notes that you want on MIDI Channel 1 vs. 2. (They'll show up red or green respectively.) Then you can use the Voice Separation Tool to fine tune. Kapture 2024-02-07 at 13.27.06.mp4 When done, View > Colors > Force Black&White.
  8. Polyphonic means more than one note at a time. I believe the MIDI channel assignment means different midi channels for different voices of the chord.
  9. A couple of places to set this up. In Settings... And individually by using the Voice Separation Tool.
  10. Here's the video I'll send to Apple, along with the project file, a short description of the issue and what the expected behavior may be. Please let me know if anything is unclear. Thank you everyone for your input! 😊
  11. Yes, that's my goal. For that reason I think demonstrating the issue with just 2 midi keyboards connected to Logic may be the best route to show the behavior of keyswitches only working for the currently selected track. I created some videos last night and will work on annotating them. (Started learning Davinci Resolve, it's awesome!) My YT vid demonstrates clicking the trigger keyswitch with the mouse on each port separately, so there's a couple second difference between the events already. Yes, the Midi Channel in the Switches tab is set to All for those art sets. In my test I'm not using section presets as described in the support link. Here's my settings if anyone is interested. I've also tried changing All to ch. 1 & 2 respectively. Same result. https://divisimate.com/support/ (Tell them eakwarren says hello. 🙂) They also have a Discord server. Exactly. Well stated. I'd add, "...by sending key switches to the instrument on each track through each port set in MIDI In Port in the Track Inspector." Yeah, that was ages ago. We're way past that now. 😂 I did ask David earlier to update the title.
  12. Gotcha. I see the vmpk port in Logic. However, this method just duplicates the same key press out both ports. To replicate the DM functionality, they'd need to be a different key press on each port. I don't think vmpk can do that.
  13. Agreed and I started going down that route. The problem with eliminating DM is that I don’t know a good way to simulate two keyswitches on different ports with default Apple tools. I setup two IAC ports, but how to feed them? I may have to hook up another keyboard and just do it manually. Any ideas there? I’d hate for the Logic team to then point back to two midi keyboards as the issue. 😂
  14. The YT vid provides context for the test, if you haven't watched it yet. 🙂 I started with a full orchestral setup in DM and noticed arts weren't switching when loading different DM presets and started troubleshooting. I stripped down the DM preset to just 2 ports and a single keyswitch on each port to isolate the issue. As seen in the YT vid, I just click the single trigger (TR) with a mouse. When I play all the E3 notes, that is done with an Akai LPK25 usb keyboard only connected to DM. The 2nd from the left black window is MidiMonitor which helped verify exactly what is coming from DM ports 1 & 2 prior to entering Logic. Note that the keyswitches in DM are different notes (F0 vs G0) on different ports. They're not duplicated by DM as MidiMonitor shows. I've scoured the documentation I linked above and there's no mention of currently selected tracks. ⌘F for the word 'track' returns no results. That's fair. But what about the inconsistent behavior shown in the video depending on which track is selected? That seems more bug-like. I disagree since MidiMonitor is not showing duplicate note-on events coming from DM. There's a note-on and a note-off event on each port, triggered individually when I click with the mouse on each trigger in DM. Agreed. That seems overlooked in the design since MIDI In Ports were introduced a few versions back. *nods* 😁 *nods* But they'll hear about it soon! 😏 Thanks for your input.
×
×
  • Create New...