I'm trying to select a new machine and debating on a graphics card with CUDA for rendering. Does Storyline currently utilize CUDA rendering by chance? If not, is there any plan to develop this capability in the future?
You'll see the current specifications needed to run Storyline outlined here, and I don't know that there is a plan to utilize that capacity in the future but you're welcome to share your thoughts in the form of a feature request here with our team.
is this already implemented on the current version of storyline 360? im dont think it doesnt have that feature yet utilizing the CUDA cores of the any Nvidea GPU for Video rendering or Video Editing.
Storyline 360 is not CUDA aware at this time. I'll let our team know you have a need for this, and you can always add more thoughts as a feature request!
When you publish a course, your videos will be encoded so they're no larger than your slide size with a key frame every 5 seconds—unless you turn off video compression.
Let me know if there's anything else I can answer. I'm happy to help!
Is there an update on this or utilizing the media engine on m1 MacBook Pro? I know I have to use parallels to run storyline in mac, but is there any chance the team is looking into updating the instruction set to utilize these newer functions?
If you are encountering any performance related issues with running Articulate 360 in a virtual environment, please don't hesitate to reach out to our support engineers so we can take a closer look at what's happening.
I understand that the M1 question was kind of thrown into the topic; however, there is still a need for those of us who build courses and export as a mp4 to have some efficiency with the way GPU power has increased over the past 5 years. CUDA cores are being wasted by having the CPU do all the work. Furthermore, not all my cores were being hit hard. I have both Mac and PC, but I am hoping that your team will work to improve the rendering process.
Thanks for sharing your need for CUDA awareness. I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them more through a feature request!
7 Replies
Hi Aaron and welcome to Heroes!
You'll see the current specifications needed to run Storyline outlined here, and I don't know that there is a plan to utilize that capacity in the future but you're welcome to share your thoughts in the form of a feature request here with our team.
is this already implemented on the current version of storyline 360? im dont think it doesnt have that feature yet utilizing the CUDA cores of the any Nvidea GPU for Video rendering or Video Editing.
Hi there, Bryan. Great question!
Is Storyline 360 CUDA aware?
Storyline 360 is not CUDA aware at this time. I'll let our team know you have a need for this, and you can always add more thoughts as a feature request!
Related areas to explore:
Let me know if there's anything else I can answer. I'm happy to help!
Is there an update on this or utilizing the media engine on m1 MacBook Pro? I know I have to use parallels to run storyline in mac, but is there any chance the team is looking into updating the instruction set to utilize these newer functions?
Hello Dan,
Thanks for reaching out!
I'd like to share this article with you, which details everything we know about M1 support in virtual environments:
If you are encountering any performance related issues with running Articulate 360 in a virtual environment, please don't hesitate to reach out to our support engineers so we can take a closer look at what's happening.
I understand that the M1 question was kind of thrown into the topic; however, there is still a need for those of us who build courses and export as a mp4 to have some efficiency with the way GPU power has increased over the past 5 years. CUDA cores are being wasted by having the CPU do all the work. Furthermore, not all my cores were being hit hard. I have both Mac and PC, but I am hoping that your team will work to improve the rendering process.
Hi Dan,
Thanks for sharing your need for CUDA awareness. I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them more through a feature request!