Community of Sexsoundlovers

There is a file size limit of [new! - see below explanation] +50mb for individual attachments due to server restrictions.
If you have bigger files to upload you may choose from one of the following proceedings:

• Split your files (recommended) using a tool like e.g. 7zip (recommended, open source), mp3splt (open source) or mp3 splitter & joiner (shareware). There are more tools around, these are the ones I am happy with.

• Reduce your files by a) converting wav to mp3 or b) reducing quality. The bit rate needn´t exceed 128kbps and there is no effect at all (except an increase in file size) in converting a file to a higher bitrate than the original.

• Upload your file to an external hoster that offers good conditions for free users and link to it in your message.

• Or ask for assistance and you will be helped out.

There also is a total file size limit for all attachments which is set by the admin. This limit is set to 6 gb for the forum. If the total size of all uploaded files comes near this capacity limit, a number of older attachments will be deleted here. You will find all files ever collected (over 73gb now) in the archives.

If you see a message talking about uploaded files but without an attachment, the files have been archived already.
Depending on the uploaders´activities, files are kept in the forum between 3 and 6 months usually.

Explanation: Today I managed to set the max upload file size to 64mb ... theoretically. I wasn´t able to upload a 62 mb file but a 55mb file made it. So please be patient

I wonder if they are counting one K as 1000 bytes instead of 1024. The old marketing vs storage capacity trick. Hard drive manufacturers used to play that game.

reggind wrote: ↑19 Jul 2017 04:52 I wonder if they are counting one K as 1000 bytes instead of 1024. The old marketing vs storage capacity trick. Hard drive manufacturers used to play that game.

Yeah, that could be an explanation. But on the other hand, uploading 32mb files worked when the setting was 32mb. I guess it is one of the other settings ... max.execution.time has been doubled already but that didn´t help.