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 - UltraBlack

Pages: 1 [2] 3 4
16
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 21, 2023, 06:33:26 PM »
oh yeah you are correct, it's  not as easy as I thought. I always trigger it by accident, and pretty reliably at that, but I can't reproduce it as easily as I thought. I'll tell you when I find out what setup you need

17
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 18, 2023, 03:12:16 PM »
I have another bug to report Xavier: If you lower the amount of voices an instrument can have to 0 (why is that a thing) while it's playing something, you can get the pfm3 to crash pretty reliably. I always do this by accident

18
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 17, 2023, 04:22:09 PM »
I think it would take too much ram to be done, unless some kind of sd card streaming, but i have no idea of the feasibility.

About the Fourier transform, you're talking about some kind of resynthesis which, i guess, would need lot of ram and cpu.

If you wish to investigate that way, i can suggest some work i done about sample mimiking with fm : https://github.com/pvig/preen-mutator
it's a puredata project which aim is to analyze an audio sample to get some metrics from it, and then generate random preenfm patch, to begin with,
then try to mutate it to make it converge to the audio sample.

Well, it does not work very well, it's not really better than the random patch feature of the preenfm ::)
The good thing with this approach is that it would not need more cpu usage on the preenfm.

I wasn't thinking to do that live. I had some sort of sample to patch converter in mind. Doing that at runtime would not work obviously. Kind of like your puredata patch, but just on the PFM3 itself (and utilizing the Fourier Transform to be more accurate. If maybe the bootloader had the ability to do that, you'd have pretty much all the resources available to convert samples).
Regarding that PD patch: I have zero clue how to use it. Maybe I should learn how to use puredata. It seems fascinating.

19
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 17, 2023, 01:55:03 PM »
I just thought of another Idea: What about a sample player? Most of the features are already there (effects, filters, an SD card, ...). They should theoretically be less performance heavy since no computation apart from playing the samples needs to be done.

Or would this have issues with the ram limitations? Could ram limitations be worked around with sort of a wave analyzer that takes the sample and converts it into something that the synth can use more easily? Maybe the Fourier Transform can be used to extract the waves to put them into the operators..

I have no idea how practical or realistic this is, but the PFM3 has quite a lot of things to it's disposal

20
preenfm2 and preenfm3 / Re: Fugue Machine
« on: June 11, 2023, 01:56:55 PM »
That seems really cool! I feel like with all of these very cool features we are gonna hit the hardware limitations pretty soon which will bring everything to a halt

I think the PFM3 needs some external ram chips for a future design.

21
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 11, 2023, 01:53:06 PM »
Oh these effects man.

If it's possible I'd like to have list explaining what all these abbreviations stand for and what's special about them. With some of them it's pretty clear, but what's the difference between e.g. LP1, LP2 and LP3? What is h+o (or however it's called) supposed to be? I have also no clue what an all-pass filter is... (I would assume it's a do-nothing filter)

22
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 11, 2023, 12:33:11 AM »
I think that's great! Awesome work on both fronts! The delay seems way better to me and the granular mode (specifically number 2) makes everything sound absolutely bonkers :) Please PR that!

And because I can't stop I have another feature request: A Phaser effect, e.g to add some texture and variation to percussive things. I've had a lot of with them on another synth

23
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 09, 2023, 08:10:12 PM »
This one parameter is not enough though, considering the very limited memory available for effects. The maximum amount of repetitions is super tiny right now, with the feedback limited to 1.

And one feedback value still does not allow me to control the time between repetitions, at least not in a way that benefits the overall outcome.

24
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 09, 2023, 11:26:22 AM »
@UltraBlack by more delay time, do you actually mean delay feedback? like the number of repeats?
and not the spacing in-between them (as is normally referred to as delay time).

I want to control this (shitty "drawing"):
<Segment width> ---- (Pause time) ---- <> ---- <> ---- <> ... (iterations and volume drop)

25
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 08, 2023, 10:57:04 PM »
Hm I can't get this to work entirely. As soon as I route a timbre into another one all of the routed timbre's output just vanishes...

Regarding the increased delay time: If it is what I think it is (a memory block with the audio data just continuously getting overwritten by a more silent copy) then you should be able to increase the delay time without any risks. I noticed, that if the delay block is shorter, it gets played back more often, so a pretty short delay "block" is pretty much not delaying enough times to be useful.
I would also prefer being able to control the time between delay playbacks and the volume drop myself, so I can actually use it properly.

26
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 06, 2023, 11:20:58 PM »
delaytime is limited by RAM. the delay is already downsampled to increase the delay time, so no it is unlikely that it can be prolonged much longer.
I'm not only talking about the length of the part that is being delayed but also about the amount of times that it's repeated and has it's volume lowered. Increasing the latter should definitely work together with the current hardware limitations.

27
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 06, 2023, 12:02:41 PM »
The 1.0 Fix works now haha thank you!

Quote
Yes that would be neat to have more noise choice
You could add more waveforms like in the LFOs. E.g. Brown, Pink, etc. noise

Could the time of the Ping-Pong and delay be increased as well? I feel like the have way too fast decay. Sometimes a really long delay is desirable.

28
preenfm2 and preenfm3 / Re: Two suggestions, two bugs and a question
« on: June 05, 2023, 12:40:45 PM »
sorry I completely missed your response. The second page just eats them sometimes...

Parameter lock is live recording of parameters into a sequencer. For example turning up and down an FX parameter gets recorded into the sequencer and the sequencer plays back that knob movement as if it was programmed in. It would allow for much more variation and possibilities.

If you are still not satisfied with this response, this is what google said: "Parameter locks" means that the step sequencer can record and play back the parameter values you input with knobs.

How can you use a BP, HP or LP filter for only one output or operator? You can only set them for everything, not for one thing specifically. You know that would be kinda neat too. Having the ability to set FX for only a select few operators, meaning you could modulate a carrier with a ping-pong delay or something, or in this case, only allow specific parts of noise into another waveform

Edit: I just noticed that this parameter lock thing would go hand-in-hand with more modulation destinations since it's basically that but plugged into a sequencer. Thinking about it, we already have something like that with the two sequencer modulators, but two is just not enough to control like four different changes at once

Edit 2: I sadly need to inform you that the crash is still occurring. I don't know what I tested, but what I tested was bullshit. It still crashes when playing a note after pasting anything into operator 1. Weirdly enough, the name of the binary is 999d but in the PFM it still sais 999b


29
yes that fix works perfectly!

I have some more suggestions too:
1. More stuff for modulation. I just wanted to modulate env levels, but that sadly does not work yet. Please add more destinations! (IMO any value should be tweakable. Even things like the engine. Just make it go crazy and open up all the possibilities. At this point you should probably consider adding a function to every screen's value that registers it with a knob and modulation destination to get rid of that list containing all the destinations)
2. Parameter locks: Could you add parameter locks? They should not eat up too much performance in the sequencer, as it's usually just like turning a knob.
3. Add a "disabled" midi channel to the mixer. I usually record my sequencer into the PFM sequencer after I'm done with a pattern, because my sequencer only has four tracks, not six, and I have another synth too. Then, I rebind another instrument to that channel and map the recorded instrument to an empty midi channel. Could you just add a way to disable midi input for a track? I feel like this should be a thing as to not interfere with existing sequences by accident.

Edit: Another idea: Possible Sidechaning via the volume threshold of another instrument as a modulation source.

Edit 2: The random waveform frequency option should in my opinion rather sweep a filter across the random frequencies instead of seemingly only changing the volume. It would make it a more versatile waveform and would make it a lot easier to use. If I use it in kicks, it has too noisy of a top end, if I use it in hats, it's too low. I want to create a more textured sound, that's why I care about the random waveform so much. You need it, but in my experience it's quite hard to use in percussion

Edit 3: (Deleted, came down to incorrect usage)

Edit 4: I feel like both FX slots should contain the same effects. I think it would be really nice to have two filters set up, or two ping-pong delays

30
"OP" ? Were you copying Osc or Env ?
What algo did you use ? Can you reproduce ? If yes could you share the preset ? Maybe save the default mixer and share "mix.dfl" file ?

Crashes both when pasting Env or Osc settings. Works even on the scuffed default "Sound" preset; First engine.
Again only triggers when playing a note after pasting. It only crashes when pasting anything into the first (1) operator's settings.

(Funny that pasting incompatible settings just sais "Cannot")

Pages: 1 [2] 3 4