Even if it can't be done, I'd love to see it attempted. I'm not sure if this would be too hard to realize, but if it is as simple as I hope it would be, (but probably won't be with so many samples varying by instrument, range, and source) one would be able to duplicate the relevant samples, determine the proper amount time to fade it in enough to kill the attack so that it sounds like a slur, and apply that to all of the samples. Similar to how producers chop, splice, and arrange samples with out getting clipping. But rather than completely chopping it off, you would have to fade the sample in, but quickly. I mean using the same exact samples, duplicating them, and cutting of the attack portion of the note. And I'm not talking about finding new samples with slurs for every instrument. So this would be very tedious, and maybe even somewhat unrealistic, but once all the samples are selected for instruments like Violin, Trumpet, flute and any other instruments that have a tonguing/slurring, bowing/slurring, and maybe even plucking/slurring variant (though the latter seems less practical), perhaps slurred variants of those samples could be provided as well. I know I'm not the only one who uses musescore like this, but if I somehow am, that would make the following suggestion completely pointless. And I write notes for it in wherever real guitar shifts would occur. For example, when writing for guitar (or as a simulated guitar) I use a regular guitar sound and then I add an instrument and, using the mixer, replace it's sound with a midi instrument called "Fret Noise" which sounds like fingers sliding on guitar strings. Before using any DAWs I like to write things out in musescore, and I often try to get the musescore playback as close to what's in my head as possible. What I'm about to suggest seems really pointless, but hear me out. Yet, we all love to pursue realism with better soundfonts etc. As we all know, musescore is a notation software, not a production workstation. I know I'm kind of late to this game with suggestions, but I did have one I have been meaning to place here. I am very excited to be able to work with MuseScore-a project that I have long been passionate about-and I look forward to working with all of you along the way! I will be posting a new SoundFont for you to try very soon, so keep your eye on this thread.
SPEEDING UP BPM IN MIDDLE OF SONG RENOISE LICENSE
We are encouraging users to submit their samples under the CC0 license so that we can make as much of this "culturally free" as possible. This licensing has no bearing on scores or recordings made with MuseScore, but only applies to those who want to redistribute the samples in some way.
The new SoundFont will published under a CC-BY-SA license, but many of the contained instruments will be usable under a less restrictive license. For every user-submitted sample included in the new SoundFonts, those users will be credited in the documentation that will accompany the release of the new SoundFont. I cannot guarantee that we will be able to use every sample we are sent. We already have one generous user (ericfontainejazz) who has offered to record his saxophones. I will be posting to this message board with requests for samples as they are needed.
SPEEDING UP BPM IN MIDDLE OF SONG RENOISE FREE
Create / Suggest Instrument Samples: One of the problems with using only free samples is that the available options can vary widely in quality.
Testing: Test out the instruments as they are developed, and let me know of any problems you encounter.Ģ. I would like to avoid any functional regressions with the new sounds.ġ. Instruments that continue to use FluidR3 samples will be updated to scale better with velocity changes (both volume and tone).ĭevelopment versions of the SoundFont will be shared on this forum to get feedback from the community regarding any changes we might make. The plan is to gradually replace the instruments from the current FluidR3Mono SoundFont with higher quality samples and better programming.
Only freely-licensed samples will be used (e.g., MIT, CC0, CC-BY) Address known issues with the current SoundFont, including notes that are out of tune, and the extreme volume difference between PP and FF dynamics.ģ.
Improve the quality of the instrument sounds, starting with those most frequently used in scoring.Ģ. I have been asked by MuseScore to make some major upgrades to the default SoundFont for the next version of MuseScore (and beyond).ġ. Christian Collins, virtual instrument designer and creator of the GeneralUser GS SoundFont.
0 kommentar(er)
