acousmod@Zynewave wrote:
I believe the Acousmodules plugin are 32-bit only. In case you are using Podium x64, try the normal Podium 32-bit (x86) version to see if the plugins will load.
Yes, 32 bits only.
In other cases, I don’t see any reason that could prevent it to appear, assuming the dll file is in the VST plugin folder path you told to Podium.
acousmod@Zynewave wrote:
@H-man wrote:
@Zynewave wrote:
The screenshots you see in my first post in this topic is the full Podium 2.40, where I just have modified the default editor profiles to fit on the smaller screen.
So what’s it like? You said in a previous post that you were excited about the project (or was it the possibilities?). Does it feel workable even on the touch?
I have not fully implemented the multi-touch gestures yet. There are some gestures that needs to be tested in real life before I know if it feels intuitive.
I think the iPhone/iPod 3.5″ display is too small for serious arrangement work. It will be handy as a portable recorder, and as a quick way to make beats in the drum map editor. I would not find it enjoyable to work on a full arrangement. For that, you’ll need a tablet size device.
If you want somebody to test the multitouch features in Win7, I wil be pleased do it with my Dell XT2 Tablet…
acousmodYes, being able to choose the outputs order is an old FR 😉
You can use the MiniRoute 66 plug on the master :
http://acousmodules.free.fr/acousmodules_s_en.htm#outils
There are Presets for all the standard surround connections.
Cheers.
acousmodYes but… it is no more possible to click to change the play position and double-click to start playback ? 😯
We cannot have both like before ???
acousmodThanks !
acousmodversion 2.8
ASIO4All is set to 512 samples for every app.
Podium shows always a different value : 512 > 784, 1024 > 1296, 256 > 528.
It doesn’t change anything.
acousmodFurther investigations :
– Podium with ASIO4All driver : what I have described. Podium is the only app that shows this problem (also tested with Reaper, Soundforge, Acoustica, Wavosaur, Audition, Samplitude, Bidule, Audiomulch, Usine, with the same setup)
– Podium with MME driver : it’s OK, the fade is what it must be (what you describe)
– Podium with Rearoute ASIO sent to Reaper, which uses ASIO4All : same problem that what I have described PLUS a click each time a sound starts or ends with silence. If I record what Reaper receives and then play it back, it shows that the “sustained fades” and the clicks are recorded. If I render the same section In Podium and then play it in Reaper, it is clean (no sustain and no start/stop clicks). This proves that they are created by Podium when it plays back, with ASIO4All (sustain only) and RearouteASIO (sustain + clicks). Choosing 32 bits float or integer for the driver makes no difference.
Other apps linked to Reaper with Rearoute don’t show the problem.
So it seems definitely to have something to deal with how Podium plays with some ASIO drivers.
It sounds like if there is a “silence” dection that makes it send signal only if there is some samples.
Alas, I cannot use my RME because I have actually no more computer with a PCI card…
Can you try with ASIO4All and perhaps also with Rearoute ?
I will understand that you have other priorities, but it is a real problem for me, and I have not found any workaround.
acousmodHere is a test sound :
http://mediasonie.free.fr/temp/fadeout.wav
Description (I hope that you will understand me…) :
– in all audio softwares this sound disappear progressively, but in Podium something can be heard until the end
– if I do a fade out in Podium it doesn’t change anything
– if I draw a fade out with a volume envelope it doesn’t change anything
– the perceived sound volume (last second) is the same when the track volume is set to +12 or – 48, but the sound disappear when it is set to Off
It seems that Podium make it hear at a fix level when there is some samples that have not a 0 amplitude.
The tests are made of course without any plugin, in the same computer(s), same ASIO device(s) and same speakers (and same ears and brain too !).
Happily, it is not rendered, it happens only in playback. But it makes doing fades really difficult because in that cases I can’t believe what I hear.
Do you note the same thing ???
acousmodDesign : could the vertical bar at the right edge of the meters be set thinner ?
Future : do you think that you could (later) make meters showing all the available audio channels ? They could share the available space, and for more than 8, one pixel wide for each channel will be enough. If I remember well, it is how it is done in Nuendo.
acousmodAnd one question : how do we drag a plugin from one track to another one now ?
Same way as you’ve always done, unless you refer to the old expanded mode track header?
No, when I try to drag the name of the plugin from one track to another one like before the GUI opens (or closes), but it is not copied to the new track.
The same thing happens when I want to create a new track by dragging a plugin below the existing tracks. It doesn’t work anymore.
acousmodAnother little one : the track header of topmost tracks disappear when the arrangement has been scrolled to the bottom if the tracks are reduced.
They reappear when some change is made in the track zone.
Sliders look : perhaps it lacks some contrast ? Anyway, I prefer the dials 😉
And one question : how do we drag a plugin from one track to another one now ?
acousmodThe track volume and the event volume are limited to -48 dB (and I whish it could go lower !), but I suppose that it doesn’t apply to fades and envelopes.
acousmodIf you look at the fader design in other hosts, I believe it is rare to find examples where the value is written on the fader knob.
I agree with Slomo. It is what I found clever in your design : why waste some space when the same object can be used both for setting and showing the value ?
I suspect that the main reason for other hosts to separate the fader and the value is for looking like “real” gear ?
For me it was perfectly integrated in the GUI and even easier to read than your new design.
Another problem with the old fader style is that the visual design is not suited to be used for send faders
I don’t understand why.
acousmodThe meters can be configured as either horizontal or vertical meters. I’m now using the vertical mode as default. The horizontal meters left little room for the track name.
Very good point.
The BRXE buttons shown in the inspector group panel and the chain panels are now optional.
All I hope is that they will remain available. For me the availability of theses buttons in the track headers is essential.
I was never happy with the old track header pan/gain faders. They were a bit “heavy”, and seen from a distance the track headers would blur together. The new fader style I’m trying here stands out better, and they have the glass-look also used for the mixer faders.
Sorry, I prefer the old ones 😉
I don’t find the drop look convenient with the rest of the GUI style.
acousmod