Jump to content

Steve Moddelmog

Members
  • Content Count

    76
  • Joined

  • Last visited

Community Reputation

4 Neutral

Recent Profile Visitors

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

  1. Yes, I have both versions installed, but suddenly none of my VSTs are available in 32-bit Sonar. So if I have a "mixed" project (say, FM8 dxi plugin but Absynth VST plugin) the VST will fail to load in 32-bit Sonar. This is new behavior - I'm certain I could do this with no problem as of March 15.
  2. As I've said, the purpose is solely to open older projects that used dxi plugins. Everything new I do is in 64-bit CBB. I'm surprised that nobody else seems to want / need to do this. In many cases, all I want is to see what preset I used in a plugin that also has a VST version, for example FM8. I then replace the dxi with the VST version, load the preset, save, and then reopen in CBB.
  3. Thanks for the responses, but I think I wasn't very clear. First of all, as of March 15 I was doing exactly what I want to do - load old projects with dxi's in 32-bit Sonar, which I have had installed on my computer alongside CBB ever since CBB was released. All of my 32-bit VSTs have been visible in 32-bit Sonar as have all of my dxi plugins - until I tried it today. The dxi plugins are still visible - that's not the problem. The problem is that the 32-bit VSTs, which I am absolutely certain were available in 32-bit Sonar on March 15, are all gone, and all of the options for scanning them in Plugin Manager are grayed out. I'm not trying to load VST3 plugins or 64-bit VST2 plugins in 32-bit Sonar - I know that is not possible. I'm only trying to do what I have done ever since CBB was released - use 32-bit Sonar to load old projects since I cannot load the dxi plugins that many of them used in CBB. Any thoughts? Thanks.
  4. I have been running CBB since it first became available, but I have kept a 32-bit version on SPLAT on my computer to be able to load old projects that used dxi's. I have done that as recently as 2 months ago. Today when I loaded 32-bit Sonar all my VSTs were gone all all VST configuration options were grayed out. What might have happened?
  5. I think I mentioned somewhere earlier that I was able to boot into Win 10 once after doing an Acronis restore AND then rolling back (in recovery) the Win 10 update that happened the day before the Acronis backup was made. Then it crashed again and that sequence didn't work a second time. I'm not sure whether Acronis is to blame for that or the drive(s) were just too screwed up.
  6. It was a refurbished machine I bought on Amazon. I'll never do that again.
  7. The RAID configuration was to double the drive size, not to backup. Not what I would have done, but that's how it came out of the box. I did manage to restore a March 9 Acronis image which initially didn't help, but when I then selected the repair option of uninstalling last quality update (having little expectation that it would fix the problem), I was able to load Windows 10. Since March 8 was a patch Tuesday, I guess there was something in the update that caused my problem, the problem would have existed in the March 9 Acronis image, but the repair to remove the update did the trick. I was able to get information about a few projects, but then I noticed that my wifi adapter wasn't working, and when I tried to fix that and did a re-boot, I hung at the Windows 10 logo again. I guess I will do another restore to see if I can keep it running long enough to get some more of the file and information I wanted.
  8. Well, I did a restore form Acronis. It took 7 hours to run, said it was successful at the end, but when I tried to reboot, it just hung at the Windows 10 startup logo again.
  9. I'm setting up a new laptop to replace a dying desktop (that actually may have completely died just a few days after I started the laptop setup). One of the worst parts of the setup process: I've got old, old projects that I still go back to work on. Many of them used dxi versions of plugins that won't work in Cakewalk or 64-bit SPLAT, and many, many more used various versions of plugins such as Native Instruments, where new releases are actually new plugins and won't automatically replace older versions and simply load the preset that was loaded in the original project. Think Kontakt, for example, where there are Kontakt through Kontakt 5, and then Kontakt "6" which is simply named "Kontakt." Yesterday I loaded an old project that used Kontakt 2, and of course Cakewalk told me that the plugin was missing because I've only installed the current "Kontakt" on the new computer. Rather than install every version of every Native Instruments plugin I've ever bought, I'd like to just look "inside" the project and see what preset / patch was loaded, and then load it in the current version of Kontakt, Absynth, or whatever. In the past, I've just gone back to my graveyard of old machines if I wanted to find that information. But as I said, my desktop seems to be dead. I know there's a program called Projectscope that will show you what plugins are used in a project, but it doesn't tell you any information about what presets / other parameters were used. Obviously that information is somewhere in the .cwp file since projects load with them every time you re-open the project (if you have the plugin installed, that is). Is there any way of getting to that information? It would be a great Cakewalk feature to be able to get it...
  10. My desktop computer appeared to be headed toward death - second disk in 2-disk RAID configuration reported that it had 30 days of life left. So I bought a laptop to replace the computer and am near the end of the slow setup process. I was hoping the old desktop would keep running so that I would be able to get anything off it that I forgot to copy, and also to look at projects what weren't loading right on the new laptop and see what plugins and presets I was using. I booted the desktop two days ago in search of just that kind of information and it hung at the Windows 10 startup screen (for hours). I rebooted and it came up in repair mode. I tried the option to repair startup and it found errors (probably during CHKDSK) that it attempted to repair. It indicated that repairs had been made. I rebooted and got the same Windows 10 startup screen hang. So back to repair mode - I booted to a CMD prompt to see what the drives looked like. To my surprise, the c drive showed only the system recovery partition, what had been on the main c Windows 10 partition was now on E:, and what had been on secondary drive designated J: was now E:. Is this to be expected? Just a function of not booting fully into Windows? Or does it suggest that something important got scrambled? I have an Acronis backup which I could restore, but is that my best recovery option? I think the Acronis backup is just of the main Windows 10 partition, not the entire c drive. Thanks for any advice.
  11. My Wusik 9 example may have been a little wonky, because somewhere along the way there was an update to Wusik 9 where projects with earlier versions of Wusik 9 would not load properly. This project won't load Wusik 9 even if I delete the 64-bit version so that the 32-bit version becomes available. So I'm curious in general (I think I know the answer to this), if I create a project with a 32-bit version of a plugin and then install the plugin's 64-bit version (so that, per the above, I can no longer see the 32-bit plugin in Cakewalk), will the project open with the 64-bit version of the plugin? I'm guessing no.
  12. I agree with that. What I really want to do is see what presets/ settings I used in the original with the 32-bit and then replace the 32-bit in the project with the 64-bit using the same preset. More recently I've started adding notes with the patch names, but I wasn't always smart about that.
  13. I'll give that a try. But I have rescanned many times and literally watched the 32-bit version on V9 flash by like all the other VSTs, with no hang, error message, or anything.
  14. Can you clarify - the 32-bit version already is in a folder under "C:\Program Files (x86)" that is scanned (and 32-bit plugins that don't have 64-bit versions are showing up fine in Cakewalk). I could remove the 32-bit dll, then re-add it / rescan with logging enabled. Is that what you are suggesting? To see what the log says is happening?
×
×
  • Create New...