Just want to say a big thanks to MidiKinetics for the the YT tutorials on scripting. Nicely done.
They reminded me what a great time I had with Lemur scripting back in the day and also, with the change in pricing, how I might just get back into Lemur.
I have a question which Liine never really answered: I have both a JM Lemur and an iPad. Some .jzml projects would open on the old hardware and some would not. What is the object or script that limits projects from being opened on the JM Lemur (which I still use!)
MidiKinetics Scripting Videos and a question
-
midikinetics
- Regular
- Posts: 56
- Joined: 15 May 2015 17:46
- Contact:
Re: MidiKinetics Scripting Videos and a question
Glad you enjoy the videos! There's a lot more to come.
We don't officially support the original hardware devices—and we don't even have one ourselves—so it's hard to say with certainty. However, I'd guess it's less about explicit blocking (such as a version control mechanism) and more about compatibility issues. Newer Lemur projects rely heavily on objects and features that weren't available when the original hardware was designed.
For example, newer objects like Canvas, Image, and Sequencer simply don't exist on the original JM Lemur. Additionally, newer projects might expect arbitrary screen sizes, whereas the original hardware has a fixed screen resolution. Memory constraints could also be an issue; the older JM Lemur has significantly less memory, meaning it might fail to load larger or more complex projects.
Newer projects could also depend on language features unsupported by older devices, resulting in failed computations or unexpected graphical output.
In short, any of these factors—unsupported objects, language incompatibilities, screen size mismatches, or memory limitations—could prevent certain projects from loading on the original JM Lemur hardware.
We don't officially support the original hardware devices—and we don't even have one ourselves—so it's hard to say with certainty. However, I'd guess it's less about explicit blocking (such as a version control mechanism) and more about compatibility issues. Newer Lemur projects rely heavily on objects and features that weren't available when the original hardware was designed.
For example, newer objects like Canvas, Image, and Sequencer simply don't exist on the original JM Lemur. Additionally, newer projects might expect arbitrary screen sizes, whereas the original hardware has a fixed screen resolution. Memory constraints could also be an issue; the older JM Lemur has significantly less memory, meaning it might fail to load larger or more complex projects.
Newer projects could also depend on language features unsupported by older devices, resulting in failed computations or unexpected graphical output.
In short, any of these factors—unsupported objects, language incompatibilities, screen size mismatches, or memory limitations—could prevent certain projects from loading on the original JM Lemur hardware.