Cross getting beatgrid wrong

[daniel clark]

settings 2 Capture.PNG

:cool: got it

[rhopkins]

Actually, the beatgrid is now right, but the initial cue point is still put in the wrong place.

[Jim B]

but the initial cue point is still put in the wrong place.

I'm finding that on a few of my tracks

[FigDJ]

but the initial cue point is still put in the wrong place.

I'm finding that on a few of my tracks

For me this whole thing started at 2.7 beta which never saw public release. the same kept on happening to different degrees with subsequent version 3.0 and forward.
So right now I keep 2.6 to do all my analysis and set beatgrid and cue points.
I have 3.1 to do MIDI mapping experiments using the update MIDI aliases. And I have 3.2 but don't trust it.
Once the beats and cue point are set in 2.6, I re-analyze for beatgrids only in 3.1 or 3.2.
There is an analysis directory for 2.6 and another one shared by for 3.1 and 3. 2.
For performances I stick to 2.6 unless I know I have to use titler functions or video samples.
I just don't trust 3.2 yet as I am testing for memory leaks and CPU readouts.

[discopex]

For me the cue was on the first beat. Maybe it has something to do with the wrong first analysis?

[daniel clark]

snap or quantise have any effect this way with the misplaced cue

[FigDJ]

:cool: snap or quantise have any effect this way with the misplaced cue

Well, we know that there have been two major changes related to analysis.
Key detection and colored waveforms, and unofficially the beats rendering in beat matcher which is part of peak analysis.
As users we don't know if the analysis gets affected by quantize and snap settings since there has not been any new instructions or information about features. At least not in the form of a user's manual or supplement to the manual since version 1.4.
All we can do is experiment, see what happens and post our findings here.

[RoJeC]

Took another look at the initial image.
AFAIK Cross does not put the Cue at the first beat of the track but at the first beat of the determined beatgrid. By this it is simple to match in the beat cycle.
Occasionaly you may want th first beat audible so you'll have modify manual. In the past more complex parameters were available which did not provide good results. (Like x-volume in first n-seconds). (mice for a track like school of supertramp)

Quant and snap are used while playback and not for beatgrid (else a change in any of these over time would require re-analysis).
You will have to use lower snap value if you want to put the Cue halfway '2 lines'.

Also for quant a lower value might work better for this purpose.

FigDJ: the manual is from 2.x and beta 2.7 released as 3.0.0

[FigDJ]

FigDJ: the manual is from 2.x and beta 2.7 released as 3.0.0

What? Do you have a link for the most current manual? If so please post a link for it. When I try to access from within Cross it blows up my browser and it does not display.

[daniel clark]

yes a link to the most current manual ,, kinda get lost on the fourm trying to find it,, hard to say R T F M,,when you cant point the way