Added a 3rd sidechain tutorial using a 2 track set up. It’s Frits text, I just added a bit more text and some images for illustration.
The first two sidechain tutorials covered a 3 track set that provides a dedicated Output track for bouncing e.t.c but the two track set up is quicker if you do not need a dedicated output track for bouncing different versions of the Sidechain tracks output for instance in realtime or offline.
@Pigini wrote:
Couldn’t we loose that path and have the Podium.ini file and the audio cache files in the podium folder, all self contained?
I suspect it is possible but only Frits knows for sure.
Else, everytime we test a beta we better copy that appdata podium folder from the full release to somewhere else, delete it and have a new one created by the latest beta we test. (Maybe it wouldn’t matter if we did not do that, but I remember it was often suggested to delete that folder and get it created anew, when there were problems with a new version of podium.)
Interesting points raised. I am definitely in favour of a portable version but Frits holds the keys to that version. It seems relatively simple based on his comments but only he knows just how easy adding some of your suggestions will be.
I would like to run Podium from a USB though, for sure. It will add to its appeal 😉
Cheers Frits!
To save you time…I have now added a 3rd sidechain tutorial that covers your 2 track set up.
It’s listed as a Zynewave tutorial or “-by Zynewave” (I hope that is ok) as I simply copied your text and added some bits here and there, with some images. It is less obvious that your comments are from a few of your posts here and much more like a more detailed tutorial that way
I doubt you have time to write a detailed sidechain tutrorial right now, although you came pretty close earlier in this thread. Thanks again for that. 🙂
I changed the name of the first tutorials to highlight the fact that they use 3 tracks (which can be useful as the 3rd OUT track can be used as a dedicated bounce track).
But your 2 track idea is quicker for those who do not need a dedicated 3rd output track. 8)
Nice idea that would be Uber cool… 🙂
I think Frits said something about copying some files via explorer
“program fileszynewavepodium” folder to the USB stick you want to use, this apparently should work. Not tried it but I think according to Frits comments it should work.
Here is a quote from one of the VIP threads…
“When you run Podium for the first time on a new PC it will automatically create the userappdatazynewavepodium folder on the PCs local harddrive, where it will save the Podium.ini file and the audio cache files.”
Do a search for “media” in the VIP forum only. 4th thread down in the results, page 2 on that thread. Not sure if it’s ok to discuss that threads subject matter outside the VIP forum so apologies for the cryptic directions to the thread 🙂 But as a side discussion briefly a USB version of Podium was discussed. 😉
Ok I have now wirtten 2 sidechain tutorials with a similar approach. Hopefully it will help other Podium users, (even those trying the demo) who are looking for info on Sidechaining in Podium.
I had this idea to simply mirror the names and Device Property Panels for Compressive…exactly. I did not even think it would work as the plugins appear to approach side chaining very differently.
So after creating new mappings and carefully making sure I mirrored every thing about Compressive sidechain mappings, Names, Device Property settings e.t.c…Crunchessor 2’s Sidechain mappings worked.
So what was the problem I had?
a. I could not find the “Send”.
If you drag Compressive’s 1+2 or 3+4 mapping from the Inspector to a track, the send slider in the track view is not labelled as a Send. I think it should be. This really confused me. 😕 If you click on the Mixer it is not labelled as a Send there either.
But…in the Inspectors Track Panel..it is correctly labelled as a Send. This had me scratching my head for a long time.
b. Really, even though I admire Crunchessor 2 as a plugin and I can appreciate Aleksey was going for something different and maybe even more flexible than most Sidechain capable plugs…(fair enough) it is not easy to set up AT ALL. I was pretty close to swapping Crunchessor for Compadre which also offers sidechaining but with less complexity.
I guess Aleksey is far less aware of Podium (which remains relatively low profile compared to some higher profile hosts) and simply may not have tested Crunchessor with it.
c. I have been used to a much easier process of Sidechaining elsewhere and was frankly surprised by the complexity that surrounds setting it up in Podium at least with Crunchessor 2, which is definitely *not* the first plugin I would advise someone new to Podium to use for SideChaining.
But then again with the Crunchessor 2 Sidechain tutorial written now…even complete new starters with Podium and Crunchessor 2 can be up and runnning quickly. 🙂
Sidechain Tutorials
I still think having a SideChain command of sorts is still needed to help simpify things even further in Podium though. 🙂
Did you actually get Crunchessor working with Podium as a SideChain? If so how did you do it?. If there is another way I would like to know thanks! 🙂
Added two SideChain tutorials to the WIKI, one for Crunchessor 2 and the other for Compressive.
Found another solution which is a mix of Frtis suggestion (thanks) and Compressive Pro’s set up…Im just editing a Sidechain tutorial on the WIKI for anyone looking to use Crunchessor in Podium for that purpose.
Hopefully users can quickly and easily be up an running after reading it.
More on what was the cause later…I need to finish the Wiki tutorial first… no sneak peaking until it is ready 😛
Frits please do evaluate if possible to see if anything is not right or can be improved in the write up cheers! 🙂
@swindus wrote:
@Conquistador
Just a question: Do you use a side chain routing in the Crunchessor plugin too? If not it will not work.
I was doing that yes…, but it is part of the instructions given in the Primary user guide. Frits suggested this as well (based on the Primary user guide info, surely) But without using sidechain routing in the plugin I got this error pretty quickly…which I have not seen for a *very* long time (months or longer…)
Just a simple sidechain…is this difficult. It has to be easier in Podium.
Thanks Frits. I really appreciate your effort and the amount of detail but sadly it still does not work. I followed your advice but if anything it illustrated how complex sidechaining is in Podium even if it is more flexible than most if not any other host.
I think the problem is two fold. Aleksey really IMO should have made it easier by having Crunchessor 2 expose a 1+2, 3+4 and Out mapping to Podium like Compressive but even that is proving to be a huge mountain of clicks for me to set up. Cannot get that to work either and I have seen Martin Eastwoods screen shots for an older Podium sidechain set up
Aleksey said on his forum that you have to hit play then the correct mappings show up. Seems like a host specific thing. I don’t know if that is the case for every other host out there.
A few clicks should be all that is needed. Way too much complexity for me sorry. It has to be the only aspect of Podium that remains difficult to grasp (for me anyway).
I’m going to have to find some other solution thanks. Hopefully an easier way to map side chain capable plugs can be looked at in future.
Making things easier…
No idea exactly how that might be done but something that…
a. Behaves like a command. “Sidechain set up” click on it…
b. You then are asked to pick a plugin.
c. Asks you if Podium should automatically insert the tracks and mappings needed for the sidechain would be nice.
d. Then you simply drag the audio material you want to sidechain and duck to those tracks.
As things stand right now it is incredibly complex IMO. Just giving some frank feedback Frits.
Agian thanks for the write up and guide!
Love the look of those keys Frits!
@Frits wrote:
Feel free to post your list of wishes
Putting a Piano roll specific FR list together of my own. 🙂
Ahhh yes my Lords, Rohirrim, some replys and counsel for this thread with news from the Riddermark… 😛
@Mike G wrote:
Edit Cursor configurable snap+1
Midi file preview in List view+1
I’ll use some abbreviations I think… 8)
ECCS…
This will bring a really diffferent workflow to Podium that is unique to Live AFAICT…and make far more use of Podiums rather slick gapless audio engine / playback which is ideal for real time experimentation.
MFPILV…
This will encourage the saving of Midi parts that can be re used in any project. Previewing them via the list view through any VSTi would be great. Midi files are tiny compared to much larger audio files. One could have a huge stash of Midi files but never make a dent in hard drive space. 8)
@H-man wrote:
Epic post dude.
Thanks! Although not quite as Epic as the LOTR Trilogy though hopefully Podiums fuutre will be as exciting as that. 8)
@Technophobia wrote:
Midi Patching please (zMidi ?) ++++1
What do you mean..? Something like the routing and patching Energy XT offers?
@ronin wrote:
It would be nice to have improved support for midi/hardware-controls (smiliar to ableton live for example)
I’m not really a midi hardware guy (outside of keyboard usage) but funnily enough I would have thought your Midi FR would tie in nicely with Frits Piano roll improvements for 2.09. I think he said a re design of sorts but maybe better midi support will also be looked at.
– improved “workflow” stuff like editing multiple events, notes or tracks (selecting, moving, fading, editing length [whatever applies] etc).
Oooh I do like that. Very clever. Would really speed things up!
btw. nice post Conquistador!
Thanks 8)
@ronin wrote:
But anyway the small hobbit has a small question: is there anything like a roadmap?
I think Frits has had a Road Map for some time here (last updated on the 20th of Dec 2008) so it is probably pretty much up to date, but yeah something updated for 2009 in more detail would be interesting to see.
I think Frits kind of goes with the flow though…if there is some unexpected user feedback for a particular feature that he may have had no plans for (additional zoom improvements in the PR in 2.08 for instance) then he has on many occasions just added the FR to whatever release he is working on. Very flexible.
But getting a glimpse of Frits to do list for 2009 might be more difficult than getting that pesky ring destroyed in the fires of Mount doom! 😛
Lets see what Frits has to say… your question has made want to have a good look at the current future map..its been ages since I looked at it 🙂
@Zynewave wrote:
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.
Yes. That is why I suggested using it. I think you said this before about fish Fillets plugs so I wanted a worst case scenario plug to show you the problem…but it did not really help reproduce the problem for you sadly.
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
.
I will have to Google this extensively and see what comes up. Vista might be somehow causing the clash but Podium is the only app that graphically shifts so…(scratches head) no idea here.
Two longshots…I am running a quad and even though it should help mask such an issue it might be exposing it.
Secondly…we may be using different graphics cards Nvidia here ATi for you? (should make zero difference but worth asking).
The not responding message might be an OS issue but it is still only Podium that seems to show it.
Any how I’ll Google diffrent search terms and see what comes up.
Thanks for your time on this so far!
Made the changes and loaded a project…the shifting appears on one CPU and on four.
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.
It is less frequent with plugs like RMX but Spitfish shows it up quite quickly.
Podiums CPU meter was around 70. Latency 512. One core.
I reproduced the same shifting on four cores with a latency setting of 256.
@Zynewave wrote:
IMO, it will not look good with a purely blank background that has the same color as the panel color in the color scheme. The texture is painted on areas that are unclickable or that does not show content, so having those areas look identical to the tracks region etc. will add confusion I think.
Hmmm….you know what Frits, I really don’t think it will confuse at all. The look and feel of an app will not please everyone but…while I personally like the brushed look, I think not having it visible at all (as an option) will actually provide a more unified look.
I think letting the user choose is best.