Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Read First: a few posting guidelines (Read 7947 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Read First: a few posting guidelines

Welcome to the CUETools forum.

Please read before posting. The following suggestions are intended to
  • make topics easier to read.
  • make topics easier to search for.
  • reduce repeated questions or replies.
  • help others to better understand what you're trying to say while reducing the number of questions they need to ask you.
We all accepted the terms of the Registration Agreement (aka Terms Of Service) when we registered to join this community so some of this should look familiar.

  • Please search before starting a new topic.
    • Try changing the search terms if unsuccessful on the first attempt.
    • Do not limit your searches to the CUETools forum.

  • When replying to an existing thread, stay on topic.
    • If a thread mentions CUETools, that doesn't mean the thread is about anything CUETools.
    • Your question or comment should not steer the discussion away from the original topic.
    • Read the topic title and first post of the thread to see how the discussion started.
    • If your question or comment is not on topic, start a new thread.

  • When starting a new thread, the topic title should:
    • Properly describe the content of the thread as short but precise as possible.
      • "Problem using CUETools" and "CUERipper Question?" are really short but do not properly describe the content.
      • "CUETools doesn't work on new computer" and "CUERipper - File Naming and Templates?" are short and better describe the content.
    • Only use terms or abbreviations everyone can understand.
      • You should not create a topic title that other forum members cannot read.

  • When reporting problems or requesting assistance, please describe the issue as completely as possible.
    • Provide relevant details such as:
      • Which program version?
      • Which tool were you using?
      • What specifically were you trying to do?
      • What settings did you use?
      • What output format?
      • Which encoder did you try?
      • What were the encoder settings?
      • What did you expect to happen?
      • What happened instead?
    • Provide any additional information you feel may be relevant.
      • Windows version
      • Source file type
      • Source file path
      • Extraction log
      • CUETools accurip log
      • Etc.
    • In case of a crash, exception or error
      • The developer requests that you report bugs directly to the Issue Tracker.
      • If you do need to create a new topic here, please add [crash], [exception], [error], or [bug] to the topic title.

  • Please refrain from adding replies to the pinned topics marked [Release] or [Exp/Dev].
    • The developer will make use of the threads to announce changes, prerequisites, updates, fixes, etc.
    • Adding questions or comments could transform an informative announcement thread into a drifting discussion thread.
      • See 1-4 above. We really don't need another diluted, confusing, hard to search thread with over 3000 replies!

korth