Topic: Podium 2.00 Beta

Viewing 15 posts - 16 through 30 (of 52 total)
  • #12500
    H-man
    Participant

    @Zynewave wrote:

    As a natural extension of the new merge project feature, I’m now experimenting with creating a new track template system that is file-based. The benefit will be that the track templates can be used across all your projects. Saving a track template will then no longer create a template arrangement in the project, but instead save the track in a .pod file in a new “Track Templates” folder in the library. The paths to the project template and track template folders will be settable in the preferences.

    What do you think. Would you mind that the old track template system is removed in favor of a new file-based template system?

    This sounds awesome! Couple of questions tho…

    Would I be right in assuming that the new Templates function would be available from the right-click menu on the actual track?

    Groups, tracks and effect tracks can be turned into templates?

    Custom patches (not saved to instument or .fxb) would be retained?

    and,

    Big YES for still being able to save events/clips as well.

    Also great additions for this release (I must have said that many times now 🙂 since 1.77).

    #12501
    H-man
    Participant

    @Zynewave wrote:

    • Support for drag-scrolling in the editors when dragging the mouse outside the display area. The scroll sensitivity can be adjusted with two new settings in the preferences dialog: “Drag scroll acceleration width around editor” and “Drag scroll maximum pixels per second”.

    Please post your experiences with these new features.

    May have under-sold this one a little Frits :wink:. Either by design, (well let’s just call it that), the new drag-scolling feature enables you to move back and forth through the arrangement by grabbing the play cursor and running it off the screen (right or left of course).

    Combined with the “Link Edit cursor to play cursor” option and the ability to start/stop play by double-clicking, and the fact that the cursor jumps to wherever you click on the time-line aaannnddd that the mousewheel will zoom horizontally around the mouse pointer when over the timeline

    ….well navigaing the arrangement just go a whole lot faster and easier 😀 .

    Definately worth a mention on the 2.00 feature list IMO.

    Ben

    #12502
    sam c
    Participant

    sounds great frits!

    #12503
    Zynewave
    Keymaster

    @H-man wrote:

    @Zynewave wrote:

    As a natural extension of the new merge project feature, I’m now experimenting with creating a new track template system that is file-based. The benefit will be that the track templates can be used across all your projects. Saving a track template will then no longer create a template arrangement in the project, but instead save the track in a .pod file in a new “Track Templates” folder in the library. The paths to the project template and track template folders will be settable in the preferences.

    What do you think. Would you mind that the old track template system is removed in favor of a new file-based template system?

    This sounds awesome! Couple of questions tho…

    Would I be right in assuming that the new Templates function would be available from the right-click menu on the actual track?

    Groups, tracks and effect tracks can be turned into templates?

    Custom patches (not saved to instument or .fxb) would be retained?

    and,

    Big YES for still being able to save events/clips as well.

    Also great additions for this release (I must have said that many times now 🙂 since 1.77).

    Yes to all those questions.

    #12504
    UncleAge
    Participant

    @Zynewave wrote:

    @H-man wrote:

    @Zynewave wrote:

    As a natural extension of the new merge project feature, I’m now experimenting with creating a new track template system that is file-based. The benefit will be that the track templates can be used across all your projects. Saving a track template will then no longer create a template arrangement in the project, but instead save the track in a .pod file in a new “Track Templates” folder in the library. The paths to the project template and track template folders will be settable in the preferences.

    What do you think. Would you mind that the old track template system is removed in favor of a new file-based template system?

    This sounds awesome! Couple of questions tho…

    Would I be right in assuming that the new Templates function would be available from the right-click menu on the actual track?

    Groups, tracks and effect tracks can be turned into templates?

    Custom patches (not saved to instument or .fxb) would be retained?

    and,

    Big YES for still being able to save events/clips as well.

    Also great additions for this release (I must have said that many times now 🙂 since 1.77).

    Yes to all those questions.

    I think this will help me out greatly. I do voice over projects and spoken word recordings from time to time. Having the ability to pull up a track template that I have already profiled for a certain person is a lot better than having to pull up an entire arrangement/project and strip out what I don’t need. This could turn into one of the serious strong points of the app, well, for me at least 🙂

    #12507
    Mike G
    Participant

    Just adding another Yes please to this!
    Thanks,
    Mike G

    #12508
    rinxai
    Participant

    @H-man wrote:

    ….the new Templates function would be available from the right-click menu on the actual track?

    Groups, tracks and effect tracks can be turned into templates?

    Custom patches (not saved to instument or .fxb) would be retained?

    This would be a really marvelous boost for faster work flow, making the setting up and building of new arrangements a snap once a custom library of templates have been saved.

    8)

    #12529
    Zynewave
    Keymaster

    Beta3 is up:

    • Introduced a new file-based track template system. This replaces the previous per-project template system. The templates are managed in the new “Track Templates” submenu of the track context menu. There are commands for saving the current effect track, the effect chain or the entire track or group track complete with automation tracks. The save template dialog has an option for including track timeline events in the template. All saved track templates are available for recall in submenus: “New Track”, “Insert Effect Chain” and “Replace Effect Chain”.

    • Added “Track Template” submenu to the tracks region menu button below the last track

    • The location of the project template and track template folders can be set in the preferences dialog.

    • A warning message appears when Podium starts up if some of the user configured folders could not be found. The preferences dialog is subsequently opened where the invalid folders are highlighted with red background.

    • If you organize your project and track template files in subfolders, Podium will show the files in submenus named after the folders.

    • Minor changes to the track context menu. Moved some commands to a new Properties submenu. The names of currently assigned objects are appended to the label of the Input, Source, Preset and Parameter submenus.

    • The older track context menu used in the mixer and expanded mode arrangement editor has been replaced with the newer compact track menu.

    I think this will be enough for the 2.00 release. I’ll spend a few more days on testing. Please report if you find any problems with the track templates, or if you have suggestions for improvements.

    The Podium 2.00 installer will create “Project Templates” and “Track Templates” library folders instead of the old “Templates” folder. If you run the beta3.exe, those folders are not pre-created, so you will be presented with the Preferences dialog where you should specify where you want your project and track templates stored.

    #12536
    Conquistador
    Participant

    Lovely changes in v.2! Fantastic, thanks Frits. :mrgreen:

    But I have a problem…

    I would like to try out the beta but I noticed on Vista I do not have the option to run the installer “…as an Administrator”.

    In Vista that process appears to allow an application to properly install (admin rights to access and change the registry e.t.c) and avoid problems running an app even if it appears to have installed properly.

    So far that has worked flawlessly for me with 32bit apps (on Vistax86 )and 32 bit and 64bit apps (on Vista x64).

    I am trying to install 1.99 on Vista64 (recent upgrade) and every other installer or set up file appears to have the small admin Vista shield on them but the Installer for 1.99 and I am guessing 2.00 does not have this.

    Should I still install 1.99 (+ 2.0 to test) or unless I can run the installer (get the right click option to appear that lets me run as an administrator)is it not advisable to try to install them ❓ 🙁

    I am going to download v.2 now to see if the installer is different to 1.99 or at least lets me run the installer as an Administrator.

    I am trying to remember if your installers needed this on Vista x86.

    As for the feature set for v.2

    There is only 1 other item I really think is needed and would hope you do add it to v.2….

    If I have a crash in Podium all my work is lost. It could be 1 minutes worth or hours. Podium seems to save your work properly only when you exit the application. Even if I save the project in two places with different names I still lose changes in both projects! 🙁

    Sometimes a Podium prompt appears describing the problem but either way any changes are lost.

    If there is some way to add a save process (autosave or versioning) that can survive a crash it would be easily as important as the current v.2 features. One can have many features but if your work is lost (should the application crash) it can negate many useful features IMO.

    Live, ACID, Sonar all provide either a way to recover a crashed project when you start the app up again or… project versioning.

    Your feature focus for v.2 has been simply spot on so far, hopefully you will complete the feature set with a more reliable process of keeping projects from being lost please, thanks! 🙂

    #12537
    acousmod
    Participant

    If I have a crash in Podium all my work is lost. It could be 1 minutes worth or hours. Podium seems to save your work properly only when you exit the application. Even if I save the project in two places with different names I still lose changes in both projects! Sad
    Sometimes a Podium prompt appears describing the problem but either way any changes are lost.
    If there is some way to add a save process (autosave or versioning) that can survive a crash it would be easily as important as the current v.2 features. One can have many features but if your work is lost (should the application crash) it can negate many useful features IMO.
    Live, ACID, Sonar all provide either a way to recover a crashed project when you start the app up again or… project versioning.

    I have taken the habit to save evry 5 minutes… So yes, I will appreciate an automatic crash recovery too !
    By the way, a simple Save icon will also be appreciated since it will avoid to have to jump to the keyboard or to the project menu. And it might not be too hard to implement 😉

    #12538
    acousmod
    Participant

    There is only 1 other item I really think is needed and would hope you do add it to v.2….

    I would have another one 😳 : automatic scan of subfolders !
    Yes, I know, this is a very old request, but I think that it would be nice to have it together with the new template structure and folder paths (and for all the other reasons too…).

    #12539
    Conquistador
    Participant

    @acousmod wrote:

    By the way, a simple Save icon will also be appreciated since it will avoid to have to jump to the keyboard or to the project menu. And it might not be too hard to implement 😉

    Yes please 🙂

    would have another one : automatic scan of subfolders !
    Yes, I know, this is a very old request, but I think that it would be nice to have it together with the new template structure and folder paths (and for all the other reasons too…).

    I thought Podium already scanned subfolders, if not then yes that would be useful especially with the other v.2 features….definitely.

    @Frits

    Forgot this one as well… sorry 😛

    Auto copying imported audio or midi files imported into a project folder. Pretty much every host I know of does this. I keep thinking Podium already has this feature for some reason.

    I have often run into issues where Podium cannot find a file it was referencing that has since been moved. It can search for it but having to copy every file one imports into the arranger, into a project folder manually can be a major hassle.

    A user could be asked with a simple prompt if they want to copy an imported file (midi or audio) into the project folder, perhaps with an option to ‘remember your preference’ or a global set and forget option instead.

    Run as Admin issue…

    Well the 2.00 beta does allow me to run the installer as an administrator?!?!? So why does 1.99 not allow me to do the same? I am reluctant to install 1.99 if it will cause problems later. Or am I missing something?

    #12541
    UncleAge
    Participant

    @Zynewave wrote:

    I think this will be enough for the 2.00 release. I’ll spend a few more days on testing. Please report if you find any problems with the track templates, or if you have suggestions for improvements.

    I’m going to jump into this for a few hours and see if any issues come up. I’ll report back.

    Also, I’d like to say thanks for tackling this issue.

    #12544
    Zynewave
    Keymaster

    @Conquistador wrote:

    Should I still install 1.99 (+ 2.0 to test) or unless I can run the installer (get the right click option to appear that lets me run as an administrator)is it not advisable to try to install them ❓ 🙁

    I am going to download v.2 now to see if the installer is different to 1.99 or at least lets me run the installer as an Administrator.

    The 2.00 beta is just a zip with the Podium.exe. You should install 1.99 before running the 2.00 beta. I never had to use the “run as administrator” with the Podium installer on Vista.

    There is only 1 other item I really think is needed and would hope you do add it to v.2….

    I don’t plan to add more features for 2.00. When I said I welcomed suggestions for improvements this was in relation to the track templates. It’s more than a month since 1.99, and I would like to go back to a more frequent release schedule, so no more new features for 2.00.

    #12545
    Zynewave
    Keymaster

    @acousmod wrote:

    There is only 1 other item I really think is needed and would hope you do add it to v.2….

    I would have another one 😳 : automatic scan of subfolders !
    Yes, I know, this is a very old request, but I think that it would be nice to have it together with the new template structure and folder paths (and for all the other reasons too…).

    What do you mean with automatic scan? And what subfolders?

Viewing 15 posts - 16 through 30 (of 52 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave