Jump to content

Keni

Members
  • Posts

    2,176
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Keni

  1. Ah... many thanks here for many things. I wonder how slow/long my 1818vsl is in comparison? The USB generation makes big jump differences. I wish I could address this but at this point in my life I am now working with a Mac Pro "trashcan" so though it’s a decent machine unto itself, it’s connectivity is severely limited. No add in card capability. No pcie connectivity. so I’m limited to TB2 USB3.(0/1 specs vary). The TB2 is ever so slightly faster than that generation of USB3 ...but I digress. My apology for getting off topic... again.
  2. Thanks David... I'll look at that too. I’m a bit reluctant to do a program wide change for this one plugin issue. First I will live with the forewarning and work arounds if/when I again use Amp5 instead of Amp4. I really miss Amp3. The only plugin (of consequence to me) lost on this machine moving from my older win8.1 DAW to this win10 DAW. Addendum? I just booted up, opened CbB (which opened at normal speed), loaded the song, unfroze all instruments/tracks, then carefully (?) froze one at a time leaving the Amp5 track for last. Shaky finger clicked to freeze the Amp5 track and it froze as expected... So regardless of if anyone else is seeing this on their' systems, here it's becoming more certain that there's something going on between Amp5 and CbB where it doesn't like freezing at 512. I didn't try higher latency, but going back to 128 solves it every time. Which isn't really too bad for me here as 512 is far too long for live performance so I'm rarely ever out there except when special circumstances arise. I'm almost always at 128. My system will run faster (64) but even with Xeon 12core with hyper-threading, and 128G RAM, so many of the recent generation of plugins have become far too demanding for more than carefully selected and setup uses. It seems my only other recourse is to sell my sould for an interface that has better latency performance than this old Presonus Audiobox 1818VSL I've been so (mostly) pleased with. Is there a listing anywhere that compares relative latency of the various interfaces on the market. It seems that none specify any realistic info about such in their specs... or at least I've not spotted such. Interesting piece my heart is drifting towards (not that I can in any way afford it) is the new Arturia AudioFuse 16. But again no mention of latency specs. If it's a matter of USB bus speed, I'm stuck on a Mac trashcan with usb3.0/1 (I'm still uncertain seeing both quoted in machine specs and not finding such locally). Sorry for the rant... It's one of those days for me...
  3. I wonder what's going on here. I didn’t have any of these problems before this final update 1. These are all things I do constantly. Was there a windows 10 update this past week?
  4. Thanks Lynn. I don’t know if you've read my other responses about this, but I verified that A5 is crashing here when I attempt to freeze at a latency of 512. When I change back to my usual 128, the crashing stops.. I went back to 512 to verify and sure enough, crash! back to 128 and it froze as expected.
  5. Thanks... Interesting that both you and gustabo immediately thought about the scanning... As I mentioned in my reply to him, I hate running the scanner and don't allow it to run on startup. This plugin had been freezing fine here until this so the scan should still be what it was. I'm more leaning towards my recent ability to freeze after lowering the latency back from the unusual here (512) to the usual 128 but I need another experiment to verify if this indeed changed things... OK... Verified I believe. I closed CbB, then reopened it, loaded the song, unfroze and successfully refroze Amp5 while latency set at 128!
  6. Thanks I may try that too at some point. I hate running the scanner... and this plugin has been working fine here for quite some time. That's why I'm posting in the feedback thread instead of general Cakewalk forum
  7. I just tried something that seems to have worked but it will take some more times trying this to verify. Normally the fastest latency I run here is 128 but I had it raised to 512 to deal with the use of Amp5 in this situation. I just lowered the latency back to 128 and Amp5 froze fine this time?
  8. OK... This is really crazy... I just opened the same song to work. I unfroze the guitar track and ctl-drag copied the clip (8bar) on it. Then went to re-freeze and once again CbB is crashing from Amplitube 5. I'm gonna go back re-launch CbB, Open the same song file, replace Amp5 with Amp 4 and begin the replacement process I posted in my previous message about this issue (above) I know I'll get it to freeze again after enough changes between plugins as I did before. .. or at least I believe I will. This is frustrating. I avoided both Amp4 and Amp5 continuing to use Amp3 being so much more resource efficient and still decent sounding. Then I moved up to my new DAW with win10 (I was on win9.1 on my previous DAW), I discovered I can't get Amp3 authorized here. Another calamity of the changeover to Microsoft control of signing ID and all it's issues. So I switched to Amp4 and all is well except that I lose a few amp models that for whatever reason(s) didn't make the transition over from Amp3 so I began to think, I might as well move up to Amp5 where I have more available than Amp4.... which brought me here today. I do like the sound I'm getting from Amp5 better than the closest I've come to same setup in Amp4 but at least it freezes ok. Is anyone else experiencing freeze issues with Amplitube 5? Keni Oh yeah, things are stranger yet... I did my best to repro the successful procedure I used earlier and it disn't work, so I though about it and remembered an error that happened while doing the successful event. That was accidentally, I loaded both Amp4 & Amp5 into the fx bin before realizing it and then deleted Amp4 to fianlly get a successful freeze of Amp5.... And that now worked twice as a work around here it is boiled down Work my part enjoying Amp5, then (this will require a bit more experimentation to see what I can .successfully trim out of it) Place Amp4 into the FX rack with it and then see if removing Amp4 then allows Amp5 to freeze. If not, the longer and now twice successful method was to replace Amp5 with Amp4, Freeze, unfreeze, replace Amp4 with Amp5 and finally get Amp5 frozen! <sheesh!> Am I the only hangout using Amplitube 5? ...or at least trying to?
  9. After crashing twice in a row attempting to freeze a track, opening CbB took near 30 seconds as opposed to the usual 3-5 or even long taking 10.... I was ready to relax about it and simply wait it out seeing 10 seconds appeared the longest, but this time 30? I don't understand but right now I've gotta figure out why it's repeatedly crashing instantly hitting the freeze button. I will begin by removing one little used but now thinking that's on a send buss? More investigation needed. This is a simple 8-bar mono guitar (DI) running through Amplitube 5 I've never had this happen before. Cake drops like a hot rock. No crash warning etc, jut gone! Only unusual plugin is in the fx bin of a bus to which this track is sending. That's first to be removed in this experiment... OK... This one is a surprise. Turns out it's Amplitube 5 that crashes attempting to freeze. New here. Going to substitute Amplitube 4 and see... OK... Back to the drawing board. No answers. I rebooted, loaded CbB and song, once again attempting to freeze Amp5 and it crashed... Re-opened CbB and song, replaced Amp5 with Amp4 and the track freezes fine... Replaced Amp4 back up to Amp5 and guess what? The track froze correctly! ...those little gremlins are getting tricky! Keni
  10. Thanks Tom... Possibly. This is my only machine running this update of CbB... My other machine is far behind (good self-reminder to update it already?) and my other machines far too old.... It's not the end of the world if it's as simple as waiting the extra few seconds to load, it's more knowing it's ok, be patient and wait.... That's hard! 😉 As I said previously, when it actually did lock up my machine a couple of times (previous release) that brought me to even pay much attention to this possible issue. Thankfully it has not done that with the latest/final update... OK. I'm off too bootup my older win8.1 system and update CbB there too! Keni ...Ha! That was painless. win8.1 DAW, I updated both the program and the offline help then needed to signin to Bandlab which of course I expected having not done so on that machine in quite some time, but it activated instantly with my signin... Excellent!
  11. Thanks t... It's not so much the length of time it's the suspense of "has something locked up/gone wrong" that quickly becomes a concern... 👀 In the previous release I actually got forced to Task Mgr to stop then restart CbB. That hasn’t happened with this release, but it’s recent in mind, so when it takes a full 10 seconds or more for the empty program to open, I grow concerned.
  12. I was about to post a similar response. ..and remember that all modifier combinations are available to be used including ctrl-alt-shift, so performing a drag operation during such an execution may be necessary... yes?
  13. Sorry I can't help with the SoundID issue, but this other issue is still on my mind... The Opening of the program itself. No song file. Sometimes it opens normally and sometimes it takes longer.... and sometimes it takes much longer? Nothing else is running on my DAW any differently at any of these times. I set everything to manual everywhere. So this is a thought.... Might it have to do with verifying activation etc.? That would quickly supply a reason for the varying lengths of time as the internet through speeds vary constantly.. If this is the case, can't the program finish opening with it's current status and have that verified after it's open? It would go a long way to comfortable launches. So far my Windows 10 experience still pales to how much more cleanly and easily my win8.1 system still runs, but this stuff makes it feel like 3 steps forward, two steps back...? I know this CbB issueproably has nothing to do with that, but I'm on a roll...
  14. Exactly... It's on going, but becoming a paid version. I think of it simply as the next major update as compared with simply bug fixes as this last update is. They froze the feature set etc so all new features will appear in Sonar. I'm guessing there's other new things. More than the big issue of the vector graphics change, but they are in the upcoming version (Sonar, not CbB).
  15. Keni

    DarkSky Socora FREE

    Thanks. I kind of guessed that but thought I'd ask...
  16. Keni

    DarkSky Socora FREE

    Will it run in the free version of Kontakt?
  17. Very true, except these things need fixing going forward into Sonar. I think it's possible that many of these fixes may be applied to both programs? For us, it's unknown the extent of differences. For example, I doubt they're gonna re-write the audio engine in this changeover. There may be some surprises, but the only thing I/We know for sure is that the gfx portion of the UI has been altered to be vextor based gfx.... Everything else (afaik) is the continuation of Cake/Son
  18. Thanks Jonathan! Once again you are quick to the rescue! I'm off to do it the long way! 😉 OK... Update finally installed.... this was a rough one though.... Not only wouldn't the updater respond, but after downloading the installer from the web page as suggested, when I ran it, nothing happened for near 5 minutes when I went to inspect. Seeing only a taskbar icon with nothing happening, I then opened Task Manager to end the process and try again but when I was about to proceed it notified me that setup was running, so I chanced a bit more wait and finally the installer ran. Changes in the install windows had me a bit uncertain of how to proceed without possibly wrecking my established setup (I hate having to rebuild that!) but finally it is installed and appears working. Now gonna check for whether it has left me "signed in to Bandlab") as expected etc... Not trying to be a pest, but... Please get Sonar out soon so we can escape all this (almost) pointless issues with a software that's ending... Thanks for everyone's hard work. It looks as though you Bakers really put a hard push into getting as many fixes as possible into this final release.... Many Kudos! Keni
  19. Ouch! I responded without noticing the new update! Still trying to get it but I keep receiving the error message: validateUpdateResponse: client request failed (0) Overloaded server? or..... Sheesh! Still the same.... I keep trying. Including closing and re-opening CbB but I continue to get this response.... I'll wait longer.... What else is there to do? ...and 45 minutes (or so) later, still the same. Frustrating!
  20. Interesting... Not the case here. It consistently takes it's time loading with spinner than ever before. This is a relatively new Computer build and essentially does nothing but Cakewalk/Sonar and related internet. I did not have this lag prior to this update. 2022.09 was much faster opening...
  21. I have always avoided using that kind of stuff while recording outside of Dolby/DBX noise reduction back in the day. The chances of losing some stuff while recording has always out weighed the noise issue. Safer to remove it later. Luckily, these days, tech has evolved to a relatively decent level. Far fewer noise problems than in the past. ...but when it perks up it's scratchy little head we have bluenoise to help!
  22. Not to worry... We all suffer the issues of typos! 😉 This is true for all forms of art. It is very rooted in the actual living experience of the times it was created and trying to feel that is truly difficult if it hasn't been experienced. So as for scientific examinings, again we face the changing/evolving of technologies. So many people still vie for vinyl... Me? I've got a fairly large vinyl collection which I never listen to or plan to. I grew up with 78's before LP was invented! 😉 I have all the pops and crackles and skipping etc. that vinyl suffers as well as understanding the RIAA curve and it's reasons for existing as well as the horror it places on quality reproduction.... Not a great technology but I was thrilled with it when it was all there was. Each medium has it's good/bad aspects. Early CD tech suffered when they thought to get away with a single DAC converting the audio and the incredible loss of depth that resulted... But it was overcome and continues to improve. Maybe one day we'll have "natural" digital recording where it's analog-style continuous? Who knows? I just hope that in your musings you find the good in things always!
  23. For me, being old enough to remember these artists first appearances and seeing most of them live... Some of the appreciation of these is understanding the times and what existed before. The Beatles performed with no monitors through most of the band's live performances! Things were different on many levels! BTW, Not "defending" something that needs no defending. I can’t count how many songs/artists I dissed over the years only to find hindsight provided a very different perspective. So many styles/genres which each contain interesting elements even if I’m not attracted to such styles. Time changes everything! I've managed to love all of these in their' time and continue to find and enjoy new artists and things. They are each additional, not replacing and uniquely tied with the times they flourish. Sometimes I find myself seeking to remember/imagine the mindset of my avatar in those times/places. Some of which I did live through. Sheesh! Drum hardware became more solid and stopped shaking all over the sad flexing risers! Ha! Now everyone accepts stomp boxes. They all bitched at me for all the gadgets and wires... are things better now? I don’t believe so. Only different. Much has improved, but so have our expectations increased.
×
×
  • Create New...