Jump to content

abacab

Members
  • Posts

    9,210
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by abacab

  1. I guess WUP would be handy if you ever needed tech support or a bugfix for compatibility. New features are rare, but the resizable UI and preset browser was added a few versions back. That was the only time I ever paid to update WUP.

  2. 1 hour ago, John Vere said:

    My favorite HOG is the LP multi Band. Put that on the master and forget about editing in real time. 

    FYI, the LP MB has a "non-linear" precision mode that works for mixing. See the "Expert" button for the settings...

    The linear modes are really just for mastering, after the editing is done.

    • Like 1
    • Great Idea 1
  3. 24 minutes ago, mettelus said:

    This reminded me to follow up with a patch issue I was having with LABS.  LABS will load but most of the patches will not, and the culprit is an error in the coding of "junction bypass" they are using. I just sent them the below message and will see what happens. A few vendors do the "drive jump" directory alteration on junctions, but only a couple have mucked it up (Unify and Corel).

    "I have a directory junction from "C:\Program Files\VstPlugins" to "F:\VstPlugins" and most of my LABS patches do not work. I just checked a few *.unify files and the file path is listed as "F:\Program Files\VstPlugins" which does NOT exist. I can replace the LABS in patches, but since the error occurs on load, the rest of the patch is default. There is an error in coding the "bypass" on junctions here (not sure why you would want to do that anyway TBH).  The help associated with this is of no use since LABS is visible to Unify and usable, but the patches are not (a few work, but the rest do not)."

    Contact their support and I'm sure they will assist you.

  4. 1 hour ago, Simon Wilkinson said:

    That's good to hear you've fixed it! I've always had Cakewalk setup that way too (with 'Stop at project end' selected, so I have to loop an empty project) but for whatever reason it doesn't seem to cause an issue on mine. Anyway, well found! 

    That's interesting. I was able to replicate the same "loop" issue on my laptop, which is almost a completely different hardware/software setup from my DAW. Except they are both running the same version of Cakewalk 2022.11, Windows 10 Pro 22H2, and the Wotja 22.9.0 VST3 plug-in.

    1 hour ago, Simon Wilkinson said:

    One other thing I noticed with Wotja in Cakewalk is it does seem to make the now time marker move quite slowly and jittery if the plugin window is open while playing. As soon as I close the plugin's window, the now time marker moves a lot more smoothly.

    Not having any slow jittery display here, but maybe that is just my Nvidia GPU handling that part well for me. I have noticed that some plugins put a heavier load on my GPU than others.

    Edit: I just tested the newer Wotja 23.4.0 VST3 plug-in, and that appears to handle the transport loop OK. Yay! :)

  5. 6 minutes ago, cclarry said:

    If they are going "Sub" exclusively that is the final nail in their coffin

    As kite said...

    1 hour ago, kitekrazy said:

    This will take the hobbyist out of the picture. 

    Is their pro market large enough to carry Waves?

  6. 14 minutes ago, Grem said:

    Here we are complaining and moaning about a sub plan, but what if it is at good price?

    But if it is exclusively a sub like Adobe has, without any perpetual licenses, you would lose the use of your software authorizations if you stop paying for the sub.

    • Like 1
    • Great Idea 1
  7. 3 hours ago, Simon Wilkinson said:

    Hope you have some luck getting it to work but if you've got it working in Reaper maybe that's enough.

    Hey, thanks to your nudge, I finally got Wotja working in Cakewalk! Since you said it worked for you, I decided to do a deeper dive in Cakewalk. So for reference I installed a clean version of Cakewalk on my non-DAW laptop, which is a fairly vanilla Dell i5, with just Realtek audio and WASAPI.

    Wotja ran OK with Cakewalk on the laptop, so I opened up Cakewalk on both computers and went through all of the settings line by line in each.

    • What I discovered on my DAW PC that made the difference was under "Options". I had selected "Stop at Project End", which has been that way since I set it like that a long time ago.
    • Unfortunately, that setting requires an active "loop" in the Cakewalk transport, in order to "play" with empty tracks (no clips) in the project. So I have always been setting an empty loop region of 4 bars or so for Wotja to play while in sync to the Cakewalk transport. I have not encountered any related issues with other plugins.
    • Bottom line, it is looping the DAW transport that apparently causes Wotja to behave badly and overload the DAW.
    • I have reproduced this behavior in Reaper (which I had NOT been using a loop with previously) by enabling a loop there.

    Cakewalk solution: deselect "Stop at Project End", and run the Wotja project without an active loop in the Cakewalk transport. Wotja plays uninterrupted! :)

     

    • Like 1
  8. 5 hours ago, Simon Wilkinson said:

    I'm running a pretty old but stable i5-7500 PC with 16Gb RAM, Win 10, Focusrite 8i6. I've only been using Wotja for about a week but mainly running it as a VSTi in Cakewalk using its own audio output. I have tested echoing it to other VSTi's (e.g. Kontakt/Korg Wavestation) and it works fine but I prefer its own output for now. Haven't had any dropouts yet although I have set the 8i6 buffer size a bit higher than usual (256) as input latency isn't an issue with how I'm using it.

    I'm running a stable i5-9600k PC with 32GB RAM, Win 10, Focusrite 2i2 at buffer size 256, although I've played around with that setting. Tried ASIO and WASAPI with same result even using the Wotja internal sounds. When I use output to VSTi, the MIDI seems to drop out first.

    I've been trying on and off for over a year to get Wotja to run stable in Cakewalk . Basically got tired of testing when I found that it runs without issue in Reaper. Not sure what it could be, as I have been pretty much over everything.

    Glad that it's working for you!

    Edit: see my latest post for a resolution.

  9. 1 hour ago, Simon Wilkinson said:

    Just to chime in, the Wotja23 VST3 is working perfectly in Cakewalk for me. My PC isn't particularly high spec but it's working pretty smooth so far. I'm new to Wotja but bought the Pro license straight away because it looks such an interesting app. I haven't delved very deep yet but it seems there's a lot of scope and the devs are very responsive to feedback (I found a couple of minor aesthetic bugs).

    Just curious what your system specs are and what is your audio setup? Are you driving VSTi plugins in Cakewalk with the Wotja MIDI output?

  10. 1 hour ago, Magic Russ said:

    but I would still have to go with the Triangle patch.

    If I pull up Triangle, or any of the other old 32-bit Cakewalk VSTi plug-ins in CbB, I get a lot of pops & crackles.

    Not sure what's going on. My 64-bit plugins never do this! I normally run them at 48KHz with ASIO buffers at 256. I even tried dropping it to 44.1KHz and upped the buffers to 512, but no improvement. No signs of CPU hits here either. No big deal as I never run 32-bit anymore. Just curious!

  11. 48 minutes ago, Spice3d said:

    I get why John pushes those features. It's cool. It's eye candy. However, unfortunately, I think it undermines how powerful Unify is beyond those things.

    If you really think about it, John came up with this idea after decades as a sound designer and former KORG employee, and more recently with his own PluginGuru "label" that has produced sound packs and presets for many leading synths.

    Unify is apparently the product of all the features he wished he had access to inside of one program that did not exist. So he hired Shane Dunne, PhD Computer Science, to do the programming. https://getdunne.com/

    Shane took John's specs and developed Unify using JUCE, a framework for audio application and plug-in development. https://en.wikipedia.org/wiki/JUCE

    They work together to test and get the features working correctly. A very small team with big ideas! I guess you could say that Unify likely represents John's mind and years of sound design experience in code. That probably explains its depth, and supposedly its appeal to MIDI geeks... ;)

    • Like 3
  12. 6 minutes ago, Reid Rosefelt said:

    It's easy to do and offers a lot of possibilities. 

    The "lots of possibilities" is rather huge, and that IMO is what keeps many potential Unify users away, as in what the heck is Unify?

    There is a clear opportunity for PluginGuru to produce some professional "Unify for Dummies" getting started videos to remove some of the mystery from this awesome tool! That is especially important because 99% of the great Unify features are invisible just by glancing at the GUI, which is rather opaque and not very user-friendly until you get some experience with it.

    But there really is nothing else that compares to what Unify can do!

    • Like 1
  13. 15 hours ago, Starship Krupa said:

    The most clamored-for major feature right now is, I think, an integrated sampling instrument. No matter how many good ones are out there, even for free, a DAW these days should have that.

    Right! I believe that many leading DAWs have added that feature by now. The integrated samplers are usually rather simple in form, and are designed to quickly map (drag n drop) a sample (or a few samples) across the keyboard with some sound shaping features for using them directly in a production, such as selecting sample start and end, one shot or looping, slicing, filter, LFOs, and ADSR envelopes.

    Not to be confused with creating complex multi-sampled instruments like you would use in Kontakt or something like that.

    • Like 1
×
×
  • Create New...