Zynewave's Forum Page
Forum Replies Created
-
March 11, 2006 at 02:01 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.March 10, 2006 at 19:22 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.March 10, 2006 at 16:18 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterwhen i pass the pencil on the note event , i cannot see anymore the double arrow that indicate a possible modification of the length
It works ok for me. Are you sure you have selected the pencil tool in the piano-roll editor, and not just in the arrangement editor? The cursor should show the pencil image attached to the arrow. If you press the Alt key and click+drag the note event, does this resize the event?
ZynewaveKeymaster- Minor improvements and bug fixes.
ZynewaveKeymasterPodium 1.53 will be released within a day or two. It has support for using MIDI inputs both from an input mapping and an external device mapping on the same track.
ZynewaveKeymasterAnd what if track inspector info panel will show generic plugin editor even if plugin is not configured to use the generic editor?
I thought about it, and I may implement this in a future update. For now I’d like to know how users feel about the embedded generic editor.
March 7, 2006 at 13:04 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterEverything is working nice exept one thing – ‘gain’ control in track inspector is not updated when tweaking.
Ooh, you’re right. I’m amazed I haven’t spotted this during my testing. It is just the graphics update that is lacking. I’ll release a bug-fix version in a few days time.
ZynewaveKeymaster- Redesigned track inspector panel headers.
- Embedded a generic plugin editor in the inspector info panel.
- Added VST 2.4 support including double-precision processing.
ZynewaveKeymasterI still have a problems with coping curve sequences. Some events just disappears. Did you received the project file?
Yes I did. The problem occurs because when you drag+copy a sequence event, the copied sequence object is cropped to the range of the sequence event. The last curve point in your sequence lies just outside the range of the event, so therefore it is deleted. I need to modify the drag+copy function so that it will include an additional curve point. I’ll probably release 1.52 later today, and I’ll include fixes for your two bugs reported here in the next 1.53 release.
You can avoid the problem if you drag phantom copies instead, and then use the ‘clone phantom sequence’ menu afterwards. This will not crop the sequence.
March 6, 2006 at 02:48 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterRemoving bounce mode option worked.
Great. I’ll implement a popup warning for tracks that are both bounce enabled and have an audio input assigned. This will hopefully help the user resolve this type of problem scenario.
ZynewaveKeymasterBit resolution is 32 bit floating…
That is because it is configured as a bounce track. If you enter the track properties for the track and remove the bounce mode option, then any audio you record onto the track will be set to the proper bit resolution for your soundcard inputs.
Did you notice my previous reply in this topic?
What should happen if I click on “open sound editor” from that panel? I get a blank box regardless of the wav object I do this to.
Are you referring to the ‘open sound editor’ command in the context menu for the sound event? That command should open a slave sound editor, same as if you double-click the event on the track. If you double click the sound object in the list panel, this will open the sound in a master editor (with transport toolbar and no links to the arrangement). If you get a completely empty editor window, then the sequence profiles have been messed up. You can fix that by loading the default setup.
ZynewaveKeymasterOoh, hang on. I just took another look at your project file. The audio track you are recording onto is bounce enabled. Meaning that even though you have an audio input on the track, the recorded sound will be treated as a bounce track, so it will only play if you activate the B button. You should generally not enable the bounce mode on regular audio tracks.