@markI have a Native Instruments Komplete Audio 6 (Mk 1 version) which is at the budget end of things, but its four outputs have worked just fine with Isadora 2.x on a Mac.It's just a plug-n-play USB audio interface, equivalent to Ryan's Roland Rubix 24 or the Scarlett 2i4, and in the same price range. Designed and engineered in Germany :-)

@ainsleyphillipsYou can either use a modifier, then you have to press a button for the mouse position to be tracked. Or you put a gate after each output (horz and vert). If you switch the gate to off the position will not be passed.Best Michel

@markThank you, Mark.  I will try the wave/envelope generator.  My media is all photo jpeg codec.  Are there advantages to using HAP or ProRes422 over photo jpeg?   

@ray I had some problems with mapper settings being lost in 2.6 when the changes were small. Can you try making the last movement large and radical just to test if it saves the positions if the adjustments are not small (and try with the mouse not the keyboard, I think there was a difference).Sometimes I was able to get over this by having an extra slice that did not do anything (it was out of the source and destination areas) and moving this a lot and then saving. It drove me crazy at the time as the movements I was making were small and I could not tell if the projectors were moving (they were 100m away). This was a bug that was caught but I don't know if it was fixed in 2.6.1 or not until version 3. I also did not test V3 for this.

I have a case where I want to use a user actor for mapping a lot of small pieces, but I want to use the same mapping for an alpha layer, but the pieces in the two need to have different blend modes. It would be great if the projector blend mode had some other options, like when the mapper was engaged the blend modes still worked, so they could be additive, transparent opaque OR mapper. and when the mapper was used and transparent was selected it would set all the mapper pieces to transparent. If it was set back to mapper then it would use the blend setting of the individual pieces. I think there are other options for doing this, but a way of having the smae mapping with different blend modes for using alpha layers with different projectors into the mapper would be cool.

I have been using a https://www.presonus.com/products/AudioBox-1818VSL/downloads

@guntherThank you for your efforts. This may work for now, but the numbers you shared are not actually correct because of a bug in the Keyboard Watcher that I am in the process of fixing today. Your system above will work for Isadora 3.0.2 through 3.0.6 but it will break as soon as I fix the bug and we release Isadora 3.0.7.Details: Because we switched all character input values to Unicode for Isadora 3, the constants used to represent special keys (arrow keys, escape, etc.) had to change. However, the output range of the Keyboard Watcher not properly upgraded from the eight-bit value (0-255) used by Isadora 2 to the required sixteen-bit value (0-65535) needed to represent Unicode characters in Isadora 3. So, the numbers you are getting is because the high 8 bits of the actual value is getting chopped off which is not at all correct. Your workaround does in fact work, but it will stop working as soon as Isadora 3.0.7 comes out, which will contain the actual fix for the problem. This morning I completed the hard part: extending the range and making a major improvement: you can now simply enter the name of the key you want and it will show up that way in the Keyboard Watcher. See below. The other part which I will do now is to to automatically update those old constants to new values when importing a patch created in 2.6.1 or before. This will ensure that Isadora 2.6.1 patches continue to work. If you need this functionality urgently, please to join the beta program by submitting a ticket. I will be getting 3.0.7b1, which will have these fixes, to relatively soon. Best Wishes,Mark

@blackmoonhowlingDid 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.

it was working OK with me earlier today.

@juriaan said: why TouchDesigner (yes I know I should not compare software) works with the latest SDK and the features are quite the same as Izzy in that regard   But seriously, I logged this and Mark will investigate when there is time to do so.

@tease said: That was the key: movie player speed at 0 and HAP codec  https://giphy.com/gifs/well-do...

@tr742I think the same codec as what has been working well for you should be fine.Just make sure the audio settings (usually separate from the video codec settings) are not mixing down to stereo.I would recommend Uncompressed for the audio, as this has worked well for me.Do a couple tests to find the right setup.

The provided test videos import and run in both Isadora v2 and 3 on my test machine, so I believe some type system configuration issue is responsible.I am continuing to troubleshoot the issue with dritter via a support ticket. 

Dear All, So, there is an issue with the Blob Target Proximity in that it does not allow take the aspect ratio of the source image into account when calculating the distance to the target. If the image fed to Eyes++ were square, then it would work. But given that it is 16:9 in Fred's test patch, the height is incorrectly calculated. There is nothing to be done about this at the moment, because we'll need to add more information to the "blob" structure so that it knows the resolution of the source image.  In the meantime, see the attached modification of Fred's patch. It contains a User Actor called Target Proximity Pixels which accepts a blob, the height and width of the source image, the target position, and the target size, all of which are specied in pixels instead of percentages. (It could be percentages too... but maybe it's clearer with actual pixels?) There is another User Actor called Quad Target Proximity Pixels that accepts a blob input and allows you to specify four targets. (If you don't want to use a target, set it's size to 0.) The example now contains four white circles at 25% size, and one yellow circle at 50% size. The white text reports the output of the Quad Target Proximity actor, showing a value whenever you approch any of the four white targets. The yellow text reports the postion within the larger, yellow circle. Hopefully that's enough to get you going on your own and address the problem until we can update the Blob Target Proximity. Blob Proximity - User Actor Fix.izz Best Wishes,Mark

Dear Community,We've now officially released v3.0.6 to address the bug found by Windows users (only) in 3.0.4 and as documented in this forum.Even if you're on MacOS, you should upgrade to this version, as there are a few other minor fixes included in 3.0.6.Get Isadora v3.0.6Best Wishes,Mark

@mark said: we should add a bug report  Added to the sheet as "Name: Converting Strings to Timecode"