Jump to content

David Baay

Members
  • Posts

    4,649
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by David Baay

  1. Preview files are generated by default the first time you export from Sonar unless you deliberately uncheck the box and will remain in place until over-written by new ones. They can be freely deleted without consequence but will survive Clean Audio Folder because they are associated with the project file internally. EDIT: I should also mention that they are CWP file-specific so if you save alternate/evolving versions of a project in the same folder, each will get its own set of preview files when you export from it.
  2. Preferences > Colors > Show Strip Colors Make sure Views > Icons > Show Icons is enabled and Sonar is looking in the correct path for custom icons in Preferences > Folder Location > Track Icons.
  3. Looks like it might be more than just Tube Saturator. Prochannel EQs and Compressors may also be contributing. I would just disable all the Prochannels completely if you're not using them. And/or delete all modules except EQ and turn those off. The easiest way is to create a preset that only includes the disabled EQ (which can't be removed), and load that into all the tracks and buses. There seems to be something going on with Prochannels in this project in particular as just enabling those modules with no input signal to process will not normally generate any output.
  4. Meng's in it, and he is independently wealthy. ? That said, it should be understood that the expression "not in it for the money" typically implies "not only/primarily in it for the money".
  5. A. To keep you from leaving for a product that's being actively developed. B. To keep the developers from leaving because they're bored to tears. Like Craig said, the developers aren't in it for the money; it's the intellectual challenge of innovating that keeps them around.
  6. As mentioned in the other thread about this, Massive X has a 'View Size' scaling factor in the pick list next to the logo at the upper left, and Ozone 11 is continuously resizable by dragging the lower right corner.
  7. Massive X has a 'View Size' scaling factor in the pick list next to the logo at the upper left, and Ozone 11 is continuously resizable by dragging the lower right corner.
  8. Try un-checking 'Enable Plugin DPI Awareness' in the Settings drop-down of the CLA-NX UI (and maybe SSL E Channel as well). In general I'm finding that plugins with a scaleable UI behave better with this option disabled. And some plugin UIs (especially older ones) will render too small with it enabled.
  9. No doubt some users really like and depend on the one-click delete for their workflow and any change at this point would need to be optional/customizable (as it should have been when they changed it previously).
  10. Yes, I should have mentioned it. I sometimes find it difficult to accurately double-click a note when the PRV is zoomed out or the note is short so usually just lasso it and use the Event Inspector... after I undo the initially mistaken right-click erase.
  11. I should have mentioned: the option is in the Settings pick list in the plugin title bar so pretty easy to switch it as needed and to know you're changing the right plugin.
  12. I've found it doesn't work for everything, but it is odd that I'm getting a different result with the same plugin unless maybe it's a version issue. Are you loading the VST3?
  13. Yowza! Frankly the way all this scaling stuff works under the hood is a bit of a mystery to me, but I suspect that high scaling factor has something to do with it. I'm at only 160%. But I'd be surprised if the UI doesn't change size at all when you disable DPI Awareness...?
  14. That would be the "Obfuscation Team", an indispensible part of any good marketing department. I suggest you submit your inquiry to them directly: http://bandlab.com/inquiries/roundfile
  15. +1 Right-click used to open properties. I still inadvertently delete notes ? At one time you could customize tools, but not currently. The best you can do is get in the habit of using the Event Inspector.
  16. I tried it with FM8, specifically, and it worked as expected here; the UI becomes the same size as in CbB. Possibly it's a limitation of demo mode that you can't change it.
  17. - Disable 'Plugin DPI Awareness' in Plugin Properties for affected plugins. - I have deteriorating eyesight as well but I get along pretty well with the PRV in the Mercury Classic scheme. The keys are black and white - are you referring to the shading of the sharps the runs across the notes area? I could wish for darker/bolder gridlines, but they're usable for my purposes. It's not missing from Sonar but the hotspot has narrowed a bit; you have to hover over the lower half.
  18. +1 Jurassic Cakewalk had this feature and I used it with some regularity.
  19. Cool. Glad to help. I love a good mystery. ;^)
  20. I see about -82dB at the output. FX Bypass kills it. I looked at a few tracks and found instances of Sonitus Compressor and Reverb. I didn't try removing them, and I didn't check all tracks, but that's where I'd start. EDIT - Looking further, I found Prochannel active on all tracks and buses with Tube Saturator enabled. I think that's the source. You can kill them all with Quick Grouping.
  21. I understand that, but this thread is not really about that (or at least the OP wasn't); it's about the net cost either way. And conserving energy can help pay that cost either way.
×
×
  • Create New...