Jump to content

Fred's Gratis Scores

Members
  • Content Count

    94
  • Joined

  • Last visited

Community Reputation

76 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Great song Barry. Loved the extra presence in the second mix.
  2. Thanks Wookie, hope your monitor situation can get resolved quickly. Thanks Kurt. Thanks Bjorn. For the longest time the working title was "Idea 21-06-28" and "Fantastic Journey" came together almost at the last minute.
  3. It's been a while since I've been on this forum, busy "summering", working on a new articulation template and writing some new stuff. Here's the first to make it out the door, should have it on Spotify/Apple Music, etc. in less than 2 weeks. Fantastic Journey by Fred's Gratis Scores CC-BY (https://creativecommons.org/licenses/by/4.0/) (c) 2021 Fred’s Gratis Scores, some rights reserved. This piece is licensed under Creative Commons - Attribution (CC-BY) and includes license to use commercially and create derivative works. You can download to use in your playlists, repost, or in videos offline and/or on any social media or broadcast platform. If you are able, please credit “Fred’s Gratis Scores” with a link to the download page below. Have fun! Download available at: https://soundcloud.com/fred-evad/fantastic-journey Stems available at: https://www.bandlab.com/freds_gratis_scores/fantastic-journey Instruments used in this piece: - Cinesamples CineWoods CORE - Cinesamples CineBrass CORE - Native Instruments Damage - Spitfire Albion ONE (Percussion, Strings) - Native Instruments Noire - Spitfire LABS Pedal Pads - Native Instruments Pure Pulse Bass - Cinesamples CineStrings CORE #Soundtrack #FredsGratisScores #Cinesamples #CineWoodsCore #CineBrassCore #NativeInstruments #Damage #Spitfire #AlbionONE #Noire #SpitfireLabs #PedalPads #PurePulseBass #CineStringsCore
  4. Sorry for the delay, I've been away from this forum for a while "summering". Here's my completed template (the screen shot was still in progress) using articulations. Enjoy! https://drive.google.com/file/d/1pVg6uScgS-5iPYV8btD4gJV8dzSvbh1W/view?usp=sharing
  5. I use templates extensively and include: Tracks and track settings (Volume, Pan, Gain, MSR/Archive, Pro channel, MIDI settings like negative delay, etc.) Track FX Routing, Buses, etc. Instruments and VSTi settings (it even remembers that Kontakt instruments are purged) Control bar layout Articulations
  6. I'll second this request. I regularly use negative track delay. @Glenn Stanton That's a good thought, but although nudging notes will work, it's extremely labor intensive when you have many MIDI tracks (my projects usually run 20-30) and doesn't allow you do cut, paste, and duplicate whole bars and arranger sections cleanly. Also nudging is destructive, meaning if you nudge, then change tempo the timing going to off again whereas real time negative delay accounts for the tempo when the note is played.
  7. Thanks for the reply @msmcleod. Actually, you can create a Cakewalk Project template (save as .cwt) with track events and articulations, I already have and use a few of these templates. This workflow idea comes from work I'm currently doing to update my Project templates with articulations. This feature request is related to Track templates. As I acquire more virtual instruments, I don't want to add all of them to the template - it takes up resources (even when archived) and takes a long time to load, unload, and save the project. The idea here is to have a smaller or minimal Project template that takes up less resources with instruments I commonly use, then after creating a project based on the template, quickly fill it in with balanced instruments and articulations I don't commonly use with Track templates. Having the CCs and articulations setup in the Track template will save allot of time and not interrupt the creative process.
  8. I'll add my name to this feature request. My standard template is about 500 tracks and not only would help with organization, but also help with the amount of scrolling I have to do (even with one level of folders it alot).
  9. As an orchestral composer, I want the ability to save track MIDI events and track articulation maps with a track template so that I can insert instrument track templates that are ready to use without having to re-balance and setup articulation maps. Use Case: When setting up templates, particularly orchestral templates in my case that use many VSTi instruments, one best practice is to balance the instruments. This is done by writing default CC values for CC7 (volume), CC1 (modulation), and CC11 (expression) to the beginning of the track so that the instrument is balanced relative to an audio output level. To manage resources when using large projects, one could save all instruments as track templates and either start a project with a template of commonly used instruments or start a project with a template that has routing only and add instruments as needed. Unfortunately because there is no option to save MIDI track events with a template, the CCs needed to balance the instrument must be documented and setup again when a track template is imported. This slows the creative process. The same applies to Articulation Maps. If the articulation maps used on a track could also optionally be saved with a track template, if a default articulation is set at the beginning of the track it would also not have to be setup again. This feature would be helpful so that as VSTi instruments are added to a project, the creative process is not interrupted with setup tasks. Thank you!
  10. Absolutely enjoyed the music and all the cool visuals in the video. ... and I did notice you got a "sign of the times" element in the opening shots when the guy takes off his face mask.
  11. Fred's Gratis Scores

    Hope

    I downloaded the free Yangqin VST instrument from Native Instruments over the holidays and have been wanting to do something with it since. Here it is... Hope by Fred's Gratis Scores This 80pbm piece features a Yangqin (Chinese Hammered Dulcimer) and Yueqin (Moon Guitar) with the orchestra. CC-BY (creativecommons.org/licenses/by/4.0/) (c) 2021 Fred’s Gratis Scores, some rights reserved. This piece is licensed under Creative Commons - Attribution (CC-BY) and includes license to use commercially and create derivative works. You can download to use in your playlists, repost, or in videos offline and/or on any social media or broadcast platform. If you are able, please credit “Fred’s Gratis Scores” with a link to this song's SoundCloud page. Have fun! Download available above or on SoundCloud. Stems available at: www.bandlab.com/freds_gratis_scores/hope Instruments used in this piece: - Cinesamples CineWoods CORE - Cinesamples CineBrass CORE - Native Instruments Damage - Spitfire Originals Cinematic Percussion - Spitfire Albion ONE (Percussion) - Amplesound Cloud Drum - Spitfire Labs Moon Guitar - Native Instruments Play Series - Native Instruments Factory Selection - Native Instruments Yangqin - Cinesamples CineStrings CORE #Soundtrack #FredsGratisScores #Cinesamples #CineWoodsCore #CineBrassCore #Spitfire #OriginalsCinematicPercussion #AlbionONE #AmpleSound #CloudDrum #GuitarM #SpitfireLabs #LabsMoonGuitar #NativeInstruments #NativeInstrumentsYangqin #NativeInstrumentsPlaySeries #NativeInstrumentsFactorySelection #CineStringsCore #CakewalkByBandlab
  12. I almost did this time. I'd like to take part in the early access if I can time it so I'm not trying to finish up a project.
  13. I use Cakewalk with BandLab and was excited to see the feature where you can open from and publish to BandLab directly. I've spent a little time playing with it this morning and noticed a few things: Muted tracks in my Cakewalk project are not muted when uploaded to BandLab. My use case is that I want to upload the MIDI tracks with audio stems so that when the project is forked, others can use the stems and have the MIDI to figure out the chord progressions or just start fresh with their own versions. Unmuting tracks that I set to muted renders them on the revision when they are not supposed to be there. To work around this I need to manually open the project on BandLab, mute the tracks, and save which creates another revision. After fighting this for a while, I found out that an instrument track counts as 2 tracks toward the publish limit of 16 tracks. I had to manually spit the instrument track and select only the MIDI or audio that I wanted included to publish. Perhaps you could only count an instrument as 1 track, and automatically publish the MIDI if the instrument is not frozen, or the audio if the track is frozen. If we really do want to publish both the MIDI and audio, then the user can split the track and select both (or ideally not have to select both if the track count is still below the maximum). I understand the track limits as each audio track takes up space on your servers. However, this makes collaborating using the publish feature difficult for those that compose in the "Classical" category (all the woodwinds, brass, and strings alone are already much higher than the limits). If I ask a collaborator to add a solo violin that I don't have, they would have to render the audio, and increase the audio track count. I'm not sure what the solution is that respects BandLab's servers and allows higher track count composers to collaborate using this feature.
×
×
  • Create New...