ConquistadorConquistador@pj geerlings wrote:
@Conquistador wrote:
… I am putting together a drum map tutorial and I am 60 – 70% of the way there. I use Stylus RMX but of course the principles applied should work with any drum VSTi.
I have Stylus RMX myself – I would really like to see your drum map tutorial when it is ready!
Thanks!
pj
Hey! Another RMX user. 🙂 Thats great. The tutorial will be ideal for you then. Although for anyone else reading this thread, if you do not use Stylus it should be very useful as well, as the steps apply to just about any drum module. 😉
Conquistador@pj geerlings wrote:
I found a thread regarding Drum Maps from around May of this year but seemingly nothing newer. Is there a tutorial available (or in the works) that could maybe help out a complete newbie (me)?
I suspect some of my confusion is simply not understanding the Podium vernacular. Is there a central glossary of terms for Podium? That might help too – then again, I’m pretty thick at times 😉
TIA,
pj geerlings
Hi PJ,
I suspect if Frits had the time he would gladly put together a more detailed drum map tutorial. The fact is, he has to juggle a high number of things as a single developer and to some degree might rely on other users sharing their knowledge on Podium (based on their usage of the Podium guide he has already written), but in much more detail.
I doubt Frits has the time to go into granular detail just yet but… I am putting together a drum map tutorial and I am 60 – 70% of the way there. I use Stylus RMX but of course the principles applied should work with any drum VSTi.
I remember ‘SuperCrunchy’ I think was/is is his Podium forum name, he put together a tutorial on getting started with Podium.
Now I had already spent plenty of time with the Podium demo before that but gave up as I just could not get a sound out of it, having used many times more complex hosts before successfully. This is over a year ago.
His tutorial just went a bit further and I finally ‘got it’. Sometimes providing even more detail on a particular area in a product is the only way to ‘get it’ so I know how you feel.
Podium is radically easier to get into now. Also the Wiki is designed to allow users to add their ideas and tutorials. So once I have completed the tutorial I will post it on the Wiki. Probably here as well as many people search the forum first.
I hope that helps. 😉
Conquistador@Zynewave wrote:
The people who bought the Beat won’t be able to fix the midi bug?
I’m sending an updated version to Beat Mag tomorrow, which will be included in the 2|2007 issue.
Nice move Frits. That is a very nice gesture. 😉
ConquistadorThanks! 🙂
Pulling down the file now 🙂
Conquistador@Zynewave wrote:
I fixed it today, and I’m about to test it tonight. If it works ok, I’ll release it later tonight.
As usual Frits your quick bug fixing keeps Podium 100% reliable.
This is one of the major reasons why I use Podium. You can simply rely on it completely, no surprises. Even if a bug is found it’s fixed very quickly! 🙂 Sadlly this is so rare in todays competitive market.
Please keep it up and thanks, your efforts are really appreciated. 8)
Conquistador@xis23 wrote:
maybe a cool idea would be if the hitpoints colours always pick the opposite colour of the clip they are employed on for maximum contrast and so it never blends into the colour of clips. this is to say for instance a clip that had hue 70 would have a hitpoint hue of 197 (as 127 is half of the 255 hue range adding 127 to a number would give the opposite hue exactly), obviously using mod 255.
this could result in some garish combinations but you would at least never have to worry about visibility problems
That is quite clever xis23, I think that actually could work very well.
Also Frits, to clarify further regarding which icons I suggested having separate colour options for…I was referring to the recent icons that were introduced in 1.68.
“icons for device mapping, preset and parameter objects.” These should at least have a white background and black text by default and other icons for MIDI input, audio input and audio output mappings should not be tied to other colour settings for other areas in Podium, as it can just too easily make them needlessly too dark.
As the purpose for the icons is to priovide increased visibility and to aid a user in better identifying certain aspects of Podium, anything that complicates that process should really be revisited.
Of course I am 99% certain none of the current issues with colours were intentional 😉 but with many more features now added to Podium since 1.68…I think the Piano roll, “1.68” icons and hit points need their own colour settings.
The Piano roll really does not even need a ‘colour’ setting but but simply black and white keys that do not change whatever colour settings are changed elsewhere in Podium.
ConquistadorJust to clarify what I meant by “just a few changes” to the colour options…
1.The piano roll keys should not have *any* colour setting. I know this is not deliberate but Podium is the only sequencer that I know of that has a piano roll that can change colour!?!?!?
So the piano roll keyboard graphics should simply be always black and white.
2. The track icons. Change certain colours to something moderately dark and the icons follow suite making them almost impossible to see. They should always be white with black text. Again I think they should not be affected by *any* colour changes elsewhere.
3. The hitpoints for the new fades…now I think because clips will vary in colour they (hit points) *should* have a colour setting.
So really just a few changes are enough to make a big difference.
Conquistador@Podianer wrote:
I think on 6th of Dec. the issue will be delivered for those non-subscribers…
Max
It looks like it is available from tomorrow Dec. 1st. Thanks for the screen shots 8) and well done!
Podium beat: KOMPLETTER SEQUENZER!!!!!!!!!!!!!!!!!!!!!!!!!!!! 🙂
ConquistadorThanks for the mp3s. I actually think the Podium mp3 sound “fatter”
Well as the developer of Podium you were always going to say that! 😆
When I load my z3ta+ demo on a new track and call up the “031 stella c2 (velo)” preset, and play on my midi keyboard, it sounds exactly like your Podium mp3.
Ok.
Some things you could check: Verify that you don’t have several z3ta+.dll files installed. Maybe Sonar uses a different version than the one found by Podium. Also check if the MIDI file you imported into Sonar created parameter automation tracks as well. I tried modifying some of the filter parameters and oversampling setting in z3ta+ but I could not get near the sound of your sonar mp3. Changing the samplerate in the project did not affect the sound much either.
I checked all of those things.
Otherwise I don’t know why there is this difference. Try playing this z3ta+ preset in some of your other hosts, to determine if it is only Podium that produces a different sound.
Ok well I tried this as well and the preset, sounds the same in Project 5 and Live6! So clearly Podium is not, I repeat not doing anything wrong as far as this issue with z3ta is concerned.
I even tried Dimension Pro and sure enough the Producers 20 synth bass preset, sounds different in Sonar6 than Podium or Live! It seems like Cakewalk perhaps deliberately or likely not, have a certain type of communication or optimisation on thier plugs when used in Sonar. I seriously doubt it but I can’t explain it otherwise.
I suppose since Z3ta and Dimension Pro are theirs that is a possibility but I really have no idea. The whole thing is bizarre. In any case Podium is in the clear and Live 6 😆
I have not come across anything like it. I definitely however noticed some sort of inconsistency with certain patches even with the same preset within Podium as in the sound would change while looping.
I guess my description might fit the discussion on francois thread but it was intermittent so I cannot pin it down.
It only happened a few times.
ConquistadorOk Frits…I have sent the info over.
Thanks.
ConquistadorThe fades look classy. Very classy. 🙂
The fade curves and the horizontal line.
Even when the waveform will reflect the sound amplitude, it is important to know at a glance if it is the original amplitude or if it is due to an event setting.
Like Max says, it would be nice if it is a global option.
Easily my biggest problem with the current fade implementation. One must be able to see at a glance what the state of each event in a project is regarding fades, essential IMO.
At the very least being able to view fades even when the mouse is not over an event, should be made optional. ❗
Great feature, it just needs a little more refinement. 😉
Currently when splitting an event, the two new events are assigned the same fade-in/out settings as the original event. Would you prefer that a split should always set fade-in/out to zero, or would you want the possibility to define the default fade times for splitting?
I think this should be optional.
The curve is updated as soon as you tab away from the value input field. You can also click and drag horizontally in the upper and lower halfs of the curve graphs to edit the curve values.
This does work and can be very effective at getting the desired curve but I think being able to make that sort of change to a curve on the clip itself would be far quicker. So…Fade properties for a bit more detail but quicker and more immediate results should be possible as you put it, if you were to…
“click and drag horizontally in the upper and lower halfs of the curve graphs to edit the curve values” but on the clip fades on the clip itself is the suggestion here, as well as the existing Fade properties horizontal drag action.
Also another problem I have is yet again the colour of one area in Podium is linked to another. In this case the fade hit points are linked to one of the existing colour settings in Podium. I really think this needs to be looked at again, please Frits. It is a real problem trying to balance colour settings to fit every area in Podium now. It should be something you simply set and forget.
Not asking for some sort of advanced colour palette here, don’t get me wrong, but there are many areas that really should not have the same colour setting in Podium. A few additional options would go a long way. Just a few.This problem is getting worse IMO.
Also I think it would be great to just right click on a clip to get a simple choice of fade shapes as in ACID. Very quick and simple.
For one developer I think it is a superb effort overall Frits. Really. Just some details that still need adjusting.
Conquistador@Zynewave wrote:
I will continue working on e.g. automatic crossfades, applying fade edits to all events in a multiple selection, fade curve defaults etc.
That’s good, thanks. 8)
Conquistador@acousmod wrote:
if you use the MIDI input focus track option the instrument played may change. Not always desirable if you have selected an instrument track for monitoring, and want to adjust events on other tracks.
Do you think that people often make copy / paste of events while monitoring a MIDI track (while playing keyboard) ?
If it is an option, everybody will be happy 🙂
Agreed, yes. Making it optional is the best way. 8)
But it is hard to do when you have to put the new events far from the previous ones, and when the arrange window doesn’t scroll when the mouse is at the edge.
I really would like to see more flexible scrolling in Podium. I don’t know how many times I have tried to scroll up or down in an arrangement only to be reminded that it just cannot be done that way. This kind of flexibility can be found in other hosts. It would be very useful in Podium.
Conquistador➡
