thcilnnahoj's Forum Page

Hi,

I’m not sure I get what went wrong from your description, but I can say that it’s most likely not a bug. You just have to find the invisible track that’s still left over somewhere in your arrangement. 😉
First, deactivate all track tags that you may have enabled, so you really get to see all tracks. Secondly, expand all your group tracks and look through them.

If you still can’t find the problem, please post a screenshot of your arrangement, or upload the .pod project file somewhere (without audio files).

It’s also best if you delete the “master bounce” wave file from the master track and render a new one after you’ve found the culprit. This will make sure that the new bounce will be the same length as the arrangement.

@Infinitoar wrote:

Now I know I’m not a “licensee” so really “what I get is what I get” but how am I sure that the final product won’t have the same problems such as this IF I decide to buy it? More or less on that “note” what I’m saying is: If the freeware version is just a “nerfed” feature version of the full version, yet they are both overall the “same”, how am I reassured this problem will not exist if I become a “licensee” in the paid version?

The free version is indeed exactly the same as the full one, bar the limitations mentioned in the original Podium free thread. Any bugfixes that appear in, e.g., Podium 2.40 will be in Podium Free 2.40. The only difference is that the free version is not released simultaneously with the full version update, but a few months later. You know, there has to be some incentive to “upgrade”! 😉

Hey… it’s been a while, but I managed to play with Podium today. I have a weird bug to report:

When opening the inspector via shortcut keys, the scrollbars to the right of the editors disappear during the panel sliding animation, causing the UI to shift. It only happens with panel animations enabled.

1. Are you sure that the note sequence (in the arrangement editor – not the MIDI editor) is the right length? The problem is most likely that your MIDI sequence indeed has notes inside bar 2 and beyond, but they are not played back because the sequence is cut off in the arrangement editor.

Probably like this (notice the beat markings above the timeline):

In this case, you simply need to extend the sequence by grabbing its bottom-right edge. Be careful the first time, though, as there are two handles at each edge, and the top one is used for time-stretching! 😉 The bottom one is for resizing.

2. There are two types of sequences in Podium – phantom sequences (these are linked, meaning if you change something in one of them, if affects them all), and unique sequences. Assuming you already have 12 phantom sequences (each one bar long), you can right-click the last one, select ‘convert to unique copy’ and edit this sequence without changing any others.
Phantom sequences can be easily recognized by the + icon next to the sequence name.

Hope this helps!

It apears that Podium tries to insert a plug-in on each track when importing a MIDI file (as it says in the Guide). However, if there are no plug-ins in the project, it goes wrong, and there’s indeed no master track created either. 😕

Looks like a bug for Frits to fix!

For now, try to import at least one VST instrument before importing MIDI files, and please report back.

@outsiderinvention wrote:

this is a work around, but i can’t imagine sitting around for 40 minutes everyday real-time rendering test mixes.

Yep, no argument there. To be honest, I don’t know why it hasn’t been looked at for this long, as it actually is a quite serious bug if you think about it for a minute… I just didn’t bring it up a lot since I first reported it because I always use real-time bouncing ever since that was restored to working order.

As for turning on higher quality for plug-ins during rendering… This is just my opinion, but I would disable such an option, as I don’t want the final render to sound different than what I’ve been mixing and listening to for the last n hours. 😉

Let’s just wait for Frits to tell if Podium does anything differently during offline and real-time bouncing.

Well, the only way to make sure everything gets written to a sound file the same way you hear it in this case is using real-time bounce recording, meaning you need to real-time bounce record individual tracks that have plug-ins causing dropouts because of latency before rendering a master bounce.
If it’s impossible to record the whole mix in real-time because of CPU use, you could still put all your tracks in a “dummy” group (just before the master), which you then offline bounce. This way you can run the mix through those problematic effects on the master track in real-time… in a sort of 2-pass bounce. 😕

In my findings I’ve had dropouts only at the start of individual sequences, never anywhere else. Since the “pre-master” bounce would be one long sound sequence, this should work until the bug finally gets fixed…

I’m curious if you’ve experienced it in other places, like right in the middle of a bounce of a single sound sequence… :-k

In the meantime, can’t you do a real-time bounce of the master track, or just the problematic tracks before rendering the master? At least that’s how I work around it (though I prefer to use real-time bouncing in most cases anyway).

That being said, I kinda already do this: 😳

@LiquidProj3ct wrote:

…and I’ll make the songs in another host. 😉

Yes, that’s correct. If Podium doesn’t detect your audio interface bit depth setting (it doesn’t with mine either), you can change it in the preferences (engine tab – new sound bit resolution).