Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Jonathan Sasor - thank you for your engagement with this. I have PM'd (in three parts) the relevant files. Edit - I have also added a link to an (18GB) dmp obtained by procdump64.exe during the memory-hogging phase.
  2. Well, I'm happy to report some positive progress here, at last. I can load the AAS instruments now, quickly and successfully with no sign of the memory-hogging. The key was resetting my entire AUD.INI to default (something I did after AAS's tech guy asked me if I had altered anything from default, as he could not replicate the behaviour). It occurred to me that, as I have used Cakewalk for many years, the init file has presumably evolved along the way. The first use after this was not encouraging. When I attempted to load Chromaphone 3 VST 3 by dragging and dropping within Cakewalk, the entire Cakewalk GUI vanished instantly. Cakewalk.exe continued to appear in Resource Monitor, but with zero CPU and occupying its normal amount of RAM (i.e. the previous RAM-gobbling behaviour was not present). After some time, Cakewalk.exe silently exited, the GUI never having reappeared. To cut a long story short, each time I restarted PC and/or Cakewalk then attempted to load the AAS instruments, I got a little further (although with two different Unhandled Exceptions along the way). I now seem to be able to load these instruments successfully. However, I'm very puzzled as to what the initial issue was and also why these following instabilities happened, but are seemingly not reproducible at will (even though I have made no further changes to AUD.INI). I'd be interested to hear @Noel Borthwick's thoughts on any of this. I have the original aud.ini and the mini-dumps from the UEs for anybody sufficiently curious to want to examine them. All observations gratefully received!
  3. Aah! That's interesting. I've finally received a list of diagnostic questions from AAS, so, with your permission, I'll pass your experience to them, too. But the difference is that you are getting beyond the point where my OS gives up and actually having the instruments become usable.
  4. AAS at an earlier point did say something along the lines of "You're using Cakewalk? That'll be the problem, then!" for which the author subsequently apologised (sort of) when I asked him for some evidence. As for piano tuning, ours had reached a remarkably stable point and it just stayed in tune for what seemed like forever. We eventually decided we needed to let a piano tuner loose on it, but it only stayed in tune for a matter of weeks after that. So we found another guy, who came armed with some impressive technology (I can't remember whether it was on a laptop or a tablet, though) which let me decide the amount of stretch that I wanted in the tuning, f'rinstance. He did a great job, which has lasted more than a year so far. He was an excellent player, too, and gave us an impressive recital before he rendered his invoice! And in the UK, he presumably is not prevented from making house calls at the moment (although I personally would probably not invite him in just now). And I must say that, were I an oboe player, and I got my new instrument out of its case, at which point the it expanded entirely to fill the room. but refused to make even a squeak, I'd be just a tad annoyed.
  5. Thanks for replying - I'm encouraged that you are running successfully, but I don't select the NKI option from AAS.
  6. @Starship Krupa - I just read your brilliant piece about the evolution of VST in another thread. Funny and insightful, like all the best satire!
  7. Thanks for your observations, Starship. Resource Monitor shows cakewalk.exe as the process gobbling up memory and it just keeps going until the entire OS malfunctions (something that doesn't seem to happen much in Windows 10). I have tried these plugs in Cantabile (which does nothing other than handle plugins, of course, so it seemed like a good test bed) and they are slow to load, but not massively, and then they work fine. And the standalones work fine, too. That would seem to implicate CbB, but, as I mentioned, Noel Borthwick seemed certain that the issue was AAS's after he had looked at my memory dump, and I've never known him to be wrong! And all of this happens long before the instrument is called upon to generate audio, so I don't feel it's the complexity of the sound generator. What I noticed in Cantabile is that the instrument is loaded and capable of sound generation long before its GUI appears, which is what made me wonder about graphics issues. I used AAS's combined installer, which selects the revised sound packs along with the instrument, so I don't think sound pack incompatibility can be the cause. It sometimes feels that the technology now gets in the way of creative music making rather than aiding it.
  8. 16GB of RAM and Quad core cpu. Standalone, Chromaphone 3 uses less than a GB of RAM. In CbB (for me anyway) it filled up all RAM and then created a 32GB swap file before crashing. So I don't think its resources as such. I have wondered whether it's because I use the CPU graphics rather than a separates graphics card, but that has not been an issue with anything else.
  9. Thanks - I'm pleased they are working for you, but that thickens the plot, of course. I also have previously had good experience with AAS support, but this time Eric keeps telling me he's sorry and that he'll get on to it, but then somehow doesn't. They're a small organisation, I know, but 2 months is a long time to wait. I got notifications about updates, but not to these products - I'll have another look, so thanks for the heads-up.
  10. I have always liked AAS products (going right back to Tassman that was included with some earlier version of Sonar many years ago). At the end of November 2020, I upgraded to the new generation Chromaphone 3, Virtual Analog VA-3 and String Studio VS-3. They work fine as stand-alones - and they sound superb - but they are disastrous in CbB. Typically, when I attempt to load any of them, Cakewalk becomes unresponsive and hogs more-and-more memory, until Windows gets into trouble and starts glitching on graphics and eventually the screen blanks. Even when the screen blanks, I can see that there is constant disk activity (presumably Windows furiously writing to Virtual Memory). I then have to restart the PC. Hoping that the new release of CbB might have altered this behaviour, I just tried again - attempting to load String Studio VS-3 caused Cakewalk's memory usage to climb steadily to over 32GB Commit in Windows Resource Monitor before the screen blanked and I had to reboot. I posted about this phenomenon at the time in the CbB Feedback thread (but that version is history now, so a new thread seemed necessary). Noel was kind enough to look at a memory dump and said he thought it was an AAS issue. I had already attempted to get AAS's Tech Support to take an interest, but I have had no meaningful response in 2 months - makes me wonder whether they are in some kind of difficulty. So 2 questions: Is anybody else successfully using any of these version 3 AAS products with CbB? Does anybody have any clue what is going on and whether therefore this is a configuration problem in CbB or Windows 10? I am using the most recent Windows 10, CbB and AAS versions.
  11. Thanks, Noel - if it's any consolation, it also took a while to compress the file! I assume you are OK with my forwarding your message to Eric at AAS. To your question, I was not playing, because the plug had not completed loading. I don't know whether this has any relevance, but when this plugin is loaded, I think I have seen odd behaviour with the "dirty" marker. I think the asterisk appears again immediately after a file save in Cakewalk, although TBH this is just something that I saw out of the corner of my eye and did not really observe in detail. I'll let you know what AAS makes of this.
  12. @Noel Borthwick Hi Noel - I PM'd you the dmp sometime ago. Meanwhile, I've had a lacklustre response from AAS (which has not been my previous experience of them). Support did not respond, Sales did not respond, so I posted on Facebook (which must be the last resort of anyone!). I got the following response, which I find quite shocking and disappointing - "I'm sorry about your inconvenience. We only have one person handling support, which he does on top of his regular tasks. I think he's contacted you a couple of days ago right? On the other hand, I believe that since their recent move with BandLab things got weird with that software, supporting it becomes harder and harder." An unbelievably unprofessional response from a company that I have held in high regard since the days of Tassman 3. And I am no further forward.
  13. I appreciate the help, all - it demonstrates the excellent responsiveness and knowhow that has always characterised this forum. I'll upload the dump to the cloud and let you have the link via PM. Further information - I had the same experience with AAS's Ultra Analog VA3 in Cakewalk, too. By contrast, this is at version 3.1.2, stable since January. Also, I tried all three of UA VA3, Chromaphone 3 and String Studio VS3 in Cantabile Lite (x64) and each loaded with no unusual wait and was immediately fully operable. All three running simultaneously with GUIs open used about 2GB RAM more than idling Cantabile, but there is a noticeable increase in GPU usage from about 25% at idle to around 50% with all three plugs running and open. Cakewalk uses no GPU, at least, in my set-up.
  14. Hi Noel - thanks for your prompt response. I used ProcDump to generate a .dmp while Cakewalk is hanging. The output is some 32GB, so I'm guessing that no-one wants that (and/or I'd be exposing private data, as that represents twice the RAM in my PC!) What would be your guidance here, please?
  • Create New...