Zynewave@suges wrote:
You mention that Podium offers you to choice of using library presets or plugin-suppled factory presets (I really have to learn how to use quoting on phpbb). 99% of the time I only use factory presets. Are you saying there’s a quick way for Podium to recall those settings when you come back to the arrangement later? Because that’s what I mean, Podium is not retaining the basic settings like which patch I selected for my Minimoog plugin. I don’t care about the positions of the every little parameter and knob, I just want it to remember the patch I was on.
If you select/assign the factory program preset on the track with your plugin (using the preset panel), Podium will remember it. If you change the preset from within the plugin editor, Podium will not detect the change.
Some plugins implement their own internal factory preset system, which is not made available to hosts as VST programs. That may be the case with the Minimoog. For those plugins you need to use library presets to grab a copy of the internal preset.
ZynewaveHi Jeff,
There are already some key shortcuts to zoom tools. Press and hold the following keys, and click and drag at the point you want your zoom to be anchored:
Control+shift to zoom vertically
Control+alt to zoom horizontally
Control+shift+alt to zoom both x/y
Shift+alt to slide zoomed area.
Zynewave@papawillow wrote:
Just a minor request… when moving notes around is it possible to switch off (or option) the preview sound (of midi notes) when Play button is active?… Its just that it interferes with the pattern sound as it is playing. Nice to have when you need it.
Added to the list.
ZynewaveI could implement a command in the arrangement editor that would check that all tracks with plugins were assigned library presets. It would then create and assign library presets to the tracks that either has no presets assigned, or are just assigned program change presets.
I mean, the plugin already HAS its own presets, why do I have to make a second set?
Compared to how other sequencers handle plugin state storage, Podium does not store extra copies in the project file, quite the contrary. Podium offers you the choice if you want to store the plugin settings (using library presets), or if you just want to select plugin supplied factory presets.
In other hosts, when you add a plugin either to a synth-rack or insert it on a track, a copy of the state of the plugin is implicitly stored in the hosts project file. In Podium I decided to separate the storage of this state data into preset objects. Some advantages to this approach are:
It allows you to create easily accessible libraries of presets within Podium without the need to store them in fxp/fxb files.
When using global plugins in several arrangements, you can assign different library banks to the plugin in each arrangement.
If you have created a preset in a plugin that you want to use on several tracks with other instances of the plugin, you just assign that library preset to the other tracks. In other hosts you would need to copy the settings from one plugin instance to the others, every time you make changes to the preset.
ZynewaveFor the time being, the way to do it is to assign library presets to the tracks. An option to save the states of all plugins does not mix well with the preset objects used by Podium. Insert plugins only exists when monitoring is enabled for an arrangement. Even a global plugin instance may have different states/presets in different arrangements if library presets are used.
Frits… I have noticed a bug with this actually… whilst the data is saved, the name of the original preset that the ‘sync’ed one is based on gets forgotton. If you use say 3 instances of a plug, each with a library preset based on a different preset; then save all changes, quit and reload – all the library presets for that plug in the project now have the same name.. (I think they all go to either the first library preset name, or the name of the first preset in the plug, not worked out which it is yet..)
I tried this with the Vanguard demo and could not get it to fail. Need more info. What plugins are you using? Maybe you could email me a project file with the setup that fails.
ZynewaveZynewaveYes it can be done. MIDI file import is not fully implemented yet. Importing .mid files will create an arrangement, but the device mappings created by the import are currently not working. You need to assign the device mapping for your synth to the track containing the sysex messages. If you encounter problems, you could email me the .mid file or your project file, and I can verify the MIDI file is imported ok.
ZynewaveI don’t think disabling load or save of projects is a good idea. It would mean that the demo users would need to go through the studio setup process every time they start Podium.
ZynewaveI don’t find kagemusha’s posts confusing, but they occasionally deal with pretty complex stuff :). Kagemusha is a long-time beta tester so he has tried some of the more hardcore stuff in Podium.
I still think you need to implement a way that you can move a volume (or any parameter) without it has effect on the curve (modifier key)
Agreed. It’s on the list.
If you want to avoid ‘leaving’ a curve breakpoint when you drag a slider, use the right mouse button (while still holding left button down) to abort the drag action. This will reset the slider to the position before you started dragging, and undo the curve change.
I just verified that I can record both curve and parameter events with my AN1x. There doesn’t appear to be anything broken that once worked. However the parameter events so far only work with MIDI parameters. The floating point parameters such as mixer level and pan and VST parameters does not currently include a dial. I’ll get around to implement that at some point.
ZynewaveHi Dustin,
I fully understand your request. I had intended to keep the demo updated on each version. However, a crack of the 1.00 demo appeared the day after I released 1.00, and yesterday 9 out of every 10 visitors to the site came as referrals from warez sites. I suspect a lot of the ‘ghosts’ you mention are just waiting for a new crack of the latest version.
I will update the demo soon, but I’d like my paying customers to be a step ahead of the warez users. I’m thinking about how to cripple new demo versions so that a demo-crack will not be as complete as the full version. What kind of crippling would be acceptable to you?
ZynewaveYou need to set a minimum and maximum value before it is enabled. If min and max are the same there will be no effect of using a curve sequence for the parameter. Parameter objects with 0 in both min and max are typically used for ‘mode’ parameters that will cause an effect just by being received by the device.
ZynewaveA perfect four-bar part. I copy it (into the clipboard). I want to quickly make 31 copies of it (say it’s drums), each copy appended to the tail end of the one before. Is there a quick way to do this?
I’ve added a ‘Create phantom copies’ menu to the future list. Currently you can only do it manually with the mouse. To avoid doing the clone drag 31 times, you could start by doing 3 of them, select the 4 events and clone drag them to get 8, 12, 16, select the 16 and … you get the picture.
Also, just curious, what is the ETA of the finished documentation (filling in the “To DO” sections)?
Judging from the feedback on this forum, there have been plenty of requests for feature implementation and no requests for the guide so far. So I chose to dedicate my time to coding. I was hoping people would point out specific areas in the guide that they wanted clarified, so that I could make occasional additions to the guide. Any particular page you had in mind?
Frits
ZynewaveA plug-in is able to bring down a host like that?
Yes. To optimize latency and CPU usage, the plugin code is called directly from the audio processing thread in Podium. The plugin thus acts as an extension to the host code, and has access to the same memory and system resources as the host. Podium wraps all calls to the plugin in protective code that will catch basic illegal operations, but it is still possible for the plugin to corrupt the host memory without the host knowing about it.
Calling plugin code directly from the audio thread is the way it is done in all major sequencers to the best of my knowledge. Access to a plugin could theoretically be encapsulated in separate processes, which then would make the host secure, but this would be at the cost of added latency and extra CPU usage.
Edit: You’re fast Duncan 😉 I started this before I saw your response.
ZynewaveWhen I move that volume slider in the mixer -of the group track- audio drops as long as I hold my mousebutton or moving the slider.
This happens because the parameter track is muted when dragging the slider, to avoid that recorded automation overrides the fader movements. The sideeffect is that any audio routing through the parameter track also gets muted. I’ll have to implement another way to bypass recorded automation when dragging the slider. Thanks for pointing this out.
When I want to set the volume of a track group or for any track to a certain percentage it is written in the parameter file as curves/peaks for that moment. but it would be useful if you could also set a global volume >> if you move the volume that it makes that percentage for the whole timeline.
I am not entirely sure I understand what you mean. Could you describe it differently?
I remember using the parameter events a “long” time ago (instead of curve) but I can not find them anymore
You drag parameter objects onto tracks to create parameter events. It may be that the level and pan mixer parameters are not active currently. I will check up on this when I start work on the curve editor improvements.
ZynewaveYes, it seems SIR 1.0.0.5 does not like to be automated. I could not make it crash with the dry parameter only, but once I had tried automating attack level (not recommended 😯 ), a little later a dialog saying ‘SIR GUI: invalid pointer error’ popped up inside SIR, and the plugin editor went dead. The SIR audio processing were still okay, but closing the editor and reopening it again made Podium vanish up in thin air.
Not much I can do about it unfortunately. SIR is a fine plugin otherwise.
Frits