@LiquidProj3ct wrote:
@Zynewave wrote:
Is that the bug where changes in the plugin is not saved when doing a save project in Podium?
Yes, it was. Now I can load the samples in pads and I can save the plugin changes. Marvelous support!
Well, there you go …happening here too now?!?
Off to email Shannon.
@UncleAge wrote:
@Conquistador wrote:
3. Much better use of the Event view…
The is a big space to the left of the Piano roll view…why not fill it up with the Event view which clearly will have info directly related to the Piano roll?
In no way, form or fashion am I trying to derail this discussion but could someone tell me how or why they use the Event View? I always thought of it as a nice thing but never found a use for it.
Hey UA,
Just a different presentation of the midi data really, but in a somewhat condensed form (all info at your finger-tips) with no need for graphical interpretation.
My thought was to be able to access and edit this info from the note as displayed on the Piano Roll as like a tool tip that you can make changes through, like the current mixer Meter & Fader routings display.
I’m not married to the idea but I think it could be handy.
@Conquistador wrote:
@UncleAge wrote:
@Conquistador wrote:
Putting a Piano roll specific FR list together of my own. 🙂
No doubt 😆
Indeed… 😛
My list for the Piano rolll for now…
1. Note names…with a user configurable colour option for the text.
2. Horizontal highlight…with a user configurable colour which could include an option to choose the selected tracks colour.
3. Much better use of the Event view…
The is a big space to the left of the Piano roll view…why not fill it up with the Event view which clearly will have info directly related to the Piano roll?
Large empty space…
I think this is much better…
4. New Midi Preview browser window
I initially thought this would be better in the List view but it could work just as well in the PR.
Since the Piano roll already knows which track is selected why not add a Midi import command to the Piano roll File menu? (Midi Export is already there) so surely Midi Import should follow. The midi file gets imported and an additional preview function in a new browser would play the midi file through whichever synth the PRV has focus on.
This could work for drums as well. Simply select your synth track in the Piano roll, select the Import Midi command and browse your hard drive for midi files. Press a preview button (in the new browser) to hear the midi file playing through your drum VSTi. If you are happy with what you hear click ok to import that midi file into Podium.
The volume of the track with the synth on it, could determine the volume of the preview.
That is all for now…heh 🙂
+1
I had been thinking about the midi event list properties as a tool tip or pop up but this would work.
The changes so far are really great! For me though I had always found the Pencil in Podium to be the ultimate weapon, it does everything except chords (in one shot).
hmmm …new FR, Chord Brush, Arp Brush etc. Probably better as midi plug-ins maybe.
Any feedback on the Piano Roll Keyboard responding to an attached controller? Also, step recording from midi controller keyboard?
Again, new features and options are wonderful (I’m running out of superlatives…) 😆
Ben
@ZChris wrote:
Hey all, just wanted to write here to say I’ve been testing Podium and it’s really impressing me, It took a little getting used to but boy was it worth figuring out – such a clean and elegant interface and customizable too.
Greetz ZChris,
I think you’ll also like the way that Frits is so active on the updates. It’s quite a phenomenon!
You can also slave ReWire FLStudio into Podium too :D, gotta juggle the latency and use Realtime-record to bounce but it’s generally pretty good.
Ben
LP,
I have been able to use multiple kits accross multiple instances of Poise (1093) by dragging the intstrument repeatedly onto the track lane.
Note that Podium scans this pluging and creates 16 (midi input) versions however if you open the device settings these have no outputs (or inputs from the mixer).
I don’t use these as I have grown acustomed to dragging the midi input between tracks.
Maybe Frits can shed some ligjt on this. I bet it is covered serveral times in the forum somewhere.
Note that copying and renaming the .dll seems to work as well but it’s not necessary IMO.
@LiquidProj3ct wrote:
2. The second one, mainly poise related and no Podium (I think). I noticed that in this new version from yesterday (1.093) Poise don’t load the samples when you close and open again the project in Podium. It gives the error:
Poise: There was an error while restoring chunk data. (Count not load Pad Data)
Okay, not getting that one. Regardless of whether I choose to embed the samples in the project file or not, they come back fine when I reload the Podium beta.
I’ll keep stuffing around. Please post any interesting findings.
Ben
Hey there,
Just got home from work. I’ll have a look at this in a minute.
Also I saw the post on the Poise support forum on KVR just now so I’ll run some tests and see what I come up with.
Looks tricky. 😕
Big-tah! 😀
Soooo off topic but this skin was pretty good. I have been trying to finish my Akai-ish one for ages. Nearly done, will post on KVR soon (Next week).
As for your question, you can drag audio clips (among other things) from the ‘list’ menu on to the track lanes. The tracks feature in the inspector dose surprisingly little however once Frits turns his attention to it ….well, you know the rest!
Ben
Whoa!
How’d you get your hands on that Poise skin????? I thought they were just PhotoShop Mock-ups 😯
Oh-kay then, thx for the info.
I’m guessing that with a multi-core PC and my keyboard skills there really isn’t any need to have this checked :).
@Zynewave wrote:
@H-man wrote:
@H-man wrote:
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Okay …seems to have eliminated the problem. Recording resumes as expected.
Any ideas on why this occurs Frits?
Faulty driver, I would guess. This problem has popped up many times over the years. Apparently there are not many sequencers that utilize the driver timestamping so that could explain why there are so many drivers where this is not implemented/tested fully.
Okay, cool. What does one miss out on by not having it?
@H-man wrote:
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Okay …seems to have eliminated the problem. Recording resumes as expected.
Any ideas on why this occurs Frits?
PS: michi_mak, did you get similar results?
@Zynewave wrote:
Sorry to hear that.
One more suggestion: Make sure the “use time stamps from driver” option is disabled in the interfaces dialog.
Hi Frits, I have always had a similar issue but just put it down to either Windoze or my focusrite/Roland (PC-200 MkII …almost ‘Retro’ now) setup.
Typically what happens is Podium will kind-of lose contact with the keyboard after a period of time (maybe 5 mins). To re-establish midi recording through the keyboard I would just click on Setupmidi/audio interfaces and ok and midi would record again.
I don’t use the keyboard all that much so given that there was a 70% chance the problem was outside Podium I never bothered raising it
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Ben
@Zynewave wrote:
@ronin wrote:
How about zHitCreator? 🙂
How do you pronounce that?
If it’s “ShitCreator” then I can have the plugin ready for you in a couple of days 😆
Nah Frits, I thinks it’s pronounced ‘Zit-Creator’ …gives you pimples apparently 😳
Sorry CQSD for the frivolities all over your thread.
Is there an existing FR for the keyboard in the Piano Roll editor to respond to (show depressed key I suppose) the key played on the midi-controller keyboard?
Epic post dude. 🙂