I installed the latest version and snap (v2.1.43 b486) and the auto determine cue points isn’t working, or am I missing a ‘new’ setting? All software is clean installed on this comp.
On a other computer mAirList crashed (computer reboots) when I try to PFL a track from the playlist (v2.1.43 b484)… with no error report (oke, on this case I don’t trust this computer).
The [FileImport] section is literally only half the story. Do you have a [General] section in your mairlist.ini—probably the first section in the file? Mine looks like this:
If those (dB) Threshold values are not set, mAirList will not automatically set the cue points. (Incidentally, which values do other people use for these? I find that the ones above work very well!)
I am using v2.1.43 b486 here and the automatic cue points work AOK. During the time a file is being auto-cued, you should (briefly!) see a small dialog box centred on the main mAirList window, with a title bar which reads Preparing file ….
[quote=“Cad, post:12, topic:4755”]If those (dB) Threshold values are not set, mAirList will not automatically set the cue points. (Incidentally, which values do other people use for these? I find that the ones above work very well!)
BFN
CAD[/quote]
Hello CAD,
These settings are present in the mAirList.ini :
Umm … that is normal in European mainland countries, and because locale=nl (Goedemiddag, Vincent! ) I expect that Vincent’s Windows Regional Settings (Nederlands? ) specify , as the decimal separator and . as the ‘thousands’ separator—the exact opposite of the standard for USA and UK. So to sum up, Charlie, that is a red herring.
The non-appearance of the ‘Preparing file …’ dialog is more puzzling, because here, that dialog appears for every file dragged from Windows Explorer (or a mAirList Browser Directory pane) and dropped on to the Playlist! It doesn’t matter whether or not the file has previously been tagged with cue points: the dialog is (ik denk) informing you that mAirList is trying to load the corresponding MMD file, so the dialog should always be displayed when a file is added to a Playlist.
Vincent: have you tried this with build 486 installed, which is the mAirList.exe currently in the Snapshot download directory?
[later] Oops! Looks like you have tried this. I admit I’m stumped by this one. ???
The dialog appears everytime a file is imported into the playlist, and its tags, MMD file or auto-cue values are loaded. When auto-cue is disabled, and you only import a single file, the dialog might disappear again in the same moment, because the operation finishes so fast. I introduced the dialog because I thought it was good to have a feedback when performing lengthy file imports, just like dropping hundreds of files into the playlist with auto-cue enabled.
In the German forum, other people have reported strange errors related to BASS.DLL, only ocurring in v.43 but not in the previous snapshot. This misterious auto-cue bug might also be related to BASS.DLL. In between snapshot 484 and v.43, I have changed the way in which several internal components are initialized, including the interface to BASS.DLL. However, these changes are not relevant for version 2.1 (but only for v3.0, which I have started to prepare - more details to follow). I will undo a these changes and prepare a new snapshot based on .v42-484, plus the bug fixes since then (yes, Cad, also stop logging). Let’s see if that helps.
I was careful when I copied mAirList.exe (from the ZIPfile) into my (dev) mAirList program directory, to also copy all the BASS DLLs in the ZIPfile, just in case they were updated or different versions from the existing BASS DLLs in my (dev) mAirList program directory.
Could that be a possible reason for the BASS problems the German forum users are seeing? b486 is working 100% fine here.
I’d rather say it’s related to the initialization changes.
I have now uploaded Build 487. As mentioned above, this is v.42 Build 484 plus all bug fixes since then. No other internal changes. Please give it a try.
And by the way, as I mentioned mAirList 3.0, here’s a little information about it:
It will be released very soon, but still in development status. It will have roughly the same feature set and interface as mAirList 2.1, but with massive changes in the internal structures, code cleanup etc. I figured that these changes are necessary in order to prepare the forthcoming stable release, which will be mAirList 3.1.
I will continue to provide bug fixes for v2.1 until v3.0.0 is out. Thereafter, I will concentrate on adding the final “urgent” features and fixing the remaining bugs in v3.0, and then release v3.1. I think it time is due for a new stable release.