Keni

Yes... That's the point. There's nothing to get now. If you've registered, come back on the 24th. That's when it will be available. They also mention that they will send an email notice at that time too! We'll see...

Though it doesn't appear to be in freezes/exports, while listening/working on a project with Little Plate in it, I get periodic (not equally times) "chirps" Does anyone else get this? ...just now thinking. Maybe increase latency? Maybe it's a result of that? I'll see...

I got a confirmation in Firefox... It tells me to expect an email when it becomes available...

Once again... Days in a row. Opening CbB taking a solid 30 seconds first open. (Not ptoject, just CbB itself)... This never happened before the 2023.09 release but has been constant for me and some of my friends/clients mentioning as well... So something is different in this release that is causing this. Thanksfully, most of the time that's all it is, waiting longer. ...but a few times it leads to CbB lockup and Task Mgr. to close and clear from memory... It's not so horrible, but I wish someone would address this issue and offer reason(s) for this new behavior. It might alleviate some of my concerns...?

Still too steep for the plugin. The hardware is only a wee bit more,

Yup... All the same here. Can't add it to solo, but easily added to Player All The free Liraries I have so far? REmatrix Solo Hybrid Free Blackstar [Multilayer] Blackstar Dusty Racks Free Lots of great stuff in there. So much so that I'm often overwhelmed and simply stick to my GOTOs instead of searching the subtleties....

Yeah, I ran into all of the above.... It seems Play is replacing Lite and being renamed ans Analog Lab V while Analog Lab V is now Analog Lab Pro I too found it strange that the new "Play" which is only called Analog Lab inside, not Play or Lite, is not included in Software Center. I'm guessing it will move into there if upgraded to Pro? Very odd. It doesn't show anywhere in the Arturia online account (my account). It shows Analog Lab 4 here, but that loads as Lite... Confusing all the way but some great sounds, yes?

Not sure who this was actually targeting, but you can find my music everywhere! https://inexile.hearnow.com

just to note... It works fine here. Curious... Did you try using different latency settings? I had a similar problem with Amplitube 5 and solved it changing latency. At 512 it crashed! Disappeared in a puff! At 128/256 it freezes fine... I just say this because the free UA LA2a is freezing fine here, but I've only been running at latency of 128 . That theory just failed here. I can freeze the LA2a at 128/256/512/1024 So that's not a factor here... Sorry.

Not with UAD. It’s working here, but I had same problem with Amplitube 5. Investigation turned up that if I was set at latency 512 is crashed. If I changed latency to 128 or 256 it worked fine. Maybe try it with your situation?

I always liked them too.... they were fun as were echoplex which I also had lots of fun with... But they are/were noisy and emulations tend to leave it in for authenticity... But many offer the option to simply switch it off creating a more modern "quality". These days with how much lower our noise floor is, I fid it hard to justify at times... ...as a matter of fact, I just tangled with this issue today on a piece I'm working on where I'm using two EMT 140 simulations and I keep noticing the noise... as low as it is. In this case I'm living with it as it's so subtle, but often that noise floor is too hard to handle these days (for me) Oh, and I do like the 201 emulation. I'm not dissing it. I'd feel the same if I was sonfronted with using the actual hardware... ?

I thought it interesting to report this... I just got a call from a friend who uses CbB and I've worked with for many years. I told him to get the latest (Update 1) which he did (from the original 2023.09) which he did and he was concerned... He noticed that the program seems to take longer to open... That was with no knowledge of my experiences or the conversations here on the forum, and he's an extremely non-tech user.... So he doesn't sit (like me) analyzing every minute detail... This was big enough for him to notice and call me about with concern... ...just sayin;

Ha! I’m old enough to remember the days of fighting noise everywhere. Minimal issue in digital, but we find reasons to bring the noise back! I gotta laugh! BTW, I have this plugin too and rarely use it because of the noise, but honestly? I rarely used the hardware back in the day for the same reason! ?

My first thought due to my own experience... Check plugins...? Often problems develop for uncounted reasons Hmmm. Win11? I haven't used yet.

Many Thanks Zo! ...always nice to see someone appreciate something subtle... ?

I know the feeling. 32bit should have more depth and subtlety of definition. 64bit even more. So for me it became a decision of balanced features. I'd love to be running at 64bit (128?) but the resource consumption is far too great for the tonal improvement for me at this time. I've got a feeling I will be running at 128 if I live that long! ?

Thanks David... I used to have such a plugin but that was long ago. I'll try this one now. Off on the link...

I didn’t think so (Windows update) You’re hauling quite a load! Interesting settings. Do you have a particular reason for that? (32 bit float) I mean, I understand the increased depth and articulation expected with larger word size at equivalent speeds, but isn’t everything a tradeoff? I currently do my recording work at 24/48 to have a movie film base rate as my standard. I have played with up to 64/48 but the small perceivable quality (for me) was far outweighed by system demands. In this situation above (mine) Amp5 crashes CbB freezing at 512 here. Freezes fine at 128/256 which is where I ordinarily operate. So I’m good. I don’t know how it performs at longer latencies as operating that heavy happens only in certain situations for me and I doubt will get into the picture. Simple enough to remember (for now?) to verify/reset latency when freezing Amp5! ? BTW... on investigation I found a claim to the Audiobox 1818VSL latency of 6?

Sorry to hear you’re having some trouble too. ...but my problem is with opening the program, not loading a project. There is no roll back. This is it. Very shortly, all earlier versions will stop working.

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.

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...

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?

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.

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!

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