New machine, new software install, brand new 3.8.5 Platinum from scratch.
I have Winamp 5.541, WinXP Pro SP3. Big fast machine. Winamp configured to NOT automatically start visualization plugins. Instead, I do it manually with CTRL+SHIFT+K.
Everything works fine.
However each time G-Force starts I get "Soundspectrum log.txt" created and written to the desktop. I want to suppress that.
How? Where/what is the setting, either in Global Preferences or Preferences (Winamp), to suppress this startup log? Can't find it in any documentation.
Thanks.
NOTE: if I change Winamp to go ahead and automatically start visualization plug-in, sure enough the soundspectrum startup log IS PREVENTED! However if I use CTRL+SHIFT+K to start it I always get the log.
Surely there is a setting to prevent this!
Why do I get "Soundspectrum log.txt" created at st
Moderators: BTT, andy55, b.dwall, juxtiphi
Just in passing (again), if the window is open (regardless of auto-open or manually opened) and you re-size it, those internal details are again presented onscreen in the window and the SoundSpectrum log.txt is again created on the desktop.
So this looks not like a startup settings issue, simply to prevent the details from appearing using CTRL+SHFT+K. Rather it looks like new program behavior (which I wish I COULD PREVENT!) where it apparently displays some newly re-calculated internal values necessary for its operation, and also writes those numbers as a txt file to the desktop.
I don't mind if the program has to re-calculate things to operate in a newly opened or re-sized window. But shouldn't I be able to suppress the display of those values, and the unwanted creation of a desktop txt file?
So this looks not like a startup settings issue, simply to prevent the details from appearing using CTRL+SHFT+K. Rather it looks like new program behavior (which I wish I COULD PREVENT!) where it apparently displays some newly re-calculated internal values necessary for its operation, and also writes those numbers as a txt file to the desktop.
I don't mind if the program has to re-calculate things to operate in a newly opened or re-sized window. But shouldn't I be able to suppress the display of those values, and the unwanted creation of a desktop txt file?
dsperber wrote:Just in passing (again), if the window is open (regardless of auto-open or manually opened) and you re-size it, those internal details are again presented onscreen in the window and the SoundSpectrum log.txt is again created on the desktop.
So this looks not like a startup settings issue, simply to prevent the details from appearing using CTRL+SHFT+K. Rather it looks like new program behavior (which I wish I COULD PREVENT!) where it apparently displays some newly re-calculated internal values necessary for its operation, and also writes those numbers as a txt file to the desktop.
I don't mind if the program has to re-calculate things to operate in a newly opened or re-sized window. But shouldn't I be able to suppress the display of those values, and the unwanted creation of a desktop txt file?
GF has a verbose mode so that you can see onscreen details press the \ when using GF to stop this.
about the log file, GF can create a log file for debugging purposes.
I cannot remember how to start or stop it but its not supposed to create a log each time you start GF unless you are trying to find a problem.
I'm surprised "verbose mode" is apparently the default. It never was before now.juxtiphi wrote:I cannot remember how to start or stop it but its not supposed to create a log each time you start GF unless you are trying to find a problem.
Again, it does not occur on auto-open (i.e. if Winamp specifies to auto-start the visualization plugin, so that the G-Force window opens automatically). It occurs with CTRL+SHIFT+K to manually start G-Force (assuming I do not have it auto-started in Winamp).
But regardless of the startup story, once opened (however that happened) if I merely resize the window I get the same playout of values and again the log file is saved to the desktop. That definitely should not be normal default behavior.
Surely there is a way to suppress this behavior if it's optional. I also think the opposite behavior should be the delivered default in a newly created set of PREFS files on a brand new install.
Now if only Andy would weigh in here and indicate what the answer is, or what that controlling option is so that I can change its value...
Absolutely did not go away.juxtiphi wrote:there is a new version of GF try installing it and see if it goes away
Once again, my G-Force window is NOT auto-started, but rather I use CTRL+SHIFT+K to launch it when I'm ready. And once again, SoundSpectrum Log.txt appears in the window and is also created on my desktop.
VERY VERY ANNOYING!
In fact, after installation of the new version I see that the good old Toolbar (which I had suppressed previously) reappears on first program launch after install. Once again, I have to turn it off (in toolbar preferences)... which works, so it doesn't appear again.
Then I looked at the other "preferences" (which I'd also customized significantly for all of the timing formulas in all previous version of G-Force) and notice that the new "Preferences (Winamp).txt"" file is 100% changed in structure and content from all previous versions that have ever existed! And yet this is just an "upgrade" (i.e. from 3.85 to 3.9), not a "new version (i.e. 4.0).
Anyway I'll now have to research where and how to accomplish any customizations to the equivalent timing formula statements or methods in the new 3.90 version (I prefer transitions to occur much sooner and more frequently than the "base" preferences facilitated). I guess I'll have to read the new README or documentation, and hope all of my questions as to how to customize this new "preferences" technique has been updated along with the release of v3.90 and will be explained fully and completely.
Anyway, to answer your question... SoundSpectrum Log.txt STILL APPEARS IN THE G-FORCE WINDOW AND GETS CREATED BOTH (1) WHEN G-FORCE IS MANUALLY STARTED, and (2) WHEN G-FORCE WINDOW IS RE-SIZED (not when it gets repositioned, just when it gets resized).
GRRRRR....................
Why doesn't Andy fix this so it doesn't happen by default, and/or provide the answer as to how this behavior can be permanently suppressed through some setting somewhere?
IT IS ANNOYING AND UNNECESSARY!!!
New obvservations.
Unhappy with mystery surrounding new v3.90 "Preferences (Winamp).txt" I decided to go back. I had thought the problem with SoundSpectrum Log.txt was something new with 3.85 so I decided to go back to 3.84, just to confirm or deny.
Well, much to my surprise, it appears to have been present even with 3.84!
I suspect my sudden awareness of this issue arose sometime over the past few months when I decided to turn off auto-start of G-Force with Winamp, instead choosing to launch it manually when desired with CTRL+SHIFT+K. I did this when I began using MP3 Organizer programs to select/play MP3 tracks and the auto-start of G-Force was generally not what I wanted. Anyway, this setup is only a few months old for me, as before this I always had auto-start of G-Force and therefore never saw the SoundSpectrum log.txt situation (since it does not occur with auto-start).
Ok... uninstalled 3.90, made sure all Soundspectrum directories were clear (in Program Files as well as Documents and Settings, and installed 3.84. Started Winamp, manually started G-Force, and... surprise... NO log file created! Well, I thought, must have started with 3.85.
Closed Winamp, re-started Winamp, started playing an MP3 track, and then started G-Force manually. Lo and behold... SoundSpectrum Log.txt now appears and gets created on the desktop!!!
So, doesn't happen on the very first manual launch after install, but happens on second and subsequent manual launch after install? Seems odd, but that's what seems to happen.
Well now that I realized it wasn't something that started with 3.85 I decided to upgrade from just installed 3.84 to 3.85 (which can still use my long-standing customized prefs).
Did that, started 3.85 for the first time after install, manually launched G-Force, and sure enough NO SOUNDSPECTRUM LOG.TXT! Just like with the first launch after 3.84.
Closed Winamp, re-opened Winamp, started playing an MP3, manually launched G-Force. Lo and behold... SoundSpectrum log.txt once again now appears and also gets created on the desktop!!! Just like with 3.84, first manual launch after install of 3.85 does not create the log, but second and subsequent manual launch creates the log!
So... seems to have been present on 3.84 as well, and even earlier for all I know. As I stated above, I haven't been using manual launch but for the past few months. I'd always auto-started it with Winamp over the past years.
Anyway, I'll stick with 3.85 for now since at least I can use my long-standing G-Force customizations in Preferences (Winamp).txt, which has the same structure it's pretty much had for 10 years now.
When a documented description of the 100% brand new variables in v3.90 Preferences (Winamp).txt is published so that we know how it works and how to customize it I will install v3.90 (or newer) again.
Until then, I'm at 3.85.
Now if only I (or Andy!!!) could/would suppress this ridiculous SoundSpectrum Log.txt at (1) manual launch 2 and subsequent after initial install, and (2) any time window is re-sized, I'd be a happy customer again and be guaranteed to renew my maintenance agreement (and continue to give you my money) when it expires in April.
Unhappy with mystery surrounding new v3.90 "Preferences (Winamp).txt" I decided to go back. I had thought the problem with SoundSpectrum Log.txt was something new with 3.85 so I decided to go back to 3.84, just to confirm or deny.
Well, much to my surprise, it appears to have been present even with 3.84!
I suspect my sudden awareness of this issue arose sometime over the past few months when I decided to turn off auto-start of G-Force with Winamp, instead choosing to launch it manually when desired with CTRL+SHIFT+K. I did this when I began using MP3 Organizer programs to select/play MP3 tracks and the auto-start of G-Force was generally not what I wanted. Anyway, this setup is only a few months old for me, as before this I always had auto-start of G-Force and therefore never saw the SoundSpectrum log.txt situation (since it does not occur with auto-start).
Ok... uninstalled 3.90, made sure all Soundspectrum directories were clear (in Program Files as well as Documents and Settings, and installed 3.84. Started Winamp, manually started G-Force, and... surprise... NO log file created! Well, I thought, must have started with 3.85.
Closed Winamp, re-started Winamp, started playing an MP3 track, and then started G-Force manually. Lo and behold... SoundSpectrum Log.txt now appears and gets created on the desktop!!!
So, doesn't happen on the very first manual launch after install, but happens on second and subsequent manual launch after install? Seems odd, but that's what seems to happen.
Well now that I realized it wasn't something that started with 3.85 I decided to upgrade from just installed 3.84 to 3.85 (which can still use my long-standing customized prefs).
Did that, started 3.85 for the first time after install, manually launched G-Force, and sure enough NO SOUNDSPECTRUM LOG.TXT! Just like with the first launch after 3.84.
Closed Winamp, re-opened Winamp, started playing an MP3, manually launched G-Force. Lo and behold... SoundSpectrum log.txt once again now appears and also gets created on the desktop!!! Just like with 3.84, first manual launch after install of 3.85 does not create the log, but second and subsequent manual launch creates the log!
So... seems to have been present on 3.84 as well, and even earlier for all I know. As I stated above, I haven't been using manual launch but for the past few months. I'd always auto-started it with Winamp over the past years.
Anyway, I'll stick with 3.85 for now since at least I can use my long-standing G-Force customizations in Preferences (Winamp).txt, which has the same structure it's pretty much had for 10 years now.
When a documented description of the 100% brand new variables in v3.90 Preferences (Winamp).txt is published so that we know how it works and how to customize it I will install v3.90 (or newer) again.
Until then, I'm at 3.85.
Now if only I (or Andy!!!) could/would suppress this ridiculous SoundSpectrum Log.txt at (1) manual launch 2 and subsequent after initial install, and (2) any time window is re-sized, I'd be a happy customer again and be guaranteed to renew my maintenance agreement (and continue to give you my money) when it expires in April.
Still no reply providing the magic setting somewhere to prevent this behavior?
Are we to believe that creating a SoundSpectrum Log.txt file on the desktop every time G-Force is (a) manually started or (b) window resized, was intentional by the developer?
Come on! It's for debugging, when needed. So yes, if requested (manually somehow or through the sought-after setting) I'll be glad to generate it and email it along to help fix some bug.
But in normal mode it is absolutely NOT WANTED and ANNOYING! Every time I start the program I have to delete it from my desktop... BECAUSE I DON'T WANT IT ON MY DESKTOP OR ANYWHERE ELSE FOR THAT MATTER!
I want to suppress it, in normal program mode. Surely that's a reasonable request.
Are we to believe that creating a SoundSpectrum Log.txt file on the desktop every time G-Force is (a) manually started or (b) window resized, was intentional by the developer?
Come on! It's for debugging, when needed. So yes, if requested (manually somehow or through the sought-after setting) I'll be glad to generate it and email it along to help fix some bug.
But in normal mode it is absolutely NOT WANTED and ANNOYING! Every time I start the program I have to delete it from my desktop... BECAUSE I DON'T WANT IT ON MY DESKTOP OR ANYWHERE ELSE FOR THAT MATTER!
I want to suppress it, in normal program mode. Surely that's a reasonable request.
Have heard back from SoundSpectrum in reply to my recently opened support ticket on this issue:
"I am able to duplicate the behavior you describe, though it does not appear that there is a workaround I can provide you to stop this from occurring. I am opening a bug report with our developers so that they may hopefully address this in a coming release. I can only suggest for the time being that you launch G-Force within Winamp by clicking the "View" menu and choosing "Visualizations"."
Excellent progress indeed!
However I don't know what Winamp "Menu" they're referring to , on which "View" is a category with "Visualizations" on the dropdown list. I have no such "Menu" on my Winamp skin (admittedly, an old one named "1ANDONLY"):
As far as I know, a Visualization plug-in is either auto-started or it's not, based on the Options -> Preferences -> Plug-ins -> "auto execute visual plug-in on playback" checkbox setting. If not checked, then you can manually start it with CTRL+SHFT+K from the keyboard.
I see no "menu bar" with File, Edit, View, etc. on my skin.
Anybody?
"I am able to duplicate the behavior you describe, though it does not appear that there is a workaround I can provide you to stop this from occurring. I am opening a bug report with our developers so that they may hopefully address this in a coming release. I can only suggest for the time being that you launch G-Force within Winamp by clicking the "View" menu and choosing "Visualizations"."
Excellent progress indeed!
However I don't know what Winamp "Menu" they're referring to , on which "View" is a category with "Visualizations" on the dropdown list. I have no such "Menu" on my Winamp skin (admittedly, an old one named "1ANDONLY"):
As far as I know, a Visualization plug-in is either auto-started or it's not, based on the Options -> Preferences -> Plug-ins -> "auto execute visual plug-in on playback" checkbox setting. If not checked, then you can manually start it with CTRL+SHFT+K from the keyboard.
I see no "menu bar" with File, Edit, View, etc. on my skin.
Anybody?
Ok, I think I figured out what they're suggesting.
Right-clicking on the small red box in the Winamp display window (as appears on the above screenshot of my 1ANDONLY skin) triggers a drop-down menu.
There's a "Visualization >" item on that menu, which will generate a flyout menu if you hover the mouse over it. One of the items on that flyout menu is "start/stop plug-in Ctrl+Shift+K". And selecting/clicking that item with the mouse will start the G-Force window but does NOT cause the debug text to appear in the G-Force window nor is SoundSpectrum Log.txt created on the Windows desktop.
YAY!!
So interestingly, if you use that multi-action mouse-initiated method to manually start G-Force, the debug output DOES NOT get produced.
However if you use the supposedly equivalent CTRL+SHFT+K method to start G-Force, then the debug output DOES get produced.
At least for now, until they fix this bug, I guess I'll use this as the workaround (or just live with auto-starting). Or, I'll just deal with the consequences if my brain/fingers act instinctively and push CTRL+SHFT+K to start G-Force.
Of course the other part of the issue, resizing the window if/when you do it, still triggers the debug output. I'll just have to accept this for now and live with my window at its current size, or accept the unwanted results if I resize and deal with it then.
Right-clicking on the small red box in the Winamp display window (as appears on the above screenshot of my 1ANDONLY skin) triggers a drop-down menu.
There's a "Visualization >" item on that menu, which will generate a flyout menu if you hover the mouse over it. One of the items on that flyout menu is "start/stop plug-in Ctrl+Shift+K". And selecting/clicking that item with the mouse will start the G-Force window but does NOT cause the debug text to appear in the G-Force window nor is SoundSpectrum Log.txt created on the Windows desktop.
YAY!!
So interestingly, if you use that multi-action mouse-initiated method to manually start G-Force, the debug output DOES NOT get produced.
However if you use the supposedly equivalent CTRL+SHFT+K method to start G-Force, then the debug output DOES get produced.
At least for now, until they fix this bug, I guess I'll use this as the workaround (or just live with auto-starting). Or, I'll just deal with the consequences if my brain/fingers act instinctively and push CTRL+SHFT+K to start G-Force.
Of course the other part of the issue, resizing the window if/when you do it, still triggers the debug output. I'll just have to accept this for now and live with my window at its current size, or accept the unwanted results if I resize and deal with it then.