roninHehe. This reminds me of something: “Optimizations always bust things, because all optimizations are, in the long haul, a form of cheating, and cheaters eventually get caught. – Larry Wall” (No! offense Frits 😆 )
ronin@Mike G wrote:
1-At one point I was on “Louder” speaker volume and wanted to see what the levels were on a mic input by looking at the meters in the mixer. But to see the levels the track has to be unmuted and the input enabled, which means I had to turn down the speaker level to make sure it didn’t feedback.
I suppose I wanted to see the input levels which I can see by looking in the track view while recording but the levels in the mixer show the output volume.
What do other people do to see the input levels?2-Another issues… (a little bit contradictory to my first one!)
I had a few different audio inputs mapped to some tracks.
I had to turn down the inputs (on my audio interface) or disable the inputs in podium while I played back what we had just recorded at louder volume.
This is becuase the audio input for the mic is still live during playback and so the output from speakers spills back into the mics, and would cause feedback.
I had both problems. My “solution” was to move the recording tracks to a group and turn down the gain of that group track. This avoids feedback from the inputs and leaves the input level meter of the recording tracks unchanged.
@Mike G wrote:
Could there maybe be an “X all” button to
“X” (disable) all audio inputs and then click again to re-enable them when I’m ready to record?
(A bit like the fab new S M R buttons maybe)Or maybe disable inputs when turn off record button or something like that. (As a preferences option as I don’t think all sceanarios would suit this)
I suggested something similar a while ago. There must be a separate thread somewhere. I’ll post it later.
I needed something to disable input monitoring as my audio interface supports direct monitoring (zero latency). Maybe the already available “X” button should do this. I think there is no real need to bypass an input because it could simply be unassigned to disable it. Although it would be more user friendly to have separate buttons for this.
@Mike G wrote:
Or is there a better way of doing this already? (I bet there is. Whenever I ask this kind of question there usually is an abvious way that i’ve missed!)
Unfortunately I haven’t found a better way but I’m really interested in a solution! Let me know if you have found any.
roninJust some short notes: it looks awesome so far! Scanning seemed to be faster than ever and the new functionality seems to be everything I need. Update Audio/Midi is very useful too. Thanks! 🙂
However I’ve noticed that Bootsie’s epicVerb and DensitymkII crashed Podium while scanning. I think they never crashed it before.
This may not be Podiums fault but I thought I’d mention it (because there is another thread with similiar issues).
roninI have some similar issues. Please take a look at: http://www.zynewave.com/forum/viewtopic.php?t=2263
ronin@Frits: There is a tiny mistake in the download-url of beta1. Thank you very much for this beta! I’ll test it right away.
@all: You can still download beta1 by changing the url to “…beta1.zip” instead of “…beta.zip”.
ronin@Zynewave wrote:
I’m curious: How many crashing plugins do you encounter during a scan of your complete plugin collection?
Too much 😆 The strange thing is that the plugin collection worked back on Windows XP (with crashes too but after a few tryouts and and few quarantined plugins later the scan was successfull). The last time on Win7 I gave up. I’ve tried it two hours and everytime a different plugin crashed. Sometimes even a plugin that had been already scanned. So quarantining the “faulty” plugin does not solve the problem in every case. I’ve tried to explain that in the first post.
I don’t blame Podium for the crashes! It is definately the fault of the plugins but I think Podium should somehow handle this case. I guess I’m not the only one with this problem.
roninSounds reasonable. Does it solve the problem I had with the initial scan? Maybe there is an easy way to trace the plugins that had already been scanned and omit them in subsequent scans (in case of a crash).
ronin@Zynewave wrote:
Could you guys explain why you don’t use the “load device setup” submenu in the project templates?
My problem is the creation of the device setup and not the usage of such setups. In my case this is a really cumbersome procedure which takes a lot of time and patience. Please keep in mind that this holds true for a lot of hosts and not just Podium.
I don’t really know EnergyXT but its seems like it solves the problem fairly easy.
ronin@Zynewave wrote:
If you have time to read over the help page I uploaded to the wiki (link provided in an earlier post), and you still have questions about the controls, please let me know what needs to be clarified further.
I’ll try to read/test it in detail tonight. Since there seem to be no other complains about that I think it is okay as it is + you usually put a lot of thoughts into new features. I’ll report back when there are problems.
roninroninI used templates too but from time to time I have to redo the template, so I end up with the same problem.
The folder trick should work too but it might be a bit cumbersome depending on how many folder there actually are.
roninHi everyone,
I’ve tried beta4 yesterday and wanted to share some thoughts:
Honestly, I have to admit that I don’t really understand what the controls are doing. I had to read through this thread to get an idea. After that I knew that it wouldn’t be very useful to me but I can imagine that other users might have a good use for it.
Anyway I have some suggestions/notes for these new dialogs:
1. I don’t like modal dialogs at all. Sometimes I wish to inspect another part of the arrangement while tweaking. Maybe the new dialog can be non-modal and just stay on top?
2. There is “Adjust timing” in the piano roll editor and in the arrangement editor. I couldn’t figure out how “Adjust timing” works in the arrangement. I’ve selected events etc. but nothing happend during tweaking the knobs ( “preview” was activated). Only the timings editor in the piano roll did change something.
3. A double-left-click action resetting the knobs to their initial value would be great.
4. How about something like “randomize velocity/volume”? That would be useful to me in conjunction with the other timing commands to humanize drum parts.
roninroninNo. As far as I know ASIO4ALL just delivers the ASIO driver model/protocol to an already installed/working audio interface…so it should work with any available audio interface. You should definitely give it a try.
roninSorry to hear that.
Whats the brand of your firewire chipset? The TexasInstruments chipsets are known to perform best while other chipsets are a known to cause problems.