Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@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.
ZynewaveKeymasterThanks 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 😉
ZynewaveKeymasterIs 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”.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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 🙂
ZynewaveKeymasterAre you Kymeia on that thread?
Since I don’t have Kore2, can you elaborate on what you mean with “struggles”?
ZynewaveKeymasterLet me bring in an old post by acousmod from another topic:
@acousmod wrote:
One more thing that is not really related to events names, but that could benefit from it : you have based the audio events names not on the file names but on some chunk inside the files.
The problem is that some softwares that create wav files does not write this code, so the files appear in Podium with no name at all, which is quite unusual…
Another problem is when we rename a file in a Windows explorer and that Podiums of course shows a different name.
So, together with an event name parameter, I think that it would be good to base the names of audio events on their files names like in any other host I know (the same for the Project names that appear in the Previous projects list).
Perhaps that you had seen some advantage to base them on special internal code, but the only result I see is that introduces potential confusion…
Why not make things simple ? 😉
Thanks !That makes sense to me, and for a long time I’ve had the intention of locking the project and sound names to their filenames.
Can you describe some cases where you would want the project or sound names to be different from their filenames?
If you want more information in the project name than what you want in the filename, then you could alternatively use the project stickie note to store the extra information.
ZynewaveKeymaster@druid wrote:
What happens if I wanted to change the name of a project, as I often do when I wantto write something but have no title for it at that time and just write a temporary one?
What happens if I rename the file? Does it change the project name as well, then? If so, does nobody want the ability to save different project and file names? What if, for instance, I wanted to use a colon in my project name? What happens then?
Well, :(, those are some of the reasons why I originally made it possible to have project and sound names independent of their filenames. But unfortunately this flexibility has frequently been a source of confusion. Most people don’t want to maintain two names for the project, and so often ignore the project name, which in turn leads to the confusion when working with several revisions of a project.
Renaming the project/sound files will change the project/sound names.
Do you feel this simplification is a step in the wrong direction? Other users care to comment?
ZynewaveKeymasterI’ve made this change for 2.21:
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.
ZynewaveKeymaster@aMUSEd wrote:
I know this isn’t a priority but at the very least can you fix it so that when I save a project using “save project as” it gives it the name I saved it with in the Recent projects window so I know what I am opening? (I seem to end up at the moment with half a dozen projects all with the same name even though the filenames are different).
By coincidence, five minutes ago I made a comment about this in another topic. I’ll just show the project filename instead of the project name in the recent list.
ZynewaveKeymasterDo I need to do the MIDI in Podium in order to be able to bounce?
No, but as a test, try to place a marker event at the time position matching the duration of your Reason song. Once you’ve placed the marker event, do you see the “B” button light up in red and the waveform lines on the timeline? Remember that you need to activate the record button on the transport as well.
ZynewaveKeymaster@H-man wrote:
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.
I’ll change that eventually. Probably I’ll just show the filename in the recent list.
ZynewaveKeymasterWhen I start a redesign of the track headers (hopefully within a month or two), I’ll make room for plugin editor buttons. The plan is to get rid of the overcrowded UI controls in the track headers, and instead present them on a larger popup panel.
ZynewaveKeymasterThanks. The red lines don’t appear because your sample arrangement does not have any events on the timeline. The waveform extends to the end of the arrangement, so if I place e.g. a marker event at bar 37, then the red waveform extends to bar 37.
Could that be the problem with your real project file? Don’t you have any MIDI events on the timeline that plays the Reason synths?