ZynewaveJust tried the Imposcar 1.00 demo, and it didn’t crash. I could not find any info on the gmedia site about version updates. Maybe there is something in the non-demo or later versions that is causing troubles. Could you try to uninstall 1.16 and install 1.15 to see if that fixes it? If it does, then it must be the VST sync extensions that I made in 1.16 that is causing the crash.
Other suggestions would be;
1/ Create a new empty project in Podium and try importing Imposcar, to see if it could be other plugins that is causing the conflict.
2/ Try importing Imposcar into another host, to see if perhaps it is the Imposcar installation that has become corrupted.
Frits
ZynewaveThe error could be because you’re trying to import the Direct-X version of the plugins. When I ran the Diamond bundle demo installer, it created a Waves folder under ‘Program Files’ (containing the individual Direct-X plugin dlls) and a ‘Waveshell’ folder in my Vstplugins folder. You should import a file named something like ‘Waveshell-VST 5.0.dll’, which then will show a popup menu of all the Waves plugins in the bundle. Select one, and that selection will be remembered by Podium.
ZynewavePodium v1.16 is released, which should fix the problem with AnarchyRhythm.
ZynewaveZynewave1. Was wondering if you are considering, some time in the future, of developing the audio loops aspect of Podium?
I am going to improve this area at some point. There are a few different approaches to this; Implementing time-stretching and implementing beat-slicing. Beat-slicing will only be useful for percussive loops, so I guess the first step would be to implement some sort of time-stretching. Currently I feel there is a couple of months worth of work on other stuff, before I will begin experimenting with this.
in fact I’m not even sure how to bring them into the sequencer page.
Open an object list window (Ctrl+L). Drag sound objects from the left-pane list or wav files from the right-pane list, onto the tracks.
2. Any thoughts of adding a Music Notation Editor, in addition to the piano roll editor?
It will be a huge task to implement this. I don’t intend Podium to become a full-blown professional score-editor, but maybe at some point in the distant future I will add a simple notation editor.
ZynewaveI’ll keep you in mind when I get a quiet moment 😉
1: MIDI plugin support, either by supporting MFX or supporting the use of VST plugins with MIDI only. (specifically MFX).
Any particular plugins you are dying to use?
4: User setable latency adjustments on tracks.
Just curious; In what situations would you want to manually adjust a track latency?
ZynewaveHi,
I don’t know if there are any Podium users with this card. Can’t help you with this, sorry.
Frits
ZynewaveZynewaveTechnical explanation of the 64 bit floating point mixing:
If your music production mainly concentrates on using softsynths and encoding the final master to MP3 files, then don’t bother with 64 bit mixing as you won’t be able to hear any improvements in audio quality.
If however you are producing music recorded in pristine studio conditions and aimed for reproduction on high end audio equipment, 64 bit mixing will offer better precision and larger dynamic range.
The 64 bit mixing will only be utilized when the mixer engine is processing and routing audio internally. The VST plugin specification currently only supports 32 bit floating point audio, so the mixer engine will convert the audio down to 32 bit floats when routing audio through VST plugins.
When describing floating point numbers, the 32 and 64 bits refers to the amount of memory that is required to store the floats. The bits are split into two parts that stores the precision and the exponent for the ‘floating point’. 32 bit floats offers 25 bit precision and 64 bit floats offers 54 bit precision.
The advantage of 64 bit mixing is evident when an audio signal is gain scaled or when two or more audio signals are ‘summed’ in the mixer engine.
Gain scaling occurs when the track gain or pan settings are affecting the audio signal. The scaling involves multiplying the floating point audio signal with a floating point scale value. These multiplications will result in values that uses more precision bits than the original audio signal, causing the least significant bits of the result to be discarded.
To illustrate the effect of summing, let’s assume that you have two 25 bit precision audio sources that you want to mix together. These sources could be wave files or the 32 bit floating point output of VST plugins. If you mix these sources together without changing the gain of the tracks, the output will fit within 32 bit floats, provided that the summed output does not clip. If you change the gain of one of the tracks, then the 25 bit precision of that track is displaced up or down in relation to the other track. A gain change of 6 dB will result in approximately one bit displacement. When summing the two tracks the combined precision interval has thus been extended beyond the 25 bits that can be stored in 32 bit floats, so the least significant bits are truncated and you loose some of the precision in the audio sources.
This is where 64 bit mixing will offer an advantage over 32 bit mixing, as it can use 54 bit precision to store the results of gain scaling and summing, and thereby reduce the artifacts of the floating point truncations.
So what’s the point of the higher precision if the master output is being bounced to a 24 bit or 16 bit wave file? For every audio track that you add to a mix, you add noise as a result of the truncation of the lower bits of the signal. The accumulation of these rounding errors can result in a sligthly degraded output that can be present even when rendering to 16 bit wave files.
Despite these apparent mathematical benefits, 64 bit mixing will only yield a minimal quality improvement. 32 bit mixing is still fully sufficient for professional grade productions.
An example of how to test the difference between 32 bit and 64 bit mixing:
ZynewaveI have not tried the Vaz Mod plugin, but maybe I can help.
Since you are trying to create parameter objects manually, I assume that importing the Vaz did not automatically create a bunch of VST parameters? Maybe it’s because the Vaz does not support this, and relies on MIDI control.
Importing the plugin should at least have created the Pitch bend, modulation and channel pressure MIDI parameters (unless the plugin claims it is not a synth). If you have linked CC#70 inside Vaz, you should create a corresponding MIDI parameter in Podium. Don’t select the ‘plugin parameter’ type in the parameters dialog, but rather ‘control change’ and then enter the control change number. Look at the ‘Modulation’ parameter for clues.
ZynewaveA good way to start is to examine the new bussing example project. It includes a number of simple arrangements with various bus configurations.
ZynewaveSince the arrangements are very accesible via the object list (listview) I was wondering if it would not be possible (I know it is) to add a play function in the list view for every arrangement (comparable to the auditioning of audio files). that way you can switch live from one arrangement to another.
This will be done at some point. Also perhaps add small monitor/play/stop buttons to the arrangement cards in the browser window.
A playlist of marker regions with hyperjumps between arrangements will likely not happen. Playing an arrangement will require that monitoring is activated which could cause a pause of several seconds, depending on amount of insert plugins that should be loaded, and loading presets in plugins and external devices.
A playlist using markers within a single arrangement can be done. As I see it, this feature would be a surrogate for pattern based composition. Currently I don’t consider this an important feature though.
ZynewaveYes it is possible. I got it working with the free ‘Side Chain Compressor’ from Slim Slow Slider:
http://www.ismusic.ne.jp/slim_slow_slider/vst/#sidech
When you import the stereo version of this plugin, Podium will create two input mappings and one output mapping. The first input mapping is the regular input and the second mapping the side chain input. The plugin thus is configured as a global plugin and not an insert plugin, since it needs to be assigned to several tracks. Because the plugin is configured with separate input and output mappings, it is in itself set up as a bus, so on the tracks you assign the input mappings you use the send dial to control the input.
There is a mono version of the SideChainCompressor plugin, which will be imported as a single stereo in/out insert mapping. That’s because Podium cannot determine that it is actually two mono inputs. You need to split the stereo input mapping yourself after import.
ZynewaveI’ll just copy/paste that into the future development list, shall I? 😉
Nice list. They may not all be implemented for the next couple of updates, but I’ll make sure to consider them all eventually.
Frits
ZynewaveYes, Podium does support VstTimeInfo. This includes the use of samplePos.
I just tried the AnarchyRhythms demo, and there seems to be something in its startup procedure that assumes Podium is not supporting this. A dialog pops up within the plugin saying that the host does not support sync. If I subsequently go in and reenable the ‘Host Sync’ check box in the plugin, all seems to be well. I’ll take a note of this and try to debug this for the next next release. My head is currently buried in floating point wave files and 64 bit floating point mixing 🙂