Notes to Frits
After a reorganizing of my folder with samples on the hard drive, and the subsequent opening of one of my projects, Podium could not find the samples used in that particular project, for now their paths are changed and therefore reported as missing. So this was the occasion that drew my attention to a particular issue and made it obvious.
Apparently Podium links directly to the source files, not making their copies.
This can be very troublesome for people making collaborations, mobile users, those with more than one machine, the list goes on and on…..
After locating and loading them (took me a great while) I assumed that it would be really easy to copy them once and for all to my project folder from the arrangement section by means of a simple right button click, but….no, it is not possible.
For now the only workaround is to manually find the samples and copy them to the desired destination, then relink them in Podium in order to avoid such problems. But in this case this procedure must be repeated every time a new sample is introduced to the project. Not very intuitive.
A possible improvement:
When saving a project, Podium to save a folder , (not only the .pod file) in which it will copy all the waves included in the project, for an example in a “Samples” sub-folder by default, as well as arrangements, and the project file itself, bounces and so on. So every time a sample is imported to the project, it will be copied there. In other words, a self-sufficient project folder, making things safer and cleaner, and minimizing the risk of losing anything. In this way renaming of wave files would be much easier as well.
I really hope pointing this and the suggestion will not appear impudent.
Peace
CC
I only have started to use Podium Free about a month ago, tried things and was impressed with it.
There are still many things to be implemented, and so now I give a big
+ 1
to this particular idea!
+1 here, but as one of several options. I like what the Shortcircuit sampler did with path variables, if I may quote from the manual:
When a sample is first loaded into shortcircuit, the path and filename of the sample are stored for later reference. This is later used for session recall and when storing a group or multi (remember, shortcircuit never saves the samples, they are only referencedso they still need to be there next time around).
But before storing the path, it is compared with the user configurable path variables. If a part of the path matches one of the path variables, that part is replaced with the matching variable name. When the sample is loaded the next time, the path variable is replaced with the corresponding path again, giving the correct filename to the filesystem.
The purpose of this system is that if a directory containing samples are moved to another harddrive and/or directory, the path variable can be updated to match.
Example:
$path1 is set to “c:samples” in the shortcircuit configuration.
The sample c:samplessubdirsample.wav is loaded. Internally it is remembered as $path1subdirsample.wav
The dir c:samples is moved to d:samples. $path1 is updated to match.
The filename $path1subdirsample.wav will now load the sample d:samplessubdirsample.wav instead.
End quote. Would be good to have a few choices eh?
Would be good to have a few choices eh?
Oh, definitely so! The beauty of Nature ( and the Universe by extension ) lies in diversity.
Therefore ideas and statements are never absolute and always open to further development π
So thanks 4mica for bringing forth a different alternative.
Initially my idea was to suggest a right-click option in the arrangement section, something of the like – Copy file/s to project folder or similar.
So, here’s a counterpoise to my own post :D, and a third option.
Peace
CC
+1
Yes this has been on my mind for some time… I bounce + import tons of small audio clips for songs…
What I do for now is when I bounce a midi part to audio… I have to manual trim it down and then crop it. Then I double-click it and save it as a sound file inside my project folder… its a lot of steps ….
audio files that I import into the arrange screen I have to manually save as well.. god forbid i forget to… would have holes missing in songs if I ever moved drives around…
an easy way to pull everything into the project folder would make things so much easier, and save time…. that being said Podium is dope tho..
– also is it me or are the project files a little large… 1.8megs each? at least for me… I save multiple copies as I go along – just in case
@CymaticCreation wrote:
This can be very troublesome for people making collaborations, mobile users, those with more than one machine, the list goes on and on…..
Agreed.
It has been a problem for me for a very long time. I know Frits to be fair has had many other FR’s (many of mine as well as others) that he has implemented in the past but hopefully he can re-visit this FR. I also brought it up previously on this thread.
He has done an amazing job trying to implement user requests (sometimes at very short notice) over the years. I just hope he can slice out some time for this FR π
I also brought it up previously on this thread.
Sorry, I wouldn’t have created a new topic if I knew it already existed…yet, all this for a reason I suppose.
Seeing your posting date Conquistador, made me a bit concerned, and dare I say shocked. It was 4 years ago. And still no improvements in that field whatsoever. Makes me wonder, at the very least.
Hm…
Peace
CC
While the timeframe since that older thread is some time ago…looking at that alone (time) can be misleading. Since that time (and before that) Frits has had to juggle close to 100’s of FR’s from various users maybe more.
I have to say he is easily one of the most responsive devs out there but…he is only one man π
He has to prioritise things and attempt to please everyone = an impossible task for anyone to achieve but he has IMO done an amazing job trying to keep everyone happy.
I’ll put it another way…the number of FR’s he has implemented (many at short notice) far outwieghs this single FR not being implemented yet IMO. π
I really would love to see some way to auto copy data in Podium ASAP but…since I joined in 2005 I have witnessed a remarkable level of care, focus and design skill to match any dev. It might seem as if he simply ignored the FR but beleive me he has granted many FR requests since then. π
An FR might seem easy from the outside or small or one that should be a no.1 priority or similar but as the dev he has to make the final call on many different FR’s while maintaining the code base in a way that keeps everything stable an reliable. π
@CymaticCreation wrote:
When saving a project, Podium to save a folder , (not only the .pod file) in which it will copy all the waves included in the project, for an example in a “Samples” sub-folder by default, as well as arrangements, and the project file itself, bounces and so on. So every time a sample is imported to the project, it will be copied there.
I prefer Podium references a sample location to minimise consumption of disk space.
It is also a system which ensures project files aren’t corrupted due to an orphaned sample (the same applies with plugins) π
@4mica wrote:
Would be good to have a few choices eh?β¦
I like what the Shortcircuit sampler did with path variablesβ¦
β¦user configurable path variables. If a part of the path matches one of the path variables, that part is replaced with the matching variable name. When the sample is loaded the next time, the path variable is replaced with the corresponding path again, giving the correct filename to the filesystem.
This adaptive approach would aid in repairing broken references.
That said, I have made the mistake of editing a referenced sample outside of Podium. This left the project playing the processed version.
I understand your frustration CymaticCreation when you wish to archive or transport your project.
@bbreakz wrote:
an easy way to pull everything into the project folder would make things so much easier, and save time…
I’d like a ‘Copy Arrangement Samples‘ right-click menu entry on an arrangement object in the project start page. Currently you can double-click a sample object, in the project start page, to open the master audio editor then save the sample within the project directory (or anywhere else).
Conquistador wrote
I have to say he is easily one of the most responsive devs out there but…he is only one man
Yes, I am perfectly aware of that and can only guess how difficult and maybe from time to time overwhelming this whole job can be for a one-man-army. Didn’t want to sound cruel or harsh. My exclamation was rather an observation went out loud.
levendis wrote
I prefer Podium references a sample location to minimise consumption of disk space. It is also a system which ensures project files aren’t corrupted due to an orphaned sample…
Well, it was the very motivation that drew me to come forth with my suggestions, because after a rearranging of my samples folder, the project ended up with tons of blank spaces exactly due to “orphaned samples”, since Podium had referenced them to a sample location that no longer existed.
I thought that creating their copies in a dedicated folder would eliminate such risks for good, hence the whole topic. π
levendis wrote
I’d like a ‘Copy Arrangement Samples’ right-click menu entry on an arrangement object in the project start page.
You put it much clearer than i did in my second post on the topic. Maybe this will be the best solution, a neutral one, leaving this action to the user instead of automatically copying files.
π
Peace
ॐC☸Cॐ
@CymaticCreation wrote:
You put it much clearer than i did in my second post on the topic. Maybe this will be the best solution, a neutral one, leaving this action to the user instead of automatically copying files.
πPeace
The problem I would personally have with the manual approach is having to click on a right click command *every* time I import an audio file or even after a series of imports. I would much rather have Podium manage that instead with a simple option like this…
It’s likely Frits may be able to offer 2 options manual and auto copying. Might work best that way for all. π