Good question!
I'm curious whether other people are also interesting in this, and which platforms (windows/sdlaudio/jack/pulseaudio/mac etc) get the most votes (milkytracker supports ~11 platforms).
There are some caveats here, since selecting input sources across different platforms is quite complex to code, and these days systems have multiple inputs (webcam mic, usb audio etc) so a ' default input'-approach is probably not going to cut it.
However, the
good news is that in the upcoming release there
will already be two ways to
sample into Milkytracker:
1. easy: by launching your favorite wave-editor from the sample-editor:Basically rightclick 'Scripts > editor/wavosaur` (on windows) or `Scripts > editor/audacity` (on linux).
You can also add your own favorite wave-editor by opening `config.scripts.txt` adding it there.
Not Ideal, but so far this is the most comfortable path, as external wave-editors also let you choose inputs, apply some pluginfx etc, before it gets imported into the sample-editor automatically.
Soon I will make a youtube tutorial about this, but it's a one-click integration (and ctrl+s in the wave-editor).
2. custom: by integrating your own sampler from the sample-editor:Here are example sampler-scripts:
https://gitlab.com/coderofsalvation/milkytracker-scripts The `sampler.*`-files demonstrate various way of sampling into milkytracker, the ones with `.ps1` are for windows.
For example, I'm using `sampler.pulseaudio` on my linuxmachine which is setup to record the soundcard output (therefore no routing or virtual audiointerfaces are needed)...anything can be sampled like that..youtube..musicplayer..softsynths etc.
> change color of envelope in instrument editor
To which color?
Right now it's indeed hardcoded.
What about linking it to the waveform-color of the sample-editor? (which shares the same backgroundcolor, so it will stay consistent with the colorpalette?)