ZynewaveI’ve updated the screenshot on page 1 again. The UI is more compact now, as I’m almost settled on the number of knobs/parameters. I’ve added a waveform selector for the three oscillators. The synth is now a true hybrid of subtractive and FM synthesis. If all the nine FM knobs in the center are set to zero, the synth behaves as a pure subtractive synth.
Hopefully only one more day of testing and I’ll have an alpha version ready.
Zynewave@francois wrote:
I made a little screen capture .avi format of the problem, can i post it here or i have to send you by email?
Just send it to me by email.
ZynewaveEven if your final verdict of Nucleum will be that it is better placed in the recycle bin, I do think that the time I’ve spent learning SynthMaker can be valuable for me in the future. I can use SM as a prototyping tool for the development of future zPlugins. It’s fast and relatively easy to construct algorithms in SM, and it offers various components that can be used to analyze the audio in realtime. If I some day start development of e.g. a zComp plugin, I would start out in SynthMaker and get the parameters and sound as I want it to be. When done, it would be a simple job to port the algorithm to a natively coded zPlugin.
Zynewave@Mike G wrote:
I was trying to use track templates accross all projects.
E.g. I want to setup/maintain a vocals template track with certain EQ and Reverb or other plug-ins etc, and use this in all my projects.
Is this possible?
Not currently. I’m planning to add support for saving track templates to file, similar to the way project templates are saved to file. Don’t know when I’ll find time to implement this.
Also another minor related point is that using track templates was only available on certain context menus, i.e. When you right-click an existing track, not from the tracks regsion menu or from right-clicking in the area below the tracks. Is there a reason for this?
The track templates are not yet available in the recently added compact mode track menus. It’s on my plan.
Zynewave@francois wrote:
Hi Frits , i have a strange behaviour of the sound editor , if i select a zone ,ok , then i want to select another zone , it does , but the background colour of the first one remain…
Regarding the audio files and folders , when i relink the file , it does not reappear in my arrangement i have to reimport them manually from the List panel.
Hi Francois,
I failed to reproduce the problems you described. When you say “select zone” do you mean a segment selection or a channel selection? Maybe if you can email me a screenshot of the problem I can better understand what you mean.
Zynewave@acousmod wrote:
Added a channel select button to the channel headers in the sound editor. This button replaces the previous behaviour where clicking anywhere on the channel header would toggle the channel. Shift+clicking the button will select the channel and deselect all other channels.
Nice.
Yes, it is visually nice…, but now I have to click precisely on the button instead of the whole space, so, alas, it is not as easy and fast to use as before during editing. 🙁
I suppose of course that it is too late to undo this inverted improvement ?
Perhaps can you keep the buttons but allow to click in the whole area like before ?
Would it be sufficient if I added a “Select Channel” command to the right click context menu? This will be available also when right-clicking the wave area.
Zynewave@thcilnnahoj wrote:
Here’s a minor bug (?) I found:
Looks like there’s something wrong with the area surrounding event’s names on record-enabled tracks. I guess it has to do with some luminance offset.
I checked the code, and I think this is how it has always behaved. I agree that it could be made to look nicer, but I will save that for a rainy day.
Zynewave@Mike G wrote:
For example if I bought a MAudio Oxygen rather than just a MAudio Keystation, would all the Play, stop buttons work with Podium?
And could you control track volumes from the sliders etc?
Podium supports MMC, so the play/stop buttons on generic MIDI controllers will most likely work with Podium. Controlling track gain/pan etc. requires a device that supports Mackie Control emulation.
ZynewaveZynewave@Pigini wrote:
I (and many others) regard that synthmakers stuff a thing for hobbyists, it can’t compete with properly programmed plugins, performance -or otherwise and charging for synthmaker-plugins is widely considered a lame thing to do.
It can backfire and harm your reputation.
Thanks for your input.
I am aware of this widespread public opinion about SynthEdit/SynthMaker made plugins. I think this opinion was formed early on with SynthEdit, long before SynthMaker came on the market. With SynthEdit it became possible for almost anyone to create plugins, and so a large number of lousy plugins became available as downloads. I think it was this flood of bad plugins that gave the “Made with SynthEdit” that bad reputation. The few good SynthEdit creations suffered from this. SynthMaker unfortunately inherited that legacy. It’s equally possible to create lousy plugins with SynthMaker, but with regards to editor graphics and audio quality, the tool can produce plugins that matches the best custom made plugins.
The one downside there is to Synthmaker made plugins, is that the CPU usage is a fair bit higher compared to a properly coded custom plugin. But for the simple synth plugins I have in mind, I think the CPU usage is acceptable. If I were to make the Nucleum plugin programmed from scratch, it would take me 6 months instead of the two weeks using SynthMaker.
As I mentioned earlier in this topic, the reason I’m doing this is to bundle the plugins with Podium so that total newbie users can start making sound without having to go download various freeware synth plugins.
I hope you will try the plugin once I have a beta version ready. If you still think it bears the mark of being a hobbyist work, I will consider scrapping the project completely.
Zynewave@rinxai wrote:
@jpleong wrote:
It doesn’t look “Zynewaveish” enough!
……. give it more Zynewave vibe?JPAgreed. It would be fortuitous to have the U.Interface as consistent as much as possible.
I will try. Since this is a different development tool than the one I use for Podium, it will require a bit of work to emulate the Podium UI style in Synthmaker projects.
Would the parameters for this synth be available for automation?
Yes.
ZynewaveThanks for the detailed reply. I’ll keep this in mind when I find time to work on the edit features in the editors. This function could also be useful in the arrangement editor, to set the length of sequence events so they are connected to the start of the next sequence event on the track. It would be misleading to call this Legato though. Maybe “Set size to connect events”.
Note that there is already a quick way to adjust the length of a selection of notes, to create the gaps you talk about. Select multiple note events and then press ctrl+plus or ctrl+minus to adjust the length of all events in steps of the editor quantize value.
ZynewaveI’ve updated the screenshot on page 1. I’m still having fun working on this 😀
Zynewave@Conquistador wrote:
Would Synthmaker also simplify the development of zplugs for you?
No, although Synthmaker is equally suited to create effect plugins. One problem with Synthmaker plugins is that the plugins take a relatively long time to initialize when loaded. Having maybe more than one hundred Synthmaker effect plugins in an arrangement could lock up Podium for a long time when enabling power.
Synthmaker is ideal for me to create synth plugins, since they often require a large editor window which would not fit as an embedded zPlugin editor in the Podium track inspector anyway.
ZynewaveWelcome grymmjack
Thanks for the comments. I’m sure you will encounter plenty of missing features eventually. We’ll talk about those when you find them 🙂
Frits
