@dbini

thanks, I managed to get it go with this :)

Big thanks to @woland for sorting out my issue with opening this file. 

The solution was to reset my Isadora preferences!

Just thought I'd share this info as it might be useful to others in a similar situation. From the menu bar: Isadora - Reset Preferences.

Thanks again to everyone that offered help - great community!

Simon

@wolandJust did , We will see if this helps, My main issue is the light board firing cues faster than Isadora fade times and Isadora getting tied up with midi and soft/hard crashing

@Eva

you can try to open Isadora directly with an empty file, then to pause engine:

and third to open your corrupted file. Sometimes it helps.

best

Jean-François 

@anibalzorrilla

I have created a support ticket and replied, you should receive an email.

@millslow in NVIDIA Control Panel try going to Manage 3D Settings and in there under Program Settings you need to select Isadora and make sure that it's running via your Nvidia 2060 instead of the intel processor.

@dako-ark said:

bugs when opening isadora

 It may help to reset Isadora preferences.

Best WIshes

Russell

Hi @Eva 

Resetting preferences is often a remedy: Resetting Isadora Preferences

Best Wishes

Russell

@dusx  The problem was solved !! The graphic card configuration was the problem. No more crashes

Thanks a lot !

Best,

Maxi 

@Utopialighting 
Ok, please submit a support ticket, including your new file, and I will dig into it deeper.
The link is in my signature. Thanks

@dusx Ok, I submitted a bug report, got a few in a row with very similar situations, but it was not 100% repeatable.

Yes, Trash can.

@blackmoonhowling
Did you try my suggestion?
It could work because you are stopping the execution of the JS before going to edit it.
It wouldn't remove your code.

@goddessmoon2017 Hey I figured it out. Apparently I was upgrading and paying for the beta version I was running. thanks for the help. up and running. :)

Please file a support ticket using the link in my signature. 

thanks. 

because there is no time I went back to a previous version of my patch, that solved it. 

I actually use a very large .png file (because it's the only way i know to show fotos in rapid random sequences, I pan around the big file, real smooth and 60fps).

the error is much more likely to happen when the scene jumps have a fade time > 0. I assume that means running both scenes and obviously may be problematic.

awaiting version 3 i do not think it's worth the while to check this all out. it may be ok in version 3.

cheers 

h

Hey Isadora community,

I'm new with using Isadora & currently working on my first project: I want to control parameters in Isadora with Control Voltages coming from a Eurorack Modular Synthesizer System via a DC-Coupled Audio-Interface.

I habe already got some results, but figured out crashes, that led me to a general question:

Is it normal that everytime I pull off the usb cable (to the soundcard), Isadora simply closes without any warnings, questions or report on the next startup?
(I'm guessing a major problem in my system, that is also responsible for the "smaller" crashes...)

Working on:
- MBP, mid 2014, high sierra 10.13.6

- Motu Ultralite AVB, Firmware 1.3.4+617 (newest), USB

Some ideas?
Thx in advance!

Lukas

@pascal said:

Mr" class="redactor-linkify-object">https://vimeo.com/user7901471"...

 Thanks Pascal!

@DusX 

I just added these links to the ticket.

Best wishes,

Woland

Hey Mark! 

Thanks for the reply. It looks like I have solved it.

It seems the problem was indeed an over-abundance of Pre-load Scene actors that I had not found my first few looks through. I've never had this sort of "build up" problem before but it may have something to do with the fact that I was using the JumpByName actor to trigger my cues. Also, to answer your question they were movies.

Thanks again!

@julio_parente 

Unfortunately the files were not uploaded to our server - the logs show an error attempting to connect to our server. Hopefully they are still in the folder where the CrashRpt system puts them, which is here:

C:\Users/YOUR_USER_NAME\AppData\Local\CrashRpt\UnsentCrashReports

which according to the logs above are at

C:\Users\Play\AppData\Local\CrashRpt\UnsentCrashReports\Isadora_2.5.2\

The names of the files I need are:

c5aa950c-bce1-4e1c-a03c-afcdb4d6589e.zip
f56c99de-794b-4117-8427-69393b972168.zip
f3350635-9f37-4f52-a082-21f1c130d130.zip
fc9f5507-be95-4949-aea9-a259f8b3cd29.zip
9b70597d-12af-4734-8e1c-351186d015fc.zip

If you get me the right files I can work on the problem.

Best Wishes,
Mark