Hi,
I don’t know if there is a connexion, but some of my plugins (SpatPod for example) give exactly the same problem since a few months on my P4HT.
They worked perfectly before (I can’t tell a date, perhaps with the 1.40 version ?) and have no problem on my laptop (Centrino) with the same versions of Podium.
If I limit Podium to one “processor” on the P4HT I can generally use the plugs.
I thought that it was due to something in my plugs, so I’ve searched but found nothing that explain why some are well working and some not.
The problem occurs of course only in Podium.
The message is often : “Cannot store preset data from plugin. The reported size of 0 Mb is beyond the limit allowed in Podium” (sometimes other values like 6 Mb or 8 Mb).
Another case, with exactly the same project and plugins, is that Podium crashes and quit when I active the engine, or a window opens and says that “A plugin has performed an illegal action. This may have caused memory corruption in Podium”. When I click on the debug button Podium simply quits.
It seems to support only two channels busses ?
This is a wdm driver isn’t it ?
As far as I understand it has no advantages for apps using ASIO drivers. Is this correct ?
As it is said, this new version of the driver now supports the WDM, and has also some improvements which are available in ASIO too…
Another feature to throw on the Future Development list I guess!
Perhaps… When all the rest will be done ! 😀
it is VERY unusual for a driver to change the order of the outputs
It is not a mistake and has been made because when the ADAT I/O is used at 96 kHz it has only four channels, so it it may seems more logical to have them “at the end”.
Of course, we need to change the routings for old projects 🙁
they should offer users–through the main driver or a peripheral mini-app–the option to configure the order of the outputs and present them to any sequencer as such.
Yes, I hope that they will do it.
Podium too…works the same way, with the studio setup actually built into the project.
Not really. As I remember, Logic was like Steinberg’s, we can choose what channel bus goes to what output.
In Podium we can only activate or deactivate an output, but while it is “muted” it is always present in the bus.
For example if you have a 8 channels outputs mapping and you unselect the outputs 3 and 4, you will silmply have no sound on channels 3 and 4, the channels 5 to 10 are not “shifted” like they are in EnergyXT.
You can neither change theit order like it was possible in Logic or some others (if I remember well…).
So we can’t say that the studio setup is built in the project, it’s only the selection of the active outputs.
Having to add a plugin to change the order is not a problem, this is what I do when I use 24 channels, but it takes also some CPU resources, but I think that having the possibility to change it inside Podium will be helpfull when we change the position of connected devices or if someone go to another studio with a different interface.
I think that the easiest way is to embed your keyboard plugin in SAVIHost and send the MIDI between it and Podium with MIDIYoke
http://www.hermannseib.com/english/savihost.htm
You can also use Bome’s Mouse Keyboard which is a standalone program, you will only need to select the MIDI Yoke output in its settings.
http://www.bome.com/midi/keyboard/
Of course, don’t forget to activate the MIDI Yoke input in the “MIDI/Audio Interfaces box” of Podium 😉
Other free convolution reverb plugins :
Convolver (DX) – http://convolver.sourceforge.net/
Convoby (VST), the free version – http://www.elevayta.com/
Convolver (VST) – http://www.teragon.org/products/Convolver/index.html
RevolverbLite (VST) – http://revolverb.hostrocket.com/ (simple but realtime)
There is also some which are not free but great for the price :
– Rayspace ( http://www.dhoskins.pwp.blueyonder.co.uk/software.html ) which don’t use impulse response files but synthesize them in real time
– Voxengo’s Pristine Space which can be compared with Altiverb (not the look !), but which is not sold with impulse responses ( http://www.voxengo.com/pspace/ )
Look at this thread on KVR : http://www.kvraudio.com/forum/viewtopic.php?t=107337&sid=c50e0601e664703428a0574486eb7bba
# Multiple event selections can be dragged in the curve editor, and copies can be dropped using the Ctrl key.
# Shift+clicking in the curve editor will start a marquee selection.
# Pressing Ctrl+Left/Right keys in the curve editor will move selected events.
# Holding the shift key while dragging events in the curve editor will lock the x or y position depending on the drag direction.
Wonderful !
Thanks !
oh… well… nice… 🙂
Hi,
I have recently spend some time with a friend to show him Podium, and I’m also trying to make a tutorial in French for my general site about multichannel sound.
Something that appears to me to be a possible solution for helping people with the inputs / outputs setup of mappings will be perhaps to name the function according to the position in the hierarchy, instead of having the standard source / target names.
The problem is that it will need different names according to the type of mapping : MIDI/Audio Interface, Mixer bus and Software plugin.
For example :
– MIDI/Audio Interface Output : From Tracks (To Audio Card) / …
– MIDI/Audio Interface Input : … / From Audio Card (To Track)
– Mixer Bus Send : From Current or Lower Track / …
– Mixer Bus Return : … / To Upper Track (or Level, or Lane ?)
– Software Plugin : From Current or Lower Track / To Upper Track
Perhaps also will it be possible to have the selections that have no sens greyed, like the Source in a MIDI/Audio Interface or a Bus Send mapping.
What do you think about ?
I suppose that most people use the pre-made mappings and have no need for custom mappings.
Does it will have some interest in other cases than multichannel mappings ???
Thanks !
It just got sidetracked by some more important stuff.
I know… 🙂
Hi Frits,
Currently parameter events can only be used with MIDI parameters
The automation chapter was written some time ago, and at that time I had hoped that I would have time to implement plugin and mixer parameter events before the next release. But I needed to release a new demo version before the old one expired in August. I hope to have it implemented for the next release 1.38.
not to stress you ! but this promised feature will really be very usefull… so, if you have, hem, some, hem, time………………..
Cheers
If you want the audio track to be visible, then the automation tracks for the parent effect plugin track have to be visible too. You can minimize the automation track to make it as small as possible.
Oh, no problem… it was just some questions that I was asking during trying the new hidding concept.
Personnaly I suppose that I will not use it, since I always prefer to see the hierarchy and the tracks…
The minimize function has been perfect for me since today 🙂
So you want this menu to turn on ‘hide track lane’ for all parent tracks, instead of having to hide the lanes manually for each parent track?
Yes 🙂 since I generally prefer to view my audio tracks and hide the effect one.
I have planned an update to the track inspector where the BSMR (which currently are shown in the info panel) and the E and two X buttons are shown as buttons on the page headers. They are thus always accessible for the current track.
It will be perfect for me.
Track lanes can only be hidden if they have child tracks.
You are right, it is no linked to the status of the track.
I will try to explain.
If I have a level 2 track (a plugin) which has a level 3 child track (audio track), and the plugin track has a volume automation child track (level 3), when I hide the effect track lane its automation track remains visible.
To be able to hide it I must put the audio track in level 4, which is not in my mind logical since it looks as if the audio track is a child track of the automation track.
I is certainly a not so interesting question and I don’t see how it could be done otherwise.
I’ve asked it because it is the first thing that I have tried to do, but may be a reflex due to old habits ???