why /var/tmp and not /tmp?


I am no linux expert, but
I believe the difference between /var/tmp and /tmp is that files in /var/tmp should exists after reboot.

My system files are on a usb stick which makes /var/tmp painfully slow. I have /tmp in memory and writing there is fast.

The problem with Audacity is when importing a 40 megabytes mp3 file is that it does a lot of writing to /var/tmp and that it takes 10-20 minutes to import. When symlinking /var/tmp to /tmp
it is takes perhaps 20 seconds to import the file.

The problem with symlinking /var/tmp to /tmp is that it breaks other programs such as ntpd. And that it is not good practice.

I am using the Archlinux and the Audacity package that comes with that.

So I am just wondering if this is intentional to write to to /var/tmp? If it needs to store the sound data it could do it in memory and not need to write so much to disk?
Also wouldn’t it be better to place this temp data in the users home directory? Or be able to configure where to store this?

I tried to enable “read directly from file” in the “import” preferences, but it did not make any difference with this problem.

That’s correct, and it can be a life saver in the event of a crash.

Edit menu > Preferences > Directories

If ArchLinux are still distributing Audacity 2.0.1 or earlier (see Help > About Audacity) then you can enable the option to play and/or record using RAM in Directories Preferences. However we removed that feature from 2.0.2 onwards because it was buggy and tended to crash.

That feature only applies to uncompressed formats. MP3 is a compressed format.