@bonemap said:

As a workaround, can I edit the Isadora preferences file manually while the Isadora application is closed?

 I don't know how to edit the preferences file since it's binary and not plain text, but one workaround is:

1. Use the steps in this article to install both the newer version of Isadora, and an older version of Isadora that doesn't have this problem.
2. Delete your Isadora Preferences (use the steps under "macOS" and "Windows Option 2" from this article to delete all of them.)
3. Open an older version of Isadora that doesn't have the issue.
4. Change the OSC port in that version
5. Close the older version of Isadora
6. Open the newer version of Isadora
7. It will create a new preferences file by copying the older preferences file, in theory taking on the OSC port you set in the old one.

NOTE: If you want to change the port again, you need to perform steps 2-7 above again.

@bonemap

Thanks, we've now logged this.

@citizenjoe

Thanks for this insight. The 2 license approach is where I am leaning. Having a year on a second license allows work to take place for a longer period, after which I could reevaluate whether I still need the additional license for another year. 

I'm glad to hear that it's worth it to do the upgrade. It sure seems like there are significant things that make it all more flexible, versatile and easier to do a lot of things... especially audio. I look forward to working with it.

I appreciate your feedback.

Best,

Craig

Hi,

I'm experiencing an issue in Isadora on Mac ARM computers when trying to change the Open Sound Control (OSC) port number in the Midi/Net tab of the settings panel.

1. Normally, I open the Isadora Settings/Preferences panel, go to the Midi/Net tab, and enter a new value in the OSC port text box.
2. To commit the change, Isadora triggers an internal system warning prompt stating: “You will need to quit and restart Isadora before changes to the OSC Port will take effect. OK”.
3. Sometimes this works, but regularly, this specific alert dialogue confirmation breaks its focus layer and becomes disassociated from the parent Settings window. It fails to render over the UI properly or permanently separates from the active window layer.
4. The confirmation box blocks all background interactions and waits for the user to click OK. However, because the element is unresponsive to cursor clicks, I cannot execute it. This risks losing unsaved project progress.

As a workaround, can I edit the Isadora preferences file manually while the Isadora application is closed?

Best WIshes,

Russell

@bonemap 

Very cool!

@mr_j

I'm not seeing the exact same behavior as you, but something similar. I am able to close Isadora Settings, but I do see that on newer versions of macOS, this causes an eternal popup that can't be closed for me, so I'll log that.

Best wishes,

Woland

@kolmon3853

I work in a similar situation. It seems to me that you probably want 2 licences. That said, do you know that you can rent a licence for a short term? It's really cheap and easy to deal with. It also then put the onus on the other party to rent it and pay for it, should that be a thing.

Pricing for Isadora 4 and IzzyCast : TroikaTronix

Cheers,

Hugh

BTW, do the upgrade - it's well worth it.

@bonemap

Hello!

I'm not sure what category I should use for this query. It doesn't seem to fit in the existing options, unless the How To relates to how to do licenses.

I have been using Isadora for about 14 years in various ways, including multimedia stage productions and interactive installations. I’m currently using Isadora 3.2.6 on a Mac platform with a Perpetual License for Isadora 3. For several years it has worked well for me to work mainly in my home studio environment and mount productions and exhibits in other locations as needed. For the last 2 years I continue to work in the home space, and also at a larger studio space where we have installed a standing exhibit infrastructure with performances and events taking place in that studio several times a year.

I have been following the developments in Isadora 4, and I’m excited to start using this new version. I’m coming to ask for some guidance from others in the community about which license structure I should use. I realize that I can simply upgrade to the Isadora 4 Perpetual license and continue as things are now. But I’m occasionally getting some help from some colleagues, and I’m bumping up against the limit of 2 computers. I need to maintain the home studio computer where I do most of my development, and I need to maintain the computer at the other studio space to service the ongoing needs of the programming and development at that space. If I need to have some help from a colleague, then I have to keep activating and deactivating computers, and do a lot of coordinating to make sure that we both can do the work that we need to do.

I wonder if I should be examining some other license structure, but I’m not sure if any of the other structures service my need for this kind of use.

Should I think about using the USB Key version? I think it could help in some situations, but I see that the key version can’t be used with a subscription license.

Should I think about upgrading my current Isadora 3 Perpetual license, and then perhaps have to get a separate yearly subscription for another person to be able to work with me?

Should I pass on the Perpetual license and get 2 yearly subscriptions?

I don’t see any way to just add one additional computer to the current Perpetual or Yearly Subscription versions, and I suspect that folks here have had more experience with how this would work balancing cost and effective work flow.

Any advice you can provide would be greatly appreciated. I feel like I’m trying to make a decision with limited understanding about how this might best work.

Thank you!

Best,

Craig Harris

(Minneapolis, MN USA)

@mr_j

I still dearly want this as well. We have a plan for a new addressing system that would allow for an unlimited number of Control IDs (functioning more like OSC addresses), but we haven't been able to implement it yet.

Once Control IDs can be unique, it'll allow moving bits of Control Panels between patches and sharing User Actors with paired Control Panels without the possibility of causing a conflict, which I really look forward to.

One way you could store and recall more info at the moment would be leaning on the Data Array actor or using the method outlined in my previous post.