@dusx said:

<p>@mark_m said:</p> <blockquote>Any gotchas that we know about?</blockquote> <p> Nothing I can think of. Most Add-ons are now included by default, but plugins in the external folder won't cause any issue since Isadora 4 checks the internal version numbers. We have been running V3 and V4 side by side for months, and I haven't had any issue. Of course backup before upgrading, since file format will be updated and won't be openable in V3 if you need to go back for any reason.</p>

Hello all,

I'm working to rebuild a setup I had (modifying the Guru 13 patch) that combines/averages multiple sets of body tracking data to puppeteer one stick-figure avatar collectively. Now, I'm trying to get the data from multiple (2) iKeleton OSC apps to do the same as part of a conference demo. This way I don't have to travel with the Kinect. 

Here's the trouble: I can't seem to disambiguate the two apps running on two different phones. Right now, they are sending to the same OSC channels as each other. So, rather than getting two sets of data (a total of 68 channels), Isadora is receiving both sets as one, glitchy set (34 channels) coming into the same place. 

Does anyone have experience working with multiple copies of OCS apps like this? What can I do so that Isadora can treat the input from these separate phones as distinct? 

(it appears as though the iKeleton OSC app settings allow you to change only the IP Address and Port)

tldr; 

I'm trying to get the data from two phones with the iKeleton OSC app into Isadora, but Isadora can't tell the difference between them.

Best,

Rory

MacBook Pro, M1, 2020, Sonoma 14.5

Isadora 3.2.6 + Isadora 4.0

Hi Everyone, 

I have a setup using the SRT Player. Lots of videos selected at Random and played through a projector, is there a way to select the matching SRT file to play in sync on a separate projector/screen? 

I've no doubt Im overlooking an obvious Actor to make this happen, enjoying having the subtitles be adaptable through the text draw so would like to keep it that way if possible.

Many thanks

Simon

@peterrrrr

Hi,

There is a midi/OSC app that supports png image files:

OSC/Pilot

Then use ‘Guided Access’ on your ipad to create kiosk mode. 

Another option is hosting the controller in a browser that supports kiosk mode. Node.js can be configured with a browser interface that sends OSC commands to Isadora. Once the functionality is set up, coding images into html should be straight forward. Here is a forum thread describing node.js setup and some alternatives. There is an implementation of node.js for iPad OS.

Example: node.js into Isadora

Best wishes

Russell

Hi

I was surprised not to find a topic like this. Please let me know if there is one. 

Im helping a friend with an exhibition where they would like to screen a bunch of videos on a big screen with an ipad/touch screen to controll what video to be shown. I did it fast in Qlab just to have something running, and the function is there but the looks are what they are, not made for beeing shown to public. I would like to make a simple menu with thumbnails from the videos and the titles and one stop button. I've looked through the most common OSC apps but havent found one where you can import your own images. I've also tried with my Brightsigns but none of them have a usb port for the touch sceen and there's not enough money in the project to buy a new one just for that. An extra star if its possible to put the ipad/touchscreen in kiosk mode, to lock the ipad to that specific app and page. 

Thanks!

@dusx, oh very cool. This sounds amazing. Working with actors using text addressing could open all kinds of possibilities!

@kfriedberg said:

30%

 It may be that there is some delivery delay going thru the arc 2 the Nvidia gpu. However a heavy patch that maxes the Intel arc only processing may be easily handled using the arc 2 Nvidia path. I would suggest running some heavy test files where the Intel processing maxes out, then see how high that goes on the Nvidia. 

@jtsteph

Thank you for the comprehensive write-up, as you might have gathered the current/new addressing is the first step towards a system much like this. We have exciting plans for this and intend to base it somewhat on osc.

For now that's probably all I should say ;)

Overview

Implement a new system for routing data between actors and control panel items using an address-based approach, similar to the recently implemented SHOW/HIDE control functionality. This would complement the existing CTL# system while providing flexible and programmatic control panel data routing.

Current Control Panel Data Routing

• Users manually assign CTL# values to inputs/outputs of actors to connect with control panels
• In complex patches (especially those using many nestled User Actors or state changes like controlling layer or channel based media mixing), assigning and managing CTL# assignments becomes challenging
• The current system makes it complex to implement dynamic routing or state-based control panel configurations

Proposed Solution

Introduce two new actors that leverage the existing controller address system:

1. Send Controller Data
   • Sends data to control panel items using an address-based system
   • Uses the same addressing syntax as SHOW/HIDE controls
   • Allows for programmatic assignment of data routes
2. Receive Controller Data
   • Receives data from control panel items using the same addressing system
   • Enables dynamic routing of control panel data to different parts of the patch

Key Benefits

1. Programmatic Control
   • Enable dynamic assignment of control panel connections
   • Allow for programmatic state change and lookup table-based routing systems
2. Flexible State Management
   • Enable the same controls to serve different functions based on patch state
   • Facilitate easier management of multi-layer/multi-track systems

Technical Considerations

• The system would maintain compatibility with the existing CTL# functionality
• Implementation would leverage the established osc-like show/hide controller address syntax
• Support for wildcards and pattern matching in addresses

Impact

This feature could significantly improve workflow for:

• Complex performance systems
• Multi-layer video setups
• Installations requiring dynamic control routing
• Projects using extensive nestled User Actor networks
• Systems requiring monitoring of multiple parameter sets using the same control panels

Compatibility

• Maintains backward compatibility with existing CTL# system
• Builds upon familiar OSC-style addressing already implemented in SHOW/HIDE controls

@mark_m

Not yet, but a good idea after I do some more testing.  My latest switch to the Game Ready series of drivers seems to have stabilized load at under 30%, but that's still well above the Arc's 4%.  If I have time before vacation I'll compare to a desktop with a GeForce/UHD combo, otherwise more results to come in a few weeks.