Had another look, the afore-mentioned resetting I saw happens on playback start, not stop.
> Does anyone know what Podium sends on used MIDI output channels when Stop is pressed?
All Notes Off. Reset All Controllers. All Sound Off.
(I don’t know the details of your issue – sequence data, Podium MIDI configuration, MIDI routing, target instrument, instrument MIDI configuration, other potential MIDI sources… but something sounds off. But for what it’s worth, I’ve always found Podium incredibly precise, careful and respectful in its handling of MIDI data.)
Podium’s projects are containers for one or more arrangements; arrangements being the familiar timeline of audio and MIDI. (In other software, projects and arrangements are usually one and the same thing.)
So to create a new project:
Click the Project menu (button top left of screen) > New Project. Edit the project name if required, and if you want tweak the option to “create a new arrangement” automatically, then click the “Create project” button.
Then, to create a new arrangement:
In the middle of the screen, notice the “Contents – Arrangements, Sounds” area. If an arrangement is shown in this list, double-click it to go to the timeline. If the list is empty, click the “Contents – Arrangements, Sounds” header to show a drop-down menu and choose “New arrangement”. Da daa.
Use the tabs at the top of the screen (titled something like “New project”, “New arrangement”) to switch between project view and arrangement views.
Yeah minis aren’t critical for projects. I just mean their presence in a sample folder indicates which samples might be used in projects.
I did wonder if there’s a way of hiding them in Explorer. Something like [ http://www.sevenforums.com/customization/81717-hide-all-certain-file-type-folder-tree.html ] may do it, but haven’t tried yet. Overall I see minis in sample folders as a positive: it lets you know there are audio files potentially used in Podium projects. If like me, you’re prone to editing and reorganising sample libraries, that’s pretty helpful.
(Side note) For a minute, I did try to migrate sounds samples to the project folder before dragging them into a project. But since Podium’s Browser is such a sublime sound explorer, that workflow can be self-defeating. So now, I just run with it, until —
— At some point in time an an arrangement will be relatively complete/stable. Never mind minis, I’m going to need to collate all these scattered samples for reliable recall or archiving. An easy way of doing this is using the “New Arrangement as Unique Copy…” command on the Project page for a given arrangement. As per the Podium Guide, this “creates a copy of the arrangement including unique copies of all sounds and sequences used in the arrangement.”
Boom, all arrangement samples are copied from the original folder to the project’s arrangement subfolder. Self-containment, essentially. Once that’s done for all current arrangements, then I feel happy to ruthlessly purge all minis in my libraries and reorganise any sample folders, without breaking projects.
Sorry to interrupt 🙂 but which mda plugins aren’t being recognized? I had no real probs with them. Remember some of them are instruments which are assigned to a track via the “Source” dropdown/menu, and some are effects, assigned via + button as you know.
Hi, I’m not sure if this is the right place to post, as these issues affect 324 also, but I noticed a few low-hanging fruits (?) which could be addressed:
In the Sound Editor toolbar, the Scalpel tool doesn’t do any slicing. Instead, it functions exactly like the Pencil tool, editing the sample data. (Might just be a behind-the-scenes action mapping issue. I’ve just hidden the button for now.)
More trivially, the Help tooltip for the Pencil button is identical in both sequence editor and sound editor. I like this design efficiency, but we should note the different behaviour in each context: for example, in the Sound Editor, the Pencil tool cannot select and rearrange events, so the tooltip is confusing. (Okay this is nitpicking, sorry! But maybe some basic clarification in the text could be good!)
Hi, I gave Podium_325_x86_beta4 a test tonight, focusing on the new features reported here.
The custom metronomes worked nicely as described. A restart is required to hear them, which is to be expected. And there’s still just the two of them for now! No problems encountered using them with tempo changes in this version, and I couldn’t upset them even with manic loop range changes – using a 1/128 snap in arrange view, then moving loop markers around to create a nice granular-style scrub of the metronome sounds.
I was happy with how the new track tagging options worked. To note:
– The “Assign… in Loop range” option included the events within the range, and excluded the events that only bordered the range. That is exactly what’s you’d expect, and it works great.
– The “Assign… at Edit Cursor” option included events that spanned the cursor, and included events that began right on the cursor, but *excluded* events that ended exactly on the cursor. I’m pretty sure that is exactly how it should work, so yeah, it’s all good.
Tested on Windows XP SP3!
Everything is working perfectly again now, thanks/well done!
Hi, in case you didn’t know, the (zynewave.com) website has some issues. I have only noticed these recently, so it could be due to an automatic WordPress update breaking something? The issues are as follows, as observed in both latest Firefox and latest Chrome on Windows XP:
1. The navigation menu don’t function (no dropdown menu appears) on some pages, preventing the site from being navigated. This affects the following pages:
Zynewave > Welcome (home page)
Products > Podium
Products > Podium Free
Blog > Front page
Also affects http://zynewave.com/uncategorized/a-new-zynewave-com/#
2. Some featured videos don’t appear, instead leaving blank space. Occurs on:
Zynewave > Welcome (home page)
Products > Podium
Products > Podium Free
Also affects http://zynewave.com/uncategorized/a-new-zynewave-com/#
The Insert key is lush! Ctrl+C Ctrl+V works, but pastes at the edit cursor position. Use the numeric keypad arrows to move that around before pasting.
Hi, given the SDK changes, can Windows XP continue to be supported for foreseeable versions? Thanks.
Haven’t encountered this, but it’s either a problem with with your project, or with Podium’s configuration. If a troublesome project loads on startup, I guess it could behave like that.
To stop the project auto-loading, hunt down your Zynewave\Podium Free\Podium.ini file and carefully remove any project entry line(s) directly under the [RecentProjects] section, then save this file.
Now try starting Podium Free and now hopefully it won’t crash on launch. If you get that far, you can try performing the following steps to import the contents of the ‘troublesome’ project into a new project:
– Create a new project (let’s call it Project 2).
– Look at the project start screen and show the Browser tab on the left.
– In the Browser tab, browse to the location of your original project (Project 1.pod).
– Drag Project 1.pod over to Project 2’s “Contents-Arrangements, Sounds” section.
– Your arrangements etc. should get automatically imported.
– Hit Save.
– Exit Podium, then restart and see if this one crashes.
If it does seem okay, check your arrangements, effects etc. were fully imported intact.
If that doesn’t work, then you might want to try resetting Podium. If you can start the program at all, use Setup menu > Restore default setup. Or if you can’t start the program, backup your project folders, then maybe uninstall and reinstall Podium Free and try opening the project again.
Perhaps you clicked something in the Track Tags bar ([] Master [] Busses []Tracks) which controls the visibility of tracks?