Jump to content

Keni

Members
  • Posts

    2,282
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Keni

  1. 59 minutes ago, sjoens said:

    When you removed them from the project, did you save-as, close CbB, and reopen?

    Also, looks like there's no Pause key... or Print key on your keyboard, but they may be assigned to F14 & F15 as on mine.

    No. I did not. That's more than I was prepared to do. I will have to duplicate the project then experiment on the copy so as not to lose my work while testing.... Maybe tomorrow?

    Thanks for the thought. I didn't think of this.

     

    I'll try the function keys you mention...

  2. 2 minutes ago, John Vere said:

    Labs I found Buggy. I like some of the sounds but I had some issues a while ago and narrowed it down. I didn't bother to install it on my new computer.  

    Thanks John.

    i removed Labs from the project. Made no difference.

    If the synths are frozen, they should jot be adding resource demands anymore.

     

     I’m hoping Jonesy sees which key on my keyboard translates to "pause" as it’s a strong suspect.

     

  3. 22 minutes ago, gustabo said:

    What you are describing 

    Now why would anyone want to make the PRV response delayed and stuttering? I thought maybe pause scrolling or some such? Are you sure that's what it's supposed to do?

    Please help me by telling me which key is the pause key. I use a very unusual system and my keyboard does not have that old familiar label (This is a Mac Pro which I run only Windows 10 on as my DAW with Xeon 12 core with multithreading at 3.06 and 128 GB RAM)

     I remember that it's one of the home/end keys section, yes?

    Once I know, I will unfreeze the track and see if that key changes anything related to this.... Thanks... A good lead to pursue!

     

    I just opened a similar project with

    Same Superior Drummer 3 (unforzen!)

    Same VSampler Unforaen)

    Same B-3x (frozen

    UA Moog (Frozen

    Cherry CA2600 (forzen)

    and one frozen guitar track using Amplitube 4

     

    In this project, even with two synths unfrozen, my PRV is behaving normally to edit either/both.

     

    Same latency setting etc. Yes, it's slighly less loaded (no Labs and only 1 guitar track)

     

    But it's again mostly frozen...

     

    What is the problem in the other project? Could it be LABS (frozen involvement? That's the only very new (first use) device in my project....

    Hmmm... I will remove the Labs synth and see what follows. Frozen, it shouldn't be such an issue, should it?

     

    Nope... Even with the Labs synth removed from the project with it's tracks, PRV is still making dream of the fab handling of a Mac truck!

     

     

  4. 24 minutes ago, David Baay said:

    I don't have much to offer other than to suggest you have another go at finding an affordable x64 substitute for VSampler. If the issue is related to Bitbridge, you might try the inexpensive 3rd-party Jbridge if you're not already running it. Bitbridge has an issue that it adds and empty buffer of audio to bounces/exports; Jbridge doesn't have this issue. It also solves the problem that having a 32-bit UI focused unavoidably grabs all your keystrokes so, for example, you can't start/stop the transport with Spacebar while working in the UI. It's cheap, but you can demo it first:

    https://jstuff.wordpress.com/jbridge/

     

    Thanks David, but that's not the problem here. I've been using this plugin since it was first given bundled with Sonar many decades ago! 😉

    It has continually worked fine and I do use it on almost every song I work on. This current situation has only been within this last week... With same plugin.

    If I open an empty project and insert the synth with all my typical plugins and a 4 minute bass track (MIDI) PRV is working fine. At 128 buffer all is normal.

    On this project I'm working...

     

    There are many very resource hungry plugins in the project.

    Including Superior Drummer 3

    VSampler

    IK's Hammond B-3x

    UA Moog

    Labs

    Cherry's CA2600

    ...and three guitar tracks using amongst other fx, virtual amps (Amplitube 4)

     

    But all tracks are frozen except the VSampler track. As mentioned earlier, very few plugins running in busses.

    Yet my PRV is behaving as if I was trying to run all those synths unfrozen simultaneously???

    I don't get it. What's weighing the system down with so much frozen? Why is PRV behaing as if there's more load than there is?

     

  5. This has been going on only the last few days so I must have accidentally changed something?

    In a somewhat large project (for me Probably over 20 tracks) with all tracks frozen but one. An old 32bit plugin I use in near every project (VSampler being the only one I can affor that will play my giga bass library). Normally it's as lightweight as can be, but right now opening the PRV takes many seconds of the screen slowly flashing and re-adjusting itself trying to get to it's goal. It does this with every screen movement and edit.

    With all tracks but this frozen, there is only the waves Abbey Road Studio 3 plugin I use for my monitoring all projects, Soundtoys Little Plate VST2, Sonitus Modulator and Sonitus Delay. Nothing that should be causing this kind of response...

     

    I would appreciate any thought any of you have about this. It's suddenly like this. Never before with such light load

     

    Thanks...

  6. 3 hours ago, Kirean said:

    So I bit the bullet and installed one of the plugins.

    When you open the plugin, it asks you to activate which opens up the browser and you need to log in to your account. Then you need to press activate a few times more. Doesn't seem like there's any method to authenticate offline. Can't remember if it was there before, but now in the settings for the plugin there's a spot to de-authorize it. There doesn't appear to be a way to do it via your Moog account nor is there list of activations either.

    So yeah. Might want to stick to the older versions as the experience didn't really improve by getting rid of the iLok stuff.

    Guess I'll need to find out whether or not I've got those old versions backed up somewhere.

    Hmmm...

    So they are allowing iLok to stay in use instead of changing to this proprietary system?

  7. 14 minutes ago, satya said:

    I wanted the Eight Voice instead of this but this too is nice

    Yes! The 8-voice is astounding. It was the first synth I bought from them. I got their' Voltage Modular for free previously and was very impressed.

    Know that this single SEM truly is as excellent and "perfect" as the modules in the 8-voice.

    I like their stuff. Not only beautiful virtualizations of the analog originals, but priced so inexpensive that most of us can afford them.

    I have of theirs:

    Voltage Modular

    8-Voice

    Memorymode

    CA2600

    Stardust 201

    Oh, and of course now the SEM!

     

    and use them often!

    • Like 3
  8. 35 minutes ago, Kirean said:

    I mean, it could be less of a hassle and less restrictive than the original iLok authorization. Maybe it's just a serial with no internet connection required? 

    Maybe...

    It’s hard to say, but with it already installed and working, I hate such risks...

    It is funny though. When iLok first came out I was hard set against it and avoided it as it caused many problems on PCs of the day. But as connectivity has improved it has become mostly innocuous. It even offers some very beneficial features being able to move licenses between machines can be helpful.

    At this point I have many products on iLok. Most on a dongle. A few on the pc directly and even 1 or 2 using cloud iLok. I’m nit happy with the cloud method but so far I’ve had no problems...

    • Like 2
  9. Yes to all the above.

    This is where it began.

    Tom built this to run with a separate device he built, a sequencer!

    Then beefed it up to 2-voice, followed by 4-voice and finally the 8-voice.

    A true masterpiece!

    I already own Cherry's fabulous 8 voice, so this is real gravy for me.

     

    That said, I do own (sitting in storage) a 4-voice (hardware) SEM that was gifted to me after the owner took 2 of the SEM modules and the programmer to turn his 6-voice (we were using it for guitar synth so 6 was all needed) into a full blown 8-voice. I was gifted the remainder. Keyboard is internally electronically disconnected but easy to re-connect. No programmer however. Two original SEM modules! In my current situation I sadly have no room to bring it in. So it waits patiently for the day of my return. 🙏👽🎸🎶

    • Like 3
  10. 1 hour ago, SloHand Solo said:

    Here are the Shreddage Guitar articulation maps I created, if anyone needs them.  Every key switch is mapped, and you're able to use more than one articulation at a time by stacking them in the PRV Articulation lane.

    I attached Hydra, Jupiter, and Rosette Acoustic Guitar.  The other guitars have the exact, or very similar mappings, so you can use any of them for a template if you have one of the others.

     

     

    Hydra.artmap 18.03 kB · 0 downloads Jupiter.artmap 16.78 kB · 0 downloads Rosette Fingerstyle.artmap 13.12 kB · 0 downloads

    Nice of you to share.

    I don’t have need, but if you wish to reach others with it, you might post this in the appropriate forum. There is one for articulations. I will look and then edit this to show you were it is if you haven’t already found it.

     

    Ah, yes. In the Content forum, there is an Articulations sub-forum

    • Like 1
  11. 1 hour ago, Sven said:

    Thanks User 905133.  Your answers were very helpful.

    I've now got a default of 'show velocity for highlighted notes only'.  I've set up Alt-V to toggle show velocity for all notes.  I usually only want to see velocity for highlighted sections but I can quickly see everything if I want.  Or click where there are no notes and see no velocities.   Perfect.

    Thanks!

     

    Another thought?

    Using the show selected option, then opening the controller view (alt-c) inside the PRV would show all velocities?

  12. Just now, msmcleod said:

    Just be aware guys, this is a holiday weekend in the US, so there will likely be a delay in getting through all the applications / NDA's.
     

    Thanks Mark!

    Congrats! Kudos! Happy Everything!

    I hope you and the Bakers all had wonderful holidays and with much excitement congratulate all of you on getting this happening!

    This part of the wait is faaar easier! Waiting extra days or even weeks or such after waiting with no progress bar! 😉

    I'm hoping I get accepted for testing. I'm so looking forward to this!

  13. 18 minutes ago, Jeremy Oakes said:

    Thanks Keni, maybe the doubters will now believe  !!!

    Yes, maybe...

     

    I don't sweat it... I'm too busy being excited that it's this much closer to on my desktop!

     

    I'm praying with all my heart that they accept me for beta testing.... One never knows! 😉

     

  14. Yes! It's true!

     

    They are accepting applications for doing Sonar Beta!

    This just opened. This is not the beta for Next.

    I signed up as fast as my typing would allow! It's coming!!!

    🙂 Happy camper... Excitment rising...

     

    • Like 3
  15. 1 hour ago, Starship Krupa said:

    The headquarters of both companies is in a tiny town just outside one of the entrances to Yosemite National Park here in California.

    Having participated in their beta program enough to get my name in the credits for the Mixcraft 7 release,  something I can tell you about Acoustica is that they are one of the most quality-minded software manufacturers that I've ever dealt with. So please report your experience and findings about this performance issue to them. They will likely want to know about it and work with you and the BandLab Cakewalk engineers to fix whatever is.

    Good question, and one that I can't really answer. Without being able to read the minds of the folks at Steinberg, there's only speculation. It could be that there were starting to be too many extensions to the VST spec that weren't controlled by Steinberg, and they feared losing their grip on it.

    Maybe they thought that being able to announce a shiny new technology that their own DAW's would be the first to support would be good for marketing.

    Maybe the Cubase/Nuendo developers were having a hard time working out sidechaining support in their apps and wanted to force that work onto plug-in developers.

    Whatever drove the move, as far as I can see it backfired. Other manufacturers (correctly, IMO) saw little advantage to supporting the new format. Rather, it only increased their coding and testing burden. Adoption was slow. When they finally applied their legal muscle to force new developers to adopt the format by refusing to issue more licenses to develop VST2, it served as an alert to participating vendors that Steinberg had too much of the wrong kind of control and that a more open and flexible spec might serve the industry better. So now there is CLAP, a competing plug-in format.

    As for CLAP, as long as Steinberg continues to play nice, I don't think it will become the dominant format. But I'm glad it exists, because it serves to show Steinberg that if they do try any more funny business, the industry has other options

    My suspicion is that if you ask anyone in the business of developing plug-ins or hosts for them about VST3, they'll tell you that the canonical DLL location is the only thing that they benefit from. I'm sure it eliminated a LOT of easily resolved support issues. However, I was so used to using custom locations for my VST2 plug-ins that I initially tried doing the same with VST3's, which of course didn't work too well....

    Is it that VST3 doesn't support it or is it that plug-in and/or host manufacturers stopped supporting it?

    Communication between host and plug-in regarding presets in general seems to have gotten lost along the way. Where it seemed like most VST2's relied on the host for preset management, and reported their own presets to hosts' preset managers, in the VST3 era, this isn't the case. Now it's unusual for a plug-in to use that part of the spec to report their presets, and every plug-in has its own proprietary preset manager. Which can be hard to find and quirky to navigate, depending on the developer.

    The VST3 spec does call for a canonical location for .vstpreset files, but few plug-in companies use it and Cakewalk's support for it is clunky. That's a drag, because I like using the host's preset manager more than the ones within the plug-ins, which have to be learned for each different manufacturer.

    Interesting stuff...

    Clap, huh? I've managed to avoid that one these days. 😇

    Funny, but I always use Cake's preset mgr. so much easier to me than a dozen different systems.

    I guess Microsoft is determined not to upgrade WDM to pick up the slack. It always worked fine for me.

    Oh, and I did contact Cherry about their latency issue. The did improve that considerably not long after. If I use the vst2 versions I can operate at 128/256 which is ok with vsynths most of the time.

    We're really due a major improvement in digital audio processing speed (latency). It’s truly a severe roadblock.

×
×
  • Create New...