Infinitoar.
InfinitoarHello Frits I have a small issue, nothing major so I will get to the point.
-In Podium[Free] version 2.40, when I use “Punch In/Punch Out”[which is a VERY useful feature, and saves a lot of space when making stems], Punch Out works fine, however Punch “In” does not work it seems. When using Punch In and rendering audio[or “bouncing”] the Punch In range seems not to be detected or it may be a bug, and the render starts from the beginning of the project and “then” stops at the Punch Out range. If this is indeed a bug, whenever you have time to patch it I would be grateful. However when do you think Podium Free will be able to receive the patched bug?
[a small feature request thought: Like the “loop” button, make a Punch In/Punch Out loop button. Using Punch In/Punch Out of course most times you would only use both. If you wanted to use just one side of the feature, you can change it via right click OR just hitting “I or O”. Just a thought of a small feature…]
-In the Zynewave Podium project file[which due to making lots of bounce samples with “Punch In/Out” saved a lot of GB, or space in the folder! For example it went from 2.50Gb to 1.08GB!] sometimes when a sample is deleted, and of course sent to the recycling bin via within Podium, the .MINI file is still there. Is there a way you could in the future make a patch to where if the .wav bounce file is deleted so is the linked .MINI file? I’m a bit of a neat freak[or just a plain neat freak], and sometimes for just the sake of it, I Ctrl+A[highlight everything], right click a file then just count how many files or “bounce samples” I have within the folder. I know it sounds a bit silly, but it’s just something I do from time to time, that is also how I discovered the .MINI files were still left over even though certain stems were deleted.
-Within the browser in Podium, is it possible to implement the use of using the “Delete” key when deleting a stem? Of course the window prompt would come up confirming if you wish to delete it, but right clicking then deleting the file is just a small issue for me.
If this is due to my own error and maybe overlooking a option with the “Preferences” menu in Podium, I am sorry if I did overlook it. And please correct me if I’m wrong, if I am. If I am not wrong, I can wait patiently for an update or patch for these very small issues. Also again, the feature request for a feature already in Podium[The “Punch In/Out loop button] is just a thought. I thought maybe by chance it could increased workflow a bit. But I’m used to using “I and O”, so no worries if you and the other Podium users feel that feature could be confusing and more trouble than it is, and is therefore not needed.
Thanks again for Podium. Now if you’ll excuse me I have to get back to my debut EP/Album. 😉
ZynewaveI’ve now added support for the Del key in the file browser. It will be included in Podium/Podium Free 3.0.3.
I’ve checked the bounce rendering, and I don’t find a problem with rendering within a punch range. Remember that you must have both punch in and out mode enabled, and that you must use the “render within punch range” command. The normal render command will disregard the punch range.
InfinitoarThanks for the reply Frits.
However I do have both Punch In and Out enabled. However it seems Punch In does not work. 🙁 I really did a lot of various tests to see what I could have been doing wrong, and did “Render within Punch Range” or just “Alt+B” and still yet the punch render still ignores “when to start”[Punch In] but doesn’t ignore when to stop. [Punch Out] If you believe you need a video I can arrange one for you to show you that I am doing the right thing, just for some reason Punch In doesn’t work but Punch out does… 🙁
Just for a bit of info I am using Podium 2.40. I hope this helps.
ZynewaveA video would be helpful, thanks.
Note that the render within punch range will not erase the previously bounced audio outside of the punch range.
InfinitoarOk I will message you the YouTube link.
Sorry if it’s to fuzzy, I tried my best.
ZynewaveThanks for the video. You’re not doing anything wrong. It’s just that the render within punch range is meant to work a little differently. What you expect is that the underlying track bounce file will be the size of the punch range. In fact, the underlying bounce file is always the full length of the arrangement. If you for example work with a long track with heavy plugins that takes a long time to render, you can use the render within punch range to just render the part on the timeline that you are currently working on, thereby greatly reducing the time required to render.
Instead of saving the bounce, reimporting it and cropping it, you could use the “move bounced audio to new track”, split the event on the new track, and use the “convert to unique cropped copy” on the fragment.
InfinitoarOOOOHHHH! OK! I was so nervous once I saw you replied, I thought I did something wrong! 😀 Hehe
Thanks for the reply and that new technique you described I will try instead! I suppose I thought of the feature a different way but it’s a great feature! But just a question: Have you ever thought that feature should do that? And if so, “would” you implement it?
Because I HIGHLY believe in your skill Frits, but I know your swamped with a lot of things, but also I greatly believe that could be a VERY important and use feature in Podium! I can imagine the workflow!
The reason I also did it that “long way”[as far is re importing the bounce file and such] so I can save the MIDI event file[the box with notes] too! Never know when you may have to revisit that and redo it! 😉 But if doing your technique still keeps the MIDI file, then I will keep doing that instead.
Thanks again Zynewave and I guess you could consider that feature I “thought” Punch In/Out was, a “feature request”. But not anything that needs attention right away. I really believe it would be a great feature for making stems and increasing workflow. 🙂
Thanks again.
Zynewave@Infinitoar wrote:
But just a question: Have you ever thought that feature should do that? And if so, “would” you implement it?
It would mess up the underlying bounce system if the bounce file should not cover the entire arrangement length. If you did multiple renders within punch range in different timeline positions, the bounce track would include a growing number of fragmented bounce files.
InfinitoarOh ok then. Well it’s still a really good feature on it’s own so no worries then. 😉
Thanks again for the help and understanding Podium more.