TwoNotes GENOME!!!

[Ross Davies]

Great.
Would be interesting seeing no other company seems to think about it. It would be a great addition or maybe in the future on a capture X

Thanks so much for the suggestion. I have indeed fed it back to the team! Interestingly, we have done some reamping solutions in the past with the OG Reload - this had a unique Match feature which helped address the problem of level adjustment when re-amplifying - essentially, If the level is too high your amplifier will tend to over-saturate, if the level is too weak the tone will lack dynamics and liveliness; by comparing the signal as it comes from the guitar (plugged to the DI input) with the signal that has been recorded (and which is sent to the REPLAY™ Line Input) you can be sure that the signal you send from the DAW is exactly what your guitar itself would be sending.

 

[FrankD77]

Thanks so much for the suggestion. I have indeed fed it back to the team! Interestingly, we have done some reamping solutions in the past with the OG Reload - this had a unique Match feature which helped address the problem of level adjustment when re-amplifying - essentially, If the level is too high your amplifier will tend to over-saturate, if the level is too weak the tone will lack dynamics and liveliness; by comparing the signal as it comes from the guitar (plugged to the DI input) with the signal that has been recorded (and which is sent to the REPLAY™ Line Input) you can be sure that the signal you send from the DAW is exactly what your guitar itself would be sending.

That's the main thing from what I got the levels
When one can model whole amps and cabs i thought why not ask

 

[Ross Davies]

That's the main thing from what I got the levels
When one can model whole amps and cabs i thought why not ask

A valid question indeed for sure! With that said, we have a tonne in the pipeline for GENOME this year; I am certain you wont be disappointed with what we have planned.

 

[FrankD77]

A valid question indeed for sure! With that said, we have a tonne in the pipeline for GENOME this year; I am certain you wont be disappointed with what we have planned.

Can't wait

 

[BenIfin]

A valid question indeed for sure! With that said, we have a tonne in the pipeline for GENOME this year I am certain you wont be disappointed with what we have planned.

Hey Ross .. well as of today we are %29 of the way through the year ... so I'm assuming there are going to be a bucket-load of huge releases coming thick and fast and very soon (?)

 

[FrankD77]

If you don't mind
Now that i use the cab with the slate a bit more i run into a limitation of the capture X or I'm missing something.

I would love to connect my cab but be able to switch it off and on. Now i run a second cable from the engl to the se100 and cab. But before i could not easily use my cab. Unless i would attach and detach the cable every time.

 

[Ross Davies]

Hey Ross .. well as of today we are %29 of the way through the year ... so I'm assuming there are going to be a bucket-load of huge releases coming thick and fast and very soon (?)

Well, I cant let you know exactly what we have planned, but it's massive! I cant wait to hear what our GENOME users think of what we have in store!

 

[Ross Davies]

If you don't mind
Now that i use the cab with the slate a bit more i run into a limitation of the capture X or I'm missing something.

I would love to connect my cab but be able to switch it off and on. Now i run a second cable from the engl to the se100 and cab. But before i could not easily use my cab. Unless i would attach and detach the cable every time.

Thanks for getting back to me. Captor X doesn't actually feature a function to disengage the connected cab or not unfortunately - is that what you were referring to?

 

[Richard_G]

@Ross Davies, given Two Notes’ experience with both hardware products and software like Genome, I think it would be doing itself a disservice if it didn’t release a hardware Genome pedal/modeler/NAM capture player.

 

[FrankD77]

Thanks for getting back to me. Captor X doesn't actually feature a function to disengage the connected cab or not unfortunately - is that what you were referring to?

Indeed being able to shut off that part instead of pulling the cable. I can imagine people have the capture in a rack and it's easier to remotely disable the cab or engage.

You don't want the fysical cab active all the time.

 

[Ross Davies]

Indeed being able to shut off that part instead of pulling the cable. I can imagine people have the capture in a rack and it's easier to remotely disable the cab or engage.

You don't want the fysical cab active all the time.

Noted and understood, thanks for confirming. Regardless, I have sent this to our team now for consideration in future designs; rest assured, we have a tonne in the pipeline so stay tuned! :)

 

[Ross Davies]

@Ross Davies, given Two Notes’ experience with both hardware products and software like Genome, I think it would be doing itself a disservice if it didn’t release a hardware Genome pedal/modeler/NAM capture player.

Thanks for getting back to me. In truth, it is something we have discussed quite a lot internally but feedback is always great! If you or anyone has any specific feature requests for this hypothetical Hardware Device, let me know and I will certainly feed it back to our team! :)

 

[Ipkz]

Hi @Ross Davies,

I’ve been testing Aether’s Hold function in Genome as a sustain/drone tool for practice and ambient playing, similar to Helix Native’s Poly Sustain.

The issue I have with Keep Wet Feed is that it keeps feeding new input into the held reverb tail, so after a while everything turns into mush. That makes it hard to use as a stable drone to play over.

Cut Wet Feed gets much closer to the desired behavior because it stops new input from feeding the held tail. The problem is that if Hold is already active with Cut Wet Feed enabled, new notes won’t enter at all unless there was already sound fed before engaging Hold. This makes it difficult to use as a live/study tool.

Also, Hold Behavior does not seem to be automatable. Would it be possible to make Hold Behavior automatable or MIDI controllable in a future update? Even better, would it be possible to add a dedicated freeze/drone Hold mode where you capture a note or chord once and then automatically stop further input from feeding into it, similar to Helix Native Poly Sustain?

Thanks!

---

Update: I got close to what I wanted by setting both the mix and hold switch parameters to an expression pedal and setting the mix range between 0 and 50%.

 

[Ross Davies]

Hi @Ross Davies,

I’ve been testing Aether’s Hold function in Genome as a sustain/drone tool for practice and ambient playing, similar to Helix Native’s Poly Sustain.

The issue I have with Keep Wet Feed is that it keeps feeding new input into the held reverb tail, so after a while everything turns into mush. That makes it hard to use as a stable drone to play over.

Cut Wet Feed gets much closer to the desired behavior because it stops new input from feeding the held tail. The problem is that if Hold is already active with Cut Wet Feed enabled, new notes won’t enter at all unless there was already sound fed before engaging Hold. This makes it difficult to use as a live/study tool.

Also, Hold Behavior does not seem to be automatable. Would it be possible to make Hold Behavior automatable or MIDI controllable in a future update? Even better, would it be possible to add a dedicated freeze/drone Hold mode where you capture a note or chord once and then automatically stop further input from feeding into it, similar to Helix Native Poly Sustain?

Thanks!

---

Update: I got close to what I wanted by setting both the mix and hold switch parameters to an expression pedal and setting the mix range between 0 and 50%.

Hey @Ipkz ,

Thanks for getting in touch and a super interesting use case for sure! I have fed back your request to the team now for consideration in future updates. If you have any other requests, let me know! :)

 

[Ipkz]

Another issue I noticed:

If you have two parallel signal paths, each ending with a delay or with one delay after merge, and you switch between them (either by muting one path or using volume pedals at the start of each chain), the existing wet delay tails get reprocessed by the newly active amp tone.

For example, if I play through a dirty amp path and let the delay trail continue, then switch to a clean amp path without sending any new input into the delay, the remaining delay repeats take on the clean amp’s tone instead of preserving the original dirty tone.

The delay tails should remain independent and keep the tone of the path where they were originally generated, rather than being re-colored after switching.

 

[Ross Davies]

Another issue I noticed:

If you have two parallel signal paths, each ending with a delay or with one delay after merge, and you switch between them (either by muting one path or using volume pedals at the start of each chain), the existing wet delay tails get reprocessed by the newly active amp tone.

For example, if I play through a dirty amp path and let the delay trail continue, then switch to a clean amp path without sending any new input into the delay, the remaining delay repeats take on the clean amp’s tone instead of preserving the original dirty tone.

The delay tails should remain independent and keep the tone of the path where they were originally generated, rather than being re-colored after switching.

Thanks for letting me know - I have sent this over to our dev team now!