ZynewaveThanks for the suggestions Brian.
I’ve had similar ideas, although I have put those on ice since I started going the route of VST plugin support. It’s all logical suggestions, but it requires a lot of coding. There are dedicated applications for this purpose like SoundDiver and MidiQuest, that cost 2-3 times the price of Podium.
I’ve made a simple macro language for SysEx parameters. Doing something similar with SysEx presets, with all the pitfalls you mention, is a bit more complex. Maybe I’ll look at it sometime in the future if the Podium userbase that uses hardware synths grows considerably.
ZynewaveZynewaveI suppose that this does tie in with another idea I had for sysex. In a preset object, an option for “Sysex Transmit” under the “Program selection” radio buttons and a field for pasting and editing said message would allow for transmission of patch sysex into the temporary edit buffers of some synths – Basically a way of allowing “library” presets for hardware. (The actual creation of the sysex file or string would be left up to another program like MIDI-OX or something.)
If I understand you correctly, then this is already possible. Check out the ‘Collecting Hardware Device Library Presets’ section in the guide. If you have a bunch of .syx files with presets, then you can also import those directly, in which case Podium will create SysEx library presets for them. You have to import them under the proper device definition object though.
ZynewaveHi Brian,
It would be doable, but only for one-way communication. It would require a lot of coding and extended parameter properties to enable Podium to retrieve current settings from a hardware synth. That would give Podium the features of a dedicated synth editor application, and that is not a direction I want to go in the near future.
So would a hardware editor window in Podium have any use, if the parameters were always set to default on startup? If you recall a preset with the window open, the dial positions would not follow, etc. I can see some use of this, but I think it would also be confusing/frustrating for some users, that the functionality is only ‘half’ implemented, if you know what I mean.
Frits
ZynewaveThe one written on the contact page. I tried creating a preset, but the EST demo does not allow this. But send the project anyway, and if not too troublesome, include a short description of what to do in EST to recreate the bug.
ZynewaveHave you sent Podium into any of the big UK mags (SOS, Computer Music, Future Music) to see if they’ll review it?
Not yet. I still feel I need to fill out the blanks in the Podium guide before asking for reviews. The review in the Swedish Studio magazine was not my initiative. It’s been a long time since the guide was last updated, so I think I’m soon going to set aside a couple of weeks, to get it up to date with the last 20+ software updates 😳
Zynewavecould be a hardware error you think?
Don’t know. I have heard though that the Oxygen knobs are very sensitive, and can output controllers spontaneously.
ZynewaveI had a MIDI input map assigned to the track EST was on (a mapping for my midi keyboard). When I unselected the map, the ghost notes stopped!
Having the MIDI input map assigned to a plugin track, should only affect the plugin if there is any MIDI input received. I just tried with my keyboard, and I don’t get any random ghost notes (unless i play my keyboard 😉 ). What kind of keyboard controller are you using? If you try unplugging the MIDI cable from your keyboard, with the input map still assigned, does the ghost notes stop then?
ZynewaveI have tried EST again. I could not observe any ‘ghost hits’, but I only tried to make a simple pattern without knowing exactly what I was doing. I did observe that when looping in Podium is enabled, there is a double hit at the loop end point. Maybe you can email me a simple project file with the EST plugin on a track and a library preset with the EST patterns (assuming the EST demo will load this). I may be able to hear the ghost notes then.
ZynewaveHi Flipper,
once you set-up things and begin working on a composition is it possible to add further VSTI’s/audio tracks & FX or are you limited by your initial set-up?
You can change anything that you do during setup later on. If you want to import additional plugins, just open the wizard window and press the ‘import plugin…’ button to browse for the plugin files. You should only use the ‘scan & import all plugins’ button once though, or else all your plugins will be imported twice with duplicate mappings.
Frits
ZynewaveZynewaveZynewaveZynewaveWhat day are you releasing the 1.25 demo?
Probably friday.
We should try to get the QuickStart guide up on the Zynewave site by then, what do you think?
Just let me know when you want me to upload the files to zynewave.com. The tutorial don’t necessarily have to be complete I think. I intend to create a sticky topic in the support forum, with links to your tutorial and any other resources that users may contribute in the future.
Btw. would it not be best if you removed the ‘Copyright @ 2004 Zynewave. All rights reserved.’ text from the bottom of the tutorial pages? You can put your own name or nickname instead.
ZynewaveNo I had not because somehow I did not see the “new posts” icons! Will check it out Latest version I noticed was 1.20, heh.
😯 You’ve been working with that ancient 1.20 all this time? 😉
you should post something in the hosts-section on kvr to let everybody know. The major complaint has been the setting up phase…
Yeah, the recent changes to the project wizard is a response to the feedback on kvr. Podium 1.25 will be released this week, and a new press release is going up along with a new demo.