thcilnnahoj.
ZynewaveBeta1:
The input bypass button has been changed to only disable monitoring instead of disabling recording. An audio input that is monitored through external hardware can thus be silenced in the Podium mixer during recording.
If a track is record armed and an audio input is assigned, the track meter shows the input level instead of the track output level.
thcilnnahojNice! Finally an easy way to tell mono from actual multi-channel inputs.
roninFor 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?
thcilnnahojI can’t confirm it, unfortunately. Recording with or without monitoring works fine so far… 😕
Something unrelated: When you change the output device mapping speaker configuration to none while the arrangement is powered on, this causes a crash.
roninAt 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.
thcilnnahojYep, I’ve had it happen too now. As ronin described, the input meter (armed track) acts normally, but only short clicky sounds come out, which the output meter (unarmed track) also shows.
It doesn’t help to uncheck the inputs in the setup, but the problem goes away after you switch to another audio interface and back again, and let it rebuild the input/output mappings.
Loading my normal setup file last saved with 2.36 brings the problem back again. The same setup that is broken in 2.37 works fine in 2.36…
ZynewaveBeta2 is up. I’ve fixed a bug that I’m pretty sure is the cause for the silent recording problem. Let me know if you still have problems.
New additions in beta2:
The background of input meters are tinted with the record color.
The width of the meters in the mixer will resize according to the zoom setting.
roninNo, 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.
thcilnnahoj@Zynewave wrote:
The width of the meters in the mixer will resize according to the zoom setting.
Nice, but personally, I wouldn’t say no to even wider meters. 😉 It’s also a shame that the currently biggest meter size is only available when the strips are zoomed to 300%, because they would fit inside strips at a smaller zoom level already, and thus you could save some space.
I’m not sure if it’s really needed that they get smaller though, at least in stereo projects. It might be useful for surround projects.
ZynewaveBeta3 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.
@thcilnnahoj wrote:
@Zynewave wrote:
The width of the meters in the mixer will resize according to the zoom setting.
Nice, but personally, I wouldn’t say no to even wider meters. 😉 It’s also a shame that the currently biggest meter size is only available when the strips are zoomed to 300%, because they would fit inside strips at a smaller zoom level already, and thus you could save some space.
The meters resized with the same percentage as the strip widths. This was to ensure that even a 32-channel input meter would not grow larger than the zoomed strip width. I’ve changed it so that mono/stereo meters increase at a larger rate, and 3-8 channel meters increase at a slightly larger rate.
ronin@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.
Zynewave@ronin wrote:
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.
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.
Anyone have an opinion on this?
thcilnnahojHmm, I don’t know… How would you play along to a song without recording any audio or MIDI data? That always got me in Reaper, where you have to record arm tracks to monitor them, and there’s an extra mode that arms a track so you can monitor it, but recording is disabled on it – quite confusing. Also, what should bypassing the input do in this case?
Oh, and beta 3 looks lovely! 8)
ronin@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.
swindusThere is a problem with sending MIDI clock/start/stop. Podium sends MIDI messages to the MIDI clock enabled output but the external device does not start playback (in my case a MIDI hardware sequencer). With Reaper or Studio One the external device slaves perfect to the sequencer playback.
