thcilnnahojThanks!
@new in version 3.0.1 wrote:
The installer now logs the folders where the Podium application and the Zynewave plugins are installed. Future Podium installers will use these folders as defaults, so that you don’t have to select your customized folders each time you update Podium.
Unfortunately, this didn’t work for me, at least when going from 301 to 302. I’ll keep an eye on it when 303 comes out.
thcilnnahojOK, testing done, but it seems the problem I have might be different from yours after all. 🙁
The strange problem I remembered (and now confirmed) is that I have trouble getting the first input note recorded at all if it is played close to the start of a bar.
This happens only when a new sequence is created by the recording – NOT when I record with a sequence already present on the track and the recorded notes get added to it. (Frits, if you need any more info, just tell me once you get back!)
Other than that, I didn’t notice any timing-related problems… If and when the first played note was recorded, it was on time. 😕
Does it happen regardless of whether you ‘overdub’ an already existing MIDI sequence or let Podium create one while recording?
thcilnnahojWhile Frits might be reluctant to get people’s expectation up too much, you could always try and suggest a little feature or tweak every now and then. Some great things in Podium have evolved from a simple suggestion at the right time. 😉
(Pardon me if you’ve been doing that all along already! I haven’t been around much, lately…)
thcilnnahojYup, you absolutely deserve it! Hope you’ve been doing well these last months!
thcilnnahojHmm, I rarely ever record using a controller, but I vaguely remember also having a problem with the first recorded note. I can’t say if it’s the same problem you’re experiencing, but it sounds like it. Anyways, I’m gonna give it a thorough test this week nonetheless!
thcilnnahojHello and welcome! 🙂
I think the problem might be that you’re used to the sequencer scanning for new plug-ins on start-up (like FL Studio does).
This is different in Podium – every project can (and does) keep its own configuration of your plug-ins. When you add or remove a plug-in from your VST folder, you’ll have to let Podium know something changed so it can update its database.
You do this by selecting “Rebuild plugin database” (this scans all plug-ins and removes missing ones) or “Update plugin database” (which only scans new plug-ins) on the new project page or from the Devices menu on the project start page in existing projects.
Please excuse me if you already knew about this and it’s not the problem…
In this case you could try dragging and dropping, for example, Nucleum (the .dll file) onto the right-hand column (the one that shows all your other instruments and effects) on Podium’s project page. Please report back if it still won’t show up in the list after that!
thcilnnahojThanks. Okay, that looks all in order… weird.
Please excuse the dumb question, but I have to ask: you do know that you have to press play as well before anything will actually be recorded?
thcilnnahojHmm, I don’t recall any previous cases in which it just wouldn’t record even though everything was set up correctly, so to start, a screenshot of your record armed track might give some clues… :-k
thcilnnahojI believe I might’ve discovered the most insignificant bug in history…
When you relocate the edit cursor by pressing the middle mouse button while the mouse cursor is placed over a note, the note highlight effect is broken.
Behold…! 😮
thcilnnahojHello and welcome!
Let’s try to get to the bottom of this. I assume you have your MIDI keyboard set up already and are hearing the drum sounds when you play it?
If that works, the only thing left to do is record-enabling your track (with the “R” button on the track header) as well as enabling recording mode (the button with the big filled circle on the transport bar). If you did both, the track lane background should be colored red and you’re good to go as soon as you press play!
Let me know if this helps, or if you’re still having trouble. 🙂
thcilnnahojRonin’s suggestion indeed sounds like a pretty good way to do this. I guess the problem is just, as always, there are not that many people here to gather a reasonable sum without having to pay some hundred Euros each… depending on how high Frits’ resistance to this kind of “bribery” is, of course. 😉
I’d certainly be in if this starts to gain momentum, though.
Otherwise, there’s always the option of donating and leaving it up to Frits to decide what’s going to be next on the development schedule as usual – if you feel inclined to support Zynewave even more than you already have. I know I do. 😉
thcilnnahojIt’s the first beta… *sniff* I can’t test… 😥
Another big step forward, though!
thcilnnahoj@Zynewave wrote:
:-k Hmm, thinking about it: Maybe the “first snapshot in group” option is not needed at all. The grouping of snapshot buttons could just be determined from the four other options. A space would be inserted between two snapshot buttons, if their timeline/track options differ.
Oh, I assumed you meant they’d be automatically arranged, as in if I add a timeline zoom snapshot, it’d be appended to the timeline zoom “group” as it were. It turns out it’s not quite as neat to have snapshots with similar settings all over the place, so I’ll actually be using the insert command most of the time, I think!
thcilnnahojIt’s good enough for me. The only suggestion I have that’d make it quicker to use for me would be shortcut keys for the “+” button menu. I don’t know what the term is (shortcut mnemonics or something?)… I’m talking about the underlined letters for each menu option.
Come to think of it, I don’t think I’ve ever seen those used anywhere in Podium, so it’s probably not a quick thing for you to implement. Well, it’s just dandy as is! 😉
thcilnnahojVery nice. 8)
For those that fear they have to remake their whole setup in order to get the six default snapshots to show up – just save your current setup, restore the default one, and then load your old setup again.