|
From: Andrew C <cou...@gm...> - 2018-04-03 18:25:06
|
HI all, Long time no see. :-) I have an older sample gig library (Dan Dean Solo Woodwinds) that I'm interested in creating modwheel crossfades for. Would it be out of the question for me to enquire about the future development of a "simple and stupid" automatic crossfade creator for Gigedit? Based on the prerequistes that all velocity layers are "layer" types, would it be a reasonable idea for all layers of all dimensions have their 'crossfade' data start and end points sliced up and split from the available 127 crossfade points, evenly across all layers? i.e Instrument with 3 velocity layers: CF in-start: 0 CF in-end: 0 CF out-start: 15 CF out-end: 72 CF in-start: 8 CF in-end: 56 CF out-start: 80 CF out-end: 120 CF in-start: 73 CF in-end: 113 CF out-start: 127 CF out-end: 127 Cheers, Andrew. |
|
From: Christian S. <sch...@li...> - 2018-04-07 12:06:55
|
On Dienstag, 3. April 2018 19:24:58 CEST Andrew C wrote: > Would it be out of the question for me to enquire about the future > development of a "simple and stupid" automatic crossfade creator for > Gigedit? > > Based on the prerequistes that all velocity layers are "layer" types, would > it be a reasonable idea for all layers of all dimensions have their > 'crossfade' data start and end points sliced up and split from the > available 127 crossfade points, evenly across all layers? Mmmm, not sure if that would make sense. There are already features in gigedit to achieve that. You can either use gigedit's "combine tool" to combine existing sounds to one crossfade layered sound, or you can simply change the dimension type of such an existing instrument from dimension type "velocity" to type "layer". Then the only task left would be to fine tune the crossfade points of that layered instrument. In practice almost all sounds on the market use the same velocity split points for all regions. Accordingly you can just 1. enable check boxes "all regions" 2. uncheck check box "all dimension splits" 3.1. select the respective layer 3.2 adjust/fine tune selected layer's crossfade points Then condinue with 3.1 until all few layers are adjusted. That's probably a 2 minute job or even less. CU Christian |
|
From: Andrew C <cou...@gm...> - 2018-04-13 16:37:38
|
Fair points, I was just hoping to bring some automation, but I'm sure that's not worth the development time on your side :-) Also started another "think-tank" on the smartmidi legato scripting for westgate woodwinds and other(VSL giga instruments? Same principles) smartmidi instruments. After a few days investigation into 'how' the legato should sound/be scripted, I'm nearly ready to write some code.. (making plans for plans!) Watch this space? ;-) Andrew. On Sat, Apr 7, 2018 at 12:34 PM, Christian Schoenebeck < sch...@li...> wrote: > On Dienstag, 3. April 2018 19:24:58 CEST Andrew C wrote: > > Would it be out of the question for me to enquire about the future > > development of a "simple and stupid" automatic crossfade creator for > > Gigedit? > > > > Based on the prerequistes that all velocity layers are "layer" types, > would > > it be a reasonable idea for all layers of all dimensions have their > > 'crossfade' data start and end points sliced up and split from the > > available 127 crossfade points, evenly across all layers? > > Mmmm, not sure if that would make sense. There are already features in > gigedit > to achieve that. You can either use gigedit's "combine tool" to combine > existing sounds to one crossfade layered sound, or you can simply change > the > dimension type of such an existing instrument from dimension type > "velocity" > to type "layer". > > Then the only task left would be to fine tune the crossfade points of that > layered instrument. In practice almost all sounds on the market use the > same > velocity split points for all regions. Accordingly you can just > > 1. enable check boxes "all regions" > > 2. uncheck check box "all dimension splits" > > 3.1. select the respective layer > > 3.2 adjust/fine tune selected layer's crossfade points > > Then condinue with 3.1 until all few layers are adjusted. > > That's probably a 2 minute job or even less. > > CU > Christian > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > |
|
From: Christian S. <sch...@li...> - 2018-04-13 16:52:33
|
On Freitag, 13. April 2018 17:37:16 CEST Andrew C wrote: > Fair points, I was just hoping to bring some automation, but I'm sure > that's not worth the development time on your side :-) Yes, personally I simply would not need such a feature. In the end you have the libgig sources, which also come with a bunch of command line tools. So you could try simply copy paste gig2stereo.cpp (or any other one of the tools) as a starting point and adjust it to create your personal tailored conversion tool which nails down exactly what you need it to do. Be brave, you can do that! ;-) > Also started another "think-tank" on the smartmidi legato scripting for > westgate woodwinds and other(VSL giga instruments? Same principles) > smartmidi instruments. > After a few days investigation into 'how' the legato should sound/be > scripted, I'm nearly ready to write some code.. (making plans for plans!) > Watch this space? ;-) That's how it works. The concept always first. CU Christian |