Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@jpleong wrote:
I was wondering if it were possible for you to produce a short “Change-log” video with each new release. While it’s great to read about these new features, I have a hard time knowing what some of them actually do or how to actually take advantage of them. Now, I’m not talking about some elaborately produced video but more like a simple screen-shot video with narration (like what can be done with Adobe Captivate).
It’s a good idea, but one that I feel would take too much of my time. But maybe I should consider this at some point in the future.
ZynewaveKeymasterSorry to hear that.
One more suggestion: Make sure the “use time stamps from driver” option is disabled in the interfaces dialog.
ZynewaveKeymaster@ronin wrote:
How about zHitCreator? 🙂
How do you pronounce that?
If it’s “ShitCreator” then I can have the plugin ready for you in a couple of days 😆
ZynewaveKeymasterCan you email me your project file, so I can see how you have set up the loop recording etc.?
For a 2 bar roll-back to work, you need to start recording at bar 3. Place your edit cursor at bar 3, start recording, and you’ll notice that the play cursor jumps back to bar 1. Also remember that you need to activate the metronome in the transport toolbar to enable the roll-back.
ZynewaveKeymasterThe recording of the first note should not depend on whether looping is enabled or not. I just tried here on my system, and I can record the first note fine with looping enabled.
Be aware that if you press the key before the recording starts (or before the punch-in position if you have punch-in enabled) then the note won’t be recorded.
ZynewaveKeymasterI split your posts from the 2.08 release topic into this support topic.
What kind of MIDI controller are you recording with?
If the first note wasn’t recorded, does that mean it didn’t sound in the VSTi as well?
There is a “roll back” option in the preferences/metronome page. So if you need two bars lead, you should start your recording at bar 3.
ZynewaveKeymaster@michi_mak wrote:
Hi, i’m playing with recording vstis right now : when i record in loop mode allways the first note will NOT be recorded – does not depend on the vsti!! – i allways start with an audiorecording and play it in loop to create beats and leads and stuff …
or am i missing something?
regards,michiDo you mean MIDI input recording or VSTi audio bouncing? MIDI loop recording is not yet supported, so if you record MIDI input with looping enabled the notes will be overlaid onto the same sequence. One of the next releases will support MIDI loop recording using the same audio multi-take system that was introduced in this 2.08 release.
ZynewaveKeymasterI’m currently doing some redesign of the piano roll editor for the 2.09 release, so this bug should be fixed in that process.
ZynewaveKeymasterHi,
No plans on building an arpeggiator natively into Podium. But one of my next big feature implementations will be support for MIDI plugins (hopefully first half of 2009). Once this is done you’ll be able to use arpeggiator plugins to control your synths. I may even develop a Zynewave zArp plugin in the future, which then will provide an integrated arp editor in the Podium UI.
Frits
ZynewaveKeymasterAs the texture image is tiled, it is best to use “seamless textures”:
ZynewaveKeymaster@Conquistador wrote:
If you use the freebie Spitfish you can see this behaviour quite easily (hopefully anyway). Simply holding down a knob and moving it around for a few sconds will cause Podiums screen to shift. Of course if one was to automate another plug for instance (cut offf on a synth) you would be holding that parameter knob much longer than a few seconds.
I downloaded Spitfish. This plugin unfortunately does not implement the proper method for keeping the host UI alive when you click and hold one of its controls. This means that e.g. the Podium play cursor stops moving as long as you hold the control. But I do not get the “not responding” message. I can click and hold the Spitfish control forever without seeing this message. I am puzzled why you get this not responding message.
January 11, 2009 at 23:47 in reply to: Questioning the logic of a VST scan before saving a project #13688ZynewaveKeymasterThe “VST Plugin Folder” you select on the create new project page (which you can also set in the Preferences dialog) is stored in the Podium.ini file.
If your problem is that the folder you select is not remembered when you get a crash, then you can get around this by exiting Podium (or saving the setup manually) after you have selected the VST folder, to force Podium to save it in the setup. The next time you start up Podium the VST folder you last selected will be remembered.
ZynewaveKeymaster@Conquistador wrote:
I have reduced the cores to one for Podium but if I click on the screen when Podium loads a project, the screen still shifts left, for a few seconds.
I was expecting that. I was thinking more about the problems you have with plugin editors, when I suggested limiting the cores to 1. Let me know if this has changed anything.
January 11, 2009 at 19:18 in reply to: Questioning the logic of a VST scan before saving a project #13681ZynewaveKeymasterOk, then I don’t understand why you want the project saved before the plugin scanning. What’s the point of saving the template project when it’s not fully created?
ZynewaveKeymaster@Conquistador wrote:
However…I could not access Affinity settings for any audio hosts I have…Project 5, Sonar..CD Architecht e.t.c
Can’t you open the dialog, or are the CPU check boxes just grayed out?
Maybe it has something to do with the audio/MIDI driver that you use in your hosts. Does it change anything if you disable all MIDI/audio drivers in Podium and then restart Podium?