Jump to content

Jack Stoner

Members
  • Content Count

    80
  • Joined

  • Last visited

Community Reputation

33 Excellent

Recent Profile Visitors

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

  1. The event viewer shows it as Ozone 9 "problem", but I have no idea what it is telling me.
  2. I'm using the Windows Defender, its not intrusive like some AV programs. The one that works OK also had Windows Defender enabled for testing and it didn't interfere. It falls back to some issue between the OS and Ozone. And the only known issue I have with this system is the Ozone issue. No other application or device has any problems. Ozone 6 was completely uninstalled (PC rebooted) and reinstalled and the problem remained. I haven't uninstalled/reinstalled 9 but based on it not helping Ozone 6 I don't see where it will fix the problem. Like Ozone 6 (that I don't use) I don't foresee me using 9 very much. Ozone 5, Country Basic, is perfect for 99% of what I do.
  3. Update, I replaced the 16GB Corsair memory with 16GB GSkill memory. Didn't make a difference so memory can be eliminated. I know a clean OS install will fix it (since my other PC works OK) but I'd lose too much (paid and unpaid add-ons that are no longer available) plus the hassle of recovering MS Office/Outlook files, etc. I'm not going to do it just for this one Ozone 6/9 issue.
  4. My DAW desktop has Win 10 Pro 1903 (with all current updates). The laptop, a Dell Inspiron 15, 5577 has Win 10 Home 1903 (with all current updates). The DAW desktop is an ASUS ROG Maximus VIII Hero Z170 motherboard with an i7 6700K (no overclocking) and 16GB of Corsair RAM. A Samsung EVO SSD. Resplendence Latency Mon shows no problems. I can run recording interfaces, reliably, at 64 samples. I use Windows Defender and Malwarebytes (paid version). There is no "garbage" in startup, only what is needed. Very "vanilla" system.
  5. I finally got a chance to work on the problem. 1. Izotope allowed me to install Ozone 9 on a second PC. Its a laptop that I use for off-site recordings. It does not do it on that PC (also Win 10 like my Desktop DAW). 2. I tried scrolling through presets while playing a project with Ozone 5 and Ozone 6. It does not do it with Ozone 5 but it does with Ozone 6. I've turned this info over to Ozone support and I'll see what they have to say about that. 3. Known things it (apparently) is not. (a) not DAW specific as it does it with both Cakewalk/Sonar and Studio one 4.5 Pro (b) it does it with the Ozone 9 standalone app. (c) It does it with both my AMD Radeon RX580 and the Intel CPU graphics. (d) It does it with both the PC audio (Realtek) and with the MOTU 4Pre. (e) It does not do it with other VST plug-ins.
  6. As previously note, it doesn't happen if a project isn't playing. UPDATE: Izotope support asked me to try it with the Standalone application. I loaded a wav file and played it and started scrolling through presets and after about 15 presets it aborted and closed. Using the Standalone and playing a wav file uses the PC's audio (Realtek) not a recording interface unit. In ref to video, I have an AMD Radeon RX950 (with latest drivers) and I disabled that and tried to the Intel i7 6700K CPU Video and did the same thing. Ease of Access is at Defaults. I tried turning off the options but that made no difference. My Win 10 version is the latest 1903 (with updates). It should be reiterated that no other VST (2 or 3) has this issue. I can load any other (all that I've tried) and scroll through presets while a project is playing and it does not cause the problem. As noted, I'll be off of this problem for a while to do a CD project.
  7. It won't do it "every time" a preset is switched while playing. The fact it will also do it with Studio One 4.5 Pro (latest version) says its something other than the DAW. Ozone 9 is the only VST I've found that will do this. I switch presets often when trying one and have not had the problem with any other VST, just Ozone. I have Ozone 5, 6 and now 9 installed and have only had the problem with 9, although I rarely use 6 so I can't say if it will do it. I'll have to hold off testing for a while. I have a (paid client) CD project I'm working on (more recording today). I'll wait till after the project is completed.
  8. Have you tried different factory presets while a song (or track) is playing? That's when it will abort. Might not do it on the first one you select but at some point it will do it. That's how I originally got the aborts. I installed Ozone 9, loaded a finished Cakewalk project (song) that I had used Ozone 5 for mastering. Disabled the 5 plugin and opened Ozone 9, started playing the mix and started trying the presets. Same thing happened with Studio One 4.5 Pro. If I select a preset and then start the song or track there is no problems. Its not the recording interfaces as it does it with either my MOTU 4pre or Behringer U-Phoria UMC1820
  9. I have solved what is causing the DAW programs to abort. Its Ozone 9. I had forgot to try Studio One as I installed it when Sonar folded but have never used it. I tried Ozone 9 with Studio One and it causes it to abort too.
  10. I have 9.02 version. It was what was installed yesterday when I bought and downloaded it.
  11. I have another thread about this with Ozone 9. If playing a song and browsing through the different presets in Ozone 9 Cakewalk will abort and close. No diagnostic info, just closes. I suspect its Ozone that is causing it but ??
  12. Just installed the new Ozone 9 (Standard) upgrade. I loaded a finished song that I had used Ozone 5 on to test. As I was scrolling through the Ozone 9 presets (while the song was playing) on the mixed down track both Cakewalk (latest 09 version) and Sonar Platinum aborts and closes. No diagnostic info - just closes. I supposed its an Ozone problem but ????? My DAW desktop is an i7 6700K with 16GB RAM and an SSD.
  13. Not being detected by DAW programs but being detected by others was my problem, too. Neither Sonar Platinum/Cakewalk by Bandlab and Studio One 4.5 Pro were detecting my MOTU 4pre but the MOTU control program (CueMix FX) detected it and Windows Device Manager showed it as working OK. If all the Roland drivers and associated control programs were uninstalled, PC rebooted, and new install did not fix it then there is some Windows corruption and I would suspect what you noted was done with CCleaner and/or registry. If you have a full disc image backup (and you should) that would be the best step, restore using the disc image.
  14. CCleaner is mostly OK (I use an old version) but if not careful it can cause problems. I don't delete duplicate files as there is a possibility that different programs installed the files and if deleted potential for a problem. Same way with Registry scanners/cleaners, etc., avoid them like the plague. Revo Uninstaller Pro will scan Registry for left over items on an uninstall and I've never had a problem with what Registry items it flags for uninstall.
  15. Good suggestion. As its a known issue, I would have "assumed" it had previously been reported and maybe no fix (or no easy fix).
×
×
  • Create New...