apopsisdj
Just a litlle warning that the "browser track area" is about 9.00-12.00 min of the timecode.
In this area TC control disengage and there is a issue with the pitch.
I just wanted to let you know what this option does and and why is better to disable it in some cases, until dev staff find a better way to handle this.
[Quote my words from another post]:
[size=11]The "browser track" feature works in a simillar way to "smart cue", if the needle jumps +/- 1 minute you can switch between folders/main list/playlist. Unfortunately there are 2 negatives:
1. "browser track" timecode area starts at 9.00 min in timecode, so you loose the last 3 minutes of the timecode.
2. worse antifact, when timecode reach 9.00 timecode pitch no more taken into account as Tc is no more "drive" the song (as it where at 0%) and what you see as offset is the internal pitch in case of sync/beatlock or skin pitch slider used.
As i wrote in another post:
"vdj everytime take both internal and external (tc) pitch into account and the final pitch is the sum of the two. This is a very powerful feature allow you to use both, or internal bpm sync commands, or have external pitch slider in a "relative" way"
The timecode pitch reset on TC disengage is the bug in my opinion and will report it asap.
My safe option and recommendation for now is to disable browser track.
In this area TC control disengage and there is a issue with the pitch.
I just wanted to let you know what this option does and and why is better to disable it in some cases, until dev staff find a better way to handle this.
[Quote my words from another post]:
[size=11]The "browser track" feature works in a simillar way to "smart cue", if the needle jumps +/- 1 minute you can switch between folders/main list/playlist. Unfortunately there are 2 negatives:
1. "browser track" timecode area starts at 9.00 min in timecode, so you loose the last 3 minutes of the timecode.
2. worse antifact, when timecode reach 9.00 timecode pitch no more taken into account as Tc is no more "drive" the song (as it where at 0%) and what you see as offset is the internal pitch in case of sync/beatlock or skin pitch slider used.
As i wrote in another post:
"vdj everytime take both internal and external (tc) pitch into account and the final pitch is the sum of the two. This is a very powerful feature allow you to use both, or internal bpm sync commands, or have external pitch slider in a "relative" way"
The timecode pitch reset on TC disengage is the bug in my opinion and will report it asap.
My safe option and recommendation for now is to disable browser track.
Posted Fri 20 Oct 06 @ 8:26 pm