Guys, we're aware of the problems with loading a lot of non-DXV clips.
The problem is not a leak, it's that using a non-DXV encoded clip eats up a lot more memory than a DXV encoded version. So if you're used to loading hundreds of DXV files, you can be unpleasantly surprised if you're forced for whatever reason to use something else.
We agree that Resolume shouldn't crash. That's a given, and we really want to make that happen. But it's tricky, because it's something that has to happen without bothering you, but it does affect you in a major way.
To stop it from crashing, we'd need to free up memory somehow. Delete previously loaded clips? Force a new deck load? Stop Resolume from working until you've cleared clips or switch decks yourself? What do you guys think are good options for this?
- if there is a way to calculate the estimated memory usage while importing clips, the user could be warned, that problems will occur.
- maybe an algorithm could be made, to unload clips that are not close to the ones that are actually playing, in case memory is running low. This could work for some users who are not triggering clips randomly.
The user should be able to disable this function if desired via preferences.
I hope Clip loading background processes can be made low priority to not to interfere with normal operation.
There could be different strategies for algorithms for example, if a user does not use external methods, clips which have no keyboard mappings and are not visible in the interface,(which the user can not trigger) and are not destination of auto pilot, can be unloaded. (surely the next clip for random auto pilot can be determined, when a clip starts playing)
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
1)
Simply clip the oldest, delete it from the memory when the next clip, the storage needs.
It should be noted that not enough memory remains free for 3 more clips (about 150MB).
If are using the keyboard, or midi, immediately and simultaneously requested.
In order to have enough buffer.
Not have to wait until the memory is full, and then only delete that would be wrong.
2)
It does not matter whether 32bit or 64bit when no more memory is there, or is no longer supported, you have to react.
For 32bit, you have real about 1.5GB (2GB for the software).
Graphic Ram is also limited.
The crash came in because Resolume by lack of memory, could no longer work.
3)
Error messages, "without popup or alert message," in the lower right help, in red, in addition with a white exclamation mark as an image in a red triangle displayed for 10 seconds.
Importantly, it must be conspicuous.
Is the aid turned off, it is turned on for a period of 10 seconds.
Again, what happened:
Container: mov
Codec: Motion JPEG video, PCM s16le, Including sound
1280x720
Autopilot, one after the other, played in series,
only one level
only one clip after the other
NO simultaneously
50 clips, 5 min after crash
30 clips, 10 min after crash
20 clips, 15 min after crash
Autopilot, RR (random)
Crash after about 20 min
Striking: Task Manager, is no more free memory.
A clip will not play, which must be not loaded when the memory is full, and perhaps there are additional clips.
Whether Autopilot or Manual.
German:
Die Lösung ist einfach.
1.)
Einfach den ältesten Clip, aus den Speicher löschen, wenn der nächste Clip, den Speicher braucht.
Dabei ist zu beachten, das noch ausreichend Speicher frei bleibt, für 3 weitere Clips (etwa 150MB).
Falls die per Tastatur, oder Midi, sofort und gleichzeitig, angefragt werden.
Um noch genügend Puffer zu haben.
Nicht erst warten, bis der Speicher voll ist, und dann erst löschen, das wäre falsch.
2.)
Es spielt keine Rolle ob 32Bit oder 64Bit, wenn kein Arbeitsspeicher mehr da ist, oder nicht mehr unterstützt wird, muss man reagieren.
Bei 32Bit, hat man Real etwa 1,5GB (2GB für die Software).
Grafik Ram ist ebenfalls begrenzt.
Der Absturz kam dadurch, weil Resolume durch mangel an Arbeitsspeicher, nicht mehr arbeiten konnte.
3.)
Fehlermeldungen können, "ohne Popup oder Alarm Meldung", unten rechts in der Hilfe, in roter Schrift, zusätzlich mit ein weißen Ausrufezeichen als Bild in einem roten Dreieck, angezeigt werden, für 10 Sekunden.
Wichtig, auffällig muss es sein.
Ist die Hilfe abgeschalten, wird sie für den Zeitraum von 10 Sekunden, eingeschalten.
Noch einmal, was ist passiert:
Container: mov
Codec: Motion JPEG video, PCM s16le, including sound
1280x720
Autopilot, nacheinander, in Reihe abgespielt,
nur eine Ebene
nur ein Clip nach den anderen
KEINE gleichzeitig
50 Clips, nach 5 Min Absturz
30 Clips, nach 10 Min Absturz
20 Clips, nach 15 Min Absturz
Autopilot, RR (Zufall)
Absturz nach etwa 20 Min
Auffällig: Taskmanager, gibt kein Speicher mehr frei.
Ein Clip der nicht gespielt wird, der muss auch nicht geladen sein, wenn der Arbeitsspeicher voll ist, und vielleicht noch weitere Clips kommen.
He2neg wrote:I want to make the thing clear again :
Resolume should not crash if you dont use DXV, that it doesnt reach the best performance is allright, but it shouldnt crash.
everythink in DXV = best performance you can get
Other video Formats = lower performance
A Crash / Memory leak should NEVER be part of the System we need and want.
So as a wish to the Resolume team :
-Can you pls check if the Software has a memory leak / bug / ... if you use no DXV codec clips.
As RycoDePsyco was telling us in the first Post. ( if you cant understand his "translated" english then pls send me the Sentence via PN and i see what i can do about)
If it is like this maybe you can find a solution for that. Often you dont have the time to Convert all the Stuff, sometimes you get the Clips 10 minutes to the beginning of the show, or even while the show is running.
what? ive been with resolume for 3 years. and yeah, resolume did crashed when using video format other than dxv
