image description


Helpful guidelines for reporting issues (potential bugs) with Studio One.
  Forum Index » Studio One Forum Community Support 
Author
Message
jpettit
Presonoid
[Avatar]

Joined: 13/01/2011 23:44:45
Messages: 2211
Location: Portland Oregon
Offline

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 area

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
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 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.
    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
    Free screen capture video tool to share short clips of the issue: http://www.techsmith.com/jing.html
    A 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/

    Bugs that are "confirmed" will eventually be fixed.
    Hope this is helpful to some...
    My Website
    FRs: Tempo Detection & Mapping
    Training Videos: Advance Melodyne, Creating Macros, 2.5 New Features, Signal Flow, Audio Timing Drum Replacement, Tempo Mapping, Useful Macros, Transformations, Layer/Takes/Comps
    Simultaneous Audio Interfaces: Audiobox 1818VSL, RME 9632, Line 6 UX2, HF Presonus HP-60
    DAWs: Studio One Pro 2.6.1, Reaper 4.5, Sonar X3c Pro, Adobe Audition CS5
    Computer: OS:Win7 64-bit, Core i7 950, ASUS P6X58D Premium, 12GB DDR3 1600, GeForce GTX 470 (for CUDA) ,SSD Boot & Cache drives, 1 Tera 7200 RPM SATA II Audio & Video drives, UAD-2 x2
    [WWW]
    scottyo7
    Presonic
    [Avatar]

    Joined: 21/11/2012 01:42:35
    Messages: 579
    Location: Seattle, WA., USA
    Offline

    Nice... I've always wondered how people were attaching animated and static gifs.

    So if we report a supposed bug and our hardware (in sig.) isn't officially supported any longer, will "Tech support" give our report any credence?
    ASUS G75VX, i7 3820QM, 16GB Ram, 2 Samsung 840 256GB SSD's; Win8.1 64; Thunderbolt-Firewire 800 converter (TI chipset).
    S1P 2.6.1; PreSonus FP10; EZdrummer 2.0.1, 64; Alchemy 1.55 64. Melodyne Editor 64 - 2.1.2; Izotope Alloy 2 & Ozone 5.
    Carvin, ESP, Ibanez, Martin & Yamaha guitars.
    Roland Fantom S; Rode NT1; SM58. Line 6 POD HD500 & POD XT-Live. BBE 422A; KRK Rokit 8 Powered Studio Monitors.
    Band site: https://soundcloud.com/2guyzinabasement
    [WWW]
    jpettit
    Presonoid
    [Avatar]

    Joined: 13/01/2011 23:44:45
    Messages: 2211
    Location: Portland Oregon
    Offline

    scottyo7 wrote:Nice... I've always wondered how people were attaching animated and static gifs.

    So if we report a supposed bug and our hardware (in sig.) isn't officially supported any longer, will "Tech support" give our report any credence?

    I cant speak for Support. I am not a Presonus employee.
    However, that is the power of the "expected, actual, steps to repeat model." Other people can attempt to repeat it.

    If they can and they have different hardware, then you have removed the hardware from the equation.

    Remember that is what this thread was an example of: http://forumsarchive.presonus.com/posts/list/41207.page

    A picture is worth a 1000 words. Especially in a forum where the developers and many of the member speak a different native language.



    My Website
    FRs: Tempo Detection & Mapping
    Training Videos: Advance Melodyne, Creating Macros, 2.5 New Features, Signal Flow, Audio Timing Drum Replacement, Tempo Mapping, Useful Macros, Transformations, Layer/Takes/Comps
    Simultaneous Audio Interfaces: Audiobox 1818VSL, RME 9632, Line 6 UX2, HF Presonus HP-60
    DAWs: Studio One Pro 2.6.1, Reaper 4.5, Sonar X3c Pro, Adobe Audition CS5
    Computer: OS:Win7 64-bit, Core i7 950, ASUS P6X58D Premium, 12GB DDR3 1600, GeForce GTX 470 (for CUDA) ,SSD Boot & Cache drives, 1 Tera 7200 RPM SATA II Audio & Video drives, UAD-2 x2
    [WWW]
     
    Forum Index » Studio One Forum Community Support
    Go to: