H-manH-manA little late to the party but thanks once again Frits. Enjoying the changes here.
Ben 😀
H-man1. I really like the way that the Inspector and Browser windows store/remember their window size.
2. I’m a Bean-Button man …who would have thought?
3. Let’s have at those new track toolbar features! 😈 😛 😈
H-man@Zynewave wrote:
• The name entered in a project or sound properties dialog is now linked to the filename. When a new project is created, the project properties dialog shows “Project name (used as filename when the project is saved)”. When the project has been saved the name field is made read-only and the caption reads “Project name (same as filename)”. The same applies to the name field in the sound properties dialog.
• Creating a new project from a template will show the project properties dialog.
Nicely done Frits, very happy with these changes/additions here. The processes around Project Templates is more structured/guided now. I hope this minor loss of flexibility doesn’t cause inconvenience to others. 🙂
H-manI 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.
H-manThanks again Frits.
Would it be possible to disable Save Project As… for projects that do not yet have a folder? Some sort of stateful trigger?
Just a thought… :-k
H-man@Zynewave wrote:
@aMUSEd wrote:
To me the overall organisational scheme is where the problems lie.
The issue with “save project as” and other file management features, is something I’m going to revise at some point. These issues are however not directly related to the question of how project and sound names should be handled.
Druid, are you there? Given these pros/cons of having separate project and sound names, it’s time for your closing argument 🙂
Ha-ha IBTL? 😆
H-manThere are a number of issues on the table now and I don’t want to mega-post so I”ll stick to the one that causes me some worry.
An example:
Use the normal process to create a New Project, set it all up and save as a Project template (H-Proj1).
Okay, now work on that project for 100+ hours
Save the project (not as a template tho), then go to Projects ->Project Templates ->New Project ->H-Proj1
(The result is a new project with the H-Proj1.pod file)
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.
@aMUSEd & Conquistador – You may realise but I would point out that an auto-save feature (if implemented) won’t work to well with Save Arrangement as… workflow. Cloning an arrangement before changing it would be the only option here.
Who hasn’t overwritten a document accidentally working this way?
H-manCool. Sounds like it will remove the ambiguity around file/project names.
Thanks Frits 🙂
H-man@aMUSEd wrote:
This is why we need a “save arrangement as”
(but don’t get rid of “save project as” since at the moment it’s all I have to save versions of work in progress)
Nah I was just making lite of the fact that “Save Project As…” seems like the right thing to do but doesn’t set things up as well as “Save Project”.
(Save Project seems downright dangerous due to the fact that all filenames are the same ….a leap of faith?)
I would suggest the pop-up dialogue raised by Frits earlier in this thread however that kinda goes against Podiums work flow of not creating the folders until the project is saved. A feature I like due to the fact that if a new project is not worth saving, you can start a new one or close the program and there are no files and folders to clean up.
H-manhmmmm …now it is creating the folder 😕 Where’s LiquidProj3ct when you need him? 🙄
@Zynewave wrote:
I can. If for example you have created a template called “Sketches”, then each new project you create on that template will be called “Sketches”, “Sketches_01”, “Sketches_02” etc.
I’ve noticed that the Project folders will auto version due to Windows not liking two folders of the same name at the same level, but the Project Names in Podium’s Recent Project List would be Sketches, Sketches, Sketches unless you change the Project Title to match.
But that’s just splitting hairs really, it’s pretty intuitive to manage.
If the program creates the folder for the .pod file and arrangements then that’s the desired result.
May the best thing to do would be to disable the “Save Project as…” 😉
H-man@Zynewave wrote:
With “Load Project from Template” do you mean the “Project > Project Templates > New Project” submenu?
Yes, that’s the one.
@Zynewave wrote:
Using this function will set the initial folder and filename to the name of the template, as displayed in the “new file” line in the project panel on the start page. If you open the properties dialog and enter a new name for the project, then that name will be set in the “new file” line. Only when you save the project the first time, is the project folder and file created.
Okay, but somehow the result I get is that once saved, the .pod file and the arrangement folders appear one level under the Project folder (ie. z:Zynewave Podium Projectstest_from_temp.pod and z:Zynewave Podium Projectstest_arrangement_one), and not in their own Project folder?
The behaviour you describe above is what I expect should happen.
I guess my main concern is projects/arrangements being overwritten. Could this happen if I save the new project and forget to rename it first?
@Zynewave wrote:
Do you want the project properties dialog to automatically pop up after you create a new project from a template?
Probably a good way to approach it. I can’t think of a situation where I would want a new project (from template) to have the same name as the template.
H-manFrits, these updates are fantastic. The new editors and auto-assign/drag & Drop for the inputs make things even faster in Podium.
I found that after never using it, I have switched to using the embedded editor exclusively.
Powerful stuff =D>
H-man@druid wrote:
I also have to say, though, that it’s somewhat frustrating to make a few UI settings adjustments, and then when I want to load the default to get the new features, but want my little settings still set, I must set them each time. I’m not sure how, but I feel like there should be a way to have loading default setups not replace absolutely everything, or a way to load the newest default setup, what changed from the last one, so that other adjustments are not altered from user settings.
May be difficult to code for but …+1
H-manThanks Frits!
And this was supposed to be the ‘easy’ stuff after the previous release. 😉
Off to play.