José Sanguino
Participant
Topics Started: 0
Replies Created: 59
Has Thanked: 2
Been Thanked: 20
I’m not sure if this will help, but on the “drums” tab of your selected preset, make sure the articulation you are choosing has been loaded. I’ve attached a screen capture: with your Hi-Hat selected, go to the list of articulations enabled, click and check. You can add and remove articulations by clicking on the “On/Off” button. Needless to say, only the ones with the highlighted “On” button are loaded.
If you do not hear any sound, make sure that your reaper track monitoring (the speaker icon next to the “arm for recording” button is active. First you must make sure which MIDI notes your pads are sending, if any. Activate your track for MIDI recording and record a note with each pad. Take a note of which MIDI note number each pad sends. Since you are using Reaper, you can use JS Map Key as an input FX and set it up so that, let’s say, a pad which sends MIDI note 01 is sent to MIDI note 35. You just make a .txt note assignment file with the same structure as the default one, but you swap the input/output numbers and save with the appropriate name you wish. Then, use JS Map Key and load the same .txt setup file each time as an input FX.
Does the motu have direct monitoring? Does it come with its own mixer? (Like RME or focusrite) if it does then you don’t need a splitter. Most audio interfaces allow monitoring before it goes through the DAW.
Of course, if you use direct monitoring you do not really need the splitter. But direct monitoring will only let you hear your electric guitar completely clean (which is the way it is recorded in the track’s takes). Our friend has been able to get a very low latency out of his interface, so as long as he does not use too many instruments and effects at the same time, or freezes/render some of them as he is finished with some of them, he can record his guitar with any amp simulator and do without direct monitoring.
I mentioned the splitter because when your latency is too high, you can record your takes even with NO MONITORING and listen to what you’re playing NOT through your track monitoring or clean direct monitoring, but plugging the second output of the splitter into your own amp (with your own pedals, if you have them) and get a real amped sound without any latency while you are recording a clean output sound from your electric guitar. Once you have finished recording your takes, you can insert your amp simulater in your guitar track and tweak your sound at your taste.
1
Thanked by: entner.chrisCheck in your Reaper Audio Preferences. In the first pull-down menu you should see “ASIO”, and once you have selected that, BELOW you can select the ASIO driver you would like to use (you might see your previous ASIO4All and the MOTU ASIO driver among the choices in the pull-down menu). Take a look.
Yes. A cable like that would allow you to record your clean guitar in one Reaper audio track with the monitor recording turned off, and listen to what you’re playing in real time by plugging the other output of the cable into a real amp. That would give you direct monitoring, no matter what kind of buffer for latency you’re using.
I have never tried any other than the ASIO drivers created by my device’s manufacturer. Years ago I was forewarned by Computer Music Magazine about the amount of latency which you would get if you used Windows Media Drivers, so the moment I could lay my hands on an interface with ASIO drivers, that was the choice for me. Lower block sizes for your audio interfaces will allow you to play and listen to your virtual instrument in “real time”. There’s always a little latency, of course, but I remember reading in Computer Music Magazine that as long as your latency is below 42 milliseconds, it’s OK. Over 42 ms it is impossible to play and listen to your virtual instrument at the same time. It has to do with the ability of the human brain to coordinate its actions with the results produced and perceived. I’m pretty sure you must have seen on TV how a reporter starts babbling and has to remove his/her earpiece because he’s listening to the return signal from the studio with plenty of delay: that is what would happen to you, more or less, if you tried to play and listen to your instrument with a latency of over 42 ms. Direct monitoring is advisable if you cannot achieve low enough latency values. I normally use it when recording vocals: you must turn off the monitoring from the track the vocalist is recording, and let him/her listen to the direct signal the microphone is sending. How? Well, it depends on your interface. Some interfaces have a knob which will increase your mic input’s volume relative to your DAW’s reference tracks (other instruments already recorded, a click track, etc). The vocalist will hear himself/herself straightaway, with no latency (remember: the track which is going to record the mic imput should be disabled for monitoring – it’s the device’s direct monitor level which will allow your singer to hear himself. – Of course, the same trick can be applied to other instruments. Sometimes the direct monitoring has to be activated from within your interface’s software mixing console. The results will be the same.
In your case, you can turn off the monitoring for your SD3 track (you may even DISABLE the plug-in, since the MIDI notes sent by your e-drum will be recorded anyway) and listen to your e-drum sounds against the reference tracks in your DAW. You won’t be affected by latency. If you play a MIDI keyboard with internal sounds, you may use those while you are recording your MIDI performance instead of overloading your CPU with your virtual instrument – You can enable your preferred instrument afterwards, since the MIDI notes are already recorded. If you wish to record an electric guitar which will be later processed through an amp simulator like Native Instruments Guitar Rig or IK Multimedia’s Amplitube, you can split your guitar’s cable and record the clean signal from one, and plug the other into a real guitar amp. Just turn off the monitoring from the track where you’ll be recording your guitar and that’s it! Use your amp as a reference for your playing together with your DAW’s reference tracks. You insert your amp simulator afterwards.
Hope this helped a bit at least. Keep on drummin’!
1
Thanked by: entner.chrisIs there any reason you’re not using the drivers for your audio interface?
My guess is that emtmer.cris does not have a dedicated audio interface. That’s why he’s using ASIO4All! – entner, you should know that ASIO4ALL won’t give you the best results when working with a DAW. That’s where the crackling comes from. And if the computer you are using does not have enough RAM and a good CPU, you’ll always have the same problem. If you’re using a laptop… don’t. – You should get a good desktop computer and at least a mid-range price, 2-channel audio interface with its own up-to-date ASIO drivers ASAP if you’re planning to do more serious work.
Hello everyone; I have a question. In Fl Studio, the VST Sd3 loads, the only problem I have is that the hi-hat is played as open again after each hit and I can’t stop the cymbals either.
I do not use FL Studio, so I do not know how it works internallly. I’ve seen YouTube videos, and I guess you program MIDI clips (I hope they can be edited). Just remember that SD3 works in a way that in order for a MIDI open hi-hat note to stop it needs either to be followed by a close hi-hat Pedal midi note, (a closed hi-hat note may also do the trick) or have been recorded from an e-drum kit so that pressing the hi-hat pedal has recorded a MIDI CC message indicating the pedal was being pressed. As for cymbals, the sound can be cut short by inserting MIDI Channel Aftertouch messages leading from any value towards 0. Remember that for any crash or cymbal to be heard properly again, a Channel Aftertouch message with a maximum value must be sent prior to the cymbal note.
1
Thanked by: Christian083First of all, you have to make sure that the Reaper track which contains your Superior Drummer 3 plugin is set to record MIDI and not audio. Then, make sure that you are recording from the appropriate MIDI port (In Reaper you can select multiple MIDI ports as active in your “Preferences” window, so you must plug in your e-drum kit to a specific MIDI port and select that one for the track you are planning to use). Within the track, next to the record enable button, you can choose if you’d like to hear sound from SD3 or not while recording (it’s an icon for a speaker: set it to “on” or “auto” if you’d like to hear SD3 while recording, or to “Off” if you would like to hear just your e-drum kit). After that, if your e-drum kit MIDI notes are set properly to match SD3’s, when you play back the MIDI in your track, you’ll hear SD3 playing back your beat/groove.
1
Thanked by: entner.chrisCan’t say I’ve tried that myself, but I guess you have to save your kit as an user preset and the assigned drum articulation will remain assigned to that particular MIDI note. But that will only work whenever you use that preset. If you wish to use that articulation again in a kit where it is unassigned, you will need to assign it to the MIDI note again and save again as an user preset.
Clicking on the screen does not really give you a really precise “velocity sensitive” performance of the kit drum piece. It’s true that depending on the area clicked you might get different velocity samples. – I agree with this previous comment
Reduce the velocity range from 127 to 90, i. e. Drag the right 3 points to the left in the curve editor
– You can edit the velocity curve so that your Virtual Drum Kit reacts with a non-linear curve. – But you can always edit your recorded drums and then scale the velocities of each drum piece. I suppose it’s more convenient to adapt your kitdrum pieces’ velocity curves so that you hear the result you’re going to record. Just save your kitdrum patch with the velocity curves you’re planning to use in your song(s).
1
Thanked by: tendingtropicPor tu e-mail y por tu nombre de usuario en el foro de Toontrack creo que hablamos el mismo idioma. Durante la instalación de cualquier programa, tienes que asegurarte de que tu DAW va a encontrar el archivo .dll del plugin en la carpeta adecuada. Asumo que tu secuenciador Studio One 4 es la versión de 64 bits, y por lo tanto, tu sistema es de 64 bits (dado que, por lo que recuerdo, Superior Drummer 3 es ya sólo para sistemas y secuenciadores de 64 bits). Por lo tanto, cuando vayas a instalar Superior Drummer 3, al instalar el instrumento virtual, asegúrate de que usas una carpeta que Studio One 4 esté configurada en las preferencias de Studio One 4 para buscar instrumentos y efectos VST. La librería de kits de baterías se puede instalar ya aparte, si quieres en un segundo o tercer disco duro, en una carpeta que puedes nombrar como quieras (el instalador ya se encarga de enviar la información a Superior Drummer 3 de la ruta donde están instalados los kits). Pero lo importante es que al instalar el plug-in, que sea en una carpeta que tu Studio One 4 reconozca. Yo tengo Studio One 5 Artist 64 bits (aunque no lo uso). Dentro de Studio One, en el menú de la barra superior, desplegando “Studio One”, te aparece “Options…” como última opción. Pulsando ahí se abre una ventana adicional que te permite saber en qué carpetas de tu sistema está buscando Studio One los Plug-Ins VST (Selecciona en la ventana “Locations” en la parte superior y la pestaña “VST Plugins”). En la parte inferior te aparecerá una lista de las carpetas en las que Studio One busca tus instrumentos virtuales y efectos VST y VST3. Puedes añadir una ruta otra carpeta con el botón “Add…” (Añadir), o puedes borrar alguna ruta marcándola y pulsando el botón “Remove” (quitar).
Si ya has instalado Superior Drummer 3, asegúrate que la carpeta “Toontrack” donde se encuentra el archivo “Superior Drummer 3.dll” está en la lista mencionada. Si no lo está, añade la ruta a esa carpeta. Al reiniciar Studio One con la ruta añadida, deberías poder usar Superior Drummer 3 como instrumento virtual en Studio One. Si no puedes… a ver si el problema es que tu versión de Studio One es de 32 bits y al ser Superior Drummer 3 un plug-in de 64 bits… no vas a poder. Puede que haya alguna forma de usarlo con jbridge, que según tengo entendido, permite usar plug-ins de 64-bits en sistemas y programas de 32-bits y viceversa.
Adjunto captura de pantalla. Suerte.
I’m not a Pro Tools user, but I guess you must make sure that Pro Tools has identified your e-drum set as a MIDI input device, and that you have it enabled in your settings/preferences before you send it to the track where your SD3 VSTi has been loaded (I use Cockos Reaper, and you set your MIDI devices in your preferences before they can be used – So I’m guessing it must be more or less the same in every DAW).
Well, you’d have to set your beat preferences… but it will jam over those when receiving audio. Get into the downloads area at Rayzoon site. Download the manual and the bottom of page 59 you’ll see the “Jamming with Jamstix” section.
Alternatively, Jamstix 4 is now available for MacOS
I use Windows, and have been a Rayzoon Jamstix user for some time now. Well, let’s talk about it a little: Jamstix can be used both as a full drum VSTi (it has its own sampled drumkits) or as a MIDI drum generator for any other Drum VSTi. Depending on the number of expansion packs you own, you get different “drummers”, each one has its quirks and “personal” nuances which can be adjusted.
Jamstix can be made either to respond to audio input or just create a structure of sections (intro/verse/pre-chorus/chorus/bridge/outro, etc…). You can make each section as long in bars as you like. Jamstix will jam according to your preferences & drummer chosen.
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.