View Issue Details

IDProjectCategoryView StatusLast Update
0021228MMW 5DB / Backuppublic2024-09-19 10:38
Reporterpeke Assigned To 
PriorityimmediateSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Target Version5.1.1 
Summary0021228: Per track crossfade setting in track properties
DescriptionWhen app is playing Now playing list and transition from track to track in playlist, many automation and DJ apps have more accurate crossfading of track at start/end because they have ability to set per crossfading option track and it will have priority over other playback settings if set.

StartPosCrossfade = LONGWORD (usually [if not set] either track Start Time or Start Time+StartPosCrossfade [for tracks that have long intro])
EndPosCrossfade = LONGWORD (usually [if not set] Stop Time or Stop Time-EndPosCrossfade)
PreloadBuffer = WORD (in Milliseconds to tell MM playback engine when to preload/prepare it as next track on playback)
CrossfadeStartType = TEXT [Setting or crossfading curve on how it will crossfade during transition from previous track, usually (SET PLAYBACK VOLUME to 50 -> PLAY NEXT 3s -> FADE IN to 100 for 1s)]
CrossfadeEndType = TEXT [Setting or crossfading curve on how it will crossfade during transition to previous track, usually (LOAD AND PLAY NEXT TRACK -> PLAY CROSSFADING NEXT 3s -> FADE OUT to 0 for 1s)]

Apps that extensively use this are RadioBOSS, ZARA, Jazler, RadioDJ, Traktor, VirtualDJ, MashUP, FLOW, ... and also hardware Pioneer DJ controllers, bars/caffee shops, malls, ... automatization devices.

This has been used also in output Plugins like SQRCrossfader that analyzed tracks more efficiently based on curve algorithms.

NOTE: This is low risk, low maintenance feature as it will be used only by users in need of automatization, and if DB supports it then with API Access can be easily opened up to any upgrades easily
TagsNo tags attached.
Fixed in build

Relationships

related to 0005924 closedLudek Framework: CUEPoint Support 

Activities

There are no notes attached to this issue.