Archive: Crashing...
Sonic Ether
6th February 2006 05:31 UTC
Crashing...
Hey, I've been making some major progress with AVS, but it is tremendously frustrating when I must keep re-doing everything I've done because winamp keeps crashing. It's only when I perform some sort of action, like arranging a superscope, or changing a rendering mode. This is driving me mad. Has anyone come across this problem?
PAK-9
6th February 2006 09:08 UTC
AVS crashing? Never happens.
Grandchild
6th February 2006 20:47 UTC
Just negate pak's answer and you're at it! :)
This is well known and there's no other fix than frequent saving.
Sonic Ether
7th February 2006 03:57 UTC
Yeah, I was afraid of that. Thanks for the help!
jheriko
7th February 2006 05:51 UTC
When coding do it all in notepad, then copy paste across to test.
In my experience 99% of crashes seem to happen when code compiles. So I write some code, save my preset, paste it in... then if it crashes I can just load and do the paste again.
Its easy to not follow tho :p
StevenRoy
7th February 2006 07:02 UTC
I've found that AVS seems to crash much less often if I edit while the visualization is "docked" in the AVS editor window. It still happens, of course, but less often... I think...
I've used the Notepad trick, too, and it helps. Another major reason I like that is that I can maximize Notepad and edit my code using the full screen with word-wrapping.
Of course, even with these hints in mind, AVS isn't completely stable, and never will be, so you should also get into the habit of saving frequently.
JaVS_v2.5
7th February 2006 12:21 UTC
Maybe your computer performance are low?
It's the same thing happened on my aunt's computer while I playing with codes in AVS editor. My aunt has a very low computer performance.
Grandchild
7th February 2006 17:45 UTC
I experienced most of the crashes while WA was ready with one song and went on to the next track. So I hold on my activities for some time and when the Notifier is gone, I resume.
gonna use the txt-editor now too...
Tuggummi
7th February 2006 18:07 UTC
My crashing occurs the same way grandchild's does, when winamp changes to the next song. Never has AVS crashed on me while editing something, codewise or not.
jheriko
7th February 2006 18:49 UTC
One of the great things about AVS, is that its flaws never seem to be consistent on different machines. Also the way it passes those problems onto APEs too... its all great stuff :)
Tuggummi
7th February 2006 18:53 UTC
Given enough resouces and time one could build a system that never experiences crashes or problems with AVS...
Omg! The holy grail! :eek:
jheriko
7th February 2006 19:36 UTC
Originally posted by TuggummiYeah, and just like the holy grail... it will stay fiction.
Given enough resouces and time one could build a system that never experiences crashes or problems with AVS...
Omg! The holy grail! :eek:
Tuggummi
7th February 2006 20:44 UTC
Blasphemy! Kill him!
^..^
7th February 2006 21:57 UTC
Originally posted by TuggummiWhat an enticing imagination!
Given enough resouces and time one could build a system that never experiences crashes or problems with AVS...
Omg! The holy grail! :eek:
JFASI
7th February 2006 22:40 UTC
My crashes only tend to happen when I accidentally click in Tentacles 3D -------> I blame UnconeD for the losses of some great ideas of mine.
Tuggummi
7th February 2006 22:44 UTC
I blaim Tentacles 3D for some ideas that were greatly lost.
^..^
7th February 2006 22:55 UTC
Blaming "Tentacles 3D" (or "Metaballs 3D") is like blaming an infant for breaking a valuable vase or something. Actually you can't really blame them for that, cause they aren't fully developed (yet).
Tuggummi
7th February 2006 23:13 UTC
You're right, that would be disrespectful....
But i do hate babies though! :mad:
^..^
7th February 2006 23:27 UTC
Well, that's your right. So do i hate the aforementioned ape's.
Just avoid blamimg something for a fault they are not guilty for! ;)
Tuggummi
7th February 2006 23:29 UTC
Aah, words of wisdom, my friend, words of wisdom. Okay, i hate everyone who uses babies! :mad:
^..^
7th February 2006 23:37 UTC
Seems as if i'm having some kind of wise philosophical phase tonight. Guess i should go to sleep before something bad happens... :weird:
Tuggummi
8th February 2006 00:08 UTC
When using philosophical against irrational, it is best so, i believe.
JFASI
8th February 2006 21:55 UTC
Is there any way to get rid if the APE's?
^..^
8th February 2006 22:43 UTC
Of course: just delete them from your AVS-folder! ;)
JFASI
9th February 2006 21:32 UTC
Yeah, but they still show themselves in my render bow, and I occationally hit them.
^..^
9th February 2006 21:52 UTC
Sure? After you delete them they shouldn't show up there anymore!? :weird:
Tuggummi
10th February 2006 15:16 UTC
Unless they are hard-coded-in of course and not included as external .ape files... don't know, the list is outdated and should be updated...
^..^
10th February 2006 22:57 UTC
That's new to me! I always thought that an effect imported through an ape would disappear as soon as the corresponding ape is missing! :confused:
Well, you never stop learning! ;)
fastingaciu
11th February 2006 16:26 UTC
My crashes are very ofen so i started using notepad it's much more better then rewriting the whole thing all over again. It usaly hapends when i add stuff to the preset or when i save it .... so one day i got relly mad and i started using notepad......... but it would be much more better if the next verison of winamp would fix this.....
JFASI
12th February 2006 15:02 UTC
Mine doesn't crash all that often. Frankly, it never crashes. Ever. Apart from the obvious tentacles problem.
Grandchild
12th February 2006 19:03 UTC
a triple, no, endless: o_O for that!
originally posted by Jherikoit seems you're wrong...
Yeah, and just like the holy grail... it will stay fiction.
hornet777
13th February 2006 04:59 UTC
mine rarely crashes either, but when it does, its usually catastrophic, or it has a weirdness where it offsets the mouse cursor by one line.
Magic.X
13th February 2006 08:38 UTC
How about writing some kind of ape that forces avs to save frequently to a temporary file? Just needs some dogy UI hacks ;)
Grandchild
13th February 2006 14:46 UTC
I thought about exactly this yesterday!
Would it be possible??
Magic.X
13th February 2006 15:32 UTC
Should not be a major problem to force AVS to save.
The only new thing is the Save-File Dialog Box popping up.
As I am thinking of this, its probably better to have an external agent running that will detect crashes and reload your preset in last state automatically too when AVS is restarted.
The only problems would be a slowdown, depending on the saving rate and it might also be possible that the dialog box is taking some time to get the file information it needs and will force AVS to idle meanwhile. The first thing could be cutomized, but if the latter occurs, this would probably not make sense at all.
Grandchild
15th February 2006 20:08 UTC
but I could live with a short break every 5 minutes.
I simply can't get myself to save frequently, I just forget it. even when I think "now this is cool, almost finished" I don't have the automatic reflex of saving...
so this would really save me a lotta time
[although it can't be denied that many of my good results came when I rebuilt sth deviously after a crash.]
GC
JFASI
15th February 2006 22:27 UTC
I can tell this auto-save thing is not going to get off the ground...I dare someone to make it!
hornet777
16th February 2006 00:43 UTC
since AVS is open-source now, why not just rewrite it instead of making yet another ape?
^..^
16th February 2006 00:48 UTC
Well, no one keeps you from doing that.
The point is, that it just can't be done in a few moments.
JFASI
16th February 2006 01:10 UTC
I looked back at the original post. WOW. My AVS never crashes when I do something as simple as change render modes...That's pretty extreme.
Magic.X
20th February 2006 10:13 UTC
Originally posted by ^..^Not a few moments but should be ready after 2 hours, at least for me as i've the needed routines already done for Hotlist. If I've some time left beside my major projects, I'll give it a shot.
The point is, that it just can't be done in a few moments.
^..^
20th February 2006 17:52 UTC
No i meant rewriting AVS in order to include autosaving would take quite long.
Magic.X
20th February 2006 18:40 UTC
Why?
Its even easier without the need to hack. Again, all you need is a timer and a call to the save procedure.
But I dont think doing your custom AVS is so good.
One should ask the dev group if one could contribute stuff to the official version instead. Otherwise there'd be a need to rewrite every new release your own, also there'd be finally some progress on AVS developement.
hornet777
20th February 2006 22:32 UTC
how about rewriting it for better overall stability, obviating the need for "auto-save" or any other band-aid. Yes I know it would take a while, and I certainly am no coder, so am vulnerable on these points to criticism, but don't we already have enough experience with kludges with Windows? What's needed is a master C-programmer to rework the code, and doesn't have a day job :).
Delphi: :down:
Visual Basic: :down:
.NET: :down:
C: :up:
assembler: :up: :up:
Tuggummi
20th February 2006 23:22 UTC
I know im probably the odd man out, but i really hate auto-save feature in any program :mad:
It's just... just... see! I can't even explain it, because it frustates me so! :igor:
PAK-9
21st February 2006 09:47 UTC
Originally posted by hornet777Writing it in assembler, yea that will make it stable
how about rewriting it for better overall stability, obviating the need for "auto-save" or any other band-aid. Yes I know it would take a while, and I certainly am no coder, so am vulnerable on these points to criticism, but don't we already have enough experience with kludges with Windows? What's needed is a master C-programmer to rework the code, and doesn't have a day job :).
Delphi: :down:
Visual Basic: :down:
.NET: :down:
C: :up:
assembler: :up: :up:
Grandchild
21st February 2006 14:02 UTC
Originally posted by PAK-9Why would it? Because it's closer-to-the-root programming, more basic?
Writing it in assembler, yea that will make it stable
PAK-9
21st February 2006 16:34 UTC
It was sarcasm
The lower level you program at the less stable the result is likely to be. If you coded AVS in Visual Basic it very rarely fall over (unless you used r33t h3x) but it would be crushingly slow (again, unless you used r33t h3x).
If you coded it completely in assembly it would be excruciatingly difficult to track down any bugs and probably be going over all the time... it would be pretty nippy though.
When its all said and done though, fixing (patching, bodging, whatever you want to call it) the existing AVS to a stable state would make a lot more sense than writing it from scratch... assuming all you want is the same functionality but stable.
And by the way it would take about 5 minutes to add an autosave to AVS if you get the source and have a passing familiarity with C.
Grandchild
23rd February 2006 00:14 UTC
Originally posted by PAK-9So I take it you folks are making 'fridge' to achieve the next level vis program :)
fixing [...] the existing AVS to a stable state would make a lot more sense than writing it from scratch... assuming all you want is the same functionality but stable.
PAK-9
23rd February 2006 09:21 UTC
yea... 'making'
hornet777
24th February 2006 00:23 UTC
admittedly, C is probably the best overall compromise, in terms of language
jheriko
24th February 2006 14:18 UTC
Originally posted by Magic.XROFL
One should ask the dev group if one could contribute stuff to the official version instead.
MaTTFURY
25th February 2006 05:37 UTC
maybe with the sourceforge page up, something or someone might be able to make it stable ¬_¬
Fork me on GitHub