Posted
When you have a figure that loops where you've recorded CCs, for example velocity layers why doesn't the CCs loop with the figure?
Say I have a figure where woodwinds are just supporting strings and I've recorded the figure with very low values for CC #1 just as a supporting timbre, then when the figure loops CC #1 is reset and now the woodwinds are blaring which means using a looping figure is pointless.
Isn't there a way to have everything recorded in the original figure also happen when the loop takes over?
Mo., 20.05.2013 - 21:23 Permalink
Sounds reasonable. To me this looks like an unwanted effect. Recorded CCs should default to the take length too.
So., 09.06.2013 - 07:33 Permalink
I have the same problem with wind controller. Also, afer recording if I move
a note, I have to move the controllers (3 or 4 cc). Is there any way to link
the position of the controolers with figure?
So., 09.06.2013 - 12:36 Permalink
^ yeah CC's should be connected to the notes so they moved with it, but that's a VST3 feature I think.
It becomes a real pain with for example Samplemodelling instruments, they are extremely flexible and use a ton of CCs to control every little thing and moving notes after recording is very time consuming because you end up with 5+ CCs that also needs to be moved.
Mo., 10.06.2013 - 02:15 Permalink
@KenDK
^ yeah CC's should be connected to the notes so they moved with it, but that's a VST3 feature I think.
No ... it's a DAW/ Sequencer feature that permits copy/ paste/ duplicate/ move of sections of midi with CCs. Pro Tools does this and it doesn't have VST3.
Another reason I prefer to stream midi with virtual cables to my DAW.
Prado
Mo., 10.06.2013 - 06:17 Permalink
Yeah I know some daws have this, but it's also a feature of VST3 called "Note Expression" or something like that, basically each note has their own CC, mod and pitch wheel data.
But yeah, it would still be great to have in Synfire not necessesarily pr. note, but just the cc data moved with the current selection, because who knows how long plugin companies are going to drag their feet getting vst3 implemented, just look how long it took getting 64bit support.
Mo., 10.06.2013 - 07:54 Permalink
Ah ... I see what you mean. You were referring to "notes" in the sense of the individual 'note' as in VST Expression. not as 'notes' in a midi track.
Actually I believe it is a little more complicated as VST Expression requires specialized VSTi software to process the 'note' information. Only a few of Steinberg's VSTis can do this and I haven't heard whether any other developers have developed any ... well ... VST3i instruments yet.
AFAIK, all major DAWS, i.e., Cubase, Logic, Pro Tools, Digital Performer, Sonar, Reaper, etc., permit moving CC and automation data with selections from a particular slice/ section of a track.
I am eagerly awaiting the coming 'new and improved' Synfire. I really wish most development was focused on the AI and compositional aspects of Synfire ... as well as making it more 'user friendly,' than on trying to compete with the myriad features of an advanced DAW.
Prado
Mo., 10.06.2013 - 17:17 Permalink
I am eagerly awaiting the coming 'new and improved' Synfire. I really wish most development was focused on the AI and compositional aspects of Synfire ... as well as making it more 'user friendly,' than on trying to compete with the myriad features of an advanced DAW.
+1
Please improve those features and capabilities that distinguish Synfire from all those DAWs on the market and define its uniqueness (compositional AI, "Tonsatz", recognition and "understanding" of music, separation of different aspects of musical parts, re-usability, hierarchical structure of arrangements etc.)