TwoNotes GENOME!!!

[dronerstone]

No.
View attachment 17974

Thanks!!! Nice to know.

 

[DLC86]

The only way to oversample an AI based capture till now is to capture it at a higher sample rate, and that has recently been made possible on NAM.

 

[Enchilada Jones]

So for us old guys and gals who don’t understand the science…can you distill/translate all that down to ‘what settings should we use when loading NAM amps into Genome to get optimal results?’

 

[Senor Blues]

Learned a lot from this thread. While I probably will buy Genome , since I am a guitar plugin addict and I admit it, I prefer the sound and feel of --in order of my preference--NAM, Tonocracy and Tonex. Distantly followed by THU captures. Genome sounds great but I like playing the others better though cans, late at night. Edit oh, and AIDA-X is right up there as well, the freebie GitHub plug in plays the Genome captures nicely.

 

[littlemusicbox]

Max instrument input of Two Notes Opus is 2.8 dBu (12.8 dBu with Pad). So maybe this indicates how to set the proper instrument level for Genome? Will try later.

 

[AmyTwonotes]

Hey Amy !

Hope all is well ! Two very quick questions that are a bit more OPUS related but come from using Genome.

In Genome ... the Oversampling options are as per the pic below.

View attachment 17946

In the OPUS Hardware Pedal and its accompanying Genome Control Software

(a) => is the Oversampling Rate adjustable / selectable and saveable in the OPUS Hardware Pedal ? -or- is it preset to one of the above settings ?

(b) => is the Input Gain adjustable in the OPUS pedal (?) and if so over what db range ?

Many thanks,
Ben

Hi Ben,

And you! Please see below:

(a) => is the Oversampling Rate adjustable / selectable and saveable in the OPUS Hardware Pedal ? -or- is it preset to one of the above settings?

• No, there are no oversampling options in OPUS and it is a preset parameter

(b) => is the Input Gain adjustable in the OPUS pedal (?) and if so over what db range ?

• It is not adjustable but there is a 20dB pad and a three way selectable on the side of the unit.

Let me know if you have any further questions!

 

[Sedaxel]

Do We know the reference input gain of the plugin? I'd like to try it, but don't feel like guessing the value.

 

[dronerstone]

Do We know the reference input gain of the plugin? I'd like to try it, but don't feel like guessing the value.

I tried with my 2nd gen Scarlett, setting the input to "instrument" with Hi-Z "off" and level all the way down, then raising the input level in the plugin itself by +6dB sounds alright.

Not sure if there's any official measurements/numbers at this point.

 

[Sedaxel]

I tried with my 2nd gen Scarlett, setting the input to "instrument" with Hi-Z "off" and level all the way down, then raising the input level in the plugin itself by +6dB sounds alright.

Not sure if there's any official measurements/numbers at this point.

Thank you mate.

Anyway, I think that plugin developers (every single one) should specify that info as an elemental spec for correct use of their software. Nowadays I think it's more than proved that the reference input gain is absolutely relevant to avoid misuse of plugins... So We (users) should strongly ask manufacturers to provide the info.

 

[Sascha Franck]

Anyway, I think that plugin developers (every single one) should specify that info as an elemental spec for correct use of their software.

Just do it like in Guitar Rig. Press "learn", hit the loudest thing your guitar can do and call it a day. Helix Native ie fine too as you can just trim the input level so it's sitting around that white little mark on the input meter.

 

[Sascha Franck]

What's funny about that, @dronerstone?

 

[Orvillain]

Of course I'm not exactly happy. But that's entirely Apple's fault, as they're rendering a fully functional computer kinda worthless, at least regarding its main purpose, namely running macOS and doing other computational things.

If I didn't need an NVIDIA card for super speedy 3D work, I'd be using a Hackintosh. Alas.... I have to use Windows. Which is more or less fine, all my stuff is cross-platform anyway... but yeah... Apple don't make computers for people that actually need to use them in anger.

My M1 would do a lot of stuff. But it is nowhere near powerful enough to do anything like what I have to do on my main desktop in terms of the development work and machine learning and stuff like that, which I do. Even though I have no business talking about machine learning.

 

[dronerstone]

What's funny about that, @dronerstone?

It's just plainly wrong, imho.

I'm in bed, sick with the flu right now, so I don't really have the nerve to explain further - but setting input level automatically just seems wicked crazy, when this could very well be solved by actual physics/math.

Also, haven't you ever wondered why (almost) no one's talking about GuitarRig anymore?

 

[Sascha Franck]

If I didn't need an NVIDIA card for super speedy 3D work, I'd be using a Hackintosh.

Those got harder to build during the last years and might even vanish from earth once Apple scraps support for their last Intel machines (hence their latest run of Mac Pros).

 

[Sascha Franck]

It's just plainly wrong, imho.

No, it's almost perfect. Because it'd just set the level where it should be. Every bit the same as gathering the information from the company and doing it manually.
I mean, you don't want to do this on your interface's inputs, do you? Because that'd be plain wrong.

but setting input level automatically just seems wicked crazy,

No, it seems great. Seriously.

Also, haven't you ever wondered why (almost) no one's talking about GuitarRig anymore?

No. I know precisely why nobody is talking about it anymore. But it's got nothing to do with the input leveling feature.

Edit: And get well soon!

 

[MirrorProfiles]

Just do it like in Guitar Rig. Press "learn", hit the loudest thing your guitar can do and call it a day. Helix Native ie fine too as you can just trim the input level so it's sitting around that white little mark on the input meter.

Yeah, this is entirely the thing we're trying to move away from because it doesn't yield accurate responses from the amplifier. Do you want your Telecaster to hit your amp at the same volume as your Les Paul? The lower output pickups should hit the amp proportionally quieter for accuracy.

What is required, is knowing (for instance) what dBFS level a 1Vp sine wave is seen by the plugin as.

 

[dronerstone]

No, it's almost perfect. Because it'd just set the level where it should be. Every bit the same as gathering the information from the company and doing it manually.
I mean, you don't want to do this on your interface's inputs, do you? Because that'd be plain wrong.



No, it seems great. Seriously.



No. I know precisely why nobody is talking about it anymore. But it's got nothing to do with the input leveling feature.

Edit: And get well soon!

Thanks! Day 2, still crappy but a tad better than last night ("that's what she said").

And I agree about the interface/hardware inputs - that's why I back the gain all the way down, and would only ever raise input gain in the plugin.

Also, thanks for the heads-up, maybe I'm too stubborn and need to give this a chance! Cheers

 

[dronerstone]

Yeah, this is entirely the thing we're trying to move away from because it doesn't yield accurate responses from the amplifier. Do you want your Telecaster to hit your amp at the same volume as your Les Paul? The lower output pickups should hit the amp proportionally quieter for accuracy.

What is required, is knowing (for instance) what dBFS level a 1Vp sine wave is seen by the plugin as.

Maybe I'll try both and compare what sounds more natural. Of course, I'd never doubt the calculated/logical approach, but that doesn't mean auto-leveling won't get it right in this day and age.

BUT: Two of my guitars (DP104 and MMK45) put out a signal that's almost hot enough to send the Scarlett into clipping, even with the gain at zero.

 

[Sascha Franck]

Do you want your Telecaster to hit your amp at the same volume as your Les Paul?

No - but that is precisely what you'd be doing in case the plugin maker would deliver any number. Unless you'd do it with a testtone at a fixed level. Which you could do every bit as fine using Guitar Rig.

 

[Sascha Franck]

And fwiw, with Guitar Rig, you could just grab your hottest guitar, use the input level learn function on that one and call it a day. That way, all level differences between guitars would be kept intact and you'd never get too hot for the plugin.