the SOUND INSURGENT
Can someone please explain the benefits of the new "Lists" vs "Playlists"??
Like is there about to be a shift in the industry that we haven't heard about yet, or is this just a VDJ thing?
I now have like 3 copies of my playlists in 3 different folders, some are "Lists" and some are "Playlist" format.
Things just seem messy now and I'm not comfortable with all this.
Like is there about to be a shift in the industry that we haven't heard about yet, or is this just a VDJ thing?
I now have like 3 copies of my playlists in 3 different folders, some are "Lists" and some are "Playlist" format.
Things just seem messy now and I'm not comfortable with all this.
geposted Mon 08 Apr 24 @ 3:40 pm
kradcliffe
https://www.virtualdj.com/forums/257950/VirtualDJ_Technical_Support/___IMPORTANT_CHANGES_IN_VIRTUALDJ_2024___.html
From what I read it just replaces the "outdated" m3u format and streamlines things to be less confusing for the user.
From what I read it just replaces the "outdated" m3u format and streamlines things to be less confusing for the user.
geposted Mon 08 Apr 24 @ 3:57 pm
Stephane Clavel
VirtualFolder's xml format has been used in VirtualDJ for more than 20 years, so it's not really new vs old.
But it's more powerful than m3u, it can both contain files and subfolders, have or not duplicates, can be split over several drives, etc.
It made no sense to keep having both virtualfolders, and m3u playlists, since they're both serving the exact same purpose and it was very confusing for new users, so we had to choose one.
From now on, unless you have a good reason not to, people are encouraged to use only vdjfolders.
We only kept options like browserShowLegacyM3UPlaylists or browserAutoExportM3U for the handful of users who integrate virtualdj with other tools, until these tools can switch to using xml. But if you don't need, you should use only vdjfolders.
But it's more powerful than m3u, it can both contain files and subfolders, have or not duplicates, can be split over several drives, etc.
It made no sense to keep having both virtualfolders, and m3u playlists, since they're both serving the exact same purpose and it was very confusing for new users, so we had to choose one.
From now on, unless you have a good reason not to, people are encouraged to use only vdjfolders.
We only kept options like browserShowLegacyM3UPlaylists or browserAutoExportM3U for the handful of users who integrate virtualdj with other tools, until these tools can switch to using xml. But if you don't need, you should use only vdjfolders.
geposted Mon 08 Apr 24 @ 5:26 pm
kradcliffe
Stephane I just installed the latest early access and noticed that history is still stored as .m3u?
I thought that with the changes everything would be standard as .xml across the whole of VDJ.
I thought that with the changes everything would be standard as .xml across the whole of VDJ.
geposted Mon 08 Apr 24 @ 6:14 pm
the SOUND INSURGENT
kradcliffe wrote :
I thought that with the changes everything would be standard as .xml across the whole of VDJ.
I thought that with the changes everything would be standard as .xml across the whole of VDJ.
And that's where most of my confusion is coming from, unless not everything has been updated yet...
geposted Mon 08 Apr 24 @ 7:54 pm
kradcliffe
Yes it's puzzling me a bit too. What's the point of making changes so everything is universal except it's not ......
geposted Tue 09 Apr 24 @ 10:01 am
djdisturbed
I'm finding the xml folders dont like to behave properly when making list, i put things in a certain order and the folders keep changing that order no matter what I try, the older m3u list behave properly and stay in the order i put them in unless i change the order myself
geposted Fri 12 Apr 24 @ 5:26 am
kradcliffe
Was there ever an answer as to why playlists are now .xml but huistory files are still .m3u?
geposted 19 hours ago
locoDog
Not an official answer but my take on it.
A history file is just a record of what happened, the order of things is the only important bit.
A playlist on the other hand could be this follows that, follows that, but it's more a living list, a work in progress, it could change, it could be added to, it could be reordered, it could be subtracted from.
Instead of the confusion to new users "if you want no repeats use a vfolder, if you want repeats use a .m3u" It's all Lists now, a minor change for the long timers, something easier for new users and if you need m3u for external reasons you can do that too, but generally, in app lists do the job.
A history file is just a record of what happened, the order of things is the only important bit.
A playlist on the other hand could be this follows that, follows that, but it's more a living list, a work in progress, it could change, it could be added to, it could be reordered, it could be subtracted from.
Instead of the confusion to new users "if you want no repeats use a vfolder, if you want repeats use a .m3u" It's all Lists now, a minor change for the long timers, something easier for new users and if you need m3u for external reasons you can do that too, but generally, in app lists do the job.
geposted 19 hours ago
kradcliffe
I understand the change to .xml but am just wondering why history is the old format. Surely it would make sense for all lists generated by the software to be the same instead of some old and some new .....
geposted 18 hours ago