Axoloti release 1.0.12

[jaffasplaffa]

Hey @johannes

Was just testing the osc/brds/cymbal. And the "strike" input doesnt seem to do anything. I looked in the code an it doesn't seem to be used.

Besides that everything is working great. Many interesting objects

Thanks!

[hellcore]

discard midi data sent to the usb host port when there is no usb-midi device connected

Great, now I don't choke my Axoloti when I forget to plug my Launchpad in.

[orbitbot]

Since the runtime has not been changed, would it be possible to not bump that version (or rename the file) in the releases unless it actually does? I decided to create a Homebrew package for Mac for the Axoloti, and TBH I feel that the current process is more confusing than beneficial.

Homebrew package will be updated over the weekend, unless someone beats me to it

[Mindsetup]

I changed the name so it has no spaces. I think it fixes the first error. But still get 'no sdcard' and red errors when trying to compile anything to live.

[Blindsmyth]

The reverb is quite a great addition, the release goes stable till now. Is it anyway possible to mute the dry signal and only get the wet reverb signal?

[jaffasplaffa]

Is it anyway possible to mute the dry signal and only get the wet reverb signal?

I think that is what the amount knob does.

[Blindsmyth]

Oh you're right I was under the impression that amount mixes in the wet signal but its a crossfade indeed!

EDIT:
Played a bit with it, when gain is at 0 and amount full on, no sound, but when you increase gain I have the feeling that dry signal comes through.

[jaffasplaffa]

Yeah not 100% sure about it myself now either

EDIT:
From looking at the code, the gain is added to the input. But not sure when in the signal chain the wet/dry signal is split up... But to me it sounds fine when amount is full.

[jaffasplaffa]

Hey @johannes

I noticed an issue with copy/pasting values on all the dials in 1.0.12:

Every time I try to push apple+C to copy the value, Axoloti just writes a “c” instead of copying the value. And therefor you cannot paste the value either. In general I see that I can write any letter into values on the dials.

[lis0r]

I think this needs "if (!ke.isShortcutDown())" adding after line 304 in DialComponent.java, but I don't have the time to test it right now.

Letter values can be entered into the dials so you can enter values in different units.

[lis0r]

Fixed by https://github.com/lis0r/axoloti/commit/ce41ba4ab8b389f4b1d8f696794e1497a40c0c75

I have an appointment now, I will try to make a pull request later.

[johannes]

@Mindsetup it looks Axoloti 1.0.12 is using the firmware of Axoloti 1.0.11, caused by the parallel installation of v1.0.11 and v1.0.12. Could you change the "Firmware Dir" in preferences to Applications/Axoloti 2.app/Contents/firmware, close Axoloti, and then launch it again? I believe this will also address the 'no SDCard' issue you've reported.

[Mindsetup]

I can't type address in that Firmware dir selection, Im only able to do Open.. and can't type address in that window.

Do I need to do that from terminal?

NEVERMIND, fixed it from axoloti.prefs with texteditor. Thanks for help! It fixed the "no sdcard"

[jaffasplaffa]

Letter values can be entered into the dials so you can enter values in different units.

That letters occur is new, it have never done that before. I dont think I need it cause there are really object where you need to write text into... Maybe later on we will have that.

Anyway, thanks for looking into it @lis0r

When should we expect it do be -reimplemented? Can I redownload 1.0.12 and it will work?

Thanks

[lis0r]

Hi Jaffasplaffa,

I don't think this has been documented, but was discussed in another thread, but it's not a case of writing text into a dial. It allows you to enter amount with units, so rather than having to enter a number between -64 and 64, you can enter the values that get shown to the left, e.g.

For an envelope attack, you can enter 3ms, rather than -60.15.
For an envelope decay, you can enter 1s, rather than 53.28.
For an LFO, you can enter 5hz, rather than -0.51.
For an oscillator, you can enter 2khz instead of 31.21, or C#5 instead of 9.00, or x2 instead of 12.00.

Hopefully this makes a little more sense, now?

[jaffasplaffa]

I know that you can write numbers into the dial. But it is new that you can write letters into the dial. You have not been able to do that before. You could write numbers, but not letters. There are no objects you would need to write letters into, so it is not really relevant to be able to do that.

I just tested it on 1.0.11.... On 1.0.11 you can only write numbers into the dial, not letters. They keyboard simply does not work with letters ONLY with numbers. Test it yourself!

1.0.12 you can write numbers letters anything into the dial. So something have been changed.

But anyway, I just wanted to point out that you cannot paste values from one dial to another anymore, cause apple+c only writes a "c" in the dial and does not paste the value. This is a bit of an annoying problem....

When should we expect it to be -reimplemented?

[lokki]

it is relevant, as lisa explained it will let you write in 45hz for example, great addition!! of course the c that you describe is a bug...

[lis0r]

Hi jaffasplaffa,

Yes, the copy shortcut should work, and doesn't. That's what my recent patch fixes, and it's been merged into the main repository, but it's up to johannes when it will be released as a precanned package.

As lokki says, the acceptance of letters is new, because it's part of a new, useful feature. "c" is accepted, because it is necessary for the entry of musical notes. You can only write meaningful letters into the dial, though it's up to you to enter them in a meaningful way. Try some of the examples I gave to see what it does - it's highly beneficial to almost every object.

Lisa

[jaffasplaffa]

Ah yeah, I see it might be handy for writing notes into the dial Good addition.

Thanks for putting the effort into it

[alexk]

huge update! congrats on new objects and fixes! Really enjoying the release!