After looking at this some more I have to ask, doesn’t this have more in common with AES31 or Cue Image with pointers and paths to other files than it has to basic cd track list reporting, and names from a source cd tracklist that have no reference to the final file paths the M3U can refer to.
I think the easiest way to approximate this in current Wavelab is probably this:
Create a Basic Audio CD.
Drag in your final files (in your case your final MP3s).
Convert to montage.
Go to the Files tab and export the file names with extension (with or without paths !!!).
The advantage this has is that it’s referring to the real files with their extensions that will be referenced in the M3U. And they can be a mix of different file types and sample rates.
The other limiting thing about just taking CD Track names is that M3U can refer to the mix of different file types (wav mp3 m4a, flac, ogg) and sample rates, and DIFFERENT file paths all in one M3U document.
I think if M3U would be integrated in Wavelab it should include this basic functionality, and not be limited to mp3 and only relative path. Right now it seems very easy to drag all these file types, even with different sample rates into a Basic Audio CD to get the final names for the M3U.
It’s kind of a cool thing, I tried it with MS Groove player, a mix of wav, mp3, aac, 96 and 44.1 k all in one M3U.
But I have to ask, in your particular case, if you’re using one folder and M3U with internal relative path, is it any better than just playing a folder of MP3s on a stick in the car? Don’t the MP3 folders playlist themselves in most players now?