Apple dumps Intel and shows Final Cut Pro on new Mac with Apple CPU !
- Thread starter joe1946
- Start date
filmguy123
Veteran
Peter, quick flashes of black intermittently, or longer black outs?
How long is your cable? Who makes the adapter? Certain adapters and/or longer cables can cause issues. Hopefully just a driver/OS issue. Sorry to hear.
How long is your cable? Who makes the adapter? Certain adapters and/or longer cables can cause issues. Hopefully just a driver/OS issue. Sorry to hear.
Peter C.
Veteran
Video interface is known issue with M1/Big Sur. Before buying my BenQ monitor I did a lot research to find the right cable to support 4k. It's highly rated https://www.bhphotovideo.com/c/product/1414395-REG/iogear_g2lu3chd02_usb_c_to_4k_hdmi.html
The effect is like change the input on your tv, it momentarily loses signal for 2 seconds and comes back on. Its minor inconvenience but I could use the computer to record or stream anything critical.
combatentropy
Veteran
M1 Mac users report excessive SSD usage, potentially affecting the component’s lifespan (9to5 Mac). I would wait to see them iron this out before I bought one. Or have any of you witnessed this yourselves?
Thomas Smet
Veteran
I have been through 3 different USB-C to HDMI adapters and finally got one that doesn't have any issues. While this could partially be a Big Sur bug I think some adapters are impacted by the bug worse than others.
Luckily I mainly use my MBA away from my desk so I don't use an external monitor all that much.
Luckily I mainly use my MBA away from my desk so I don't use an external monitor all that much.
Thomas Smet
Veteran
If you read the comments the testing for this may have been flawed and there may not be a problem at all. Just an overexciting testing tool that is not translating the results correctly.
Apple has a very long history of using flash storage and they can't possibly screw up this badly. When it comes to writing files to a drive it either has a file to write or it doesn't. A system can't just suddenly decide to write random BS to a drive thousands of times just for the heck of it.
I think we should let the details get worked out before people jump to conclusions. If it a flawed design I'm sure Apple will replace the machines affected by this. Thats part of the advantage of buying Apple. When they do have a design flaw they tend to take care of it down the road. Apple replaced the entire logic board on my 2011 17" MBP twice.
filmguy123
Veteran
I’ve also had the aforementioned issue on a windows PC and it turned out to be the cable in my case.
Peter C.
Veteran
I discovered that was the problem. Despite the good reviews of ioGear usb-c to HDMI cable was causing the intermittent black screens. When I switched to a HDMI to HDMI cable I no longer had a problem. There are less resolution settings available but that's a better trade off to random black screens.
Retrospective
Well-known member
Been using the M1 Macbook Pro (8 GB RAM) with Davinci Resolve 17.1 beta for about 2 months now. I had to replace my iMac 2012's Fusion drive which dies every 4 years and didn't want to replace it anymore.
Performance is way better than my iMac 2012 (32 GB RAM, 2 GB NVIDIA GeForce GTX 680MX). Couldn't be any happier with the performance. If this is any indicator of future performance, I will eventually get the M1 version of the iMac when it comes out .
M1 Macbook Pro works great with the LG Ultrafine 5K display.
The biggest issue is SUPPORT for your software.
- Had to work without FilmConvert Nitrate since they didn't have support for M1 at the time but now they do. Red Giant plugins still don't work on the M1.
- SoftRAID support is broken on the Big Sur 11.2 update. Doesn't mount any SoftRAID volumes. This is pretty much a big deal since I rely on SoftRAID. The support is not 100% even before 11.2 update.
Performance is way better than my iMac 2012 (32 GB RAM, 2 GB NVIDIA GeForce GTX 680MX). Couldn't be any happier with the performance. If this is any indicator of future performance, I will eventually get the M1 version of the iMac when it comes out .
M1 Macbook Pro works great with the LG Ultrafine 5K display.
The biggest issue is SUPPORT for your software.
- Had to work without FilmConvert Nitrate since they didn't have support for M1 at the time but now they do. Red Giant plugins still don't work on the M1.
- SoftRAID support is broken on the Big Sur 11.2 update. Doesn't mount any SoftRAID volumes. This is pretty much a big deal since I rely on SoftRAID. The support is not 100% even before 11.2 update.
Thomas Smet
Veteran
To be fair any plugins or software that still doesn't work is pretty sad and blame is 100% on those developers. The M1 has been out now for many months and the test Mac mini devices were out for months before that for developers to use. Considering how quickly some open source software out there is adapted I find it inexcusable for software developers to not yet have M1 support. Its not like Apple made the process complex either. If software is developed properly Xcode practically does most of the work for you to make it M1 compatible.
Resolve, Affinity and Sketch are some pretty complex applications and they had native M1 support within weeks of the M1 launch. This is why I say blame falls 100% on the 3rd party developers for their "motivation" to support M1.
BMD still isn't supporting my Thunderbolt Shuttle capture device however which is a bummer. Most of their I/O devices are now supported excluding the Shuttles. Granted those are pretty old now but still very functional for HD.
The SoftRAID part does suck. I'm lucky I don't currently use any RAIDs. To be fair I would say most users using RAIDs likely wouldn't buy entry level Macs so I'm sure the impact is minimal. Most formats entry level Mac users are using work perfectly fine on HDD or SSD drives. Hopefully that gets ironed out soon because the M1 is powerful enough to edit formats that require RAIDs.
filmguy123
Veteran
I suspect by the time the more powerful models are released (ie 16" later this year), things will be much more ironed out. IMO Apple released the lightest weight Macs first intentionally, to give developers time, work out kinks, and make for a much smoother launch when they aim this at pros later in 2021.
Peter C.
Veteran
I've never had good luck with plugins. Most are incompatible with my MacPro because it's too old and my M1 because it's too new. They can get expensive, have short lifespan, slow down playback, export, and can cause crashes.
I had a question about the installation of plugins. On my MacPro I they're located either in hidden somewhere deep in the Applications Library folder or in Users Document, Motion folder. On my M1 I didn't have Motion installed and after some experimentation I found the only way to add custom Motion template was to copy it inside the actual Application. Hopefully I won't lose my custom plugins when I install the next FCP update. Why doesn't Apple provide a simpler way to managing plugins? There should an interface or separate utility that shows their location with options to backup and install/uninstall.
I had a question about the installation of plugins. On my MacPro I they're located either in hidden somewhere deep in the Applications Library folder or in Users Document, Motion folder. On my M1 I didn't have Motion installed and after some experimentation I found the only way to add custom Motion template was to copy it inside the actual Application. Hopefully I won't lose my custom plugins when I install the next FCP update. Why doesn't Apple provide a simpler way to managing plugins? There should an interface or separate utility that shows their location with options to backup and install/uninstall.
Last edited:
Retrospective
Well-known member
True, Mac developers had access to the M1 transition kit for a while now but the excuse I get from companies is they have limited resources. Check out Adobe, a behemoth but they only have Lightroom as the only Adobe software with native M1 support.
Not sure what is SoftRAID's excuse is but Im not the only frustrated customer.
Retrospective
Well-known member
Pretty much! Its not easy being the guinea pig, it comes with a lot of frustrations!
filmguy123
Veteran
I've never had any real issues with plugins, but I've been in the safe middle of traditional modern x86. You definitely jumped from one niche to another! The good news is, your new niche has an upward trajectory rather than downward... whereas the old MacPro had death pains, now you've got some teething pains but it will get much better soon.
A very reasonable justification... I have to imagine, looking at total revenue stream from a company, the amount of users impacted by Colorista IV not operating properly on their M1 Macbook is absolutely miniscule. This will inevitable change once more M1 chips are in the wild, and especially with more professional adoption later this year.
As geeky as I am and naturally drawn to the bleeding edge, it does pay to be slightly behind the curve on bigger changes! A fundamental architectural switch for a professional platform is about as big as it gets. While this transition from Apple exceeds every expectation I could have had for smoothness, it's definitely "guinea pig" territory for now. Overall though from what I hear it sounds like some of the perks may be worth playing pig for a day!
Looking forward to a 16" M1X system once I know all my plugins will work and all the key apps are fully native and out of beta, which at the current rate, may be surprisingly soon.
Thomas Smet
Veteran
As a software developer I totally get that but there is no excuse for Adobe since they moved to a subscription model. They get new revenue every month.
With that said I know it can be hard. Especially if the software/plugin isn't selling very well anyway. The thing about FCPX is it does a very good job at not needing many plugins. FCPX may look like it has a ton of plugin options out there but that doesn't mean its a very lucrative industry.
Much like the lack of user need for SoftRAID the same may be true for plugins. The vast majority of M1 users out there likely don't do anything with video and those that do either use iMovie or the very basic version of FCPX which already does everything they could possibly want. I don't have any stats but to me it seems like either luts, grading or Motion based effects seem to be the mostly widely used plugins. Lots are for the most part supported directly in FCPX and Motion template based effects are 100% supported of course. That leaves the occasional user that needs more robust grading tools, better keying tools or some fancy filters that Motion can't do. I'm not sure how much of the target M1 audience needs fancier keying or grading tools. I'm sure they exist but we have to remember we live in this world and tend to hear about the needs of similar people in the industry. I would say 99% of those using the M1 likely are not using any type of plugins.
All of this may very well change once the pro level Apple Silicon Macs come out this year. More pros will buy into the iMac and 16" MBP that have more potential need for higher end plugins and applications. With that said its not going to be a mad rush for all of us to suddenly sell our 2017, 2018, 2019 and 2020 Intel Macs just to switch to M1X. It may still be some time before developers feel the pinch to bother supporting Apple Silicon. Thats pretty sad as its supposed to mostly be about republishing the apps to be universal. I don't developer desktop apps so I'm not entirely sure how that all works. I'm a iOS and Android developer but I use a hybrid platform to develop code for both.
filmguy123
Veteran
Unfortunately this can be said for all things Adobe these days. If only their quality scaled proportionately with their revenue... in the upward direction, that is!
stoneinapond
Veteran
This!!!
I have a ton of demo plug-ins that were not actively installed, and I have yet to find a method for easily removing them.