Jump to content

brundlefly

Members
  • Posts

    4,457
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by brundlefly

  1. Essential is sufficient, and my understanding is that the drag-to-timeline function should continue working after the trial has expired, but I can't verify that because I have Studio. Personally, I prefer Set Measure/Beat At Now because Melodyne interpolates tempo changes every 8th note where they are not needed and often makes gross errors if the tempo is more than slightly variable. EDIT: Here's quick example of two projects using the same short audio clip - one with tempos set by Melodyne and the other using Set Measure/Beat at Now. The tempo map in the Melodyne project might look "smoother" and more precise, but the metronome is terribly out of sync with the audio: SMBAN vs Melodyne Tempos.zip
  2. CbB or Sonar? It should work without having to arm the track; sounds like the input port is not being opened as it should be Input Echo alone. What audio interface and driver mode? EDIT: Or possibly the audio engine is not running. Verify the metronome is set to Audio (not MIDI), and try toggling the Run/Stop Engine button in the Transport Module or momentarily starting playback . If there's no MIDI/audio content in the project yet, disable 'Stop at Project End' in the track view Options menu to allow the transport to run with no track content.
  3. brundlefly

    Clip color

    The new position should persist for the session but will reset on re-opening the project if it isn't re-saved.
  4. brundlefly

    Clip color

    Once you save a project with a plugin UI in a different position, that position will be the new default. You can achieve the same for completely new projects by saving a tempate with some plugin moved to the preferred position (not sure if this persists with no plugins in the template). Workspaces may also recall I changed default position - I haven't tested that. EDIT: Project and Track Templates can also be used to define default clip colors, and the Clip Properties tab in the Track Inspector allows independently specifying custom foreground (waveform/notes) and background colors.
  5. Set the Now time, right-click the timeline and choose 'Set Project Start Marker at Now Time'.
  6. Cakewalk does not currently support changing bar numbering or have 'pre-roll' measures. The best you can do is set some later bar (e.g. 5, 9 or 11) to fall on the absolute start time of the video using Set Measure/Beat at Now (Shift+M), and just remember that everything is offset by 4, 8 or 10 measures as you work. When you do the 'Set', CW will change the initial tempo to make that specified bar hit the specified Now time, and insert a matching tempo at that point. You can then change that second tempo to be whatever you want for musical purposes.
  7. 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.
  8. 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.
  9. 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.
  10. 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".
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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).
  16. 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.
  17. 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.
  18. 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?
  19. 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...?
  20. 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
  21. +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.
  22. 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.
×
×
  • Create New...