Hi everyone! There is something bugging me for a while, it's just me or resolume always crashes during a gig?
Is it of using a lot of different loops and decks; using most of the times 3 layers; using and mixing at the same time swf, mov and avi; or because a still have files that aren't coded in Indeo 5.x or just pc configuration?
I just had 2 gig's that resolume didn't crash, but where gig's that i used a small number of loaded deck's and used just a small number of loops...
I hope someone give me some input because this is starting to make me a little crazy.
Many thanks in advanced!
Operating System: XP Professional (Multi boot)
Processor:Core2duo T7200
Memry: 1 Gb
Videocard:Nvidia 7600 Go w/ 256 Mb
File type: avi, mov, swf
Codec:Indeo 5.1, Cinepak, Apple photo jpeg
Does you resolume crash?
from you set up i dont see any major problems that you could be having!
what resolution of clips are you using? if you are using many different sizes then i think this could be a problem and a do recommend that all clips should be encoded in indeo 5.1
thats all i really have
is there anything else that happens before the crash? is it when you play a certain clip or anything like that?
for example i do this
all clips same resolution 720x576
all clips Indeo 5.1
2 layers of video maximum
2 effects maximum.
thats just a general of what i do. your system could be heating up way to much and that could also be another reason.
Thats just my 2 cents
hope you get the problem sorted!
what resolution of clips are you using? if you are using many different sizes then i think this could be a problem and a do recommend that all clips should be encoded in indeo 5.1
thats all i really have
is there anything else that happens before the crash? is it when you play a certain clip or anything like that?
for example i do this
all clips same resolution 720x576
all clips Indeo 5.1
2 layers of video maximum
2 effects maximum.
thats just a general of what i do. your system could be heating up way to much and that could also be another reason.
Thats just my 2 cents
hope you get the problem sorted!
So... for what you both said the problem is probably from using files with different sizes and codec's. I just started recoding my files (400x300, Indeo 5.1), it's gone take a few days by will do it. Hope resolume will stay more stable this way because normally it crashes 2/3 times in gig during a night and gone start thinking in buying a platform with coolers to keep the laptop fresh under it.
Many thanks but if you have other ideas please say!
[Edited on 22-7-2007 by miau]
Many thanks but if you have other ideas please say!
[Edited on 22-7-2007 by miau]
Re: Does you resolume crash?
This is also a major problem for me .. within minutes if not seconds of starting into my set, everytime without fail Resolume crashes cold. I'm usually using over 3 layers at once with alphas from a midi device.
Running Resolume 3 Avenue on a Macbook Pro 2.4 core 2 Duo, 2 gigs of RAM .. all files are compressed as recommended: videos without alpha are Quicktime DXV .. alpha channeled videos are Quicktime PNG .. runs perfect up until it studders and freezes .. FPS upon crash reads around 35-40.
Is this an issue with version 3? .. i chose Resolume because its absolutely perfect for my needs, however a crash within seconds of starting to really get into my set is obviously unacceptable.
Any thoughts or possible solutions to try and troubleshoot here? Thanks!
Running Resolume 3 Avenue on a Macbook Pro 2.4 core 2 Duo, 2 gigs of RAM .. all files are compressed as recommended: videos without alpha are Quicktime DXV .. alpha channeled videos are Quicktime PNG .. runs perfect up until it studders and freezes .. FPS upon crash reads around 35-40.
Is this an issue with version 3? .. i chose Resolume because its absolutely perfect for my needs, however a crash within seconds of starting to really get into my set is obviously unacceptable.
Any thoughts or possible solutions to try and troubleshoot here? Thanks!
-
gpvillamil
- Posts: 550
- Joined: Mon Apr 04, 2005 03:33
- Location: San Francisco, California
Re: Does you resolume crash?
I've gone for a few years and lots of gigs without seeing Res 2.4 crash, but it took a bit of testing to get there.
If you're on Windows, try downloading the G-Spot codec info tool (http://www.headbands.com/gspot/) and use it to open your clips.
Resolume has very specific requirements in terms of being able to seek within a video file, and this is not handled by a codec, but by something called a splitter. Some splitters are not compatible with Resolume, as far as I can tell. When you open a clip using G-Spot, check to see if the clips are being handled by anything other than "AVI Splitter": you might see "OSAVI Splitter" or "Haali Media Splitter". Remove or reinstall these - you can reinstall Haali without having it handle AVI.
Also check to see if G-Spot suggests multiple possible decoding paths, or if the decoding paths have errors. Delays on launching a clip typically suggest that Windows is opening a file, can't play it with the "preferred" decoding path, and then tries others until it finds something that works. You want to make sure that the best decoder is also the preferred decoder. PicVideo MJPEG does this automatically (unless ffdshow is installed... see next paragraph.)
A very very common problem that can occur is if you have ffdshow installed. While this is a great package overall, it does have the bad habit of overriding DirectX merit system, and installing itself as the default. This means that if you load a clip that it can't handle, there will be a delay while it hands off to DirectX. Also ffdshow installs with postprocessing enabled by default, which can slow things down, and interfere with seeking. So if you have PicVideo AND ffdshow installed, go into ffdshow setup, and DISABLE MJPEG decoding in ffdshow. This will let PicVideo take over automatically. You might also want to disable Indeo and Cinepak decoding in ffdshow if they happen to be turned on. (Alternatively, set up ffdshow to play all these formats, but give them all an autoloading profile that turns off postprocessing.)
G-Spot will show whether ffdshow or PicVideo is being used for decoding.
Good luck!
If you're on Windows, try downloading the G-Spot codec info tool (http://www.headbands.com/gspot/) and use it to open your clips.
Resolume has very specific requirements in terms of being able to seek within a video file, and this is not handled by a codec, but by something called a splitter. Some splitters are not compatible with Resolume, as far as I can tell. When you open a clip using G-Spot, check to see if the clips are being handled by anything other than "AVI Splitter": you might see "OSAVI Splitter" or "Haali Media Splitter". Remove or reinstall these - you can reinstall Haali without having it handle AVI.
Also check to see if G-Spot suggests multiple possible decoding paths, or if the decoding paths have errors. Delays on launching a clip typically suggest that Windows is opening a file, can't play it with the "preferred" decoding path, and then tries others until it finds something that works. You want to make sure that the best decoder is also the preferred decoder. PicVideo MJPEG does this automatically (unless ffdshow is installed... see next paragraph.)
A very very common problem that can occur is if you have ffdshow installed. While this is a great package overall, it does have the bad habit of overriding DirectX merit system, and installing itself as the default. This means that if you load a clip that it can't handle, there will be a delay while it hands off to DirectX. Also ffdshow installs with postprocessing enabled by default, which can slow things down, and interfere with seeking. So if you have PicVideo AND ffdshow installed, go into ffdshow setup, and DISABLE MJPEG decoding in ffdshow. This will let PicVideo take over automatically. You might also want to disable Indeo and Cinepak decoding in ffdshow if they happen to be turned on. (Alternatively, set up ffdshow to play all these formats, but give them all an autoloading profile that turns off postprocessing.)
G-Spot will show whether ffdshow or PicVideo is being used for decoding.
Good luck!