Allow the grid to start from where the user desire. Eg. If song only has a one bar intro, I dont want to start from a one bar intro. Instead i want it to start from begining of first bar of song
This can already be accomplished. In Export Mode, click on the Grid button. Note the red/white vertical line in the toolbox (located between the two arrows). This is what defines the start of the beatgrid. I'd encourage you to read the manual, check YouTube for great tutorials like this one and simply experiment. You'll find that it's much easier to learn about the software this way.
Publicação fechada para comentários.
So you adjust your own grids then, yes?
Yes i do my own grids from time to time if i see that they are off
https://forums.pioneerdj.com/hc/en-us/community/posts/115000030186/comments/115000038923
i watched the video and though very helpful it did not adress my concern.
what i am asking is that the count of the bars dont start from the begining on the track where there is silence. i want it to start counting on the first bar of intro or somthing.
eg...a track with a bit of silence for 2 bars, then a 4 bar intro, then the first verse.
in this case 1 should start at the begining of the 4 bar intro and not at the begining of the silence, so the verse would now start on 5.
hope this explains it clear
Unfortunately there is no "negative count" like Serato DJ has. As @lostnthesound described, find the first beat, put your cursor there and press the red/white marker button to set that as the first beat. Even though it won't be the 1.1 beat (if there is audio before that point, it may be a higher value, like 5.1 for example), you can set a memory point or hot cue at that point and it will load to that point when you load the track (if set to load to that within the preferences).
I am happy to see this feature introduced in beta 5.0. Great direction. Only problem with it is that as soon as i try to lock the anylyze on the track, the grid numbering is messed up. Maybe a bug
@koolbreeze > I don't seem to notice anything unusual when locking the analysis, can you show some screenshots to illustrate the issue?