Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster1. Scanning plugs:
Sometimes Podium will just not pick up certain folders. I have done this soooo many times on XP but on Vista it is very unreliable. I have folders that are set up as Compressors, EQ, Modulation e.t.c about 10+ different types of folders like this but Podium will only successfully find 3 or 4 folders.Is it random which 3 or 4 folders Podium finds on each scan?
2. CPU spikes:
On XP Podium without any tweaking to the OS can run up to 70% – 80% without that CPU reading changing by more 2 or 3 percent, if that even. On Vista however I have found Podium to utilise 4 CPU’s very well but still on playback the CPU meter can be more “twitchy” on similar settings compared to XP.This could be related to the soundcard driver. Is it the same soundcard you are using on your XP/Vista machines? Both running ASIO drivers? If you try with another host program, does this run equally stable on your XP/Vista machines?
3. Some plugins that worked in Podium (Sonitus VST) are now not loading properly. At that point I just switched back to XP.
This could be an issue with the plugins.
4. When Podium is accessing my hardrive to load a project sometimes the whole project start page will move diagonally about a cm upwards then fall back into place. Nothing like that in my experience on XP.
Strange. This may be a problem with the way I’ve implemented full screen mode. If you restore the Podium window so that it has a frame, does the window still jump when loading projects?
ZynewaveKeymasterI think it is certainly very close to XP’s performance levels (Podium) but really there are one too many issues in Podium for serious work on Vista IMO. YMMV.
Can you please describe these issues. Are they all related to CPU spikes?
ZynewaveKeymasterI don’t have a Vista machine yet, so that is why I can’t officially claim that Podium supports Vista, but some users have reported success with running Podium under Vista. If you have problems with CPU efficiency and spikes, it may be due to audio drivers. Which soundcard are you using? Are you using ASIO drivers? If you increase the buffersize/latency, does this influence the CPU spikes?
September 25, 2007 at 23:17 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.September 25, 2007 at 01:56 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterI’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.
ZynewaveKeymasterNot before the 2.0 release.
ZynewaveKeymasterHow 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.
ZynewaveKeymaster@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.
ZynewaveKeymasterHaving 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.
ZynewaveKeymasterOne 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.
ZynewaveKeymasterSince 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?
ZynewaveKeymaster@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.
ZynewaveKeymasterThere 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.
ZynewaveKeymasterAutomatic scrolling of the timeline when dragging beyond the edges, is on the future plan.