Zynewave's Forum Page

@druid wrote:

When choosing to create default folder or use a different one, it would be more helpful if it had a browse option where a user could select it straight up. Or if it detected one already set up in the podium.ini, it would just not display the question at all! (I didn’t get to test that though, because I made a fresh install, so podium.ini was not there.)

I’ll consider adding a “Browse” button. The dialog should not appear at all, if the setup file already contains valid folder assignments, or if Podium detects existing default folders created on a previous run.

The installation is still creating the [Program Files]Zynewave folder. I always install to c:ongenpodium so I don’t know why it’s creating it. Maybe because you have two folders deep as default, in order to show the potential second folder, it must create the first? That seems likely; it never makes the Podium folder, only the Zynewave one.

I’ll keep that in mind when looking for a new installer tool. I did not realise that the “Zynewave” parent folder was created even if you selected a different install folder.

Thanks for the feedback.

@druid wrote:

Hey Frits, I’m just wondering why this release was even announced on KVRAudio but it’s still not on the front page of the Zynewave page? It’s no problem, just making sure you didn’t forget!

Thanks. The home page is updated, and a new demo version is up.

@pavouk100 wrote:

I have also one FR regarding ‘Follow play cursor’ option. It would be nice if view would not scroll in case that the end of the arrangement/loop(if activated) is already present on the screen, but on the very right end. Most prominent example is doubleclicking navigator (ie. zoom exactly to the whole arrangement) and let the whole arrangement play. The view scrolls when play cursor reaches cca 3/4 of the arrangement length, although scrolling in this case is actually distracting and counterproductive.

I believe it already would not scroll if the loop end was within the display range, but I’ve now extended it so that it also won’t occur if the arrangement end is within range (unless recording is enabled).

@all:
2.17 beta1 is uploaded. Please give this a try, and let me know if you find problems. If all is well, I plan to release it this weekend.

@Conquistador wrote:

Possible Bug…

Maybe this has been fixed already in 2.17 but…if you click on either side of the Navigator (during playback) PDM’s (Podiums) gui will freeze up completely. I can hear playback but several seconds pass before the GUI returns to normal. Also playback stopped after the GUI recovered here.

Confirmed. It can happen if you have enabled the “follow play cursor” option in the view menu. I’ll fix this.

@Pigini wrote:

Would it be possible to have one vst-folder within the podium directory without needing a drive letter in the path? When using a usb stick, the assigned drive letter keeps changing from system to system.

When possible, the Podium.ini setup file will store folder paths using relative references, such as: [program]Vstplugins. So if you have copied projects, plugins etc. to subfolders of your Podium folder on a flash drive, then they should load even if the drive letter changes.

Thanks for the input. Here’s a screenshot of the revised startup dialog:

So, the new default folder layout is a “Zynewave Podium” folder created in the users Documents folder. Within are two subfolders: “Projects” and “Library”. The Library folder has further subfolders for project templates, track templates and hardware definitions, like in previous Podium installations.

Further additions to the changelog:

• The installer no longer creates the “Zynewave Podium Projects” folder in the Documents folder. Instead the user is presented with a “project folder preferences” dialog the first time Podium is started. The user can let Podium build the default folders, or configure the folders in the preferences.

• Removed the “Relative to project path” option from the sound properties dialog. Sound files are now always referenced with a relative path in the project file, if the sound file is located within the project folder.

• Removed the “Relative path” plugin file option from the Device Mapping properties dialog. Plugins are now always referenced with their full path in the project file.

• Multiple VST plugin scan folders can be specified in the preferences dialog.

• Added “automatically search for missing plugins when loading a project” option to preferences. This option is enabled by default.

• Redesigned the “create new project” page. The page can be scrolled vertically if it does not fit within the window. This can be necessary with for example 1024×600 netbook screen resolutions.

• The track inspector embedded in the project window is automatically opened/closed when an arrangement editor is opened/closed.