General Guidelines for Posting to Resources

Forum users are creating and posting more content than ever before and this is wonderful :). Here are some suggestions to help both those creating content and just as importantly, those who download it.

  1. CHECK FIRST. Before going to the effort of creating and uploading a song or drum kit, your first step should be to always search the forum to see if the song has already been uploaded and in which format, e.g., multi-part or one-press bass (OPB). If it has been posted already and you still intend to forge ahead, please state what’s different about the song i.e., multi-part, OPB, different key, etc.

  2. ZIP IT. It’s good when users include tabs, chords and lyrics (cheat sheets) with their songs; sometimes, hunting down, verifying and transposing cheat sheets takes more effort than actually transcribing the song in a DAW. Content creators are encouraged to include the midi source file (unless it’s purchased from a vendor). When all’s said and done, there are at least 3 files for a song/beat that are uploaded: the .sng, the cheat sheet and the midi source file. Rather than uploading 3 separate files, take one extra small step to compress these 3 files into a single file. Makes it easier to download, and saves a little (but probably not much space on the server).

  3. DO NOT DOUBLE POST. Unless you’re filling a user’s specific request, there’s no need to upload the song to Resources and then to advertise by posting in the general discussions or other part of the forum.

  4. THANK THE UPLOADER. It’s not that difficult and it let’s the content provider know that his or her efforts are recognized and appreciated. Take an extra step and rate the song—but if you’re going to criticize, please offer constructive feedback (if it’s going to be hyper critical, it might be better to contact the user that uploaded the song via private message). NOT HELPFUL: “your song sucks el big wazoo” HELPFUL: "the 3d verse in the song is missing or “hey, the bass or keyboard notes are clipping in the chorus.”

  5. OTHER.

  • try to transcribe the song for the key it was performed in; if it isn’t, point out which key it’s transcribed in. If there’s no mention of a key, it’s presumed that the song is transcribed to match the performance key. This is why it’s a thoughtful touch to include the midi source file—if a user wants to transpose the song to a different key, the user will have the source file to try his own luck.
  • include a count-in for the song, especially if there are several measures before the drums begin to play;
  • it’s always nice to include (but not a requirement) instructions on the cheat sheet e.g., start strumming or singing after the 4th bass drum hit on the count-in;
  • provide notes when adding a song or a drum kit to Resources. Many users do so and it’s helpful.