Jump to content

User Zero

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

2 Neutral

Recent Profile Visitors

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

  1. Hi Noel, I was thinking it'd be nice to know which specific patches were loaded into the VSTi, how their internal levels were set, etc. Having thought about it further, however, although I'm not familiar with the details, I imagine every plug-in has its own proprietary data structure that the DAW probably doesn't "understand", and just stores as a "blob'" for each instance. I did try modifying the cwp file with a hex editor in an effort to get CW to load the latest version of Kontakt, but all the methods I tried ended up with an unreadable file. So I'm guessing there's a checksum or other mechanism that's getting messed up by that effort. I eventually just exported the MIDI, routed the tracks through EWQLSO and without much tweaking at all ended up with a render that I can at least work from. Probably took less time than all the futzing around I did trying to get my old copies of K3 & K4 installed (turns out they're not compatible w/Win10 ;-). cheers, r
  2. Thanks! This is a very cool little app. Sadly, it provides the same information I can see by opening the file in CW. That is, there is nothing listed about which sampling synths were used or what sample patches were loaded. That's probably beyond the scope of the program, since it would likely require detailed specs on every known synth and how their configuration data is stored.
  3. Wondering if there's a tool or process available - perhaps something used by the Devs - to parse and examine the data in a Cakewalk project file. I have a some old .cwp project files I'd like to rework, but unfortunately I no longer have the sample synth / library that was used (Kontakt 3 & 4). These load fine, but give the expected errors regarding missing synths. I'd like to rebuild the project and can certainly do that using a 'best guess' as to what each synth in the Synth Rack probably had, based on the routing information in the MIDI tracks. However, if there's any way to examine the portion of the .cwp data that defines the synth instances, that would be a huge help. Any thoughts greatly appreciated. TIA!
  4. Hey folks, I have an old orchestral project on a backup drive that was created with SONAR and Kontakt 3 & 4. I have those libraries backed up as well, but no longer have the plug-in DLLs for the 'Kontakt3 8 out' and 'Kontakt4 8 out' synths. So of course when I load the project with CWbBL, it gives the expected errors, i.e., that the instances of the above synths are missing, etc. The placeholder synths are there in the Synth Rack and all of the routing is intact (e.g., MIDI tracks are sending data to their respective synth instances, etc.), but the instances in the rack can only be deleted, they can't be updated to point to the new Kontakt Player dll. My current system has Komplete 9 with all instruments up-to-date, as well as the current version of the Kontakt 6 player. So I have current versions of all the instruments that were used to create the project originally, i.e., the Kontakt Factory Library VSL stuff. What I need is the information on how the plug-in synth instances were set up. I can deduce some of this by simply looking at the tracks' routing, of course, and I can duplicate new synth instances using Kontakt 6 with a 'best guess' on which specific patches were loaded, but have no way to know if there were any specific settings in the original synth instances themselves. Since the placeholder synths are (still) there, I'm wondering if there is some way to examine their data, if not to actually transfer it to a current version of the Kontakt Player instance. Any thoughts greatly appreciated. TIA!
  5. Thanks, Folks. I'll give this all a look. I'm frankly not sure what Assistant did here. I kicked off the install and stepped away for a moment. When I came back it appeared to be done. cheers, r UPDATE: Registry edit was quick, and worked fine. Thanks again!
  6. Thanks Craig, but as I tried to show in the linked image, when I open the "Install Add-ons..." window, all of the plug-ins are already checked (as if they've all been installed) and the Install button is disabled, unlike what's shown in your screenshot. cheers, r
  7. Hi All, Just installed CW by BL via the Assistant on a new Win10 system. Can't find Melodyne. There's no directory for it under Program Files, etc., and the various app listings don't show it (see linked gif). Assistant doesn't provide the option to install it - apparently thinks it's installed. Also - how do I get apps and features like the Instruments to install somewhere other than C:? The installer(s) launched by Assistant don't provide an option to specify. TIA https://imgur.com/lPUfnhS
  8. Thanks, Tee'. I appreciate the comments. I'd only disagree on that one point, above. The DAW was working fine prior to the Update. It crashes when I attempt to load any project after the Update. Nothing else changed, so even if there were some problem with the plugin that was somehow being masked by the previous version of CbB, it's pretty clear what's to blame for the problem I'm having at the moment: my lack of good judgment in choosing to click the Update button. The sample library player / VST it's balking at (EastWest Play / play_VST_x64.dll) works perfectly fine in Reaper and, in fact, worked perfectly fine prior to the CbB update, so... 😉 Again, I'm not suggesting BL Tech should support Win7, but I do find it interesting that Cockos apparently does have the bandwidth to support Reaper on Win7 - as well as XP and Vista for that matter - FWIW.
  9. At no point have I implied that you're installing something that doesn't work on Win7. Here, I'll try to put it more simply... Microsoft Edge is a Win10-specific application. YES, I get it: you're not installing Edge, that's not the issue. While you (think you) may be only installing Edge's "WebView" component, after the CbB update, an "edgeupdate" service is installed on the user's system, and a task is set up to cause this service to phone home every 5 minutes looking for updates. Even worse, apparently this component is looking for updates to an application (i.e., MS Edge) that isn't even there (see the previous post where I included an Event message). Again, this service - the one you're installing - exhibits exactly the sort of resource-consuming behavior that motivates people to remove Edge from their Win10 systems. If you're going to CHOOSE to use a component that requires installation of something like this as part of your design, you should be informing your users. At no point have I stated that CbB should work on a system where Edge has been disabled or removed, so let's please not try to confuse the issue here with that. I saw the rollback installer. That only works if you have 2021 installed. I already clearly stated in my first post that after a successful System Restore, "the CW app's Help About reports that it's back to Version 2020.08 (Build 100, 64 bit)". Thus, the rollback installer won't run. Yet the DAW still crashes when I load a project that worked fine before the update. Again, if you have a link to actual installer exes for 2020.8 or previous, please let me know. Thanks.
  10. Hi Noel, I'm not suggesting BL Tech should support Win7. What I'm suggesting is that the Update function should (a) not permanently trash a working installation, regardless of what OS it's installing to and (b) not install components that are specific to Win10, and NOT intended to be run on Win7, per Microsoft, without expressly asking the user for permission to do so. It's common knowledge that users frequently choose to disable and/or uninstall Edge componentry from their Win10 systems - the constant "phone home" function being one of the reasons. The component(s) you're installing perform that function roughly every 5 minutes, so while you may not be installing the browser, you're definitely adding the offending resource-consuming components, without actually informing the user in the process. In any case, prior to the 2021 update I had a perfectly functional CbB DAW on Win7 which did everything I needed it to do. My mistake was clicking the Update button on the BandLab Assistant app. My issue now is that I can't restore it BACK to the state where it was working, by performing a successful System Restore. So the update clearly changed something that is OUTSIDE of the file system that is normally managed by Windows' SR functionality. As noted in my first post on this topic, if you have a link to installers for earlier versions of the CbB DAW, I'd appreciate a copy so I can give them a try. Thanks.
  11. With all due respect, Noel, if that were true, my Event Viewer would not contain multiple events generated by "edgeupdate" roughly every five minutes. You may not be installing the entire Edge application and all of its supporting componentry, but you're definitely installing enough of it to put tasks and services in place that the updater DOES NOT ask permission to install, which periodically run tasks in the background that phone home to Microsoft (hopefully) without asking the user's permission. One instance: I've since managed to remove this unwanted Microsoft junk using System Restore. Despite that, CbB still crashes when it tries to load sample libraries that it loaded just fine prior to the update. So apparently, one aspect of the application's present status with respect to Win7 (yes, of course that's the OS I'm using) is that any Update (i.e., from Bandlab Assistant) can permanently corrupt the application to the point where even System Restore can not return it to functionality. Nice. Thanks.
  12. I'm afraid I have to destroy the implication that I ever suggested that the webview app was the culprit. Nowhere have I stated that. I've simply noted that it's a component that should not be blindly installed as part of an update to an application on an OS where it is not intended to function (per Microsoft). Whether it's actually causing problems is completely beside the point. The System Restore operations I successfully completed seem to have removed the MS Edge component(s). Prior to the Restore, I see numerous events in my Event Viewer generated by "edgeupdate" as it phoned home every 5-10 minutes looking for updates in the background without permission, which is just ONE of the undesirable behaviors that motivate users to remove Edge from their Win10 systems. Those events stopped appearing after the Restore operation.
  13. Noted. I'd submit that it's valid regardless of anything I've said. It's simple common sense if your aim is to release a functional, user-friendly application. If an application isn't compatible with a given OS, the fact that the installer or update will run AT ALL is a pretty huge Red Flag. If it does, and the OS is not - or, more importantly, is no longer - supported, the Update process either needs to halt the process or make the user aware of potential issues. Instead, the BA Update process blindly went ahead with installing an (apparently) incompatible version of the application and, to boot, installed an incompatible Win10 component without providing the option to skip it. Not sure how this applies. I ran BandLab Assistant and used that to run CbB, ignoring the Update button because I had work to do. I used it successfully for hours on Saturday morning to do a variety of tasks on multiple CbB projects. Once I'd finished what I wanted to do, later that evening I went back and activated the Update button, after which the program crashed every time I tried to load projects that had worked fine prior to the update. Was I supposed to anticipate major problems, hunt down this forum (which I didn't even know existed) and read every post before doing that? I'm not sure anyone would consider that practical. I don't think anyone is that prescient. Pretty sure I made it clear that I'm looking for an installer that will get me an (older?) working version of the DAW, so that I can open the projects that are now in limbo, extract the stems, and move on to using a product I can rely on, like Reaper.
  14. No need to condescend. Win7's support status is public information. That's actually kind of the point. If this application no longer runs reliably on that OS, it should not be blindly installing or updating itself there, much less attempting to install a Win10-specific component which - per Microsoft - does not run on Win7. Again, this is all just basic common sense - at least for a competent development team. There's no way for the hapless user to know that when she clicks Update, she's going to have her system polluted with Microsoft glurge that is commonly removed from Win10 by users who want better performance, better privacy and better security. Not weird at all. The program crashes whenever I attempt to load CbB projects that were perfectly fine that very morning, before the update. Therefore they are - by definition - no longer accessible. This isn't an issue with drivers or backups or anything else. It's an issue created by an Update process that replaced a working version of the application with a broken one, and which did so in such a way that multiple successful System Restore operations could not undo the change. Unacceptable.
  15. Not sure I understand why anyone would ask this question. If there are versions of Windows that this application doesn't support, it should explicitly SAY so when an installation or update attempt is made. As such, the version of Windows should be irrelevant. If the application installs or updates, it should work. Period. If an OS version is not supported, the install or update should abort, with a clear message explaining why. At the very minimum, the user should get a clear prompt before ANY change is made, enumerating the possible outcomes... which should have been identified during product Q.A. This is just basic common sense. When I ran the update that destroyed my install the other day (and which has rendered my CbB projects inaccessible), I noticed with no small degree of horror that it ran an installation of some Microsoft Edge component. Microsoft support states that Edge is not compatible with Win7. This is a pretty clear indication that BandLab Assistant isn't paying any attention at all to the version of Windows on which it's running, when it absolutely should be - especially if there's a possibility that an installation or update can render the application inoperable. Independent of OS version, at a very minimum users should get a prompt warning that this Edge component is about to be installed, so they can decide whether or not they want more Microsoft garbage on their system - especially if they've previously gone to considerable effort to REMOVE it. Beyond this, the fact that a broken update persists across multiple successful System Restore operations demonstrates that BandLab Tech doesn't fully understand how to package a Windows application in a way such that changes can be undone when needed, for whatever reason. These 'dead in the water' situations, like mine, are a good indication that BandLab Tech is not testing this product very thoroughly. If anyone can provide a link to an installer for an older version of BandLab, so that I can at least salvage the stems on the projects I was working on, I'd be very grateful. TIA!
×
×
  • Create New...