jstrecker's picture
Jaymie commented on 2bitpunk's Discussion, “FFGL file naming / renaming (don't)

Hmm, we would have expected renaming to work. That's the reason we're storing the original name in the Info.plist. Our understanding is that applications that load plugins are supposed to look in the Info.plist for the original name, to handle the case where the plugin has been renamed. Yet neither Resolume nor VDMX seems to be doing that. We've contacted the Resolume developers to see what they recommend, and will let you know if we learn anything.

As you probably already figured out, the workaround, if you want to rename an FFGL plugin, is to change either the Vuo composition's file name or the Name field in Edit > Composition Information…. and re-export.

FloriPFA's picture

This workshop opened my eyes for what's possible in the world of realtime visuals. After 20 Years of working with pre-produced visuals it's time for something new - very good introduced, thank you Huseyin! And thank you Mr. Demirel for connecting us!

2bitpunk's picture
2bitpunk posted a new Discussion, “FFGL file naming / renaming (don't)

FFGL file naming / renaming (don't)

Hi,

I noticed on FFGL exports the file name is changed to Title + spaces also if you rename the file it breaks the plugin.

Example file export name change: VuoLineStripObject.bundle changes to Vuo Line Strip Object.bundle

This is fine I can work with that but if I were to change the file name after exporting to add a version number this breaks the plugin as the exported file name is included in the package (bundle) info.plist.

To help new users it might be an idea to add a warning on the Export Complete dialogue box.

2bitpunk's picture

Ask the developer he’s really helpful and a Vuo user

kokot's picture

Thanks for your replay. Yes, this is how I have it connected. It reads the ShootUSB input correctly but only shows up black screen. I dont know what Im doing wrong. I also tried with the hdmi put but get the same result. Anyway, thank you for your help!

2bitpunk's picture

Connect the iPhone using a USB to Lightning cable and it should show up in the Device List in Receive Live Video (vuo.video.receive2). I've just tested it to check and it works with my iPhone 7 Plus

kokot's picture

Hi 2bitpunk, do you know if Shoot works on all iPhones? I have 6S and cannot get it working. I dont have a Pro version, just a basic, but it should still work (with the water mark) I think. I also tried to connect it directly to VDMX, it reads the input as Shoot USB, but only sends the black screen. Thank you for any help

jstrecker's picture
Jaymie commented on Bodysoulspirit's Bug Report, “Webpage rendering problems

As you noted, problems playing videos and Lottie files in Make Image from Web Page are caused by basically the same underlying problem: limitations with the macOS web browser engine that the node uses to render web pages.

We recently tried a few more experiments in search of a relatively quick fix or workaround. But there really doesn't seem to be one. The node renders the web pages to an offscreen window and then turns the result into an image. There doesn't seem to be any way to trick the browser engine into playing Lottie animations when rendering to an offscreen window.

You asked about outputting an image vs. outputting directly to a window. If literally all you want to do is display the webpage, then you can use the Open URL in Browser node (and Lottie animations will work). In contrast, outputting to an image makes it possible to integrate the image with other Vuo graphics and to interact with the page within Vuo. Outputting directly to a window would not be noticeably faster, since macOS would still be internally rendering to an image that it provides to the window manager.

Coming back to the main question of the bug report — We'd have to investigate further to know just how difficult it would be to get around the limitations currently in the Make Image from Web Page node. Recently we thought of one potential solution, which would be to render the image to a virtual screen rather than an offscreen window, but we'd have to try it and see if it worked. If not, the only solution we know of would be to reimplement the node with a different web browser engine, as I mentioned on the other bug report.

Although the limitations with Make Image from Web Page are arguably a bug rather than a missing feature, the amount of effort required to fix the limitations is more like a feature request than a typical bug report. So if this is important to you, please create a feature request, linking to this bug report, so the community can prioritize it relative to other improvements.

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. Typically a few emails per year.