Audacity Forum

Thanks for the report. The case of Chains was clearly missed during testing.

Ideally you would use exactly the same studio set-up every time. If necessary, write down which microphone you used, distance from mouth, where you sat, equipment settings ... every detail required to get the "studio" set-up the same each time. Beyond that, it is mostly a matter of practic...

It's not my media player -- I tried the files in both iTunes (which supports gapless playback) and in VLC, and tried it using both FLAC and m4a files. (I'm on a Mac, but I don't think that matters.) Did they play the tracks as a continuous rising tone with no gap or glitch at the change over from &...

That could be pretty tough to achieve reliably and cross-platform. How would you deal (for example) with Jack Audio System? I don't think that Jack tells the application what device it is connected to. What about PulseAudio? In this case the selected device as far as Audacity is concerned is PulseAu...

I suspect the problem may be with your media player.

These two files do match up exactly. If you set your player to play one after the other, it should be gapless (it is on my media player, but I'm on Linux). If there's a gap between them, it's your media player.

It's neither a bug or your set up. The playback level slider doesn't really do anything - it's just an alias for the primary sound card main output level control. It's a convenience for many users that either have just one sound card, or only use the primary device. It's no substitute for a full fea...

There's no longer a "Convert Selection to MP3" option There never has been. There's an article in the Audacity manual about splitting a long recording into separate tracks: http://manual.audacityteam.org/man/splitting_a_recording_into_separate_tracks.html Note that one of the limitations ...

Sounds like the two sound cards are conflicting with each other, Why not remove / disable one and just use whichever is the better of the two?

And another update - It has been fixed for the next release, which is due out in December.

Just a quick update.
I've found the cause of the bug. It's now in the hands of the release manager to decide if it will be fixed in the next release. Fingers crossed