Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterAutomatic renaming of arrangement file folders is on my plan. It will require a bit of work, so I’m saving it for a future update of the whole project file management.
ZynewaveKeymaster@DanielK wrote:
Hello Zynewave,
Have you taken a look at the project file I sent you? 🙂
Daniel
Not yet. I want to wrap up the current feature I’m working on first.
ZynewaveKeymaster@Mike G wrote:
1 – Why can’t you bounce a group track? (I frequently divide by arrangements into 4 or 5 groups (Drums & Bass, Pads, Vocals, etc.) and I bounce the ones I am not working on at the moment.) It seems that I have to add an effect track (usually a zPEQ with no frequencies in use!) in order to get the tickbox on track properties that allows be to bounce. Or am I missing something?
Group tracks can be bounced just like normal tracks. Select the group track and press the B key shortcut, or use the bounce submenu.
2 – What’s the best way to add one group just before the Master? I sometimes put a limiter/compressor on Master but have to create a group track and move all sub tracks/groups up one at a time. I have also just added a limiter between the Master and MainOut but i’m not sure if that’s the best way to do it either.
How do other people do limiting on master track?Are you working in expanded track layout mode and manually adjusting the group levels? This is all easily handled with the “insert effect track” and the “move effect track” submenus.
3 – If I ‘X’ (Bypass) a plug-in does it get unloaded? (This is what I do with the Master limiter during normal mixing)
No.
4 – What difference does “use as group track” make. I can see no difference with this ticked or not ticked.
Lots of small differences: You get the “new child track” command in the track menu. The track will be drawn using the “group track luminance” color setting. The track will have “(group)” appended in the inspector group panel group menus. The group track will appear in the “move to group” submenu for other tracks.
ZynewaveKeymaster@Piltdown Man wrote:
I think the screenshots are the most important thing to update. While the text may not be 100% complete, the Wiki version of it should be a reasonably accurate description of the GUI up to and including version 2.05.
The last couple of days I’ve updated all dialog screenshots in the wiki guide. The screenshots are no longer shrinked in size.
You may notice some changes in the dialog screenshots. That’s because I’ve revised the layout of all dialogs for the upcoming 2.11 release. There is also a “Help” button at the bottom left corner of each dialog, which will open the corresponding wiki page.
ZynewaveKeymasterHi,
If you had the “scan and import surround VST plugins” option enabled when you created the project, you should have some plugins with [5.1] configuration. The zPlugins at least are available in this configuration. These mappings allow you to process all six channels on one track.
When I setup a 5.1 Master output, all my tracks are only
routed to the left and right output. How can I assign the track output
to any of the other master outputs?If you have a stereo plugin that you want to route into e.g. the back L+R channels on the master out, you can use busses. Your project should already have surround bus mappings. You need to create an additional bus send mapping:
On the project start page, locate the “Send 1 [Stereo]” mapping, right-click and select “New Copy…”. Rename the mapping to “Send 1 [Back Stereo]” (or anything you like), and change the “first channel” from 1 to 5. Any stereo track where you assign the “Send 1 [Back Stereo]” mapping will then be routed into the surround bus on the back stereo channels, and the surround bus 5.1 output will be routed to the 5.1 master output.
Of course, the use of busses for this purpose is not necessary if you have a 5.1 in/out plugin that can reroute input channels into any output channel. Come to think of it, that would be an obvious future addition to the zPlugins suite 😉
Frits
March 10, 2009 at 15:22 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymaster@psychesonic wrote:
Hi. I would like to say that the recent implementation of edits on all selected midi events is a godsend – really useful. It seems though that this does not apply to audio samples. e.g. if I have dozens or hundreds of hi-hat samples placed and wish to alter the fade qualities or sample length, it seems I have to do it individually – a mind numbing, if not impossible task. Could the simultaneous edit of all selected audio events be introduced? Or have I missed something?
Cheers
psychesonicCorrect. The recent multi-event resize drag was only implemented for note events. Eventually I’ll add this feature to track events as well.
March 9, 2009 at 21:27 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterDo you mean this one:
http://www.kvraudio.com/get.php?mode=show&id=1768
The download link on that page does not work. Do you have an alternative link?
Have you tried the latest version 1.1?
ZynewaveKeymaster@DanielK wrote:
– When Microsoft GS Wavetable SW Synth is ticked as MIDI out in preferences, ASIO (ASIO4ALL 2.8) cannot initialize even though the soundcard is unused at all.
I think this is due to the way the Microsoft Synth works. When the MS Synth is enabled, it will allocate its output to the default audio device as configured in the Windows Control Panel. Most ASIO drivers will not initialize if the soundcard is locked by another application, in this case the MS synth. Tricky 😮
– When pitch bend data (or any other MIDI event?) event block from a pitch bend track having ! (exclaimer) icon, is moved/copied to another pitch bend track, the new track cannot be deleted without Podium crashing, but when data is drawn by hand, it’s OK.
It should not be possible to get the ! error button on automation tracks. Please send me the project.
It makes no difference whether 1 or more cores are active (affinity), same with enabling/disabling rewire and multiprocessing.
Do you mean it makes no difference to the crash caused by the pitch bend track?
Zynewave, how can I send you a small project file I’m using to replicate the crash, privately?
info at zynewave.com
ZynewaveKeymasterPlease send the file.
ZynewaveKeymaster@LiquidProj3ct wrote:
Thanks but…. It’s a little buggie, I think >< 1. Import any multichannel MIDI file as you explained
2. You will get a new arrangement with a random vst loaded in all tracks
3. and now try to copy the clips from the imported arrangement to your original arrangement in the same project. You will see that you can copy the first track without problems. But when you copy the second one it isn’t pasted, but although it isn’t pasted at all it appears in the embedded MIDI editor 😆That’s a problem with the copy/paste of track events. The current system was implemented before the option to hide track lanes was implemented. If you paste a multi-selection of track events from one arrangement to another, some of the pasted events may end up on the hidden track lanes. That’s why you see the ghost notes in the piano roll, but not the sequence events on the hidden track lanes. The copy/paste of track events will be revised in the near future.
ZynewaveKeymaster- Docked help panel.
- Musical scale option in the tempo event properties.
ZynewaveKeymasterI’ve added some code that will compensate for wildly fluctuating CPU usage measurements. Podium 2.10 will be released in a day or two, so I would appreciate if you could try the 2.10 demo and let me know if this version improves the CPU spike behaviour on your PC.
ZynewaveKeymaster@Conquistador wrote:
Frits are you happy to ship Podium with drum map templates? We could all chip in with templates of drum VSTi’s, RMX, BFD, Superior D2, Addictive drums e.t.c if you are happy to allow it. Unless there is some copyright issue, permission from the devs needed?
Don’t waste time on that yet. I’m going to revise the drum map editor in the near future. My thoughts so far are:
Add a new “Create drum kit template” command to the preset menu. Once a drum kit preset exists for a device, a “Drum Kit Preset” submenu will appear below the current “Preset” submenu in the track menu. This will allow assignment of drum kit presets separately from the normal preset assignment. This means it is no longer necessary to convert the normal presets into drum kit presets in order to get to the drum map editor. You can just assign any drum kit template preset to a track to get the drum map editor, without worrying that it will override the patch preset assignment. The “drum kit preset” submenu will have commands for e.g. extracting drum key names from plugins which support this feature.
