https://www.meldaproduction.co...

https://www.meldaproduction.co...

perhaps what you are looking for?

best

Jean-François

@dako-ark

I deleted your screenshot because it showed your License ID and Password. I took a look at your activation history and it says that you have one activation left and you successfully activated the license on a computer yesterday. Are you all set then? (Also, if you're concerned about your password, I can reset it on the back end for you but it may mean you have to re-activate the license on your computer after the password reset so I didn't want to do it without asking you first.)

@Juriaan Is correct about the root of the issue, you probably had the license already activated on the maximum number of computers. 

As stated on the TroikaTronix Store hosted by FastSpring: 

For each Buy-to-Own or Subscription license you purchase you can activate Isadora on up to two online or offline computers, though you may only use the license on one of those two computers at a time. Each Rental license you purchase allows you to activate Isadora on one computer. In all cases, you may deactivate a license on one computer in order to activate it on a different machine.

Either that or you were trying to use your Customer ID and Customer Password (only used to log into the Online License Portal) to activate the license on a computer instead of using the License ID and Activation Password. I admit that I deleted your screenshot before I thought to verify this myself, I was just concerned about keeping your license information secure.

Best wishes,

Woland

@bennnid said:

Though if sharing a list of outside Isadora shaders on the forum is a bit annoying for TT's team let me know

It's fine for users to share resources if they want to, I'm merely saying that, for example, user-generated lists of shaders that work with Isadora are probably going to be much longer than any official list that TroikaTronix will be able to post because the company itself won't want to be pointing our users to content that isn't legal for them to use. It's fine for users to share what they like because an individual user posting something cool on the forum for other users to play with or learn from (it's totally legal to mess around with any shaders you find, dissect them, learn more about shaders that way, and get inspiration to make your own shaders, you just don't want to be using other people's shaders in a performance, etc) is not the same as TroikaTronix officially posting a resource for our community to use (which most users would probably [incorrectly] assume would be fair game to use for anything, like our own GLSL shaders, FFGL plugins, etc are).

TLDR: 

Community sharing cool resources to learn from with each other = fine (and encouraged!)

TroikaTronix sharing things people might assume are legal to use in any setting = not fine (because we only want to provide tools to our community that they are legally allowed to use for any type of art/performance)

@bennnid said:

I think I should ( if this remains public) indicate the creator and link to each one !

Absolutely, when license information is absent or attribution is required (but the method is not specified), listing the author and giving a link to the source material is the standard method of providing attribution. If the author purposely includes information like their a website/instagram/twitter/facebook page/etc, it's also best to include those as well any time you post their work (or something that you've done which utilizes part of their work). Providing attribution on shaders that fall into those two categories (no license information or attribution required but the method is unspecified), that's the biggest good-faith step in terms of demonstrating that you're not intending to infringe on someone else's intellectual property. If, for example, you post an Instagram video of something cool you made using someone else's shader without crediting them that's immoral and illegal, but if you post the same video and provide attribution (so long as you're not violating some other part of the license explicitly) then you move from "technically illegal" to "legal grey area". Now if you didn't credit them and you used their work (or used it in a way that violated the license) and they found out, then you don't have a leg to stand on legally-speaking. If you credit them (and aren't violating any terms of the license) then, so long as you remove the content if they find it and request that you do so, you're much safer in a legal sense and much more solid in terms of morality because you weren't blatantly stealing someone else's intellectual property (or something that was based on it) and passing it off as your own.

So yes, please feel free to share things amongst yourselves, just know that the company itself has to be more selective in terms of what we can put together and offer as a "vetted" list of resources for our community.

@bennnid

Well if the page the url is linked to does not show any information about a 64bit version, I guess not. Not many did ever update there plugins.

Best Michel

Thanks for your help, I use the actor smoother and so far moving my sphere is smoother. Thanks again and see you soon. Thierry.

@jg how did you generate the 16bit image? it is static, could you split it into 2 8 bit images and use that inside Isadora with another texture input and then calculate a 16bit value from the 2 8 bit values.

@fred haven't tested the library, but I've read it works fine with "newer" releases (post from 2018) and it might have trouble with PD extended (I think latest release was 2013), which my colleague uses. Porting all to vanilla would be a huge endeavour since it is a lot what he's done, and all relying on extended. Nevertheless, I'll give it a try and post back.

cheers

@vidasonik said:

Maybe one for Bonemap!

 Hi,

You might find something to move forward with from the patch downloads available through this forum thread...

Best Wishes

Russell

it might be that you have content rendered on multiple gpus (nvidia and Intel gpu). The plug in will only have access to the gpu Isadora is set to use. In your case that should be setup to use the nVidia gpu. If you have content on a display connected to the intel gpu you will not be able to grab it.

@woland: Thank you.

@dillthekraut totally! I could program this with actors any number of ways. I'm more interested in scene list and status APIs that could exist at the application layer, rather than in the document layer, that let you check what Isadora is up to no matter what document is opened. That way I don't need to change a designer's file to implement the non-creative feature of remote status monitoring.

Thanks so much - I will do this next week and let you know how I get on! David

@fred thank you!!

@Woland thanks for you responses, they're appreciated

i haven't disabled snapshots since i use it often and i keep the status bar open so i can measure the load whilst live mixing. i know i can feed FPS to the control panel, is there a way to do the same with LOAD and CYC?

i've been considering putting the video bin on a separate screen, maybe using bin picker and stretching the control panel over two screens... if this will work then would be easier than using Touch OSC and OSC over WiFi to extend the control panel.

rgds, Mr J

IDEA 1: TouchOSC + Tablet/iPad

As I stated on the other post, you can move some of your controls to a tablet/iPad and use TouchOSC.

IDEA 2: One Isadora Patch, Two Control Panel Scenes

You can click in between Scenes in the Scene List to split the Control Panel, giving each Scene its own Control Panel. Using one or more background Scenes for your content, (activated with Activate Scene or Activate Scene Amount actors), you can use as many Scenes as you want to make individual Control Panels that all affect your content Scenes. Putting labeled Button Controls connected to Jump Actors will allow you to easily navigate between your Control Panel Scenes. Each Control Panel Scene needs to have an Enter Scene Trigger connected to an Activate Scene actor to activate your background content Scene. 

Here's an example patch with multiple (primary [dark blue]) Control Panel Scenes and just one (secondary [light blue]) content Scene

Scene 1 (Effects) & 2 (Snapshots) are separate Control Panels that both affect Scene 3 (Content)Scene 1: Video Effects Control (Primary [dark blue]) uses Control IDs 1-29 (30 and 31 are used to navigate between Control Panel Scenes)Scene 2: Snapshot Control (Primary [dark blue]) uses Control IDs 995-999 (30 and 31 are used to navigate between Control Panel Scenes)Scene 3: Content Scene (secondary [light blue]) uses Control IDs 1-29 and 995-999 (30 and 31 are used to navigate between Control Panel Scenes)

If you use multiple content Scenes, you'll need to make another background Scene for scene control with Activate Scene Amount actors and Envelope Generator actors so that you can fade the different content Scenes in and out from each Control Panel Scene.

Here's an example patch with multiple (primary [dark blue]) Control Panel Scenes and multiple (secondary [light blue]) content Scenes.

Scene 1 (Effects) & 2 (Snapshots) are separate Control Panels that all affect Scenes 3, 4, & 5 (Content). Scene 1: (Video Effects Control) uses Control IDs 1-29 and 33-46 Scene 2: (Snapshot Control) uses Control IDs 995-999 Scene 3: Scene Control (secondary [light blue]) uses Control IDs 33-46 to adjust the intensity of the content scenesScene 3 is a background Scene, controlled by Scenes 1 & 2, that adjusts the intensity of the Content Scenes.Scene 4: Content Scene 1 (secondary [light blue]) uses Control IDs 1-29 and 995-999Scene 5: Content Scene 2 (secondary [light blue]) uses Control IDs 995-999 Control IDs 30 and 31 are used to navigate between Control Panel Scenes

IDEA 3: Two separate Isadora Patches on Two Screens

Control IDs work across Isadora patches, so if you've got:

Display 1: VJ Patch (with actors using Control IDs 1-999) and Control Panel (Control IDs 1-450, for controlling your bin pickers)Display 2: A second Isadora Patch with your second Control Panel (Control IDs 451-999, for controlling your video effects)

The split of Control IDS I gave was completely arbitrary, but this should work if you don't want to put it all in the same patch and use multiple Control Panel Scenes.

@catoyo

Hi, If you have a three pin sensor the following Arduino setup is likely to work. If the sensor indicates 5v, it requires the Arduino code to be uploaded to a board with 5v pin like the UNO - which is what I have just tested it on using a 3 pin Pulse Sensor. The pin out is GND, 5V and the data / SIG (signal) pin is A0. If it is a digital pmw then change the signal to a digital pin on the Arduino board.

With the sensor correctly wired to the Arduino attach it to your computer using a USB cable. Start up Arduino.IDE and upload the code at the end of this post to your board of choice. Start up Isadora and from the Communication menu select the Serial Port Setup... In the dialog that opens go to Port 1 and in the pop-up choose the usbmodem14424 or similar as the Device. The Arduino code has a speed set to 9600 so set the speed of Port 1 to match. Leave the other values unchanged from the default. OK the changes and close the dialog. If the usb serial connection is not available you can use the button 'Detect Serial Ports' on the bottom left of the dialog box. When the dialog has closed go back to the Communication menu and check 'Enable Serial Ports'.

In the Isadora patch you want a 'Serial In Watcher - Text' actor with the parameters- 1: port, on: enable, 10: eom char. Inside the "Serial In Watcher' is this parser string: 

"Pulse Data: " pulse_sensor:float=4.#

You can also look at the Windows/Show Monitor to see if the data stream is being received.

Following is the Arduino code:

int Press = A2; int PressCapture; int PulseSensor = A0; int DelayTime = 25; int PulseCapture; void setup(void) {   // initialize serial communication at 9600 bits per second:   Serial.begin(9600);   // while the serial stream is not open, do nothing:    while (!Serial) ; } void loop(void) {   PulseCapture = analogRead(PulseSensor);   PressCapture = analogRead(Press);   Serial.print("Pulse Data: ");   Serial.println(PulseCapture);   Serial.print("Press Data: ");   Serial.println(PressCapture);   delay(DelayTime);  }  

best wishes

Russell

I scanned through the Guru Session #15 and I'm not sure what you mean. At what time in the video is this actor shown?

Have you looked through the Isadora patch provided as the download for the session? 

Do you mean the Shapes actor?

Best Wishes,
Mark

Hai Mark

Thanks for your extensive answer. I got the point more or less, but later, when back behind my computer, I will look closer to your explanation.

Keep up te good work!

Peter

@dusx WoW how did I miss that!!! thank you for the converter!!

Cheers

David

If you need something much more true to the laws of physics, you can look at this demo:

The DEMO FILE is zipped with the required Javascript files (all reside in the same folder).
I have included a number of resource URLs in the JS code, that will be helpful in figuring out how this works.