Jump to content

Promidi

Members
  • Posts

    4,074
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by Promidi

  1. As per title. https://www.meldaproduction.com/downloads
  2. I would simply write a CAL script to do this. Maybe even set a keybinding to this CAL script. (do (forEachEvent (= Event.Chan 0)))
  3. I would if I could. However, on my PC, Korg Software Pass just drops to desktop. Even Korg Support is stumped.
  4. I am going to assume you are using the latest drivers for the MOTU MIDI Express https://motu.com/en-us/download/#category=2&product=17
  5. What MIDI mode are you using? MME or UWP Is the MOTU micro express plugged direct or via a USB hub . If a hub, make sure it's powered. Personally, I would only use direct, not any HUB (even powered). Try a different USB port. Also, do any of your projects have any SYSEX banks or data that gets sent upon open. Maybe these are overwhelming your MOTU.
  6. Use a synth that allows ASDR to be mapped to amplitude. Set the sustain to a lower value than the maximum. Set the Attack, Decay and Release time to taste.
  7. Search for “Go to start of” and “Go to end of” in Global Bindings.
  8. You can also create a custom keybinding to do this. I have simply set the left and right cursor keys to move back and forward measure by measure.
  9. What I would have tried before doing the System Restore is uninstall and reinstall the latest Vdist runtimes or even reinstall CbB.
  10. Because there is an issue somewhere that is preventing it from staying open.
  11. Maybe this will help Adding Expression pedal to Amplitude 5
  12. Reinstalled your drivers for your audio interface drivers (Use manufacturers website to check for latest - not Windows Update) What sample rate, bit depth and buffer size are you using? Is your PC fully patched (or completed all updates - including final reboot)? What plugins are you using. My PC is configured as per my signature and I am not having this issue.
  13. I have created a CAL script that removes controller events that are of the same number AND that are are less than 15 ticks than the first of selected controller events. It also removes controller events that are of the same controller number AND that are the same values. (do (int resolution 15) (long Previous_test_time) (int Previous_CC_Value) (int can_delete 1) (long first_time) (long last_time) (int cc_index 1) ;find first CC Value and its time (forEachEvent (if (== Event.Kind CONTROL) (if (== cc_index 1) (do (= first_time Event.Time) (= Previous_CC_Value Control.Val) (++ cc_index) ) (= last_time Event.Time)))) ;thin out (= Previous_test_time first_time) (forEachEvent (do (= can_delete 1) ;assume can delete (if (|| (== Control.Val 0) (== Control.Val 127)) (= can_delete 0)) (if (== Control.Val 63) (= can_delete 0)) (if (|| (== Event.Time first_time) (== Event.Time last_time)) (= can_delete 0)) (if (&& (== Event.Kind CONTROL) (== can_delete 1)) (if (<= (- Event.Time Previous_test_time) resolution) (do (if (&& (!= Event.Time first_time) (!= Event.Time last_time)) (delete) ); enf if ); End do (do (= Previous_test_time Event.Time) );end do );end IF ); end if );end do );end for (forEachEvent (do (= can_delete 1) ;assume can delete (if (|| (== Event.Time first_time) (== Event.Time last_time)) (= can_delete 0)) (if (&& (== Event.Kind CONTROL) (== can_delete 1)) (if (== Control.Val Previous_CC_Value) (do (delete) );end do (do (= Previous_CC_Value Control.Val) );end do );end if );end if );end do ); end for );end do
  14. In the MIDI track, where you would normally tell the MIDI track what synth or MIDI port to send the MIDI data to, select Amplitube 5 on the drop down menu. This is assuming you have enabled “Enable MIDI input” on the Amplitube 5 Plugin window.
  15. Works fine here. Enable “Enable MIDI input” on the Amplitube 5 Plugin window menu (on the down arrow next to VST2 or VST3). Then create a MIDI track with the Express MK2 on its input. Then route the MIDI track to Amplitube 5. Make sure input echo is enabled on that MIDI track.
  16. IKM Product manager 1.0.8 Is fine here, with latest Malwarebytes Premium and latest defs.
  17. Extremely likely. Not according to the release notes. There is no mention, in the 2023.09 Build 62 release notes, that 2022.11 needs to be installed prior to upgrading. See: https://www.bandlab.com/products/cakewalk/whats-new
  18. Personally, I would simply purchase a sustain pedal that has a polarity switch, like the M-Audio SP-2
  19. Also, remember that each piano takes around 20 gig. So that’s 160 gig for the lot. Also, like I said on another post, I would want to make sure I can't make these sounds already with what I already have before I bite.
  20. As long as it does not generate sounds that we can pretty much do with with what we already have. This is what I always consider when a vendor spruiks their new offering. On the other hand, must resist GAS!
  21. I have never worried about actual bank or patch numbers. I simply let the Instrument Definition file take care of that for me. As long as the MIDI track is routed to the MIDI port that the SW1000XG is connected to, and the correct MIDI channel is selected, it just works. Also, in Preferences - MIDI - Instruments, I point the respective Output/Channel to the correct instrument (All except for 10 is “Yamaha SW1000XG”, 10 is “Yamaha SW1000XG Drums”) I have never had to enter actual numerical data to selected Banks and Patches. I also always use the patch browser (which is populated using information contained in the Master,ins file, which itself has data inserted by importing the Instrument Definition file). If I ever imported MIDI data that contains its own Bank/Patches MIDI events I would just delete those and then enter new ones that I know work for the SW1000XG.
  22. I use combination Bank/Patch changes on an SW1000XG MIDI card (which has over 1200 patches) and these patch change events are sent correctly here on 2023.09 Build 62. I use the SW1000Xg Instrument Definition file that I have always used, and the patch names on the downdown still match and play correctly. The correct Bank/patch is always selected on the SW1000XG part at the Bank/Patch change in a given CbB track (or at the beginning from the Bank/patch setting of the track). Something else must be going on here. Is there a way for you to verify what MIDI events CbB is actually sending when a Bank/Patch change is required? Maybe find a way to route the MIDI to a utility like MIDI-OX Note: My Bank Selection Method is set to “Normal”. For any of my MIDI only projects, each MIDI track’s settings are set to their specific MIDI channel.
  23. That is actually a SIT (Simple Instrument Track).
×
×
  • Create New...