Captivate V12.1 doesn't support streaming video from Microsoft Stream.

[StephenH-NAB]

As per my title this is a major issue.

Is there any plan to support internal video streaming services?

Corporate rules prevent us from using either YouTube or Vimeo and the size of embedded videos will mean that we are not permitted to embed them in the SCORM modules.

Why are they limited to only those two providers?

[StephenH-NAB]

I'd also suggest you separate Captivate and Captivate Classic in your support discussions. They're entirely different programs and responses for each are completely unrelated to the other. Currently the support is amateurish with not even a manual available for Captivate 12.

[Lilybiri]

The team had promised me to have two different forums for 12 and the previous versions, since I am moderator here. But like with so many promises, it didn't happen. Sorry to sound bitter. I had promised to continue supporting Captivate Classic, but not version 12 and also got the promise to have version 12 experts around to help starting users.. Another promise which ans not kept.

Since no one seems to help for 12 (which I find subpar in its present situation) I felt guilty to leave so many questions unanswered. Bit off topic: too much is lacking to be able to give an answer quickly about version 12, while that is much easier for older versions. By asking some screenshots (Branching view, Advanced Interaction panel, Timeline panel, Advanced/Shared action Preview) I often can find the problem solution quickly in older versions. Or I asked to insert some system variable for debugging. Most of those don't exist in version 12.

There is a user guide available, will refrain from comments. In 2008 I started my blog because I found the available documentation had too many gaps especially for intermediate and advanced topics. 

As for your question, sorry to sound like a LP which is stuck, but in older versions it was perfectly possible to use a real stream server. Since this version is at this moment not really aimed at professional developer teams, I suspect such feature was estimated too complicated.

I can only recommend to log a feature request. Positive: you can do that right from Captivate, it has that option under the Help menu.

[StephenH-NAB]

Adobe's lack of support for this new product is incredibly poor, yet completely typical of the disconnected behemoth Adobe has become, especially in the learning space. Frankly Captivate V12 feels like an early alpha and misses so many key features that it's laughable.

It's not aimed at any real users I can see - especially with the bug ridden nature of its modules. It's not currently fit for purpose and they may want to consider that a complaint to the Australian consumer protection services, as an example, will see them hit with fines and penalties for offering such a product with claims that obviously are not met.

Not every country is the USA with no consumer rights for software subscriptions.

The lack of a dedicated forum after promises to create one is sadly typical.

[Lilybiri]

I just want to clarify that I am not being paid by Adobe to help users in this forum (and on many other social media). Up till version 12 I did believe that Captivate was the most versatile, multifeatured eLearning authoring tool and have defended it everywhere. For that same reason I created my blog in 2008 and have lot of fans. Here is a quote from a message I received yesterday:

"...Your content has always been one of my main resources for the 'classic' version."

For several reasons I have not blogged about version 12. Since weeks I try to recreate a very simple responsive project (original with fluid boxes) in version 12, without success. You can see the original project, which I based on multistate objects (which are available in 12) and shared actions (which I need to replace by Interactions which cannot have parameters, but need to use the dangerous Copy/Paste workflow).

https://blog.lilybiri.com/classic-captivate-vs-charm-test-case-responsive-project

I planned my focus on the Interactions, but even creating just the content caused me already so many crashes and loss of the project completely that I feel desperate. That will be the first time I gave up with Captivate. My only hope is that they will keep the Classic Captivate beyond 2027 for professional and company users. Just like Photoshop is for professionals and Photoshop Elements for other users, Premiere Pro for video professionals and Premiere Rush for other users. However they need to debug 11.8.2 which has a lot more bugs than 11.5.5.553.

[StephenH-NAB]

Hi Lilybiri - totally not directed at you, I appreciate that you're doing this to support the community and not part of Adobe.
I do wish Adobe were supporting their own products the way they used to 20 years ago however.

Their current model is awful and customer hostile.

[Lilybiri]

Thanks for understanding. Hope you feel my concern about the future of Captivate at this moment.