Waldorf Largo
- KVRAF
- 35276 posts since 14 Sep, 2002 from In teh net
-
- KVRAF
- 2006 posts since 16 Apr, 2004 from between my ears
no GUI improvements that i can see.
very disappointing, as they specifically indicated they were working on that.
very disappointing, as they specifically indicated they were working on that.
-
- KVRAF
- 3021 posts since 6 Nov, 2006
Is the AU showing as intel for apple silicon users or is it just me?
- KVRAF
- 2946 posts since 31 Jan, 2003 from Ghent, Belgium
Not that I care (Windows user), but wasn't this mentioned on the previous page?
- KVRAF
- 35276 posts since 14 Sep, 2002 from In teh net
According to the app 'Silicon' the AUs are native not Intel
- KVRian
- 614 posts since 24 Oct, 2006
Forgive me for asking: what DAW are you using?
“Madness, as you know, is like gravity: all it takes is a little push.”
-
- KVRAF
- 2583 posts since 26 Aug, 2002 from here
I am trying to Log into myWaldorf on the new snazzy website and am getting nowhere. Is anyone else getting it to work?
I believe every thread should devolve into character attacks and witch-burning. It really helps the discussion.
-
- KVRAF
- 3021 posts since 6 Nov, 2006
yes and according the app "Suspicious package" the file is apple silicon/intel meaning universal binary.. however when you actually run the AU in logic or Live and then launch activity monitor it says that its running as intel via the translator app thingy.
edit: inaGRM is having the same issue. Sknote had the same issue and was able to fix it. Quinto from Sknote said it was a stupid "naming convention" they had missed but it was a simple fix.
Last edited by dayjob on Thu Mar 30, 2023 7:20 pm, edited 1 time in total.
-
- KVRAF
- 3021 posts since 6 Nov, 2006
yes it was.. by me... and now i'm asking if anyone is having the same experience.
-
- KVRist
- 49 posts since 14 Mar, 2010
I can confirm that the AU is loading via the compatibility service while the VST2 and VST3 versions both load as native AS plugins.
- KVRian
- 614 posts since 24 Oct, 2006
Thanks! I was asking because I thought (erroneously) that I could help because I had (and still have, actually) a similar issue with Studio One 6.
“Madness, as you know, is like gravity: all it takes is a little push.”
-
- KVRAF
- 3021 posts since 6 Nov, 2006
if you have a moment and don't mind it'd be helpful if you could report this to waldorf so they can forward it on to their developer. once they realize it's more than just a couple people experiencing this it might get fixed a little quicker but.. i guess we are all aware of their pace for updates.DoktorTenma wrote: ↑Thu Mar 30, 2023 7:42 pm I can confirm that the AU is loading via the compatibility service while the VST2 and VST3 versions both load as native AS plugins.
here's a link to their support request form.. which annoyingly asks for serial number and purchase date which is information they already have saved in the "my waldorf" section where purchases are archived etc.
https://waldorfmusic.com/support-request/
-
- KVRist
- 49 posts since 14 Mar, 2010
I have and just got a reply stating that they have got similar feedback from another customer and have forwarded the information to the developer. And they'll get back to me when there's news about this issue.
I used their support e-mail mentioned at the top of the my Waldorf account page to contact them.