Hi David, what’s the feedback on the M1 mini?
Can anyone compare the performance of VDMX+Shaders on Apple M1 Silicon to Intel+AMD gear? For example, is it faster than a 2015 15" MacBook Pro+AMD GPU, but slower than a 2019 16"?
1 Like
I don’t have both computers to compare, but I’m currently in a laptop limbo myself. I need an Macbook Pro upgrade, but I don’t want an Intel based mac if Apple is switching everything over to their chips. I also don’t want an M1 processor, but if the rumors are true about the M1X or M2, then I’m excited.
I also think it is safe to say that if Vidvox continues to develop for Mac only, that future versions of VDMX will most likely follow the path of these newer processors. I think it’s safe to say the same thing about other Mac applications as well. Adobe, Davinci Resolve, Madmapper. If apple goes all in with their silicone processors, I think it will be more likely that older Intel Macs will be forced to emulate newer applications. Right now, it’s the other way around until all of the software devs play catch up with the latest Mac swoop of changes.
All that being said, I’m hoping a M1X Macbook Pro drops later this summer. I’m usually against buying the “1st” of anything Apple, but my 2015 MBP is starting to show its age.
1 Like
In exactly the same boat as @ProjectileObjects - have a max specced 2015 MBP and holding out for a M1X for the same reasons.
2 Likes
This is a real quandary, I have a full spec 15-inch, 2017 MBP which I would expect to last 7-8 years. But with Apple Silicon emerging like @ProjectileObjects I feel in limbo. Even tho my machine is capable (except for the sloppy Thunderbolt 3 / USB-C ports)… to use an EV term I’m suffering “range anxiety”.
1 Like
I’ve been having a ton of issues with kernel task slowing down my 2020 MacBook Pro with a Radeon pro 555. It’s been super frustrating and the fans seem to kick up whenever I do anything that touches the graphics card. I think it’s just bad heat management on that generation. I need to do more work reinstalling, etc… but that’s such a drag.
I have an M1 Mac mini with 16gb ram that I’ve been playing with and out of frustration with my kernel task issues a gave my VDMX project a whirl on it and I was really surprised. Everything runs super smoothly, it’s a simple project but it didn’t even bat an eye at what it was asked to handle and I’m sure I can push it more.
I think with a small monitor and Bluetooth mouse and keyboard, this would make a great live performance system. I’ll be exploring the limitations and how far I can push it. I’m sure that some thing will make it choke. I’d totally recommend it for replacing a laptop. For that matter the 13” M1 MacBook Pro should offer similar performance.
Just wanted to contribute to this thread and share some results.
M
1 Like
I’d say from looking into the M1’s a little bit more, that stick with the 16GB to avoid some possible headaches:
And:
https://barefeats.com/m1-versus-16in-macbook-pro.html
“The 16-inch MacBook Pro is faster than the M1 MacBook Pro in seven out of nine tests.”
Hi All,
so I’ve been testing extensively VDMX on my new MBPro 13’’ M1 16GB RAM (OS: Big Sur 11.4), in 2 live events on 4k and FullHD projector output, as well as NDI, and a home-stress test on 4k monitor. I’ve noticed SEVERAL ISSUES AND BUGS - here’s my report:
1-Running smooth with HAP and ISFs even at high resolutions (4k) and with 4k output with 3 layers (VDMX render options at default);
2-SUPERBUGGY interface when getting stressed over 80% CPU usage (NO response on most of the sliders and commands, missing menu items on several plugins, while video runs anyways smooth and MIDI response on my AKAI controller runs without issues … very strange).
3-Sound Analysis NOT working at all with internal mic (while stressed over 80%).
4-NDI has always the same issue as 2 years back (sorry I’ve never reported this before): even if I’m running NDI INTERNALLY - sending from VDMX and receiving from other app as Madmapper - when running at full load (pixel intensity / details / CPU stress) - the output comes at crashed resolution of 1/4th approx. I’ve noticed this annoying problem in VDMX even on very performing machines, while Syphoning through Madmapper and sending NDI from there solves completely this issue.
5-No chance of having more than 1 x video-out as MBpro M1 comes locked with 1 output only. I’m buying now a Sonnet TB3 to DualHDMI and will try if that works, but I doubt it…
Overall performance I think is pretty good, I guess these problems come with the new updates of the OS and probabily need to be fixed on a VDMX update (correct?)
Fede (Deltaprocess.it)
Hi Delta,
Which version are you running?
Thanks,
-Cornelius
HI Cornelius,
Version is
b0.8.7.2.4,
Please let us know ASAP if there’s any fix to my and my partners email fays.fernandes@gmail.com as tomorrow she has a show with this mac and would be amazing if she could play wothout these issues
Thanks a lot
New feedback on M1 :
- SONNET DUAL HDMI not compatible
- TB3 / display port (apple) adapter, doesn’t work for video output thus:
- MATROX TripleHead2Go SE not compatible
- 4K output limited to 30Hz
For VJING, this laptop its a complete disaster, unless u go with a single out
F
You’ll have to email support@vidvox.net for license activation resets. As for b0.8.7.2.4, try b0.8.7.2.9 and see if anything changes. b8.7.2.7 has been out for sometime now.
I thought M1 macs were hardware limited to one external display?
Here’s what apple says:
While the M1 MacBooks natively support just one monitor, the M1 Mac Mini does natively support up to two external monitors - one via the HDMI port and a second via USB-C. But the latest models of the MacBook Air and MacBook Pro support only one external display.
Ah cool, thanks! Will try that. I thought VDMX was asking automatically to update to new versions: 2.4 is still the only one that can be downloaded from the website. I did send bug report + wrote to support 3rd of September but no answer yet
1 Like
Yes, I saw your email to support in which you linked to your forum post, so we are replying to your forum post.
Ok, so tried with this last version of VDMX and the problem remains the same: video runs smooth but interface is extremely laggy - I can move most of the controls, meaning they work on the video output, but I can’t see them moving on the interface. It appears happening only after few minutes of the patch running (expecially once CPU/GPU is stressed). Basically once I set a patch, I can use it but can’t change or see anything of what I’m doing. Sound Analysis still doesn’t work. Clips luckily can be changed. Please let us know if there’s any extra information I can send to help finding a solution. Thanks a lot! :)
1 Like
Please send a bug report when using the latest version. We want to make sure it’s similar to another issue we are aware of and working on as we speak. Thanks
Just sent one! hope it helps, thanks!
Hi Cornelius, have u by chance managed to understand the cause of this issue? Is that something u guys are planning to solve anytime soon? Just trying to understand whether to organize our work with different machines (non M1) for our next shows beginning of October.
Thanks a lot