Jump to content

abacab

Members
  • Posts

    9,210
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by abacab

  1. 2 minutes ago, simon said:

    yes, and it could have been user error, who knows ?  I assume that user said "waves creative access" because that's what the new Waves Central pushes ?

     Personally I'd advise anyone to wait and see what happens. There is nothing in the updates I need at this point so why risk anything

    good to know it was reasonably smooth for you - be good if other people who are brave enough to update report back too

    Just be prepared for long VST scans in your DAW after the updates. It appears to reset the Waves Shells so it forces a total rescan... 🙄

    • Like 1
    • Thanks 1
  2. 10 minutes ago, simon said:

    I notice that somebody on the Waves Forum reported that the new Waves Central actively uninstalled his V13 plugs ? which is worrying

    https://forum.waves.com/t/waves-subscription-total-disapointment/7007

    That user stated he was "upgraded" to Waves Creative Access". That sounds like a Waves mis-fire (or user error)!

    But regardless how that happened, I saw a caution elsewhere against using Waves Creative Access if you want to use perpetual plugins older than v14. I believe the reason given is that Creative Access only supports v14, and that you should contact support if you need to use both.

    • Thanks 1
  3. 5 hours ago, simon said:

    I think they've removed the ability to install any v11/12/13 plugins too - it's v14 or nothing. 

    The Waves FAQ say to use the offline installer if you need anything prior to v13.

    There is so much missing detail in the FAQ though, so it's unclear to me if you are actually agreeing to any new terms if you update Waves Central or any plugins.  There is certainly something about agreeing to surrender perpetual licences that somebody posted in another thread.

    total sh!tshow - so I'm watching and waiting.

    I updated my Waves Central to 14.0.7. Then all of my v14 plug-ins showed an available update, so I figured might as well grab any updates while they are still available.

    So I installed the updates for v14, and they are still working. The rest of my plug-ins are v12 and are still working, but the install option is no longer available for them in Waves Central. Instead I am directed to a support page via a "Learn More" link: "How to Install and Activate v12".

    Quote

    Learn how to install Waves V12 plugins, via an offline installer.

    Important Notes:

    • V12 plugins can be activated by Waves Creative Access subscription licenses and by perpetual (non-subscription) V14-V12 licenses.
    • Products released after October 10, 2021 are not part of the V12 offline installer.
    • To see a list of the plugins available in the V12 installer, visit this page.
    • Sample libraries for Waves instruments must be installed manually.

    No problem yet, as all of my v12 plugins are installed on my DAW. But reinstalling them down the road could be a pain...

    FYI: the Waves Central update is automatic as soon as you launch WC. So there's no way to continue use the old version of WC... just saying...

    • Thanks 1
  4. I have Reaper installed as a secondary DAW, with Studio One as my chosen go-to. Reaper is a highly efficient, stable DAW.

    The thing I really like about Reaper is that a track is a track. It can route MIDI or audio as needed. It's all up to you what you do with a track. There are no dedicated track types such as instrument tracks, MIDI tracks, or audio tracks. Very flexible!

    So you can insert a MIDI plugin (such as an arpeggiator that outputs MIDI) on the same track as a virtual instrument. Just place it in the plugin chain ahead of the instrument, no second track or special routing setup required!

    Or you can easily route audio directly into an instrument plugin that presents an audio input to the host. One use case would be sampler plugins that can record live audio from a direct input. Other DAWs with strictly defined track types might not allow audio input to an instrument track.

    • Great Idea 1
  5. I'm OK with a company offering subscriptions, as long as they are optional, and an alternative to reasonably priced perpetual licenses.

    What Adobe did is unforgivable. They did away with perpetual licenses for all of their pro graphics software. Stop subscribing and you lose the ability to edit any of your works previously saved in the Adobe file formats. Apparently Adobe has a firm grip on the pro graphics industry. SMH.

    • Like 3
  6. 1 hour ago, msmcleod said:

    Changing MIDI volume will affect notes played after the volume change.  It will not change the volume of notes that are already playing. 

    Good point! And good explanation. I've never tried to automate MIDI volume, as I normally just rely on the volume of the audio track for mixing soft synths.

    The OP had asked how to make the volume go up in a single channel in TTS-1 as in the example GIF. So you wouldn't get a smooth volume rise that way with sustained notes, as you would get jumps as new notes were played.

  7. 21 minutes ago, Grem said:

    I ain't doing no sub, don't want no sub, ain't down with subs at all. They can take that sub and stick it....

    That's exactly how I feel. ;)

    I have some Waves plugs that I really like, and the only thing that I honestly really dislike about Waves is the one seat activation per license. The "industry standard" is usually for at least two. Since I now store my Waves licenses on a USB stick, they are portable - not as convenient, but not an issue for me.

    WUP has always been a la carte, or bundle, and always optional.

    • Like 3
  8. 6 minutes ago, Demii said:

    What if I wanted to make this kind of "increasing volume over time" effect using TTS-1 by myself? How can I do that?

    I think the most popular way for "increasing volume over time" would be to assign a track automation lane in the track header. You can automate a plug-in's audio parameters such as master volume or pan, or MIDI control parameters, such as the MIDI volume for each MIDI ch 1-16. These options will vary depending on the plug-in in use. TTS-1 will show 16 channels, but most plugin instruments only use 1 MIDI channel.

    You can draw in an envelope that will be used to control the assigned parameter over time as the track plays back.

    Using Automation lanes: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.10.html

     

    • Like 1
  9. 24 minutes ago, Magic Russ said:

    Odd, because I update the whole collection back then and haven't seen this until now.

    Right! The DX7 V update was a straggler. The rest of the Collection was updated on Mar 9th... 😉

    • Like 1
    • Thanks 1
  10. 22 minutes ago, bitflipper said:

    And that's partly why I'm curious: Cakewalk's config files are plain text. But I also can't imagine why a plugin would be reading those files in the first place. All of a plugin's communication with its host should happen exclusively via the VST interface. 

    I think plain text config files are just one of the places that Cakewalk keeps it's settings. Seriously doubt that a third party plugin is coded to read a DAW config file.

    I would take that response with a grain of salt.

  11. That's not exclusive to Cakewalk or TTS-1.

    Imported/opened MIDI files can contain MIDI events other than note on and note off, such as MIDI CC controllers or patch changes. So playing the MIDI file back unedited will likely override changes that you have temporarily made to the instrument, as the instrument responds to the time-stamped events in the file.

    Suggest reading up on how to use the MIDI "Event List" view in Cakewalk, as you will need some type of MIDI editor to alter the MIDI file if you want to make any changes.

    Event List view:  https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Views.27.html

    Event List buttons and overview:  https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.46.html

    Editing events and event parameters: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.49.html#1085602

     

    Edit: to simply change the instrument you should use the suggestion in the response to your other post on this topic. 

    Use the MIDI track inspector. http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.3.html#1220713

    • Like 4
×
×
  • Create New...