This is a very specific issue I've noticed, and it's starting to bother me a little bit. Let me go into detail so you all know exactly what's happening:
When I use the Media Library search window in Foobar2000 and it brings up a list of audio files matching my search criteria, if I then sort those files by some tagging field other than filename, select multiple files that are next to each other after sorting them, and then use drag and drop to import them into an Adobe Audition Multitrack sequence directly from the Foobar Media Library Search window, for some reason they are imported into Audition in the order that they appeared in the original search (alphabetical order), before sorting them by some other tag metadata. Take the following example:
BEFORE SORTING:
(https://image.ibb.co/jDC7Dn/before.png) (https://imgbb.com/)
IMPORT UNSORTED SONGS INTO AUDITION:
(https://image.ibb.co/noNJKS/beforeaud.png) (https://imgbb.com/)
AFTER SORTING:
(https://image.ibb.co/b10im7/Screenshot_1.png) (https://imgbb.com/)
IMPORT SORTED SONGS INTO AUDITION:
(https://image.ibb.co/d5DQzS/afteraud.png) (https://imgbb.com/)
You'll notice that, in both cases, they were imported in the same order when I used drag and drop despite, in the second case, being displayed in Foobar in a different order. Naturally I'd like the album to play in the order of track number inside Audition, but as you can see, that's clearly not the case.
I know that this is a very specific issue, but I'm just kind of curious; what's going on here? Is this even a bug with Foobar's drag and drop? If so, can it actually be fixed? Or perhaps is it a bug on Auditon's end? Thanks.
EDIT:
For reference, if I sort these files by track number in File Explorer and then drag and drop them into Audition, they are imported in the correct (sorted) order, and NOT alphabetically anymore. So it must be something on Foobar's side of things.
Issue confirmed and fixed for the next update, thanks for reporting.
Nice!
Issue confirmed and fixed for the next update, thanks for reporting.
You mentioned that this issue was fixed, but I'm not exactly sure which update fixes it. I downloaded the newest version 2018-06-14 foobar2000 v1.3.19, but the issue still does not seem to be resolved in this version.
Am I being too impatient? If so, in which version should I be expecting the fix? Sorry for any inconvenience.
^ Check if it's fixed in the latest beta.
Okay, it's fixed in the beta release. Thanks!