After clicking on either sequence or audio events and dragging, the control key can be held to create a unique copy which will be cropped to the event time range.
Phew !
After clicking on events and dragging, the shift key can be held to lock either the time or vertical position of the events depending on the direction of the mouse drag. This can be combined with the control or alt key when dragging copies of events. The shift-lock also works when dragging track headers.
Phew Phew !
Thank you VERY much !
My next work with Podium is going to be far easier to do than the previous one…
Holding the alt key while clicking on a resizable event will start a resize drag action.
Direct resizing WITHOUT any key when the mouse is on the edge in the next build ? 😉
Nice 😉
The second thing that bothers me time after time, is that when I split items with scalpel tool, both parts are selected after splitting. Much better to have only right part selected, like in cubase-family programs, because 99% that you need to move only right phantom event, not left.
I have pointed that some time ago… But there is no need to have any part selected, we can move the left or right without having it selected before.
Another thing that often causes me some trouble is that when I drag a file from the list into the arrangement and move it, all previous clips which were selected remain selected and are moved together.
I think that a better behaviour will be that previously selected events are automatically deselected when a new file is inserted, like when I draw a new event.
But maybe TapeIt 2 would be helpful for you acousmod? Smile Bidule looks like it takes a bit of time to set up, from what I’ve seen so far. TapeIt 2 is really quick to use
Thank you, I know Tape iT too, but I needed to record a 16 channels file…
Your problem is really very strange.
Could it be related to the place where the files are stored ?
For example the files used in your project on a partition, and the ones which are bounced on another ?
just out of interest, can you explain how you would use Bidule to record the output of say a VST instrument playing a midi sequence in Podium? Would you insert it on a group track and press record in Bidule?
Yes, just insert on a higher level track, this is the magic of Podium 🙂
Hi,
I’m not sure that I have correctly understood this discussion, but if the problem is dropouts DURING the bounce, which was my case, I have recorded within the plugin version of Bidule instead of bouncing internaly, and all has been fine (with 1.43, with previous versions I got also some dropouts).
I needed Bidule for multichannel file recording, but I suppose that it can work the same with any plugin which can record audio.
I think that this is a usability thing that is more relevant than the terminology. As the uptake of Podium increases, it will be harder to get a userbase to update their practices, and having non-std key functions will slow the adoption of the app. This is the best time to make those changes, and I’m all for them
…same for me.
The hard part is that nearly each software use different key combinations.
I’ve tried to put together some of them at http://sonart.free.fr/logiciels/shortcuts.htm
The best solution will be when Podium will have a customize key and mouse option…
Concerning the Ghost or Phantom name, I’ve no real preference since I don’t use this function, and always have to “clone phantom sequence” and “crop unique sequence” after copying…
For me “clone” is better for real duplication. Since ghost seems to be used by other softwares, I suppose that it is better to use it also in Podium ?
Perhaps that control for real copy (like you say Frits) and control + shift for “ghosts” will be good ? In Windows we can use alt or ctrl + shift for the same thing.
This would preserve the alternate key for someting else ? (alt + drag is used for real copies in Live…).
The shift key which is used for moving between tracks (in same time position) in Samplitude and Tracktion (like moving instead of copying in Windows) will be a nice addition…
Concerning the copy itself, there is something a little bit disturbing in Podium, certainly due to the use of the same control key for duplicating and resizing : we must press the control key AFTER begin to drag the clip, wheras in other softwares we can press the modifier key BEFORE (like for resizing).
This will mean that the previous use of the control key as a shortcut for drag-resizing events must be abandoned
So, the solution will be NO NEED for a shortcut to resize events like in all other apps ? 😛
Speed-optimizations of audio streaming and processing in the engine.
Concerning the CPU, the difference is asthonishing : about twice less than before, and no more CPU spikes. I can now play my project !
It doesn’t change anything with the bounce problems for me, but now I can export the 16 channels mix with the VST version of Bidule.
Thanks a lot !
There is a better chance that I may be able to speed-optimize disk streaming in November. Would that make it possible to work with your project?
Yes, I think that it will be enough, since there are only two or three passages that have the problem in playing.
I will be very greatfull !
Thanks.
Hi Frits,
Any chance for the offline bounce feature in November ?
I have not succeded to bounce my project in Bidule since there are always some parts that Podium can’t read properly through the 35′ duration of the project.
The offline bounce is now my last hope.
It will be a disaster for me if I can’t finish my work in time…
Sorry to bore you with this 🙁
Jean-Marc
Frits,
It is indeed a very good new for all of us.
I whish too that it will worth the “risk” for you.
A new event can be created with the rearrange tool by double-clicking on an empty area in the note and curve editors. Double-clicking on an existing event with the rearrange or pencil tools will delete the event.
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaahhhhhhhhhhhhhhh !
And the track copy are great also…
Thanks A LOT !
Just a quick suggestion: Maybe you can optimize the bouncing process if you solo the track that you are bounce recording.
Yes, of course ! I always mute all the tracks that are not in use for the bounce.
(the exemple that I have done with EnergyXT as plugin was made with only one track…)
But my actual problem is to bounce the tracks of my project.
Even with two or three active tracks, there is sometimes drop outs during bounces (with a correct average CPU).
To mix all the tracks I might make several series of partial bounces, then make new partial bounces with them to be able to finaly mix three tracks… And all of, this section by section (limit of 2 Gb files).
I had a hope by disabling the card outputs in the preferences, I thought that this way Podium could bounce without auditionning to obtain better performances, but they are not recorded in the bounce… No chance.
The only solution I think that is possible for me, is to use Bidule as a VST to record only two partial mixes of the total length in separate mono files (each less than 2 Gb), and after to synchronize and mix the 32 mono files in Podium (ah, a MIDI external sync would be helpful…).
I’ll hopefully start work on offline rendering soon.
This is a really good new…
Nevertheless, I hope that you will have some time also to look at the “streaming issue” for normal playback.
I have tried all sort of buffer settings, but it doesn’t seem to change anything.
It is logical : it only changes the CPU spikes and crakles, not the “random holes” in the tracks.
I also defragment the drive very often, but I’ve not noticed a difference between before and after.
Thanks !
Hi Frits,
Sorry to repost on this subject, but it is actually for me rather impossible to bounce my work.
When Podium bounces, it takes a lot of more CPU power, and the passages that I can read but are about 80 % become completely crackly with intermitent aleatory silences on tracks when I try to bounce.
I’ve intended to make partial bounces for some parts only. But for some the bounce is only clean with 2 or 3 tracks (16 channels). Due to the complexity and the duration of the project it is very complicated to do it.
The limit to 2 Gb wave files is also a constraint.
I’ve tried also to process some individual 16 channels sequences with EnergyXT as a plugin to host several stereo plugins in parallel (I didn’t succeded to do it right inside Podium).
When I play, the CPU indicator shows an average of 50 %, but when I bounce it goes to 90 / 100 % with crakles. So it is impossible to record.
I’ve made the same config inside Bidule : 32 % when play and 34 % when I record with its internal multichannel file recorder.
I don’t understant why Podium takes so much CPU while bouncing, where others takes nearly nothing.
Without an offline bounce option (which will be the final solution ?), I dont’ see how I will end my work…
I know that you are working on audio optimizations and that you always do your best, and I am sorry to bore you with my little personal problems…
Have you see yourself, or other people, this increase of resources when bouncing ?
If yes, do you think that the bounce process have a chance to be improved ?
Or is there another solution, workaround ?
The support for Hyperthreading has not change anything in this domain for me.
Thank you !
Jean-Marc