Zynewave.
Malcolm JacobsonHi Frits,
I have emailed you a copy of the template file.
Cheers,
Malcolm.
thcilnnahojThe side-chaining versions of FF Timeless and Volcano are separate DLLs, and Podium creates a device definition for them, followed by the side-chain mapping. The original stereo mappings for these plug-ins are of course pretty useless.
But I guess there’s no creating side-chain mappings without importing the ‘normal’ plug-in first…
There’s also a mono side-chaining version of FF Volcano 2 (filename FabFilter Volcano 2 (Mono SC).dll). Beta 5 imports this differently to how it handles the stereo side-chain version (it still creates the two inputs and one output separately).
Besides that, all plug-ins seem to import fine for me in beta 5.
Zynewave@thcilnnahoj wrote:
The side-chaining versions of FF Timeless and Volcano are separate DLLs, and Podium creates a device definition for them, followed by the side-chain mapping. The original stereo mappings for these plug-ins are of course pretty useless.
But I guess there’s no creating side-chain mappings without importing the ‘normal’ plug-in first…There’s also a mono side-chaining version of FF Volcano 2 (filename FabFilter Volcano 2 (Mono SC).dll). Beta 5 imports this differently to how it handles the stereo side-chain version (it still creates the two inputs and one output separately).
Besides that, all plug-ins seem to import fine for me in beta 5.
Try the new beta6. It should import mono-sidechain plugins (2-in, 1-out) correctly. I’ve been testing with FabFilter Pro-C, which I think uses a similar dll filename system as Volcano 2.
The insert mappings created for the FF sidechain dlls are indeed unnecessary as there are other dlls for non-sidechain usage. But I can’t see a bulletproof method for not creating these insert mappings. Take for example the Rocket compressor, which only comes as one dll supporting 4-in and 2-out. In that case you need the insert mappings for when you want to use it as an insert without external sidechaining. :-k
Other minor new stuff in beta6:
Right-clicking the power button shows an option menu.
Shift+Click and Alt+Click can be used on the loop, punch in and punch out buttons to set loop/punch at the edit cursor position or around the current selection. Right-clicking the buttons will open an options menu.
Increased the font size used in stickie notes.
When adding a bus send that does not yet have a return track, a messagebox pops up asking whether the return track should be created.
The New Arrangement dialog now defaults to zero audio tracks and zero bus sends.
The “+” buttons for inserting effects are now also shown on the track lane headers.
michi_maki’m looking forward to 2.27!!
thcilnnahoj@Zynewave wrote:
The New Arrangement dialog now defaults to zero audio tracks and zero bus sends.
What’s this! A cunning plan to confuse new users? 😛
I’m just kidding… However, I do honestly fail to see the reason.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
The New Arrangement dialog now defaults to zero audio tracks and zero bus sends.
What’s this! A cunning plan to confuse new users? 😛
I’m just kidding… However, I do honestly fail to see the reason.
I thought that with the new “+” button in the track toolbar, and double-click in the tracks and mixer regions, it’s now more obvious how to add new tracks. I found that more often than not, I prefer to start out with no tracks, and drag in sound files or mappings to create tracks. If I’m not mistaken, I believe that most other hosts also start out with an empty track list ❓
michi_makme too – starting ‘from scratch’ means NO tracks to me …
but this is subject to personal taste for sure!
SlomoI can only confirm that Pro Tools start with an empty track list. You even have to add a Master track.
It’s easy to do a setup of different tracks in PT. You just dial in how many, what type and then there’s a “+” button to add another amount of another type of tracks and another, etc.
thcilnnahojOh, okay – my bad then. I imagined starting out with a blank tracklist would only add confusion. 🙂
But to make it painfully obvious, maybe the new track button could pulsate like the power button when there’re no tracks besides the master.
Regarding tags…
Seeing as the “Tracks” tag is meant to provide a view of all tracks, don’t you think new tracks should always receive this tag, along with any and all tags that are selected at the time of track creation?
Bus tracks are now nicely tagged automatically unless you go the old-fashioned way of creating them, in which case it would make no difference which tags they get, as you’ll have to change it anyway (unless you select only the busses tag).
I would even go as far as to suggest the master, busses and tracks tags should be non-removable, but maybe that’d take away a little too much freedom…
ZynewaveBeta7 is up:
The Drumatic 3.02 plugin is now imported correctly.
The “+” and selector buttons in track chain panels are translucent when no devices are assigned.
Modified the Fader and Meter submenus. Added “After Sends”, “After Effects” and “Before Effects” shortcuts and moved the effect track list to a submenu.
Sound and MIDI files can be dropped below the last track lane header to create new tracks. Previously they could only be dropped on the timeline area.
Fix: Deleting a track would not always set focus to the next track when showing tagged tracks.
I’ve added a couple of YouTube videos that demonstrates the new features in 2.27:
http://www.youtube.com/ZynewaveDotCom
If you have suggestions for further videos, please let me know. I’m working on creating one or two videos demonstrating how to set up sidechaining.
thcilnnahojThe “+” and selector buttons in track chain panels are translucent when no devices are assigned.
Wow. When you think it can’t get any better, it just does like that. 🙂
The way you show the separate bus inputs in that video is a real eye-opener!
thcilnnahojThere’s a super-minor thing I noticed in beta 7, which might very well be intentional. I just don’t think it’s very pretty. 😉
I’m talking about the text color on empty/transparent selector buttons – when you bypass them, the text is dyed as well, making it unreadable with the default color theme.
ZynewaveI have finally finished writing the help page for the adjust timing dialog:
http://www.zynewave.com/wiki/doku.php?id=guide:edit_actions#adjust_timing
If you previously found some of the adjust timing controls confusing, please read this and let me know if all your questions are answered.
Zynewave@psychesonic wrote:
Hi. Just on the subject of plugins – since the last few Podium updates I’ve had a couple of plugins that have lost the ability to save presets at all, and thus lose the settings when I close the project. In particular, Kjearhus MPL-1 , and Ruction – I don’t know if it’s me or a bug so I thought I’d mention it. Cheers.
This can happen if the preset has been removed from the track with the plugin. To test, try and create a new project, import the plugins in question, set them up in an arrangement, and see if preset changes are saved with the project.
Zynewave@Malcolm Jacobson wrote:
Hi Frits,
I have emailed you a copy of the template file.
Cheers,
Malcolm.
The template file seems ok to me. It imports like shown in the screenshot of your previous post. Can you give me more details about what is not working?