1 post
Page 1 of 1
Here are some helpful guidelines for reporting issues (potential bugs) with Studio One.
I can personally testify that if you do follow it, the chances of your particular issue being fixed are GREATLY increased.
I have had more than two dozen issues fixed in a timely manor.

First is the issue a bug?
A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. A serious bug may cause the program to crash or freeze.

If you believe you have such an issue REPORT IT TO SUPPORT first. http://support.presonus.com/home

Some issues may not be consider a “bug” by the developers as it is in fact the developers “intended” behavior or just and area that has not been coded yet.. In other words your “expected” behavior and the developers “expected” behavior are out of sync.
You have two options:
a) re- align your “expectations” or
b)Write up a new FR with your preferred behavior , but be sure to post it in the Feature Request database http://answers.presonus.com/

It is best to call it an issue until others have confirmed it as a bug.

DEFACTO STANDARD for Error Reporting.
This is the de-facto software industry standard for reporting errors (in order to be able to reproduce them)
1) Always make sure your system software and hardware is in the report. Most add it to thier signature line. Specifically OS version 32/64 bit, the version of the software you are testing, and hardware if applicable See my signature for a link to add your specs.
2) Describe the “expected” behavior
3) Describe the “actual” behavior: be specific: ( a picture is worth a 1000 words)
.You will notice many users will always take the time to add an animated gif, or a Jing video clips to help explain the issue

4) Describe the “steps” required to reproduce the error ( do this with text or video/animated gif)
If the error can’t be reproduced, odds are you are NOT going to see it fixed.

An error that can be reproduced on more than one system has more credence and increases its priority.

Always post your technical issues or potential bugs to SUPPORT first and then if needed post the issue as a "open questions" in the Community Support area and ask for others to confirm it.

How to questions are only supported through the help manual and the community forum.
Help the others in community verify issues by trying to reproduce the error on your system. No matter what your results is “confirmed” or “not confirmed” it helps to further define the situation.

Here are a few helpful links:
Support: http://support.presonus.com/home
A free screen capture video tool to share short clips of the issue: http://www.techsmith.com/jing.html
A free tool to create animated GIFs of the issue: http://www.cockos.com/licecap/
You will need a server to put your animated GIF’s on: https://www.dropbox.com/install or http://www.google.com/drive/
NEW IMPROVED GIF MAKER https://screentogif.codeplex.com/
Snagit: Pro Screen Capture,Animated GIF, Screen Video recommendations: https://www.techsmith.com/snagit.html ($49.95 US)
Camtasia Studio: Pro level Screen videos for tutorials https://www.techsmith.com/camtasia.html ($299 US)

How to add pictures to your post. viewtopic.php?f=145&t=5262
Bugs that are "confirmed" will eventually be fixed.

How To Get Your Issue Fixed
To add your specs to your signature, click HERE
For FAQ or to submit a request go to Presonus Answers
My Website, Free Studio One Advance Training
Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, Studio 192, Faderport 8, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Line 6 UX2, Studio One Pro 3.4, Reaper 5.4, Sonar Platinum

1 post
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 7 guests