Conquistador's Forum Page

Green light with Vista x64. No problem so far based on a very brief run.

As stated already it does indeed appear to be a Vista – XP specific problem at least based on initial feedback.

@Zynewave wrote:

Don’t waste time on that yet. I’m going to revise the drum map editor in the near future. My thoughts so far are:

Add a new “Create drum kit template” command to the preset menu. Once a drum kit preset exists for a device, a “Drum Kit Preset” submenu will appear below the current “Preset” submenu in the track menu. This will allow assignment of drum kit presets separately from the normal preset assignment. This means it is no longer necessary to convert the normal presets into drum kit presets in order to get to the drum map editor. You can just assign any drum kit template preset to a track to get the drum map editor, without worrying that it will override the patch preset assignment.

Ok thanks. 🙂 Sounds like a good idea. Less steps to completing the process.

The “drum kit preset” submenu will have commands for e.g. extracting drum key names from plugins which support this feature.

This sounds like a way to avoid editing the drum map in the list view to remove excess notes.

If I understand this correctly in RMX for instance could I use this to extract Kick, Snare, Hihat note names from the plugin so only those note names will appear in a drum map?

Having read your comments it seems better for me to wait until the drum map changes arrive before updating the Wiki drum map tutorial, that way it can be 100% up to date with the new features. It would be great to have an updated drum map process in Podium with a fully updated Wiki guide as well, looking forward to it. 😉

@pj geerlings wrote:

Sadly, no 🙁

I spent a very tiny amount of time on it this past weekend ( though I really should work through your tutorial instead of just reading it 8)

Maybe yes. 😛 I think I will update it after 2.10 is released. Nothing major but new images and better structure (table of contents e.t.c) that might make it easier to read. But it will not reduce the steps that much.

I actually own RMX but I haven’t installed it yet – and I probably won’t ’cause I just ordered Steven Slate Drums LE 3.0 – damn, I’m pretty flakey 😉

Oh….you may want to have a look at 1.7…it is causing a massive stir on KVR.

Stir 1.

Stir 2.

Of course if you have not installed it maybe you do not really need it. 😐 Maybe sell it and use the money for something else you really need. But If you are not sure please watch these videos first.

I would definitely start with this one. 😉

Maybe I need to start with an existing Drum Map and modify but I can’t seem to find any existing Drum Map templates in the release …

Might be an idea. Frits are you happy to ship Podium with drum map templates? We could all chip in with templates of drum VSTi’s, RMX, BFD, Superior D2, Addictive drums e.t.c if you are happy to allow it. Unless there is some copyright issue, permission from the devs needed?

FWIW RMX 1.7 seems to be working very well in Podium so far. Super Slick.

@LiquidProj3ct wrote:

Now in the new 2.10 beta 1, I can use six gladiator tracks without problems with the option you added (and seven with artifacts). Thx you very much. Oh, and the GUI doesn’t freeze when CPU is overloaded! 🙂

Very interesting feedback. Even more CPU usage out of Podium quite a result 🙂

EDIT: As I said in the 2.10 discussion, since GUI doesn’t freeze, I think you should disable that option by default, so those people with non-optimized pcs haven’t problems with this and think that podium is CPU expensive.

Seems like a very good idea. That might be the best way forward to avoid confusing new users. I had my fair share of issues with it in the past. I wasted a huge amount of time troubleshooting it sadly.

I’ve changed the default of the new option to be off. The automatic bypassing was implemented years ago, on an older Windows version running on a single-CPU PC. Without the automatic bypassing, the PC could freeze up completely, requiring a cold-boot. Today multi-core machines are more common, and on these machines you seldom have problems with GUI freezes.

Something to consider Frits….most demo users IMO will not post their thoughts on a forum and may silently compare CPU usage with their current host. I really think it is better to leave the new option on instead.

Better to have one demo the product on an equal CPU playing field with other hosts than to lose a customer who immediately thinks ” this is a no go…the CPU usage is much higher with Podium than my current host”

While I completely understand your admonitory tone (makes perfect sense), I think LiquidProj3ct’s suggestion to make it the default really will simplify the CPU issue and lower the learning curve considerably for anyone trying the demo.

Just look at how many recent posts on CPU usage there have been from new and even existing users.

Less time fire fighting these issues for you as well. Even if someone posted an issue with glitches I see no problem there as the CPU reading will mirror other hosts. So it is a very unlikely scenario as a user will almost certainly use similar plug ins in a new host (at least initially) so they are unlikely to complain about Podium having glitches compared to anything else…LiquidProj3ct’s excellent feedback seems to back this up.