Perhaps something is'nt working like your keyboard or Studio One. Check your controller and setup again if nothing else seems to be wrong. Check you don't have any automation that is responsible.ĩ. Check you have a sound loaded in the plug-in.Ĩ. Check if the track or the plug-in volume or any parameter affecting this behavior is'nt 0.ĥ. Check if the Monitor button on the track is engaged.Ĥ. Be sure your amp or monitors or whatever is turned on and is'nt turned down and everythng is connected correct and works.Ģ. You can try this - some depending on you are playing your keyboard or playback a recorded track or both:ġ. I figure I am missing a step here somewhere again. Presence is set to have my Keyboard as the controller, the output is set to main, and no sound. I have confirmed the notes coming in, track is armed, and can see signal on the channel meter to left of track window, but no sound is coming out the mains. Turned the system on this morning to finish some tracks, and now I am getting no sounds from my instrument track. If this indicates an issue any of you know (and a fix ) please let me know, and I will try to get the info you need. I figured posting this might help someone else with the same issue. Since I'm new to MIDI, maybe this is the standard way to power up MIDI setups, and if so, forgive my newbness. I found starting the keyboard, then the Audiobox, then the computer, then open S1 seems to be the only way to get the midi I did record to load up properly and just start listening to it. After various squeels and resets, I found that there seems to be a particular order that things like to be started. Shutting off the audiobox removed the squeel but now I had to reconfigure all the devices again (good practice I guess). This was one of the reasons I was putting off updating the driver I had installed. S1 asked to restart, restarted, and all of a sudden my ears were bleeding as the Abox just started screaming at full VU meter. Opened Abox VSL and changed settings to 64 samples. Until I realized that the ABox was running at 2048 samples. Once I did that, started getting signal and output. I did not have the keyboard selected as the controller in the Presence GUI. Though I'm not so sure the driver is working properly. It was a combination of my setup and my driver. Though test of only Pitch\Mod wheels will be enough (Ie it assume that if they work, then other will too).Ok. So, it works.Ħ) Now, disconnect LFO from Gate, and connect respectively to "Mod wheel" or "Pitch bend" jack in backward Midi out device panel - so, this is it : See what will occurs with Pitch\Mod wheels at your VSTi UI - will it modulate or not, and will or not appears yellow column (midi activity) indication in your vsti track.Īnd the same for jacks "CV In to MIDI CC Out" at backward panel of Midi out device. (And together with this, you will see yellow vertical animated column in your VSTi track, that represented incoming MIDI activity in S1 track). But I've no idea how to do similar thing in Studio OneĢ) In S1 as second track add any VST instrument who have Pitch\Mod wheels (graphically, in UI)ģ) In this vst track, in "Instrument Input" dropdown list choose "ReasonRackPlugin"Ĥ) Open RRP and add "MIDI Out Device" (from factory instrument devices list)ĥ) For test outcoming MIDI signal thru midi out device, add Subtractor in RRP, and connect his LFO output to "Gate" first (Gate at backward panel of MIDI out device), and increase LFO1 rate in Subtractor for better activity - you start to hear repeating sound of your VSTi. How would I actually test it? It's easy in Bitwig, because there's dedicated device that captures CC signal and changes it to modulation that I can attach to whatever. (I could also check in Ableton, but I have v9 unfortunately, it seems it will the same).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |