Moselle Modular Synthesizer: Softsynth with a Thoughtfully Constructed Patching Language
ฝัง
- เผยแพร่เมื่อ 11 ก.ค. 2024
- Moselle Modular Synthesizer: www.moselle-synth.com
Support this channel via a special purpose donation to the Georgia Tech Foundation (GTF210000920), earmarked for my work: • Support This Channel v...
0:00 -- Introduction
2:03 -- Demo patches
3:27 -- Tutorial patches
6:20 -- Resources
7:21 -- Workarounds
Hello Dr. Lanterman! Again many thanks for the comments and copious feedback. Some of the problems you've reported here may be fixed in my latest version while I'll make available for the usual free download this weekend.
4:20 Dr. Lanterman, General1-4 are MIDI's official nicknames for controller number 16-19. General5-8 are controller number 80-83. Controller number 1 is ModWheel, number 2 is BreathCtrl, and so on, hence the ease of confusion. I'm editing the tutorial to make that clearer.
As you mentioned in the end: a Mac version and indeed an AU plugin would be wonderfull ! Nice project !!
Couldn’t even make it a week without my mind being blown by this gem of a channel again. This program looks incredible and I get wait to install it and start getting into the tutorials. Thank you for making these and bringing us this info!
Thanks for the pointing to this Synth. Just the things I'd like to play with. At the moment I'm busy with my NTS-3, but Moselle comes next. BTW: My Audio system is Scope by S|C (based on Pulsar) 30 years old (nearly).
Thanks, Prof. Aaron 👍
You are welcome!
Thanks a lot :) this is really sweet!
Thank you for the intro to the synth! Too bad that it is not an open source.
8:33 correct: MIDI device availability is only checked at startup... one of literally 1000s of TODOs. I've got so many exciting things to do with performance, user interface, and more audio capability, that I'm not polishing things like this. (Or doing a DAW, or a Mac version, etc. etc.) Thanks for bearing with me.
Small fonts: I'm awestruck that this even runs on the emulator. Early Win10 had a similar small window/big font issue but I think it doesn't after SP1. Win11 seems fine.
Strange sounds: Excellent trouble-shooting! What you show is what we'd expect if you edited the INI file from 44.1 to 48 but the file wasn't written to disk, then Moselle restarted and read the old contents, only then the save took effect? So is there a few seconds' delay in your emulation before the PC side sees a file edit? And the subsequent restart did read the 48000 ini? I don't want to ask you to try to reproduce this as I don't think I will be able to fix the problem regardless. That said, kudos for finding that file to edit.
You know what is quality : )
I have a RME digi96/8 in my G4 quicksilver power mac.
Cool, software mangled waves and controls.
RME is amazing. Fireface 800 is twenty years old, and RME is still keeping the drivers for it up to date! I'm using a Mac M1 with the latest OS and the Fireface is rock solid.
@@Lantertronics They have zero cpu load drivers. check their website who is using RME around the world, pretty stunning list even in places you wouldn't expect.
It's publicly traded company. i often argued with friend to get RME and i was a RME fanboy.
1:26 this is a place where reaktor core does a bit better, with grouped signals, named variables that take the place of wires, and some stuff for replacing wireless grouped signals within a node group. but it does still have the limitation that you can't use code to define a system that can scale to whatever, code reuse in reaktor is basically non-existent.
1:49 honestly i think reaktor would fare about as well here. a full programming language would do better as you could have this done generically and defined with far fewer lines of code
It's been a while since I looked at Reaktor (the patch shown there is one of mine), and I didn't have time to get too deeply into its features. I should give it another look, especially if it has features that would help clean up that patch (it's my mockup of the Buchla 400 architecture).
also i think the strength of reaktor core is in part that you can figure out how stuff works and modify it however you want. once i was waveshaping a saw to create other waveforms, and the blep on the default saw osc was causing a discontinuity, so i opened up the default saw osc and pulled it out of the signal flow, problem solved. the only things you can't look inside of are the first submenu of stuff, math ops, basic memory actions, etc
i still always prefer the flowcharts more. they are easyier to follow than a bunch of symbols. one example where i think this is useful is in mortiz klien's resonant lowpass tutorial. i find it disengenuous to call the first stage in his vid- a lowpass. i see it better as a highpass+ sum of op amp output. yes it has lowpass topology but it is being used backwards as a mixer+hpf.. ive done a few experiments to back up my findings. i think it was a linguistic barrerier of sorts. it looks like a lowpass at first glance but caps block 0 hz dc. while passing 99999 hz better.
02:16 Lol! Not sure if your response to the Tom Sawyer sound was deliberately understated ...it's either that or you really aren't a Rush fan! 🤘😎
th-cam.com/video/OECgtx-LcOs/w-d-xo.html
Heh! Check out the intro to my lecture on State Variable Filters:
th-cam.com/video/jAokGV71MEw/w-d-xo.html
@@LantertronicsLol! 🙈 I should have known! ...I wouldn't mind, but I had watched that video before! 😂👏👏👏