Stereo Tool
https://forums.stereotool.com/

New things...
https://forums.stereotool.com/viewtopic.php?t=4334		 Page 49 of 76
Author:  DJ-DOGGY [ Sun Nov 11, 2012 6:19 am ]
Post subject:  Re: New things...
I cannot tell actual CPU usage , because i have huge jumps .... latest version and betas is about from 25 to 52 % and sometimes CPU usage is constantly say 32-35 .. i don`t know when appears , but most of the time when start the program and see the usage , it have huge jumps.
Author:  Brian [ Sun Nov 11, 2012 8:43 am ]
Post subject:  Re: New things...
Quote:
any crash causes the whole program to lock up (deliberately - there are and should not be any protections against crashes, there just should not be any).
As a developer, that statement doesn't sit well with me, but maybe I don't understand what you're trying to say. Are you saying that you are not doing exception handling at all?
Author:  hvz [ Sun Nov 11, 2012 10:53 am ]
Post subject:  Re: New things...
About these crashes: Can someone tell me which panel was open when you got a crash upon loading a preset? So far I've been unable to reproduce. Screen size and which view is active at the bottom may also be useful information.

@Brian: I use exception handling where I should: File access, web access etc. I don't use it to handle programming errors such as divide by 0 or writing outside of a block of allocated memory. They will - and should - cause the program to crash to I'm forced to fix it, which leads to better software in the end. Although I could probably replace crashing by displaying a popup. Anyway, when I worked at Philips it was actually quite common in cases where you got into a situation that should not occur to just write: *(int*)(0) = 0; - causing a hard crash. We're talking about software used during medical operations etc! Of course this causes program to crash - but in the end you get better software because you have to fix all the crashes. Instead of hiding them and just hoping that nothing else will break as a result.
Author:  Brian [ Sun Nov 11, 2012 1:50 pm ]
Post subject:  Re: New things...
Quote:
@Brian: I use exception handling where I should: File access, web access etc. I don't use it to handle programming errors such as divide by 0 or writing outside of a block of allocated memory. They will - and should - cause the program to crash to I'm forced to fix it, which leads to better software in the end. Although I could probably replace crashing by displaying a popup. Anyway, when I worked at Philips it was actually quite common in cases where you got into a situation that should not occur to just write: *(int*)(0) = 0; - causing a hard crash. We're talking about software used during medical operations etc! Of course this causes program to crash - but in the end you get better software because you have to fix all the crashes. Instead of hiding them and just hoping that nothing else will break as a result.
I'm not really sure that is the best way to handle things. If you're in a situation that "should not occur", to be able to do anything at all, you have to know that you have arrived at something that should not occur.

From your perspective, what is wrong with the following?

Try
{ Try Code block
}
Catch (exceptions) // At first, all exceptions via (...). You could refine it to specific exceptions over time as needed.
{ Catch Code block // Includes code to write various things to a log file or submit the log via internet, and clean up and shut down gracefully.
}

This would unload the app gracefully and would not hide anything. Yes, you'd want to limit the number of try/catch blocks to code that is more fragile, or else it would start dragging down performance.

You could add in a "Submit Crash Reports" option into the application, which would then enable you to add a call stack reporter functionality in the Catch block. Just over the past day, I submitted a crash report to Mozilla for something that happened in Firefox when it prompted me to do so via a handler like what I described.
Author:  Valiant [ Sun Nov 11, 2012 4:04 pm ]
Post subject:  Re: New things...
Quote:
@ Valiant..
Also to me not clear.. are you using preset for FM transmitter or home listening?
Currently, I am just enjoying ST for in home listening, plus been doing some streaming audio, until I recently moved, however I am hoping to run an FM transmitter early next year. :)
Quote:
About these crashes: Can someone tell me which panel was open when you got a crash upon loading a preset? So far I've been unable to reproduce. Screen size and which view is active at the bottom may also be useful information.
I played around with that this morning, I found the fastest way to crash mine was to (at default opening screen) click "RESET" (All settings - Factory Reset), then select "Generic Presets" (not necessary to select any profiles) then scroll down and try to select "FM Radio Stations - US (75us)" Crash achieved every time on my system. :roll: hmm, screen size?, it doesn't crash when it is at full screen. :roll:
Author:  Bojcha [ Sun Nov 11, 2012 10:48 pm ]
Post subject:  Re: New things...
Apparently you don't like clearer highs then :)
Image
Author:  hvz [ Sun Nov 11, 2012 10:50 pm ]
Post subject:  Re: New things...
Quote:
I played around with that this morning, I found the fastest way to crash mine was to (at default opening screen) click "RESET" (All settings - Factory Reset), then select "Generic Presets" (not necessary to select any profiles) then scroll down and try to select "FM Radio Stations - US (75us)" Crash achieved every time on my system. :roll: hmm, screen size?, it doesn't crash when it is at full screen. :roll:
Not here, tried about 20 times on a lot of different window sizes... :(

Edit: GOT IT! I needed to make the window really small so there's a scroll bar. Trying to fix it now....
Edit: Scroll bar is bigger than the window. Causing writes outside the allowed memory area.
Edit: Fixed. Problem was: If you open a SMALLER sub-section, with the scroll bar at the bottom, the scroll bar position is too low. The first redraw that occurs shows too few lines of text, but worse, the image that shows which part of the scrollable area is visible partially falls outside the window. That caused the crashes.

I'll build a new version with this change, display code is also more optimized by combining some steps (on my system the CPU load is about 3-4% lower than in the previous version when processing at maximum speed, large screen size; throughput has not changed).
Author:  gpagliaroli [ Mon Nov 12, 2012 3:53 am ]
Post subject:  Re: New things...
First of all, I like the new look of ST, looks very professional!

I'm a little late, but I use to have some details that I have seen on the last beta37 ... :)

- Quality control CPU has an offset error is half in the bar when the value is 60% instead of 50%.
- Consumption per core CPU is not even, in my case (AMD Dual Core), Core 2 is a 50% consumption with more than core 1. Besides being a bit high (in my case the average is around 75%, 10% more than the 6.32 version)
- Bass indicator AGC is not visible due to the combination of very light colors.
- Would be good, that when moving the mouse over a control, a short description appears indicative of the same (as the comments Previous versions were fixed in the form) ;)

good job! ;)
Author:  hvz [ Mon Nov 12, 2012 6:59 am ]
Post subject:  Re: New things...
Stand alone: http://www.stereotool.com/download/ster ... 33-038.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 33-038.exe
VST: http://www.stereotool.com/download/vst_ ... 33-038.dll
Command line: http://www.stereotool.com/download/ster ... 33-038.exe

Fixed:
- Improve GUI drawing performance
- Hangup on preset loading fixed

TODO:
- Add sound card display to status bar (?)
- Move status bar up a few pixels when display is very small (no bottom section)
- Mouse unresponsive reported
- Mouse shape
Drawing issue (things are drawn outside the allowed area, threading issue)

Less urgent for usability:
- Design (several people are working on something)

For later:
- Multi-language support
- Add basic/advanced modes
- Add '-6' '-12' etc. beside output bars where possible.
- Context sensitive Help (help button should be next to the preset buttons)
- Drag (resize window parts) lines, also between to/bottom part (scopes/meters).
- Confirm on close (stand alone version)
Author:  DJ-DOGGY [ Mon Nov 12, 2012 8:55 am ]
Post subject:  Re: New things...
Why i see a line under the Pilot signal in the MPX window ?
Horizontal line .
When play some music , this line goes over all MPX signal from left to RDS signal ...
Hans check that one.

And one more : When click on message for registration and Registration window too, again when click on "Cancel" the program goes down minimized and when click on it ...goes to taskbar.Then i must click on the icon to restore it again !
Page 49 of 76 All times are UTC+02:00
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/