ZynewaveI’ve fixed a bug that probably is the cause for your problem. When merging curve sequences, the resulting curve sequence was not set to use the time resolution of the arrangement. Meaning that when you work with samplerate time resolution arrangements, the merged curve sequence was stored using the default musical time resolution, causing a stretch of the curve.
ZynewaveNot before the 2.0 release.
ZynewaveHow I can verified that the dual core cpu is actived ?
In Podium, make sure the “enable plugin multiprocessing” preferences option is enabled. To check that your PC actually uses both cores, you could bring up the Windows Task Manager (ctrl+alt+del on XP). There should be a graph for each core. When running Podium, the CPU load should be evenly distributed on all the cores.
Zynewave@Igr0 wrote:
I think it’s better, if automation tracks(both) never had the edges.So, when you create the automation track, you will see endless clip by default.In this case you will never do any mistake with crossfading(by accident) automation parts.
I’m considering adding a new “auto-size event to arrangement length” track option. This was mainly intended for bounce tracks, but it can equally be applied to parameter tracks. You would then only have one curve sequence on the parameter track, and it will automatically be resized whenever the arrangement length changes.
ZynewaveHaving ONE window that is maximized across two monitors, is not standard Windows maximize behaviour. It will require special coding to remove window borders from a non-maximized window stretched across two monitors.
ZynewaveOne thing to possibly consider is the fact that when I look at the new arrangement, I can’t tell that the Drums track (purple) goes through zMaster unless the track (or child) is selected. On the old arrangement, I can glance to see it goes through something.
I’m thinking about adding a miniature group panel to the track headers. This will show the mappings that are on the hidden tracks in the chain. Thus the zMaster plugin will appear on the master track header.
ZynewaveSince I first designed the track inspector years ago as a panel inside the tracks region, the inspector has grown in size with the addition of embedded plugin editors and the group panel. I’m considering moving the inspector out of the tracks region and instead embed it as a panel at the left edge of the browser window, similar to the “List” panel at the right edge. Imagine there is an “Inspector” tab at the top left corner, just before the project tab. This has the advantage that the inspector can be the full height of the window, and showing the mixer will not reduce the height.
What do you think?
Zynewave@estwing wrote:
Is the buffer size the same as the latency set on the sound card ?
They are related. Sometimes ASIO drivers report a latency in samples slightly larger than the buffer size, to compensate for the delay introduced in AD/DA converters. You can see the real buffer size in the “Input/Output latency, buffer size” line on the interfaces dialog report page.
ZynewaveThere is no difference in the format of the sound files. The only difference between realtime/render bouncing is that rendering uses a max buffer size of 128. If your ASIO driver is set to a lower buffer size, then this is used in rendering also. The difference in buffer sizes may result in a slightly different bounced sound if you use VST parameter automation, since VST parameters are processed once for each buffer.
ZynewaveAutomatic scrolling of the timeline when dragging beyond the edges, is on the future plan.
Zynewave@Igr0 wrote:
I CANT START VST INSTRUMENTS WORK. 😳 😆 I have created midi track, then i choose vsti FireBird, but have the message: “The mapping produces audio,but there is no parent track mapping that processes audio” On the mixer strip.I know,that search button in forum… 🙄
I can recommend that you follow the “getting started” chapter in the Podium guide. This should get you going quickly. If not, then please report the first step in the getting started chapter where you encounter a problem.
I’m glad that I started working on the new track layout option, because the new compact layout mode will prevent these kinds of problems happening for Podium newcomers.
ZynewaveThere are no limits to the number of VST instruments you can use.
how many effects per track
This works a little different in Podium compared to other hosts. You can only have one effect per track, but you can create chains of tracks which will act like the channel strips you may know from other hosts. With the current 1.94 release you can have max 16 tracks/fx in a chain. This is extended to 32 in the coming 1.95 release.
ZynewaveThis is a bug that I have fixed for the coming 1.95 release.
ZynewaveIf you’ve enabled the “link edit cursor to play cursor” option, the play cursor will stay at the play position when you stop playback.
ZynewaveCurrently they are fixed at 0 dBFS.
Should this be an option in the arrangement properties, or is there a need to customize this for each track meter?
I’ve been meaning to look into the K-System, which seems to have become a standard:
http://www.digido.com/bob-katz/level-practices-part-2-includes-the-k-system.html
What’s your opinion on the K-System?