TwoNotes GENOME!!!

[madmarcus1960]

That is what I am doing. By selecting import from where you are showing in Bank D I get the window I showed you. What do you see when you hit the import button? what choices/ location does it offer you?

EDIT to add:
I got it. apparently microsoft One drive was holding my files due to not syncing. New laptop, never asked for, or used, One Drive. It said I had used .05 percent of 5 Gig of my 'free' space yet it was 'full'

Shut off one drive, redownloaded the file and it let me use my own computer. 'Thanks for the generous offer Mr Gates...now piss off please you and microsoft!!!'

Anyway, Thank You Sascha for helping!

Good old MS makes OneDrive the default. You need to select "store my files locally on PC" with every update that reboots to "What's New" screen.
It's awful, intrusive and a scam to buy cloud storage. I rebuilt my PC with a 4TB main and 8TB secondary internal drives to avoid ever needing to use the cloud.

 

[Sascha Franck]

Now this sucks incredibly big time:

Thing is, if I remove the instance of Genome existing in my Logic project and reopen Genome, things will just work fine. Standalone is fine, too.
But that way I will not be able to reload the channel with its settings. In case I save it as a preset, the same thing will happen and Genome's plugin slot will be indexed with an exclamation sign.

As Genome is the only plugin to ever do this, I'd say it's not a Logic issue.

And fwiw, I tried rebooting, started Logic in Rosetta mode, reinstalled Genome, was running the Standalone. No change.

@AmyTwonotes, this needs to be adressed urgently as it results in actual data loss.

 

[Sascha Franck]

Yuck. Apparently it happens with each and every project I had been using Genome in. Fortunately not often, but that's some major suckage.

 

[jellodog]

Now this sucks incredibly big time:

View attachment 34644

Thing is, if I remove the instance of Genome existing in my Logic project and reopen Genome, things will just work fine. Standalone is fine, too.
But that way I will not be able to reload the channel with its settings. In case I save it as a preset, the same thing will happen and Genome's plugin slot will be indexed with an exclamation sign.

View attachment 34645

As Genome is the only plugin to ever do this, I'd say it's not a Logic issue.

And fwiw, I tried rebooting, started Logic in Rosetta mode, reinstalled Genome, was running the Standalone. No change.

@AmyTwonotes, this needs to be adressed urgently as it results in actual data loss.

Yep. This just happened to me. Had to remove and re-add the plugin in my Logic project, so lost the settings data that I was using.

Not a big deal for me because I'm just playing guitar for enjoyment and not recording projects; but this would be terrible for people that have fully realised songs with the Genome plugin.

Logic Pro 11.1
macOS 15.0.1
MacBook Air M1

 

[Sascha Franck]

Yep. This just happened to me.

Ah, great! No, of course it's not great at all, but it's very good to see it's not just a personal issue. Means that Two Notes really have to get back to their drawing board.

Logic Pro 11.1
macOS 15.0.1
MacBook Air M1

Logic Pro 11.1
macOS 15.2 (updated yesterday, 15.1 before)
MacBook Air M3

So, a pretty similar configuration.

I'm actually wondering how this could slip through their betatesting when there's already two folks in this thread running into the issue. At least on paper, their testers should've used and hammered Genome inside their DAWs a lot more than you and me did (I was really only using it in two test projects, I usually try to stick with Helix Native), so it's making me wonder how testing is done @ Two Notes, especially as this defenitely qualifies as a most serious showstopper bug. If anything, with DAWs you absolutely rely on total recall.

So, @AmyTwonotes, please foward the issue to your development team!

 

[jellodog]

@Sascha Franck I've never seen this happen with an AU plugin before TBH. It does seem to be very Genome-specific.

I wonder if the devs and QA team only tested with fresh plugin installs and new projects, rather than upgrades to existing installs and existing projects

 

[theimageofall]

I re-visited the plugin after being underwhelmed when I first tried it a while ago and was quite surprised by good how it was to play and sounded now. I’m not sure what they have updated since v1 but it is much better to my ears now.

I’ll continue testing!

 

[Sascha Franck]

I wonder if the devs and QA team only tested with fresh plugin installs and new projects, rather than upgrades to existing installs and existing projects

Well, it happened to me after I completely wiped the old install (using a tool called "Audio Plugin Uninstaller" by Wide Blue Sound, excellent stuff, also scanning for and cleaning related folders) and on a new project I really only created because I liked the Genome patch so much.

Really should be adressed ASAP (and yes, it's also the only plugin to ever exhibit this for me).

Too bad, because:

I re-visited the plugin after being underwhelmed when I first tried it a while ago and was quite surprised by good how it was to play and sounded now.

Yeah, there's some absolutely amazing sounds in it just using the (new) stock content. I absolutely love the combination of the new Calibro and the Ultra Drive. May post a snippet later on.