ZynewaveBeta 3:
• The title bar has an auto-hide option button when the window is maximized. When auto-hide is enabled the title bar can be shown by moving the mouse cursor to the top of the screen.
This makes it possible to reclaim the added vertical space occupied by the new title bar. I added the title bar because it was getting a bit overcrowded with the menu buttons in the middle of the inspector, browser and project page tabs. The new layout is a bit cleaner. I also didn’t like the fact that the menu buttons were moving around when you opened/closed the inspector.
Zynewave@aMUSEd wrote:
I can bounce while I’m playing?
While you’re recording & playing, yes. Let me offer another suggestion instead of the bus send/return: Add your VSTi track as a child to a new group track, and then set up the group track for realtime bounce recording. That way you have it all neatly together. Also note that the realtime bounce recording only is working if you have some events on the timeline. So you’ll need to set a marker at the end of the timeline where you want to stop.
ZynewaveYou’ll need to use the bounce feature, as normal audio recording only works for audio interface inputs.
If you need to have the audio recorded on a separate track from the actual VSTi track, then you can use a bus send on the VSTi track, and assign the bus return on a second track. Then set up the bus return track for realtime bounce recording.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator.
Hmmm, let me ask… Do you have anything else planned then for the big empty space right above the track headers?
No, not besides the display of the marker name, tempo, time-sig and scale info that is currently displayed there. You’re of course free to remove the track toolbar, or move it directly above the tracks region. I think the track filter feature will justify using up space for the new track toolbar, but I need to experiment with that.
I’m also not keen on the bean-shaped 80’s sci-fi device look and placement of the transport bar elements. This time there’s no way to keep the old setup, so I guess I’ll have to get used to it…?
Specify please: Is it the fact that the buttons are no longer rectangular, that they are joined in a button bar, that the elements in the toolbar have been rearranged?
Zynewave@H-man wrote:
I like the new button shapes on the toolbar(s) but the edit icons get blury when the toolbar region height is increased.
IMHO the default size is too small which is why I changed them in the first place.
That’s not new for 2.21 though. The tool buttons are actually a bit wider than previousy when they are joined in a button bar. I agree with the blurry tool icons. Unfortunately they were created in a small resolution, so I will need to redraw them in high resolution to get rid of the blur.
ZynewaveBeta2:
• Added a title bar at the top of the project window. This holds the menu buttons that previously were placed between the inspector and project page tabs.
• Moved the browser page tab next to the inspector tab. Selecting either the inspector or the browser will automatically hide the other.
• Moved some of the commands in the Setup menu into a new Window menu.
• Updated the button layout in the inspector and browser pages.
Zynewave@Ohrbruch wrote:
>Note that it starts out in the arrangement menu, which may not be noticeable if the Zoom device does not have a display. You need to turn power on in an arrangement to make the faders active.
Hmm… I’m not sure If I got this right. Do you mean turning the Zoom on while I’m in an arrangement?
No, I mean make sure the power button in the arrangement editor is on. But it is also worth a try to power on the Zoom device while Podium is running, and if that doesn’t work, start Podium while the Zoom is powered on.
The MIDI indicator is lit green when I move the faders… but I can’t
find a “Follow control surface” menu item…
I assume you are looking for it in the mixer menu. If it’s not there then the Zoom is not auto-detected by Podium as a MCU compatible device. You can also check if the MCU mode is working by looking for the semi-circle channel indicators on the mixer strips, as illustrated in the guide.
Check the Zoom manual, and see if there is some option in the device setup menus where you can configure the MCU emulation.
Zynewave@soundquist wrote:
What’s the procedure for safely trying out Betas? The download is just a executable, should it be run from the Zynewave folder?
You can run it from anywhere you like. If you want to ensure that the “program files/Zynewave/Podium/VSTPlugins” folder is detected when Podium starts up, you can copy the beta exe to the program files/Zynewave/Podium folder, next to the installed Podium.exe.
ZynewaveIf the zoom is connected via USB, make sure you enable both the MIDI input and output device for the Zoom in the interfaces dialog. Set focus on the Zoom MIDI output device and make sure the “detect mackie…” option is enabled. I just checked with my MCU in Podium 2.20, and the device is detected ok. Note that it starts out in the arrangement menu, which may not be noticeable if the Zoom device does not have a display. You need to turn power on in an arrangement to make the faders active.
ZynewaveAs long as NI acknowledges it’s a result of their design, and the issue is present in almost every other host, I think it’s a bad investment of my time to look into this. There are a lot of new features I’d rather be working on.
Zynewave@pj geerlings wrote:
Where are they documented other than in these forum pages?
I’ve been neglecting the Podium guide, if that is what you mean. The video that accompanied 2.20 is a good way to illustrate new features I think, so I’ll probably do one for 2.21 as well.
ZynewaveThanks for the input everyone. I’ve uploaded a new 2.21 preview/beta so you can try out the new project/sound name behaviour.
Druid, I pondered your wish to call folders by kanji, and then decided to go against you on this one :P. I’ll let you have the final word on another future feature 😉
ZynewaveIs it the same VST parameter number(s) that gets recorded both when using the morph pad and the quick buttons?
If so, then I’m guessing the problem lies with the way that Kore uses the VST BeginEdit/EndEdit commands to notify about parameter changes. These commands are used to allow the host to ignore automation playback as long as the user has grabbed a control in the plugin. That it works in Acid could be because Acid ignores the BeginEdit/EndEdit system. Just guessing. I also read in your linked topic that NI responded with “This is a known bug of Kore 2 and will be hopefully fixed with a future update”.
Zynewave@H-man wrote:
Now,acknowledging that the program hasn’t asked for any other input, how safe you feel about clicking Save Project?
The original project is of course safe, Podium/windows will force a folder verson (ie. H-Proj1_01) however you still have your second H-Proj1.pod file that you’re stuck with, regardless of whether you change the Project name or not.
I’ll make the project properties dialog pop up after you’ve created a new project from a template. With the name label now reading “Project name (used as filename when the project is saved)” it will be more obvious that you’re entering the filename. Note that the project is not saved at this point. The “New file:” path shown in the project start page shows the eventual file location when the project is saved for the first time. You can change the project name repeatedly before you save, and the “new file” path will change.