Hi Keith,
First of all, congratulations for your work, it is extraordinary.
Sorry i don’t know much about it,
but I wanted to ask you if it was possible to change the resolutions of the displace and fluid effects to possibly avoid this kind of pixelation
PS : I specify that I have a commercial version
Many thanks in advance to anyone who can help me
Good day to you
Simon
Hi Simon Thanks! Glad you are making use of it.
Yeah I think for the both those effects there are some hard coded parameters setting the resolution. There are a few options:
Hope this helps. I think the second video on YouTube gives a rundown on how to make a new or edit an effect without issue.
cheers
Keith
Thank you very much Keith for your quick response
so I looked in the effect component on the disc but I can’t find a constant top module connected to a top feedback.
A big thank you to you
have a very nice day
Hi Keith,
big thanks for sharing this powerful tool with us. Having a lot of fun with it when playing with it. With 2018.27550 most things are running really smooth.
Do you have any plans to update the tool to the latest TD version?
I wasn’t really able to get it running including the mapper/previs section which is a great tool for itself.
I’m trying to read into the structure but for now it’s quite hard for me to repair and tune the tool. Will keep digging and watch the tutorial again, especially the part about the structure, how things are storend and handled. Plus it will require me to get more into Python to play and tune this beast.
Happy to support further development in any required way!
If someone is interrested and able to fix the bugs in the latest version I can play around and list issues, test versions or such. Please let me know how I can help.
All the best
Sven
Hi Keith,
there is one thing I’ve just figured out in 2020.23680…
When I start go to Setup > View Previs the model is shown as expected but when I click into the window the camera setting is getting screwed and therefore everything become black.
I thought the mapper is not working when starting luminosity in TD 2020, but it’s cool that its working in principle but the mouse readout is causing crazy moves.
Any ideas where this can be fixed?
Will keep testing in 2020 now that the mapper is basically working.
Best regards
Sven
Keith. What kind of superhero you are?
Huge thanks at this one! 
Put this one in next week to work with.
Hi @stevok apologies I completely missed your questions. I’ll take a look and see if I can figure out what is happening.
Hi,
This is an awesome project.
Does this need a TD pro license to work? Which version is currently supported?
(from above) how do I change the display layout to fit on an HD monitor? Can’t seem to add more channels in any version.
Will you be updating it? Sorry so many questions. Thank you…
I found this…searching to not have to reinvent the wheel. After going through tutorials on building media pools, clip launchers etc…Please keep this going. Building an aux/effects plugin system is beyond me atm. Be well!
Hi @Chalice Happy to hear you found Luminosity.
You can use it with any version of TD but you’ll be limited by the TD license limitations.
Unfortunately I partially hard-coded the UI to be 1920x1080 when I built it. It can be changed if a person were to go into the various UI elements and modify them, but it would definitely require some effort… The reason I partially hard-coded it was at the time dynamic UI’s using expressions were super slow and would kill performance but now that pars are cached a lot of that can change. For many things like plugin controls panels they get built procedurally by an init function.
Unfortunately a serious refactor of LM is not overly practical for me atm… I really haven’t had much time to update it recently. I did just load it using the newest official TD build and noticed drag and drop of generators and clips is broken and a few other small issues. I’ll try and take some time in the next week or two to look into them.
All that being said if anyone wants to take the time to dig into a serious overhaul and refactor I would be happy to provide some help on how things currently work and what would need to change to in order fix or refactor various aspects.
@keithlostracco Those 2021 drag-drop changes must have a few things out of place still, if you can narrow them down we’ll get on them immediately.
Hi. Thanks for the reply. I had a bit of help on a FB forum too. I’ve got it running fairly well in TD2020_22080. It’s really an amazing bit of work! and does pretty much everything I might need atm. Optimizing the settings to maximize frame rate is a further battle. Time will tell. I hope some tweaks will be forthcoming. It would be a shame to lose it to the usual entropy. But I do appreciate what a commitment it is. Cheers. Be well!
@Chalice I’ve just fixed the few issues I found in the newest official build. 2021.13610 . I think most things are working in that build now. If you clone the current master branch of the repo you’ll have the updates.
@ben yeah it seems the Legacy Drag drop is not working quite the same. It looks like there is no way to disable drop using the legacy setting. A container within a container was calling a drop script where previously the lower level container wasn’t. Not sure if I would call it a bug and in either case I simply changed a couple things to resolve the issue.
I’ve already used the new drag drop system in the KeyframerComp and it is far superior, I really like the callbacks and the way it works.
thanks for the update!
We thought we fixed all the cases, there were a number of bug fixes added since 2021 launch. We’d really love an example because people should not have to update their drag/drop scripts to update to 2021 build. Send to support if you can, or point us to the path.
Hi. Awesome. I tested your latest upload to github in 13610, Everything works all Gens, all FX, Drag n drop etc. But there seems to be an issue with cliplane controls on the left not working & channel clip triggering (i.e. the thumbnail preview in the clip channels…there’s an invalid path error in ui/channels/clipchannels/ ("triggerclips"select). (This is in Channel mode…with several lanes) 
Hope I have the right file.
Looks like I caused an error by removing clip1001 from each lane, I’ve added it back (I had forgotten is used for the Stop Clip button on the right of the ClipLaneControls). It’s fixed in master now.
Not sure what you mean by “too large UI” do you have a screenshot of the issue? You may need to set DPI Scaling to use DPI Scale if your windows setting is not 100%.
Cool. Channel Clip thumbnails now working! EDIT: Lanestop buttons now working, no Idea why. Don’t worry about the UI issue. DPI had to be set to “Native” in my case. All under control. I was confused at first by it always opening the menu overlapping two screens…as the user earlier in this thread was. So I replied to their (old) post just in case someone else searches for the same issue. …Also I would humbly suggest making it default to Channel mode to ease in new users.
Also. Oops. Just found the animation “add parameter” menu has an issue. Can’t add parameters ( in the TD animation interface that pops up on clicking C in the preset window.). Actually I can add the first item on the menu or add all. So this is just a niggle. Awesome. Everything is really working. THANK YOU. If I notice anything else I’ll just add it on github. This thread is gettin messy.
I’ve turns out the bug you found where you can’t add a parameter in the animation editor is a new TD bug. I’ve created a workaround and pushed a commit to master but I’ll report the bug in the bug forum.
Luminosity is the only free VJ application on Windows platform that can be picked up quickly and has no restrictions other than those of TD non-commercial license. This is literally a lifesaver in an educational environment and a very important tool for teachers of video performance tools that have to travel and go to work in short-term workshop events.
I’m teaching a BYOD class of 21 students this winter with mixed macOS and Windows machines and we don’t have enough time to dig deep enough into TouchDesigner itself. Luminosity works perfectly as a front-end for the Windows users. HAP support works out of the box - fantastic; easy to reconfigure to create Spout or NDI outputs - magical.
On macOS Big Sur MBP16" with AMD Radeon Pro 5500M unfortunately I’m getting compile errors on the GLSL Multi TOPs with the latest versions of Luminosity, so master output mixdown doesn’t work - but as long as Luminosity works on Windows, it is heaven sent.
