David Baay

I created a comparable project with Sonitus Delay delaying a track by one beat and nulling against the same audio manually offset by 1 beat. I then added CW's TS-64 Transient Shaper which adds a significant amount of plugin delay to the Sonitus-delayed track and confirmed the two tracks continued to null. I then moved Sonitus to the bus through which that track was outputting, and the project continued to null both before and after restarting playback. For good measure, I tried moving Transient shaper to the same bus and other buses and tracks, and the project continued to null as expected. So I think this issue is either specific to ShaperBox or possibly involving the live synth which I'll test next. EDIT: Did the same test using two nulling instances of Session Drummer (because two instances of SI Drums already weren't nulling well), and got the expected result regardless of where Sonitus Delay or Transient Shaper were located.

I installed the plugins, but the demo of ShaperBox isn't doing anything - possibly because I didn't want to install the 300MB of presets and other content. I can see that Voxengo is set to add 1000 samples of delay to the synth audio track, and I can hear that delay vs. the metronome when engaged, but with ShaperBox not doing anything, there's really nothing to hear. EDIT: As I re-read the OP, it seems I may have misunderstood and this isn't even about PDC but more about tempo-syncing. Is that right? Also, as I read that Voxengo "Latency Delay introduces 10000 samples latency itself and delays the audio signal by 10000 minus the specified amount of samples or milliseconds, thus eliminating the unreported latency", the expected behavior of the test project becomes even harder to predict. I'll have to experiment with some other tempo synced plugin.

I can't reproduce a problem with my own test project, simply routing the phase-inverted one of two nulling audio tracks through a bus with a PDC-inducing plugin on it and moving that plugin back and forth between the bus and the track. I haven't yet tested with your project because I'll have to install the demo of ShaperBox and the Voxengo Delay and review what they're doing, but I see a couple issues with the project at a glance that could be contributing: - SI Drums is inserted in the audio track's FX bin; this is technically supported for backward compatibility with projects created before the Synth Rack was introduced, and there are some known issues with it. The preferred method is to insert the synth in the Synth Rack wiith the Input of the synth audio track set to the output of the synth. - This issue may be peculiar to live MIDI-driven synths or even SI Drums, specifically, which tends to render transients a bit late to begin with. Overall, the project is introducing too many variables to simply and clearly demonstrate whether PDC is working correctly on buses, including the use of three plugins, one of which is known to have poor timing, and two of which are 3rd-party and are altering that timing with unspecified custom settings.

Ah, okay. I was using Cakewalk back then but didn't join the forum until around Sonar 6.

48/44.1 (a factor of ~1.09 ) is in between a semitone (~1.06) and a whole tone (~1.12). No idea how you would get a 4-semitone error.

You can drop the SM/BAN click track from the demo project I shared into a new project, set the time signature to 3/4, drag the click to the timeline and you'll get the same (bad) result. Melodyne just doesn't 'get' that you only need at most one tempo change per transient, and it has trouble with material that deviates more than a couple bpm or changes rhythm even as the tempo remains perfectly constant. Melodyne can do some really amazing stuff in the pitch realm, but I have never been impressed with its tempo extraction.

Remove ASIO4ALL key from this registry path if still present: HKEY_LOCAL_MACHINE\SOFTWARE\ASIO Then click reset Config to Defaults under Preferences > Audio > Config File, reset the driver mode to ASIO and reselect the Apollo driver.

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

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.

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

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.

Set the Now time, right-click the timeline and choose 'Set Project Start Marker at Now Time'.

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.

Yes, not in CbB.

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.

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.

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.

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".

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.

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.

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.

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.

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).

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.

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.