I’m not entirely sure I understand what you’re describing :wink:, but here goes:
With Poise, you can have up to 16 MIDI inputs and 16 stereo-pair audio outputs, no problem. 🙂
I downloaded your project file and noticed both of the midi tracks you programmed are played through Poise’s first stereo output (Poise (#1) Out 1+2).
Since you have outputs 3+4 selected on track 4, I guess you wanted to split the outputs of your two MIDI channels – for this you need to assign the correct output channel to whichever drum pads you need to.
In this picture, I assigned the two samples (hi-hat open & closed) triggered by the MIDI clip on track 2 to Poise’s output pair no. 2. You do this by dragging the ‘control’ I encircled red on Poise’s GUI up/down.
Right, I hope this helps a little. I don’t know what you mean by “I tried to create another preset in the Library and assign one preset to Track1 and other to Track2“, however, the error you get in your screenshot is normal, since you tried to assign two presets to one plug-in at once!
Another thing – you can, of course, also place MIDI clips on the tracks Poise outputs audio to.
About your second problem, it’s probably best to ask Shannon (Poise developer) about that. 😕
I can only say I had no such error when loading your project file and the samples you embedded played just fine…
@thcilnnahoj wrote:
… Note move buttons, like in energy XT: for moving selected notes (or all in midi clip, if none selected) up/down by a semitone or an octave.
Argh, scratch that. Just checked the Guide and there are actually excellent keyboard shortcuts for this.
You can tell I haven’t made much use of MIDI editing in Podium yet (there’s a drum map?! :oops:) – I will, after this release, though.
@LiquidProj3ct wrote:
hey thcilnnahoj, take look at this video:
http://video.aol.com/video-detail/samplitude–sequoia-midi-multi-object-editing/3277472020
I get the idea of multiple colours from here, at least in that sequencer it seems clear and helpful. My screenshot are done with microsoft paint, you can expect a lot of it 😛
Thanks, I can see why this is helpful – but it’s not without compromise (no different colors for velocities).
Looks like Frits implemented it the same way in beta 2.
And so far… it’s wonderful! 🙂 Shadow’s very classy as well.
But please keep it optional, as there are situations where velocity sensitive coloring is extremely useful still – a solo piano part, for example.
@LiquidProj3ct wrote:
If I understand correctly, I don’t believe that they clash at all, due to the actual ghost notes haven’t any information in their color about velocity (they’re all the same grey)
But the notes in your currently selected midi clip do – I think that colored ghost notes could create confusion here.
You’d have to limit your color choices for tracks, which again is impossible when pretty much the whole spectrum is covered by velocity levels – like in my screenshot below.
(Example: the first two tracks’ colors shine through at about 50%.
Personally, I think it’d distract more than help. :?)
Another one: MIDI Scalpel tool, for the IDM and breakbeat guys among us. 😛
Or is there already a way to split notes?
@UncleAge wrote:
Not a must have but definitely a sweet feature that I liked when I used FL Studio’s demo was the ability to place chords in via the piano roll
I remember that! This would certainly be nice, but I agree that it’s lowest priority – you could probably even make midi files for a bunch of chords and import them as needed.
@pavouk100 wrote:
It would be nice to add MIDI velocity sensitivity according to the place where the piano key is clicked.
This would only be used for previewing, then? You can’t excactly add in notes by clicking the piano keys.
@LiquidProj3ct wrote:
semitransparent colours for ghost notes
It’s pretty comfortable see them with their colours. Then you can find easily without mute channels where is your chord progresion.
I think this idea about ghost notes retaining track colors could potentially clash with the very useful velocity-sensitive coloring of midi notes. Might have to try and see.
Two more to throw on the pile:
– Note move buttons, like in energy XT: for moving selected notes (or all in midi clip, if none selected) up/down by a semitone or an octave.
– Velocity level +/- buttons: pretty much like the above – to equally control multiple notes’ velocity.
Also, I’d like to add that I prefer flat notes (:oops:) to the bevelled look you see in many other sequencers.
:love: :love: 😆
That’s fantastic!
I think now’s the right time to consider some of the changes you described in the future development sticky thread, too. Especially (imho):
– When dragging the size of a note then other selected notes should resize accordingly.
– Highlight keys on keyboard when played by external MIDI keyboard.
– Option to turn off note audition. And for auditioning, maybe have the note ring for as long as the key is pressed as opposed to the current quantize setting.
I have nothing to add other than you got your colors wrong! 😀
Jupiter Jones, First Investigator
Pete Crenshaw, Second Investigator
Bob Andrews, Records and Research
(Sorry, I had to. :))
Hey,
I’m just chiming in to say I’ve never had these problems either.
I did a stress test on Podium just now with that PSP mix pack demo and a dozen freeware plug-ins without any hitch.
I’m also using 32-bit Vista, with Aero, internet stuff and everything on a dual core PC with a Radeon HD2400, so really not top of the line.
Does it happen when Podium is in full screen mode, too?
Or do you, by any chance, remember around which Podium version it first appeared?
Maybe Frits could send you a few older ones for testing.
Sorry I can’t be of much help… if anything, I’d say you could try out some newer and older drivers for your graphics card.
It’d be great if you could try on a different PC, though.
Best of luck! 😉
Ohh, such a nice update for the middle mouse button. 🙁
If only my mouse (Logixxxx MX400) hadn’t such a :evil::evil::evil: of a wheel! It was just perfect on its predecessor (xxxxtech Mouseman wheel) – now it’s rock hard and jumpy. The only good thing is the left & right tilt which, of course, no program ever uses… (done venting now)
Great job, Frits!
Many thanks! 😀
No problems with older projects here.
But – it’d be nice to have an easier method for bouncing to mono – maybe an entry in the bounce menu. (Until now I’d create an empty audio event, change its properties and bounce away. Added to that I now have to un-hide and hide the track, too. That’s unnecessarily complicated, I think.)
This’ll get some getting used to for me as I don’t need freezing (=conserving CPU power) as much as rendering midi and effects to audio for further editing (=chopping it up). But as long as the bounce track/file can be unhidden it’s all good. 🙂
I’ll just say that the bounced overlay needs to be visually emphasized more.
It can be kind of hard to notice with lower volume, which I’d say most people use during mixing:
Dunno how much work this would be, but maybe the waveform could be tinted with the parent track’s color or the bounce button color?
Looks great!
A find: The track panel in the inspector displays normal sliders even when set to readout sliders.
Blame it on 4chan and the like.