Mod Archive Forums Mod Archive Forums
Advanced search  


Please note: Your main account will not work here, you must create a forum account to post on the forums.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - leondustar

Pages: [1] 2
MilkyTracker Feature Requests / Re: Lua/Python script plugin support
« on: November 19, 2022, 11:04:26 »
Well, perhaps nitrofurano's silence on this topic, and your off-and-on focus (in openMPT) might indicate that it's a feature which certainly adds possibilities, but does not solve urgent actual problems end-users are having.
I think we're pretty much on the same page: a scripting-engine requires a lot of sparetime effort/maintenance for a subniche of endusers.
I had some off-and-on lua experiments with milkytracker too.
Implementing a midi-importer is one thing, implementing a script-engine which allows endusers to write importer-code is something exponentially bigger.

Having that said, I do like the idea.
If you ever feel like writing down a universal module scripting-api standard let me know.
I can imagine running the same pattern-scripts (`writeNote(..) getCurrentRow(..)` e.g.) or sample-scripts (setSampleValue(instr,sample,v) e.g.) in different trackers (by just implementing the same functions).

MilkyTracker Feature Requests / Re: Lua/Python script plugin support
« on: November 16, 2022, 16:45:55 »
please go on...what are you really saying to the original author here (your thoughts)?

Agreed, I've send you a reply (as private message).

Thank you very much. Haven't checked yet, but already thanks upfront for the support!

>  I saw an xbox game a year or so ago that used XM
Awesome, I can totally imagine.
I've recently created a small VR experience which also uses XM.
It's one of those few formats which is light enough on the CPU and still allows plenty of realtime features (muting channels, changing patterns) etc.

> it provides a very convenient way to sample VST's and make multisamples..
I do agree that the plugingrabber is definately amazing.

While I will keep contributing to milkytracker, I will start a sideproject called 'MilkytrackerX'.
This will be an opiniated (Xperimental) milkytracker with all the latest features & ideas, without having to worry about stepping on anyone's toes (People like trackers for different reasons).

> I'm very happy to have run into you here.

Likewise, I'm very to have run into YOU :)

Thank you very much for looking into all these things.
I hope you will make some progress with your custom stand, because I know a good physical environment really helps to stay motivated, and tricks the body into all kinds of good stuff.
Many years ago, when I convinced myself to ditch my herculean tracker muscle-memory in favor of 'plugins', I was also going down the KVR rabbithole..always looking complete some illusionary emptyness inside me :)
I've learned a lot, but I guess the biggest lesson is that eventually I didn't need all that anymore.

> Orangator (or something like it) as a part of Milky

Yes exactly this! Again, the synth and sampler approach. In that sense I think renoise went a bit too far by becoming a pluginhost..which immediately pushed out the 'zen' of a synth-and-sampler workflow.
On the midi-side I think renoise is great, as well as (a very interesting experiment, though I still prefer the sort simple non-floatingwindow grid-ui layout like ft2/milkytracker.).

MilkyTracker Feature Requests / Re: Hotkey Suggestions
« on: August 31, 2022, 15:47:33 »
bump: this became alt+/= and alt-/_

'syncing the beat for the .xm files' <-- what do you mean by this?

Interesting, can you explain this a bit further?
I've been searching online but didn't get any results for those Wxx & 8xx effects :/

MilkyTracker Feature Requests / Re: I know it's a big ask, but....
« on: August 31, 2022, 11:58:41 »
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:

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 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?)

Pages: [1] 2