…as shown in the screenshot. Is this a bug or ARA limitation?
I don’t see an explanation for this (and I don’t see this in my test).
More exactly, the only explanation I see, would be if you have changed the time ruler offset in WaveLab, as this is an option.
I haven’t changed that, but I performed tempo detection in Cubase prior opening the region in WaveLab ARA. Could that possibly cause something like this?
I don’t think so.
Try to reproduce with the same file in a fresh Cubase Project, with a single event.
I attached OneDrive link with the test project and I am pretty sure I am doing something very wrong here.
- Open the project
- Put Cubase’s cursor exactly at bar 6
- Click the drum part to open in the WaveLab editor
- Right-click on the WaveLab’s ruler and choose Bars and Beats
What I expect is that WaveLab shows 6 at the cursor as well, but it shows 29 something. What am I missing?
Thanks for clarification. Is this a limitation of ARA itself or current limitation of WaveLab?
This is a limitation of WaveLab as WaveLab has no concept of varying tempo.
I guess Melodyne does not have this limitation. Hence, I guess it is not an ARA limitation.
If ARA has to work, it has to be this way, when mouse is moved to Wavelab or Melodyne window, the shortcuts have to work for Wavelab or Melodyne, without even having to click inside Melodyne or Wavelab.
I may have assigned a shortcut S on my Daw to add a marker while S on Melodyne to change editing tool, there are high chances of shortcuts working at the wrong place.