Seems like data looper plug-in not working eg not respond to record or playback with
M2ventura vdmx 8.8.6. ?
Also
With wave clock
Do you advise not use at all in Ventura? On m1/m2
Or
Just use as self running clock bpm eg without using beat detection?
When I try to turn on auto beat detection I get warning about needing to open with Rosetta
But if I open vdmx with Rosetta all panels loose their interface visuals
Thanks ertle(paul)
Can you submit a bug report using the built-in bug reporter, via the help menu? Add a little description and send it it.
Wave clock is not Apple Silicon native, and itâs uncertain when it ever will be (developed by outside dev (plenty of posts on the forums about it)).
So Iâm not sure when it will run natively, but we would like Ventura to be able to run VDMX under Rosetta 2.
Will do today
Thanks
well Good News ! I guess⌠I started up VDMX this morning ready to send bug report- same project as yesterday but now Data Looper is reacting and responding perfectly AND even opening VDMX with Rosetta this time interface is all fine AND Waveclock beat detection also working Great! Hopefully it all stays that way⌠apologies and thanks!! PS. I have changed the Preference VUO to run as separate process- this seems to have helped enormously - occasional VUO FFGL sources freeze but VDMX keeps going-- Cheers. OF course can speak to soon-- screenshots show one of two wave clock interfaces partially disappeared⌠last image shows numbers in âclock 2â but none of the rest of the interface⌠not a big deal still usable just disconcerting :)
@Ertle Thanks. Maybe you could follow up in this thread a day or so now after youâve ran it a bit longer, and let us know.
Also, keep an eye on your memory. Apple Silicon macs do weird things when their memory is full and turns over to swap.
sure! thanks.
re Data Looper-- I think the problem was simply that I had the data looper set to a clock that was left on Auto Detect-turning this off the clock works at whatever tempo I manually set and data looper runs along with it⌠great!
FFGL VUO problems: intermittent but once gets âunhappyâ consistent major random crashes:
issues with ffgl vuo plugins? crashing -have sent bug reports -but projects too big to send-- doesnât seem. to be particular ffgl plugin almost random-- trying a fresh install of vdmx-- in case going back and forth between rosetta and non rosetta caused problems because it seemed good for a few days before this experimentâŚ
- the same ffgl vuo plugins seem to work without crashing in other vj programs BUT on the plus side the same VUO patches as Vuo files seem to work well directly in VDMX media bin-- only one crash after many hours of messing aroundâŚ
I havenât updated my OS yet. Does the latest VDMX update 8.8.0.8 fix issues with macOS Ventura, or are you still evaluating all of them?
A lot of older FFGL plugins have issues with Apple Silicone, and there are still users out there trying to run their older 32bit plugins on new Macs, which wonât work. Vuo is tricky, because it can run into similar issues with older compositions / code.
Itâs hard to pin point exact issues down, but if you can send vuo comps to the support email that run in Vuo or elsewhere, but not VDMX, at least we can compare the two and see why VDMX isnât handling them problerly.
Thanks
I donât think Apple has fixed all the issues with OSX Ventura yetâŚ
I wouldnât upgrade if you donât have to.
Yeah it is not good⌠FX are not working well.
Well, if you have 32-bit plugins, they wonât work on a 64-bit system.
Hi there,
I am new to VDMX so iâm unsure how to get past this issue. I have just updated my Macbook to IOS 13 Ventura before downloading VDMX and when trying to start the application iâm getting an error message saying it quit unexpectedly, all disk permissions are active and files and folders is active. as well as microphone access, yet still no start up. any help would be beneficial
thank you
Are you running the latest version?
https://discourse.vidvox.net/t/vdmx-beta-9-9-2-3-now-ready-for-testing-m1-intel-osx-10-15/2236/2