When I try to open a .eaf file or make a new file and import audio, ELAN stops responding and is stuck on initializing. I have tried to uninstall and reinstall the app but the same error occurs. I’m using an Apple M2 Pro with Sonoma 14.4.1. Any advice is appreciated.
It sounds like there is a problem with creating a media player for the media file. What type of media file(s) are you using (format, encoding etc.)?
If the user interface is still responsive (when it is stuck while initializing) you could go to View->View Log… and see if there are clear error messages at the bottom of the list concerning the creation of a media player.
Otherwise these might be found in the file elan0.log (elan1.log etc.) in the ELAN data folder.. (No need to post the entire content here, in case of doubt you can send the log(s) to me han.sloetjes AT mpi.nl )
Thanks for the log messages. It is strange to see messages from the AudioExtractor, which is only used for extracting audio samples from video files or audio files other than .wav files. Uncompressed .wav files are handled by other (Java or non-native) classes in ELAN. So, if the files are really .wav files, maybe they use some type of compression which is (also) not supported by Apple’s AVFoundation?
Maybe you can check with some tool how the files are encoded or maybe you can try if converting to uncompressed .wav helps? In case you have a representative test .wav file which can be shared, I’m happy to have a closer look.
With apologies; there had been a follow up on this and I intended to post a follow up here, but failed to do so.
An example .wav file was sent to me which appeared to be encoded with mu-law compression, which is not supported by our own .wav file reader. It is then possible to have the audio samples extracted or produced by one of two so called ‘native’ frameworks, AVFoundation or FFmpeg, as available in the Edit Preferences window in the Platform/OS tab. Both options may fail, for different reasons. In case of .wav, it is best to use an encoding without compression.
But it may be that in your case something else is going wrong, for that we would need the output of the log file, as described in the earlier post.