From my initial tinkering with the Advanced PFL dialog, it strikes me that on many occasions, one will want to set (say) Outro and Fade Out to the same value; or set Cue and Ramp to the same non-zero value (for example, on tracks which have 1,5s of silence at the start due to faulty preparation).
This seems to suggest more buttons are needed in the dialog, whose functions (not captions!) would probably be:
Set Ramp value = current Cue value
Set Fade Out value = current Cue Out value
Set Outro value = current Fade Out value
Set Outro value = current Cue Out value
Provided you set Cue and Cue Out points first, I think the four buttons suggested will allow all the ‘cross-setting’ needed, and could save a lot of time when tagging n thousand tracks…
Does anyone have any other thoughts on this?
PS: Not everyone has a Wheel on their mouse. I use a Logitech ‘marble’ trackball because I hate wheels (and love trackballs!). Therefore the ability to move a cue point 0,001s with a mouse wheel is not helpful. Would it be possible to have a keyboard HotKey(s) to do this? Also is it possible to set HotKeys for the buttons in the Advanced PFL dialog? I prefer to use keys when setting cue points because I find keys much more accurate than a mouse for that job. What do others think of this?
Would it be possible to have a keyboard HotKey(s) to do this?
This is already possible, take a look at the “PFL CUE PLUS” etc. commands. (What is still missing is a set of commands to toggle between the various cue point types and modify the one currently selected.)
Regarding the other suggestion, remember that setting a marker to 0 means that it’s undefined or non-existent in that file, and that Ramp and Outro are for visualization only. So you will not see any difference when setting them to the same value as Cue In (or Cue Out, respectively). Just leave them at 0.
Is it possible to have a new Cue Point, named something like Cue Next or Start Next or Segue, which will start the next Item WITHOUT fading out the current playing file (if that makes sense!).
What I am thinking of here is voice tracking. Many voice tracks are recorded so that they ‘talk over’ the start of the music. At present it does not seem possible to do this with mAirList, and my idea above is the only way I can think of to implement it—unless you can think of one?
Note that this would also make ‘sweepers’ possible!
