I ran into something the other day, and havent seen this using Studio One for the past 6 years.
Being a heavy MIDI user I naturally use alot of MIDI CC commands. In a project of mine I noticed that CC11 (expression) is not followed correctly anymore. For example, this curve: .. does not increase expression in the virtual instrument UNLESS i add a "dot" or point everywhere. Sometimes CC11 in the instrument in just increases, then waits again for some time, and increases again creating jump in volume. First I thought this was a bug in the instrument, but I have been able to reproduce this using several different instruments from different manufacturers. Ideas?
Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006
Faderport 8 | Focusrite Scarlett 2i2 3rd gen Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD |
Hi, my MIDI Monitor shows that cc11 follows the curve:
Studio One 6 Pro; OS: Win.10 Pro
Computer: Dell Precision M4700 Mobile Workstation, i7-3740QM 16 GB RAM, 256GB System SSD; 2TB Library SSD; 1TB Projects SSD, 4TB Backup HDD Audio Interface: M-Audio ProFire 2626; M-Audio Air 192-6 MIDI Controllers: Roland A49, Korg MicroKontrol, Korg PadKontrol, Peavey Studiomix, NI Kore 2 |
In the back of the manual when you buy a hardware synth is a midi implementation page.
It shows what and how it responds to midi messages. Same thing with VI, up to whoever made the synth as to what midi they respond to, what they support. That's why you don't use midi volume to control your mix, different synths have different volume curve and none of them is anywhere near linear. Nothing S1 can do to make Instruments do anything, they just deliver the messages.
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account. OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET. Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce. Studio OnePro6 Melodyne Studio Win10 Ryzen 5 3600 - Motu M2 Ventura Mac Mini M2 - Zen Go TB |
robertpaczkowski has mentioned midiMonitor. It's a great little tool that you could use to check if your CC messages are sent correctly by Studio One. That will tell you if it's an instrument issue or a problem within Studio One.
Also, are the instruments VST3 or VST2 plug-ins?
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
Further testing reveals the folling:
If I use my hardware controller, the midi messages show up in de Midi Monitor, and CC's are followed correctly. If I play a track having midi events with CC data, there are no messages displayed - and instrument does not follow. Eventhough I tested and reproduced this on different tracks with different instruments: if I insert a new track and add the same instrument back as before with a manually created new midi event - everything works OK. Why I dont know. Removing Kontakt on the "faulty" track, adding again, adding the instrument again - no difference. Dragging the midi part from the "faulty" track to the previously working test track - and it stop working here as well. Interesting. The other midi part previously created for testing still works ok. Both midi events have the same CC data (tabs) in the midi event (other than the expression curve being slightly different). I am at a loss here. I guess something is different in these two midi events, but what?
Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006
Faderport 8 | Focusrite Scarlett 2i2 3rd gen Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD |
jazzundso wroterobertpaczkowski has mentioned midiMonitor. It's a great little tool that you could use to check if your CC messages are sent correctly by Studio One. That will tell you if it's an instrument issue or a problem within Studio One. Kontakt 6, VST2.
Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006
Faderport 8 | Focusrite Scarlett 2i2 3rd gen Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD |
Tacman7 wroteThat's why you don't use midi volume to control your mix, different synths have different volume curve and none of them is anywhere near linear. I am sending midi data to a violin section (VST). Using CC11 here is common practice. But its usually not linear, this was just a test as my previous fader rides did not go as expected.
Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006
Faderport 8 | Focusrite Scarlett 2i2 3rd gen Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD |
AAV wroteCurious if you draw nodes on the cc11 trace that isn't working, if it then does? It does. Mentioned that in my first post, but yes it works. Of course it will not be as smooth as an actual curved line.
Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006
Faderport 8 | Focusrite Scarlett 2i2 3rd gen Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD |
Coincidentally similar to this post (on clip gain however):
viewtopic.php?p=302563#p302563 |
If related, as a bug introduced in 6.1.1, it would suggest the problem doesn't appear in 6.0.x
(?)
Last edited by AAV on Thu May 18, 2023 1:39 pm, edited 1 time in total.
|
Thanks for the link. Especially that part of adding nodes seem to very much the same kind of behavior.
Its just wierd that copy/pasting the midi notes in a newly created midi event seems to work, eventhough there is nothing else going on that would make a difference (other CC's or something). I had this now on several tracks, so I can agree with the OP of the other post regarding a certain "randomness".
Studio One Professional 6.1.1 | 64bit Melodyne Assistant 5.2.0.006
Faderport 8 | Focusrite Scarlett 2i2 3rd gen Studiologic SL88 Grand | Yamaha YDP-163 | Yamaha HS8 & HS8S | Austrian Audio Hi-X65 | Beyerdynamic DT770 PRO Windows 10 x64 | AMD Ryzen 9 3900x | Asus X570PRO | 64GB G.Skill DDR4 3600MHz | 6TB NVME SSD |
Sorry for the delay in replying. Obviously I have no idea if this is related in any way to the clip gain issue. Perhaps the similarity is unrelated and pure coincidence. The users in that post report that they have initiated a ticket with Presonus. It might be wise for you to do the same, and helpful to them in understanding the problem if you could confirm whether the problem existed prior to 6.1.1.
Best of luck. Sorry again for the delay in my reply. |
Users browsing this forum: Vocalpoint and 28 guests