Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterGood news Gabriel,
Today I downloaded the EST plugin demo and indeed there was an oversight in Podium that causes this plugin to ignore sync.
The problem was simply that Podium never set the (nerd-talk: kVstTransportChanged) flag. Not all sequencer-based plugins requires this flag to be able to sync. The Sonicbytes plugins apparently do. From what I read on the Steinberg VST mailing list archive, Fruityloops also requires this flag. With a bit of luck this fix will cure your problem with Fruityloops as well. And if I may dare to be completely optimistic, this will also fix the reported sync problem with the Sonicbytes Gat’r plugin.
The fix will be in 1.20. Please let me know if the sync problems remains after this release.
ZynewaveKeymasterI have not yet been able to recreate the 100% CPU lock, but I have fixed the problem with the internal sequencer not responding. This fix will be in 1.20, to be released later this weekend.
For those with technical insight into VST programming, here’s my notes concerning this fix:
The VST 2.3 documentation is vague in explaining the ‘position’ parameter in the tempoAt() plugin to host call. So far Podium has interpreted this parameter as an absolute sample position in the song. I have now changed it so that it interprets the position as an offset to the sample position of the currently processed block. Hopefully this doesn’t break the tempo sync in other plugins. Most plugins I have tested does not use tempoAt() but rather calls getTimeInfo() which provides more detailed sync info. The getTimeInfo() call is not affected by this fix. When Kubik calls tempoAt() it always sets position to zero, which caused Podium to think it requested a tempo at a position before the song started, leading to a wrong tempo sent to the plugin.
November 19, 2004 at 09:20 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.November 19, 2004 at 09:13 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterThat doesn’t sound good Joachim. To start with; if you suspect you have a bad memory block, then I can recommend the free Memory Diagnostics utility from Microsoft:
http://oca.microsoft.com/en/windiag.asp
A few months ago it helped me identify a bad memory block in my old internet PC that was causing Windows to sporadically blue screen.
Is there a parameter or setting I can invoke to tell Podium to create a crash log?
You can go to the interfaces dialog and create a report. Email it to me afterwards.
I’ve discovered that Podium streams the sound through it’s mixer from my sound card inputs, even if audio mixing for the track in question isn’t enabled. It seems to me when I enable audio mixing for such a track, the risk for a crash is at it’s greatest.
If the mapping assigned to the track is configured to route audio, then the track will be set up with audio streaming no matter what the ‘Enable audio..’ option in the track properties dialog is set to. If you could email me a project file that has the problems you describe, I can have a look at it. Maybe I can use it to recreate your crash scenario on my system.
ZynewaveKeymasterI have just tried the energyXT 1.28 demo as a VSTi in Podium. I’ve never used energyXT before, so I just tried some quick experiments. I managed to create a sequencer object and by activating the ‘External sync’ in the Options menu, the energyXT play cursor followed the Podium play cursor and responded to tempo changes. There is a ‘Synchronizer’ section in the main window which when enabled syncs tempo to Podium. Although the tempo value field only updated when minimizing/restoring the synchronizer block (small UI bug perhaps?).
Does this in any way answer your question, or did I misunderstand you?
November 18, 2004 at 18:35 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterbut i noticed that if the punch in/out was enabled , i was not able to record midi???
Hmm, try again. It certainly should be possible. It will of course only record within the defined punch range, which should be clearly indicated by the red mask on the tracks that are record enabled.
Edit: To be sure the code has not been broken, I just tested it right now, and Podium does record MIDI within the punch in/out range. Couldn’t the explanation be that you forgot to record arm the MIDI track or set the proper punch range?
ZynewaveKeymasterso, there isn’t a setting that I could be forgetting or not know about, that makes stuff sync with Podium?
There’s no sync option settings in Podium. Most plugins require that you select whether you want tempo to sync to the host. I don’t know yet how these particular plugins you mentioned are handling this.
ZynewaveKeymaster@duncanparsons wrote:
@Zynewave wrote:
I think it could be nice if the stop button reset automatically the Rec button(transport tool)
How about using the punch in/out range? When recording passes the punch out position, the record button is switched off.
That sounds very workable frits – but have it as an option, if that’s OK..
DSP
But that’s how it is already working and always have ❓
The purpose of punch out is to stop recording at the punch out position.ZynewaveKeymasterI think it could be nice if the stop button reset automatically the Rec button(transport tool)
How about using the punch in/out range? When recording passes the punch out position, the record button is switched off.
ZynewaveKeymasterI know that e.g. the MicroTonic drumsynth can sync with Podium, so it must be a minor issue that causes these others not to sync. I’ll check it out.
November 17, 2004 at 01:55 in reply to: Close 2 open list windows and Podium goes to background #4002ZynewaveKeymasterBug fixed. As usual, I’m tempted to say :roll:, the fix involved ‘relieving’ Windows of some of its ‘intelligent’ decisions and doing a manual deactivation/activation before telling Windows to close the current window. The fix will be available in release 1.20.
ZynewaveKeymasterHi Joachim,
I’ve closely studied the screenshot and I’ve closely studied my code for the painting of these fields, and I’m simply puzzled over how this could happen. Please let me know if you can find a way to reproduce this. Anyone else ever observed this?
Edit: I’ve given it some more thought, and have come to the conclusion that it must be the bitmaps for the numbers that have been corrupted. If this is the case, then the corrupted graphics should remain until you exited Podium. Can you confirm this? Also, did the corrupted graphics occur right from the start upon opening Podium, or did it appear after you had done some action within Podium? Were you using any plugins in the project?
November 15, 2004 at 23:25 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.