How to stop continous crashing on start due to crash report itself ?
-
same thing is happening to me on windows 10. removing the preferences does not solve the problem.
-
Can you open Isadora, stop the engine, and then open your file?
-
hi, I tried all the ways of removing preferencies but it didn't work. Apparently some informations are kept somewhere else than C:\Users\YourUserName\AppData\Roaming\TroikaTronix
about the crash reports that keep it crashing on and on... Do you know where it could be ? I am on windows 10 too. -
@DusX @Michel
Hi i have looked inside the computer and found those locations with isadora files.
C:\ProgramData\TroikaTronix
C:\Users\tuby\AppData\Local\CrashRpt\UnsentCrashReports
C:\Users\tuby\AppData\Roaming\TroikaTronixI erased everything, reinstalled isadora and still the crash continues.... This is just desperating.... Any idea what to do ? Should I modify something inside the register base ?
-
Crash reports really should not be the cause. So those folders probably don't matter. Do you have any freeframes , glsl shaders , and or UserActors being loaded into isadora? You may want to rename the folders that hold these files and the restart isadora. That will ensure that these files are not loaded. This is a common cause of startup errors.
-
@DusX; OK, I uninstalled the the freeframe and now it starts fine on windows 10. What a relesase !!! Thanks you !
Does that mean that the TroikaTronix FreeFrame Plugin Collection for Windows is not compatible with windows 10. ?
-
@chrisdel what was your procedure for removing freeframe plugins? Did you need to reinstall Isadora again as well?
-
@rayroyiii I used the command uninstall from the windows program lists. I didn't have to reinstall isadora.
-
Did not work for me. Isadora still crashes immediately. All preferences removed, free frame uninstalled. :(
-
:( I am using an old version of isadora : 1f3 on USB key. Maybe that makes a difference ?
-
even though you only have a version 1.x license I would recommend downloading version 2.x, there are a lot of fixes in there also for license 1.x owners. The only thing is that you will not benefit of the newest features.Best Michel -
If you are running a older version of Isadora, it does not support the new freeframeGL format, only the older freeframe format.The downloads available are Petes freeframes (older version) and the Newer Isadora FreefraeGL collection.Without seeing the error report I can only guess. But I would suggest trying the most recent beta, since it may have a fix that addresses your issue:http://troikatronix.com/isa25beta/ -
@chrisdel yes i've been trying the beta, it didn't work on my windows 10 machine, and recently freezes and is inoperable on my windows 8.1 intel i7 16GB ram nVidea GTX 960m workhorse. I uninstalled isadora 2.5 beta, removed preferences as per instructions on this forum, restarted machine, installed isadora 1.3, restarted, opened isadora.... crashes immediately.
I will now try to install the older freeframe format and see if that helps, is there a procedure for removing the freeframe GL collection?i am considering completely wiping this computer, reformatting and starting over, but honestly i shouldn't have to do that, on two completely different machines?How can I send you an error report?thanks for the help,rr -
-
OK, the freeframe uninstall and reinstall of the non GL collection worked on my i7 windows 8.1 machine.
did the same thing on my i5 windows 10 backup, still crashed immediately. see crash report attached.rr -
@michel, In fact I had old files in v1 that were working very fine on windows XP. And to port them on windows 10 with isadora v.2.0 gave me so many problems.... that I prefer to carry on with the good old tools. my feeling is that isadora v 2.0 is not fully ready for windows 10.... I will wait a bit more...
@rayroyiii, i'm not developper so you should adress the crash report to @dusX Good luck with solving your problem !
@dusX thanks for your help ! Let me know when isadora 2.0 has been tested by many users and working fine on windows 10. I had many problems of stability with the Black Magic Intensity driver. Maybe the problems comes from the driver itself ? Anyway I went back to the good old tools : firewire capture card, isadora v0.9 (much more efficient than the v1.3 for video tracking, the difference in CPU use is very important) on windows XP, maybe windows 7 (I am testing at the moment and it seems to be working fine also.
-
I have had a very small number of users ever have issues like these on Windows 10.
In my experience, the problems generally stem from either video card drivers, or 3rd party linked files (freeframe, FFGL, GLSL, and User Actors).For this reason the first 3 things I ask users having an issue like this are:- Delete your preferences.
- Rename the folders of any 3rd party modules (eg: C:\Program Files (x86)\Common Files\FreeFrame )
- Ensure you have the latest driver/s from the video cards' manufacturer. (often not supplied by the systems' manufacturer/brand)
If your system uses an Intel video card, there may be issues with Isadora v2.2 and earlier, but the latest beta has corrected these edge cases.Recently I have taught Isadora v2 to a class almost entirely using Windows 8 thru 10.Isadora proved very stable once a few simple system configuration changes were made. (Turning off nVidia Optimus, was the number change required) -
@DusX : Ok, thanks for the advices !
In fact I had 2 problems : stability of Isadora and the stability of isadora in combination with using the black magic intensity video capture.So let's say that we can fix isadora V2.2 and above to be stable on windows 10, what would be the video capture card you recommand to use then ?
-
@DusX : Ok, thanks for the advices !
In fact I had 2 problems : stability of Isadora and the stability of isadora in combination with using the black magic intensity video capture.So let's say that we can fix isadora V2.2 and above to be stable on windows 10, what would be the video capture card you recommand to use then ?
-
Black magic is likely the fastest choice. ( natice driver support) However these can be very picky about the hardware supported, and in the case of the usb 3 versions only work with a small number of usb3 host controllers. Others may work but poorly. I have used these with Isadora and windows to great effect previously but have also returned product after testing and finding that it was impossible to us BM intensity with my computer at the time.
