Welcome to the forums Divintek. No, there are various ways of manipulating the volume of a wave or of a part of it. Firstly you can chop the file and move the various parts to different tracks and manipulate the track gain (that was your example). Secondly you can use the the clip handles to manipulate the clip volume and to create fade ins and outs. You can find these handles for the fades at the /left/right side of the clip. The overall clip volume handle can be found at the upper border of the clip.
A third method would need some third party VST plugins like compressors or limiters. There are various free plugins out there. Refer to the Podium user guide if you don’t know how to use these plugins.
Sorry Infinitoear, there is no option to edit the tempo of a single track. If you refer to audio-timestretching I think this is already planned but no there yet. You can stretch MIDI-parts in the current “pro” version but I’m not sure if it is already in podium free.
Font size etc. works fine here so far. I’m surprised how flexible the GUI seems to be. Nice work Frits!
I have seen a minor glitch where the new size for the scrollbars was not corretly set when “Apply” was clicked. Unfortunately I can’t provide a way to reproduce this yet.
Sorry khaos. Currently there is no support for audio time stretching but I I’m pretty sure Frits has this already on his ToDo-list. Support for stretching midi parts has been added recently.
@Zynewave wrote:
Hmm, :-k . Doing that would mean you could not set up an audio input to act just as a live feed (perhaps from a talk-back mic in a booth). Once you start recording on other tracks, you would unintentionally record the live feed track.
Oh, you are right. I haven’t thought about this.
Well you can still play along with just the track armed, but it would not be possible to play along to a live drum recording. Anyway I think it is a quite special case but controlling monitoring and record mode separately would be confusing.
Hence, I would agree to the current behaviour and say: Everybody loves KISS(es). If you don’t need/want any monitoring, just unassign the input.
@Zynewave wrote:
Beta3 is up. I managed to reproduce the silent recording bug with another soundcard interface I had. I’m 99% sure the bug is fixed now.
Yeah! It works like a charm. Thank you very much.
There is another thing on my mind:
Personally I think the selected input should only be activated when the track is armed (no monitoring and no input metering while unarmed). The tooltip on the record button already implies this behavior.
No, sorry. I’m still seeing the same problem. I’ve deleted and reset everything. Building a new project from scratch brings me back to the problem.
I’ve tried thcilnnahoj’s solution but in my case this doesn’t work either.
At least some news: It works fine on my main system using a presonus firestudio. The described problem only occurs on my laptop with a line6 pod xt (and it’s ASIO drivers). Even if I’m using the internal sound device through ASIO4ALL the problem occurs. I’ve tried reinstalling Podium and the drivers but unfortunately that didn’t change anything.
Edit: Another desktop system shows the same problem using ASIO & Windows/MME (only internal sound device available).
All buggy systems show sporadic and gentle noise bursts when “monitoring”. When the input(monitoring) is bypassed, the noise disappears.
For future reference I’ll copy my results from the VIP forum into this thread:
@ronin wrote:
I’ve tested this beta but I was unable to record any audio. The meter seems to display the input level correctly (recording enabled) but I could not hear or record any audio input (nothing gets recorded). Playback of some samples works fine.
The same recording setup works in 2.36.
I’ve tested this beta more thoroughly but I can’t give you much more details than that Frits. It is a clean install of 2.36 with the beta of 2.37 copied over to the installation directory. Asio and Windows drivers were tested with the same result.
I did just set up a new and clean project. No VSTs were scanned. The first added track is set to the first stereo input. Playback works as expected and the meters show the input level when recording is enabled. Unfortunately I can’t hear any input monitoring (independently of the bypass state) nor is it possible to record any audio.
A screenshot:
http://dl.dropbox.com/u/2231676/Capture.PNG
As you can see, nothing gets recorded and there is no playback/monitoring through output 1+2. If you still need a sample project, let me know!
Can someone else test or confirm this?
Are you talking about send effects or the wet/dry level of regular slot effects?
I think you can have as many send busses as you want…if that was your questions.