Jump to content

Promidi

Members
  • Posts

    3,030
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Promidi

  1. Promidi

    BPM calculator

    I wrote my own in VB2010. I enter a time duration in seconds (to 3 decimal places) and the number of beats in that duration. Then it spits out the tempo.
  2. Are you using any Workspaces? Unless you configure used workspaces not to, those Workspaces will load their own specific Keyboard shortcuts. I use Workspaces and many custom Keyboard shortcuts. However, I have configured the Workspaces I use, not to load Keyboard shortcuts from those Workspaces (Done in “Manage Workspaces”)
  3. Worked for me. Got confirmation email with download link in about 20 seconds.
  4. Promidi

    Problema con vsti

    Desinstale y vuelva a instalar el VST. Sería útil saber de qué VST en particular y de qué versión de Cakewalk by Bandlab estás hablando.
  5. Please let's stop all this talk about screensets being abandoned. There has never been any official evidence that this is ever going to happen. I have used screensets and workspaces (FNA Lenses) in my projects for quite a while now For me, Screensets and Workspaces have worked flawlessly and harmoniously to date. Scroll up my previous post in this thread (April 30, 2020) for more info.
  6. The latest version is actually 3.1
  7. How are the pitch bends getting there in the first place? I do many MIDI only projects and use pitch bend all the time. The only pitch bends that get put in there are the ones I have intentionally put in there. I always remember to put a Bend = 0 event afterwards. I have written a CAL script that zeros last pitch bend event of a group of selected pitch bend event to make the easier. This CAL script is bound to ALT E I have written another CAL Script that automatically places a Bend = 0 slightly before every selected note. If no notes are selected, it puts it at the NOW cursor. This CAL script is bound to ALT W
  8. Ok. There is not really way for the PRV to ignore previous controller changes. It has to be programmed in the synth. For instance, to get a synth to not respond to pitch bend, you have to find a way to set that synths pitch bend range to zero. The method depends on the synth. You may be able to issue a specific NPRN command - again, depends on the synth. Some synths respond to RPN0 > 0 (TTS-1 being an example) Events to set the pitch bend range to zero.
  9. Well it depends on the synth. TTS-1 can use RPN0 for pitch bend range. Rapture needs to use an NRPN event If a synth’s pitch bend range can be automated, then that same parameter will be listed as an NRPN If you check the list of any synth’s automatable parameters, you will find that list will match the list of that synths NRPN parameters. If the pitch bend range of Cakewalk Sound Centre can be automated, then it will be there somewhere in its NRPN parameter list (I don’t have CSC, so I can’t test)
  10. The NRPN parameter names that appear depend on the actual synth used. The Bend Up/Down parameters are Rapture. The NRPN parameters you’re seeing are for TTS-1 For TTS-1 you need to use RPN0 This is the GM standard for pitch bend range, which TTS-1 adheres to. In TTS-1, to get the actual RPN value , you multiply 128 by the pitch bend range you want. To get a range of 4 semi tones, you use RPN 0 > 512 (128 x 4) To get a range of 7 semi tones, you use RPN 0 > 896 (128 x 7) To get a range of 12 semi tones, you use RPN 0 > 1536 (128 x 12) I tested this in TTS-1 and this works.
  11. RPN 0 to control pitch bend range is a Roland GM standard (also Yamaha XG). TTS-1 also follows this standard. Even then the RPN values are derived by 128 x Range. However, with many modern synths and VSTis, this standard goes out the window. These synths have their own method. Let’s have another look at Rapture Pro. With NRPN events, you can have 16384 discreet values. However, with Rapture Pro's pitch bend you have 25 discreet values (24 including zero) What the formula does is changes Rapture Pro's 0 to 24 pitch bend range to NRPN Events 0 to 16384 so you know what NRPN value to use Another way to get the NRPN value from the required range is to multiply the range by 683 (Which is 16384 / 24 rounded up) So to get: A range of 4 semi tones, you use NRPN Bend Up 01 > 2732 A range of 7 semi tones, you use NRPN Bend Up 01 > 4781 A range of 12 semi tones, you use NRPN Bend Up 01 > 8196 I tested this by plugging these values into the event list view and the range does change on the fly as the track is playing I had 4 notes (All B2) playing, each proceeded by an NRPN Bend Up 01 event and a pitch bend event at maximum (in that order) Audibly, the notes played the correct intervals (4, 7, 12) even though the note was still displayed as B2 notes according to the PRV I also opened up the Rapture's edit screen and I could see Element One’s pitch bend value change accordingly while the track played.
  12. I just checked mine and they are all there. Maybe flick an email to support@cakewalk.com
  13. You're right about it being a moot point. However, you can enter NRPN events the same way you enter any other events. When you add a Controller, you select “NRPN” as type. Rapture actually has 12 Bend NRPN events available (6 elements, separate up and down). Unfortunately, that values do not correspond to the actual range values. The formula is NRPN value = 16383 * (range / 24) If you have a Rapture patch that uses all 6 elements, then you would need to issue the bend event for each element. Personally I would use automation. Note: The way I use NRPN events in Cakewalk is to control drum parameters for an external SW1000XG card (an various other parameters)
  14. If you have a MIDI track driving a VSTi (or a SIT), then all parameters that are automatable are also listed as NRPN events. For Rapture Pro, the one you're after is BEND UP {1 to 6} and Bend DOWN {1 to 6}
  15. That is correct.
  16. Sometimes I temporarily need a range greater than the default of 2 Yes, I could just keep it at a range other than 2. However, most of my pitch bend are 2 semi tones. It's far easier to achieve this using PB=8191 when the range is 2. If the range was always at a fixed value > 2, then I would have to be very accurate with the mouse to achieve a bend of 2. Besides, I have a Studioware panel combined with a CAL script where all I do is enter the required bend range, and the CAL script enters the correct RPN event to achieve it. I have a separate button just for 2 -I just click it, and it enters an RPN0 > 256 (which makes the range 2) With the Studioware panels and CAL scripts, this is very fast.
  17. I do this in all of my MIDI projects for the SW1000XG.
  18. Can you not automate the pitch bend range parameter(s)? Or you can change the pitch bend range on the fly using NRPN events. In the PRV, you can see all of Rapture's accessible parameters listed. The one you're after in Bend Up and Bend Down. Or you can change the parameter with Write automation
  19. What you might want to try are the beta Focusrite drivers. The release notes specifically mention Cakewalk by Bandlab. Using a non firebox browser, head over here and scroll down to "Focusrite USB2 Drivers 4.87.4" http://beta.focusrite.com
  20. I use a Roland UM-ONE mk2 USB MIDI Interface that I have had since mid 2015. https://www.storedj.com.au/roland-um-one-mk2-usb-midi-interface?SearchID=16882502&SearchPos=1&SearchID=16882502&SearchPos=1
  21. I still would not trust a cheap USB/MIDI cable. Mine has always delivered what I have thrown at it - including all the sysex I can put in a project.
  22. If you stay away from those cheap no-name brands, you should be ok. Only buy branded items from a reputable dealer.....
  23. In my current MIDI only project, they add up to a total of 164 bytes. These are broken up into several banks. These are to set up insert effects and parameters on an SW1000XG.
  24. In TTS-1, for a given track, MIDI CC74 is a low pass filter. The value 63 is the default value. Values less than 63 will decrease the frequency. MIDI CC71 controls the resonance. Again, the value 63 is the default value.
×
×
  • Create New...