Peek 360 Default Save Location
Is there any way to change the default save location for Peek recordings? It defaults to "Documents" folder (%username%\Documents\Peek 360\) which is a network share in my workplace (and most corporate environments) and cannot be changed. This is cause for concern as unencrypted video files of confidential information is being transmitted to remote servers in this particular case. If only there were a way to change a basic setting like that. I don't understand why this is not configurable. As it stands, Peek 360 save files to locations that are not always suitable and does not allow me to manage where data is saved and stored. Any suggestions?Issue with Microphone configuration - preventing recording
I use my microphone for other applications like skype which work fine. Each time I select Peek - I press record - i get an error message: There was a problem connecting to your microphone. Please make sure it is installed correctly and not in use by another application. Then try again. I have turned off the microphone in Peek & i still get this message. Can someone please help? ThanksThe Difference between Screencasts and Software Simulations
If you’re new to creating software training—and even if you’re not!—you might use the terms screencast and software simulation interchangeably. But did you know they’re actually two different things? It can be easy to get these terms confused, so let’s walk through the nuances that differentiate these two methods and explore the use cases for each. Screencasts Screencasts are videos that show a recording of your computer screen. They’re often used to demonstrate the use of an application or software. They include all of your mouse movements and typically have audio narration that gives learners more contextual information about the process they’re seeing—such as the names of various software features or steps. Because screencasts are simply videos, they’re not interactive. When to use a screencast Screencasts are great for creating simple “how-to” videos. This kind of visual walkthrough is beneficial when you’re trying to explain a process that’s too complicated to explain with written text alone. And if the process isn’t something learners will be doing frequently, screencasts can be a helpful performance support resource that learners can easily reference in the future. How to create a screencast If you have Articulate 360, you already have access to not just one but TWO apps that are specifically designed for screencasts: Peek 360 and Replay 360. Learn more about when to use each app in this article: How to Decide Which Articulate 360 App to Use for Screen Recording. Want to see an example? Watch the “How to Add Comments in Review 360” screencast I created with Peek 360 below. This screencast provides a short overview of how to provide feedback on courses in the Review 360 web application. It’s perfect for an audience who may be comfortable with web-based technology and already have familiarity with Review 360. The screencast focuses on a simple process. It’s clear, concise, and to the point. So, how does a software simulation differ? Well, I’m glad you asked. Software Simulations While you also have to record your screen to create a software simulation, the major difference is that instead of simply showing the learners what to do, you give them the opportunity to try it out for themselves. They’re called simulations because you simulate the software’s interface by recording it and turning that recording into an interactive practice environment for learners. They can go through and click on all the buttons—like you did when you recorded it. It’s almost as if they’re using the software themselves. The advantage of doing it this way—versus simply having them use the actual software—is that you can build in on-screen explanations and feedback to guide them as they practice. Software simulations are usually the go-to for creating software training because they provide learners with a risk-free environment to help them learn a new app or process. Another thing that sets simulations apart from screencasts is that you can test your learners’ understanding by creating a simulation that’s graded. For every click in the right spot, learners can earn points. And for clicks in the wrong spots, points can be taken away. It’s a great way to ensure learners have understood how to complete specific processes within an app or software. When to use a software simulation Interactive software simulations are ideal when you want learners to physically practice using the software themselves—including entering data, interacting with drop-down menus, and identifying multiple steps in a more complex process. Software simulations give learners an opportunity to practice using the proper click-path of a specific process or software without fear of impacting the actual production environment or ruining any real-life data. With software simulations, you can put your learners in the driver’s seat so they can deepen their knowledge of a process, gain experience, and build confidence in using an app or piece of software. How to create a software simulation Articulate 360 subscribers can use Storyline 360 to create software simulations quickly and easily. Want to learn how? Here’s a tutorial that’ll help you get started: Creating Software Simulations in Storyline 360. Want to see an example? Explore the software simulation created with Storyline 360 below. In this example, users learn how to get started using the Review 360 web application. This simulation walks through four basic steps that you need to know how to do if you’ll be using Review 360. You’ll notice that because learners actually click through the software themselves, they must pay closer attention to each step in the process. This simulation is perfect for an audience who might not be as familiar with web-based technology or for users who are brand new to navigating Review 360. With simulations, learners can confidently navigate a new application because they’re practicing in the safety of a learning environment. View example More Resources Now you’re well on your way to identifying the nuances between screencasts and software simulations and you should be able to use these terms confidently when tackling your next project! To help you keep everything straight, I’ve outlined the differences in the handy table below. Screencasts Software Simulations Use case Demonstrate a simple, straightforward process. Train learners on a complex process through interactive practice and/or assessment opportunities. Interactive No Yes On-Screen Hints & Feedback No Yes Looking for more best practices around creating screencasts and software simulations? Check out these resources! And let us know in the comments what screencasts and software simulations you’ll be creating next. Follow This Process to Create Software Simulations and Systems Training Like a Pro 3 Methods for Recording Screencasts 4 Tips on Creating Software Tutorials in Rise 360 Tips for Using the Storyline 360 Screen Recorder Like a Pro Follow us on Twitter and come back to E-Learning Heroes regularly for more helpful advice on everything related to e-learning. If you have any questions, please share them in the comments.How do you keep e-learning courses engaging without overwhelming learners?
Hi everyone, I’ve been building courses in Storyline for a corporate client, and I keep running into the balance problem: how to keep the modules engaging without making them feel cluttered or distracting. For example, they want me to add more interactivity (click-to-reveal, branching scenarios, gamified quizzes), but at the same time, the content is already pretty dense. I don’t want learners to get lost in navigation or feel like they’re clicking forever just to move forward. I’d love to hear how others approach this. Do you have a rule of thumb for when to use interactivity vs. keeping it simple? How do you convince stakeholders that sometimes less is more in design? Curious to hear real examples of what’s worked for you!Recording using Peek with wider screens
We have recently upgraded our office setups and replaced our old dual monitor setup with new curved wide screens. Generally this has been great, but I am finding that Peek is unable to identify screens or windows with the wider screen attached. When I am working on the laptop alone or at home attached to 2 standard monitors, I am able to select a window or screen and Peek is able to recognise the dimensions of the window and record. If I am connected to the wide screen Peek is unable to select any window or screen correctly, even if I direct it to a window on my laptop screen Is there anything I can do about this? At the moment I am forced to do all screen recordings after hours at home and it is having a big impact on the work I can get done.Articulate 360 Peek Window issues
I apologize is this is covered elsewhere, but I didn't see it if it is. I have dual monitors because I find it easier to develop that way (pull up material in Word on one screen, copy into Storyline on the other). The Peek screen recorder seems to be a bit confused by that. When I try to record something, the "window" that shows up is about four inches from the screen I choose. For example, if I choose "full screen" of the monitor on my left, it puts the red box mostly in the middle of the two monitors instead of fully over the left side. I am posting a screen shot of where the window goes on this page for an example (attached). The weird thing is that it will record the screen as if it is in the proper place (though does record the line of record box itself). If I move it with the move crosshairs to cover the window fully over the where I want it, it does not record correctly (it acts offcenter). I've tried playing with various things in Properties to see if it is a "compatability" thing, but haven't found an answer yet. Anyone have any ideas?Blurring Names in Peek 360
Hello, Is it possible to blur names or certain areas of a screen recording using Peek? Or is it possible with any screen recording software within Articulate 360? I'm trying not to use Storyline or Studio at this point. I'd like it to be a true screen recording. Thanks, JessieSeeking Insights on DOM Attribute Changes in Storyline 360 Versions 3.87 to 3.91
Hello Articulate Community, I'm currently examining the backend code changes between Storyline 360 versions 3.87 and 3.91, specifically focusing on Document Object Model (DOM) attribute modifications. For instance, I've observed that the data-reactid attribute has been replaced with data-id in the published output. Understanding these changes is crucial for maintaining the functionality of custom JavaScript code that interacts with Storyline's output. Could anyone provide insights or documentation on: The rationale behind these attribute changes. A comprehensive list of similar DOM modifications between these versions. Best practices for adapting custom scripts to accommodate these updates. Your expertise and any resources you can share would be greatly appreciated. Thank you!
