PodianerWhat is that picture in the arrangement window?
It’s from http://www.alexrossart.com/ where you can get several nice wallpapers.. 🙂
PodianerYou’re right, but this is not the shortest way to get multiple tracks.
PodianerThanks. I’ll try that the next time the error message appears..
PodianerFine!!! Thanks for that!! 🙂
PodianerI don’t understand. Do you mean the message does not appear, if you exit Podium and restart?
Right! Sometimes I need to start Podium for several times, until the message doesn’t appear again. Perhaps this is not a Podium related problem, but my Soundcard’s fault, because yesterday I also got a similar message in Tracktion 2.
Do you use 48000 in your arrangements?
Yes.
PodianerI was initially very surprised that Podium did not have this feature when I first started looking at Podium over a year ago.
Me, too!!! 🙂
Podianer@ Dandruff
🙂 You’re right! Nobody is wrong! But in this specific poll, nearly every other feature is requested more.. that’s why I thought I need to mention it.. 😉
PodianerI voted for “engine related”, because imho the feature of offline bouncing is the most powerful. I wonder why nobody else seems to think this way. Freezing tracks takes much too long in real time, and when it comes to the final mix, I tend to master directly in the host and not in a certain wave editor.. thus every mixdown needs to be done in realtime. So Podium lacks a feature that nearly every other host has. I still do not dare to mix my band’s album with Podium, what’s really making me sad.. I like Podium, but I need that feature (together with MultiFX per Channel 😉 )
Perhaps our next album will be recorded with Podium 2.5 or so.. Time will show.. 🙂
Just my thoughts…
PodianerOops, forgot:
In the sustain parameter properties you also need to set the value range from 0 to 127.
Realized it by now… 😆
Thanks for the help.. It works perfectly well!!
PodianerPossible… but it has definetely somthing to do with the punch out marker, because I can recreate this bug the way I mentioned before.. I’ll see when you release 1.37..
PodianerThanks!! Hope you’ll find a solution… 🙄
PodianerI tried to find a reason for the spike.. I use Glaceverb, too. But my spikes occur even when there is no “action”… It’s very hard to work with these spikes. When I try to record a longer track, there is always one drop out in it, which makes the track worth to be deleted.. 😥
Today I recorded a song with a friend of mine, and I had to change to Cubase, because he was not that patient that I was. If I even knew what’s the reason for that. Frits? Any further ideas?? It’s definitely nothing to do with “The Grand” or “Sampletank”, because I temporarily deactivated them.
Higher latency didn’t solve the problem either.. This problem doesn’t exist with Cubase or other hosts.. I’m clueless!! ❗
EDIT: I know that this won’t be possible for the next few months, but offline bouncing would hinder these spikes to become part of my “bounced tracks”.. That would be very nice.. 😀
PodianerI was in the sequence editor.. I held ctrl+alt leftmousebutton and then I moved the mouse in order to zoom out.. The zoom-out was very fast and then the program crashed.. I could manage to make Podium crash twice, but the other times everything went fine..
PodianerI use the M-Audio Delta1010LT with a latency of 256 samples. I’ll increase the samples… My project just crashed a few minutes ago.. I did’nt save… 😥 No I have to record it once again.. perhaps the spikes are gone with the new sample value.
PodianerDoes the spikes occur only when you play notes on your keyboard, or can they occur when you do nothing and the plugins are silent?
The spikes occur even when I do nothing … I’ll bypass the VSTi and wait a few minutes to see if the spike is gone..