Glad to see you @DusX!

Thanks for your reply! Yes, it seems, that somehow we lost one of bug ticket. I have sent you new tickets (bug & feature req).

Yes. By "sequencer" I meant the one I have created in Isadora. 

And Yes, you are right! It seems only asynchronous threads(scanning thumbnails & main process) could solve it. But any solution of this Issue would be great! Freezing is sucks! :))) (also when loading new "big video" in movie player)

Kindly ask you to made this improvements. Thanks!

Hi @Mark,

Thanks for your feedback and advice. Using the Live Drawing actor as you described has sorted out the issue somewhat. Although the sudden jumps still appear with images of variable width and height. The set of images that have been batch processed to a standard height - leaving the width variable are OK.

@vjw

OK, glad you solved it. As long as you use only vid-gpu, you shouldn't encounter any of these problems. But again, take a look at the input or output ports. If they are green, they will "mutate" to whatever video type you use. But once you make a connection, they'll turn blue to indicate that they can no longer be changed.

(I know it's all a bit of a pain, but it was necessary to allow old patches to run.)

Best Wishes,
Mark

@davids

I found your ticket, and have responded to it.

@leben

the ffgl video mixer is the one provided by Troikatronix (there are others out there 😉 ?

If so I will try to recreate the issue, and file the bug report.

thanks

Hello,

i have a problem to run Isadora with my Geforce GTX 1060. The Laptop i use have an internal GPU and the GeForce. When i setting Isadora to use the Geforce with the Nvidia Controll and then start it, Isadora crash without a crash report. It seems that windows close the programm.

My previous and unsuccesfully steps for a solution:

-disable OpenGL in the preference

- disable complete the internal GPU

-Try it with a a few new installations and deleting the preference

-And install Isadora 2.5.2 since yesterday

Thats the specifications of may Laptop:

Schenker XMG P507, Intel® Core™ i7 (6. Generation) 6700HQ Prozessor 4x 2.60 GHz, Geforce GTX 1060, Win10 Pro

Thanks for the replies; I upgraded and so far it's helped with crashing. 
I'll create a support ticket for the other issues!

All the best

@mark

Thank you for the link. Yes it looks like it was due to the Adobe cloud software installed on the machine.

Regards
bonemap

Yes also happy here. That looked scary and strange. 

Hi,

The 'square mesh' draw mode appears unresponsive to 'wire frame size' property input - it would be great to get that fixed.

I have also experienced OSX system hangs when engaging 'point attenuation' with 0 set in the associated properties i.e. 'point constant atten',' point liner atten' and' point quadratic atten'. Over a certain 'horz resolution' + 'vert resolution' engaging 'point attenuation' hung OSX starting at 1920 x 1080 then reducing the resolution by half until it was around 240 x 135 before I could enter values into the associated properties. I know now to set the associated properties before toggling the 'point attenuation' on. As soon as the associated properties were set with a number the computer handled the parameter just fine - at least up to 1920 x 1080 resolution.

Regards,
Bonemap

Hm, this seems to work better with syphon out of my mains scenes into secondary scenes. A little clunky, but might be the solution for now.

@eight said:

Quickdraw drawing between QDBeginCGContext and QDEndCGContext

 @eight - Hmmmm... the error you're seeing 

Quickdraw drawing between QDBeginCGContext and QDEndCGContext

could be the root of the problem. I will investigate this ASAP.

Thanks for your continued patience and your efforts to help us.

Best Wishes,
Mark

I have just tried the 'AUVoiceProcessor' - but it doesn't appear to offer any in or out properties is this a bug or is something else going on?

Mac OS 10.12.5 Issy 2.5.2 USB

@grimvisions

could it be the settings you have in the 3D Particles? I see you have 5000 particles being emitted and gravity of -20 on the Y axis these parameters may give that effect depending on the frequency of particle births input at 'add obj' ? 

@Cory

The beta is no longer beta, it's v2.5.2. The links are here

https://community.troikatronix...

The message you listed  is not meaningful. It is a warning given by AVFoundation. If you google "itemasync_SetProperty signalled err=-12785" you'll see loads of matches spread far and wide for many different software apps.

So that particular error is not something that can be fixed, because it's in Apple's code.

Best Wishes,
Mark

@Fred @mark 

I have tried a couple setups, and I am not experiencing the issue as outlined.
I am able to setup for example a show on my laptop that is using 2 additional monitors as stage 1 and 2. (I added blending to each for something extra)
I can play video to each, save the file, close the file. Disconnect the external displays. Relaunch my Isadora patch, and edit the file as I would normally.
There is one glitch I ran into, in detaching my 2 displays, windows continued to see a 'ghost' display. So one of my stages opened on this display when I viewed/forced stages from Isadora.
Switching the stage setup to target only stage 1 didn't seem to correct it. I suspect a reboot would have worked (will try in a moment). However I can see the addtional of a 'gather' command might be useful.

Fred is there anything additional that perhaps I missed to cause the issue?

@Fred said:

alling, this is with the preferences set to 30 fps. Once I bring the framerate up and the srervice tasks to 4 then the flashing comes back. Using an inactive flip actor still solves this.

 Dear Fred,

We were too close to the release to fix this for v2.5.2, as it might have introduced show-stopping bugs. It is now at the top of our priority list.

Best Wishes,
Mark

Just wanted to add here, that today I updated to the Creators Update, and I haven't found any problems yet.
I am still testing, but so far I am able to open a number of my most complex projects, and they run as expected.
Creating a new project not an issue for me either. It appears nothing has changed in regards to Isadora after the update.

Hello, my version is 2.5.1.

I have already opened a bug report.

Thanks.