PS: if it was me, I'd go with the M1 as your primary Mac, and the older 2013 as the backup. Preferably an older one without a T1/T2 chipset. If there are problems in testing, you'll have to hire or borrow an Intel Mac as your backup. ![]() But make sure you test things thoroughly prior to opening night and don't let that Mac touch the internet afterwards - even if you disable software update, Apple still can silently deploy critical patches without any user notice or control. And don't get me started on butterfly keyboards. Buying an Intel Mac right now would really be a waste of money and you'd really only avoid the issues by going with an older Intel Mac (2015 or so) which would open you up to old/no-longer unreliable hardware. Since this M1 is a second Mac, not your only one, I think it's an easy decision. ![]() They were all issues with the low level operating system and/or hardware connections to the sound desk and/or projector. I'm sure none of the problems were related to QLab. Worst of all, it was often unclear what the problem was or how we fixed it. Sometimes extensive troubleshooting and changes were required. We were able to fix all of them, but not always quickly. We run QLab on one of those Macs and have had issues with both audio and video. The audio and video playback areas of the M1 are especially prone to bugs as the way basically the same system gets up to *95 hours* of audio playback from a truly tiny smartphone battery is by using hardware instead of software for media playback and the new systems have occasionally been unreliable with tasks more complex than listening to a 3 minute song or watching a YouTube video.īy the way - modern Intel Macs have the same issue, as again to improve battery life audio and video output doesn't run on the primary CPU, it runs on Apple's T1/T2 coprocessor which is basically an older generation of the M1. M1 is an immature platform and not only has a lot changed recently, but there are almost certainly more changes coming over the next few years. It absolutely does work - however it might not work smoothly. Adds support for sending audition GO and audition previewing cues to QLab 5 from QLab Remote.You're right to be cautious - I don't think the "dust has settled" yet. The best Linux alternative is Linux Show. ![]() Does QLab work on LinuxQLab is not available for Linux but there are a few alternatives that runs on Linux with similar functionality. A show that uses one Mac for playing back Audio and another Mac for playing back Video has two Main computers. Network communication is now encrypted when connected to a QLab 5 workspace. The Main computer is used to run cues during your show. ![]() Adds several validations to ensure that automatic reconnection picks the same machine if multiple copies of the same QLab workspace are open at the same time on the network. Improves the ability to recover from a momentary disconnect while the app is in the background. Or connect twice to the same workspace and view different cue lists. Connect to two workspaces and view them side-by-side on the same screen. Adds support for opening multiple windows on iPad. Adds support for previewing cues from QLab Remote. Adds ` (backtick) keyboard shortcut to support hardware keyboards that do not have an Escape key. Fixes a bug that prevented crash reports from being discovered upon launch. Fixes a bug that could prevent keyboard shortcuts from being recognized. Fixes a crash that could occur when disconnecting from a workspace while viewing the Active Cues cue list.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |