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.

 

[MonoKultur]

Anyone else finding sad, the info-box for each DynIR is missing in Genome?
In Wall of Sound it was quite nice to have this info in cheat-sheet-alike for each DynIR and beeing able to re-read the specs of the each cab/DynIR in-app.
But maybe i just overlooked this feature beeing there in Genome... ?! @AmyTwonotes

 

[Ross Davies]

Anyone else finding sad, the info-box for each DynIR is missing in Genome?
In Wall of Sound it was quite nice to have this info in cheat-sheet-alike for each DynIR and beeing able to re-read the specs of the each cab/DynIR in-app.
But maybe i just overlooked this feature beeing there in Genome... ?! @AmyTwonotes

Hi Guys, Sorry we missed all of this! Amy is on Maternity Leave but dont hesitate to tag me in for future questions.

Regarding the logic issue, this was due to how logic regsiters MIDI capable plugins at the point where we released MIDI. In the new installers on our downloads page, there are now 2 AU variants (MIDI and No MIDI) which should stop any issues you have been having.

In terms of the DynIR info, this is most certainly coming so stay tuned for updates!

 

[Sascha Franck]

@Ross Davies, seriously I really think there needed to be at least *some* sort of capture management. Just as what software samplers allow for.

- Offer one (or more) user definable central location(s) where Genome would look for captures, including folders that would then show up in the internal capture browser as well.

- Allow us to directly drag captures into the Codex block (again just as what software samplers allow you to do with samples).

- Allow for internal capture management, such as moving and reorganizing captures. That way the mentioned dragged/dropped captures could as well be integrated into your folder organisation should you want to keep them.

- In case a capture is missing or not found (you might have moved things around on your computer), offer a search function (again, just as what software samplers are doing).

Genome's Codex block is the best capture playing thing on the entire market pretty much by far, so it's a pity file management doesn't see some love, really.

 

[yocky]

Genome's Codex block is the best capture playing thing on the entire market pretty much by far, so it's a pity file management doesn't see some love, really.

Completely agree with this.

Would it be possible to allow specifying input gain on a per preset basis, seeing as NAM captures require so many different levels? Unless I'm missing a better way to do this........

 

[PatF]

@Ross Davies
I used to really love the multiple parallel processing paths in Wall of Sound. I liked being able to eq and compress a reverb or back mic separately.

Please add a wet/dry control on the cabs. I have found that being able to blend in just a few % of dry past an IR to be very helpful.

 

[Ross Davies]

@Ross Davies, seriously I really think there needed to be at least *some* sort of capture management. Just as what software samplers allow for.

- Offer one (or more) user definable central location(s) where Genome would look for captures, including folders that would then show up in the internal capture browser as well.

- Allow us to directly drag captures into the Codex block (again just as what software samplers allow you to do with samples).

- Allow for internal capture management, such as moving and reorganizing captures. That way the mentioned dragged/dropped captures could as well be integrated into your folder organisation should you want to keep them.

- In case a capture is missing or not found (you might have moved things around on your computer), offer a search function (again, just as what software samplers are doing).

Genome's Codex block is the best capture playing thing on the entire market pretty much by far, so it's a pity file management doesn't see some love, really.

Thanks so much for reaching out and we hear you! In fact, you will be pleased to hear that we have a RIG/Preset/File management update of epic proportions in the works! This feedback is really useful to have and I will certainly feed this back to the team now - the good news is, the vast majority of this is on our agenda to address! :)

 

[Ross Davies]

Completely agree with this.

Would it be possible to allow specifying input gain on a per preset basis, seeing as NAM captures require so many different levels? Unless I'm missing a better way to do this........

Thanks for weighing in. There are a lot of contributing factors here to be fair including the gain staging of your guitar into your interface (which we have a handy article for below)

https://helpdesk.two-notes.com/portal/en/kb/articles/calibrating-genome-s-input-your-audio-interface

However on a capture-by-capture basis (due to irregularities in the capture process between those actively creating captures), you can try using the V-1 Pedal prior to CODEX and saving this as part of a RIG as a workaround. Regardless, I think your comment is 100% valid and I have fed this back to our team for consideration!

 

[Ross Davies]

@Ross Davies
I used to really love the multiple parallel processing paths in Wall of Sound. I liked being able to eq and compress a reverb or back mic separately.

Please add a wet/dry control on the cabs. I have found that being able to blend in just a few % of dry past an IR to be very helpful.

Noted and thanks for the suggestion. You will be pleased to hear that we are actively working on a huge update to our DynIR block in general and I feel a lot of your needs will be addressed there. Nonetheless - as per all feedback we get - I have noted this down and will feed this back to the team now!

 

[Sascha Franck]

In fact, you will be pleased to hear that we have a RIG/Preset/File management update of epic proportions in the works!

Glad to hear that. In case you need any (more or less experienced) folks to take that through its paces before release, feel free to ask (I've got some testing experience on my belt, so to say...).

the good news is, the vast majority of this is on our agenda to address! :)

Great.

 

[yocky]

Thanks for weighing in. There are a lot of contributing factors here to be fair including the gain staging of your guitar into your interface (which we have a handy article for below)

https://helpdesk.two-notes.com/portal/en/kb/articles/calibrating-genome-s-input-your-audio-interface

However on a capture-by-capture basis (due to irregularities in the capture process between those actively creating captures), you can try using the V-1 Pedal prior to CODEX and saving this as part of a RIG as a workaround. Regardless, I think your comment is 100% valid and I have fed this back to our team for consideration!

Cheers. The V-1 Pedal is a good workaround, ta.

I do know all about the article. I've got a Volt AI and before that was published I was goosing all Genome's amps by about 8 to 10db to get them to where they sounded right even with humbuckers. The Tanger, Foxy and Albion are ones that I think I've got a handle on what they should sound like. Bit surprised when I read that +2db was the right setting for my AI. I'm a classic rock plodder not a high gain guy at all but I have to dime the input gain or the amps to get much out of them. Any thoughts?


(and yeah, I know I'm free to use whatever sounds good)

 

[Ross Davies]

Glad to hear that. In case you need any (more or less experienced) folks to take that through its paces before release, feel free to ask (I've got some testing experience on my belt, so to say...).



Great.

Awesome! I may take you up on that! Can you drop me a DM with your email address please?

 

[Ross Davies]

Cheers. The V-1 Pedal is a good workaround, ta.

I do know all about the article. I've got a Volt AI and before that was published I was goosing all Genome's amps by about 8 to 10db to get them to where they sounded right even with humbuckers. The Tanger, Foxy and Albion are ones that I think I've got a handle on what they should sound like. Bit surprised when I read that +2db was the right setting for my AI. I'm a classic rock plodder not a high gain guy at all but I have to dime the input gain or the amps to get much out of them. Any thoughts?


(and yeah, I know I'm free to use whatever sounds good)

Thanks for getting back to me. It sounds like you are really pushing the amps which is absolutely fine but rather than dime'ing your input gain you could try the V-1 or the Saber Boost? I am also a bit of a classic rock player and I tend to use a little OD on the front end of an amp just to get it where I need it to be - might be worth giving a go on your side too! Let me know if this helps and if you need anything else, I am always here to assist!