ZynewaveZynewaveWhich ASIO4ALL version?
What ASIO buffer size have you set ASIO4ALL to use?
Try if you can set it to a number divisible by 16 (256, 512, 1024 or similar), and check if this gets rid of the noise problem.
ZynewaveHi,
Podium identifies plugins by their filepath+filename. So if you have moved plugins to different folders then your old Podium projects will show the plugin mappings as being broken (colored red in the project start page device list). You can then use the “search for missing plugins” command in the devices menu. Podium will search the folder you select (including subfolders) for any of the missing plugin filenames, and use the new filepath location if found.
Frits
ZynewaveI imported your fadeout.wav into a blank arrangement, set to 48000 samplerate, no plugins, and no gain/pan changes.
If I zoom in on the fadeout.wav I see it gradually fades out until the last 0.08 second of the file which is all zeroes.
I can’t see/hear any problems. If I start playback halfway through the sound I don’t hear anything. The peak hold indicators in Podium show -88 dB and that is the same value that my RME mixer control panel shows. If I turn up the volume of my headphones I can hear the decay, but it fades out nicely to silence. Please verify what your master track peak hold values show and check if they match the reported output by your audio card control panel/mixer.
ZynewaveZynewaveThanks for the bug-reports. Beta2 is up with fixes and:
• Added “slider knob visual style” combobox to the preferences dialog. Choices cover combinations of glass/solid, rectangular/round and with/without value readouts on the knob.
The with/without value choices are still not implemented, but at least now you can try the four different slider styles. Another change is that the groove for the slider is filled with the parameter graduation colors (similar to the dial fills).
@acousmod wrote:
And one question : how do we drag a plugin from one track to another one now ?
Same way as you’ve always done, unless you refer to the old expanded mode track header?
ZynewaveZynewave@swindus wrote:
Found a little GUI bug. There is something wrong with the peak indicator of the master track in the mixer when resizing the mixer region.
Thanks.
I think the best way to fix this overlap is to hide the peak hold indicators when the strips are sized below a certain height. Agreed?
ZynewaveCan you provide an example of how to reproduce this problem?
Zynewave2.05 beta1 is available in the VIP lounge.
Changelog so far:
• Added option for vertical meters on the track lane headers. This is configured with the new “audio meters” setting in the tracks region properties. Vertical meters are now the default setting.
• Track header meters show RMS as well as peak meters. Also added indicator lines at -6dB, -12dB and -24dB.
• Updated the design of the pan and gain sliders on track lane headers. All gain, pan and send controls in the chain panels also use the new slider style if the “show sliders instead of dials” option in the tracks region properties is enabled.
• Added “show device bypass buttons” and “show device automation record buttons” options to the tracks region properties.
• Removed the E buttons from the track headers and the inspector group panel. Clicking a plugin name will open/close the editor window. Shift+click toggles bypass. Ctrl+click toggles record mode. Alt+click removes the device. Colored frames are drawn around the device name to indicate bypass, record and editor open/close states. These changes matches the update to the mixer in the previous release.
• Added “show bypass buttons”, “show record buttons” and “show sliders instead of dials” options to the inspector view menu.
• The “expanded” track layout mode uses the chain panel from compact mode.
• Hovering the mouse over buttons and sliders on track headers will highlight the control.
So far this beta only supports the new slider style. I’ll continue with the development of the additional slider styles discussed in this topic.
I’d appreciate your comments on the new sliders.
ZynewaveThe replies in this topic certainly makes it clear that slider design preferences are very different from user to user. I’ll spend some time implementing user-selection of different slider styles. Instead of the current “show sliders instead of dials” checkbox option, it could be a “control style” combobox/submenu with choices of “dial”, “solid slider”, “glass slider”, “solid value slider”, “glass value slider”. That should cover all combinations I think.
I’m still working on finishing the new fader design. When it’s done I’ll release a beta.
ZynewaveZynewaveSetup, colors dialog, timeline fill.
Zynewave@Slomo wrote:
I’m not much for the new faders.
You have to look at two places. One for the “analog” placement on the scale and one for the “digital” value. The old one had value and placement in one. The less you have to hunt the screen the better in my opinion…That’s probably why options in preferences is a good thing. 🙂
😥 I did not plan to make an option between the old vs. new faders.
My problem with the old fader style is that it can be visually confusing that the dB level readout is all over the place depending on where the fader knob is. With the new style it is easy to glance up/down the track list and trace the various dB levels. If you look at the fader design in other hosts, I believe it is rare to find examples where the value is written on the fader knob.
Another problem with the old fader style is that the visual design is not suited to be used for send faders. It’s either these new faders or back to the old faders with no fader option for the sends.
I’d appreciate more opinions on this.
Zynewave@UncleAge wrote:
@Zynewave wrote:
The track header meters now show RMS meters similar to the mixer.
Is that with the Peaks holding as shown in the picture on the Master track?
The solid bar is the RMS meter. The two floating blocks are the peak meter. The top of the meter is 0dBFS, unlike in the mixer where it goes to +12dB.
The BRXE buttons shown in the inspector group panel and the chain panels are now optional. Instead shift/alt/ctrl + clicking the device name will behave like the new 2.04 mixer defaults. Colored frames are drawn around the device names to indicate bypass, edit and record state. The buttons were perhaps more accessible than modifier+clicking, but the buttons occupied a lot of screen space. Anybody still prefer the old button style?
For me the “E” button does not fit the “state” scenario. Bypass & Record are states and I don’t have a problem Shift + clicking here. As a matter of fact I would think that only one modifier key would be needed. And this way a user would just circle through the different states. However, I think Edit is a different beast. My opinion on this is that simply clicking or double-clicking on the name of the effect should bring up the editor.
Clicking a device name in the inspector or the header chain panels now is similar to the mixer 2.04 behaviour. Shift+click toggles bypass. Alt+click removes the mapping. Ctrl+click toggles record. Just clicking the plugin name will open/close the editor instead of showing the track menu as previously.
From the above posts I gather that the consensus is to show the X and B buttons by default, and only hide the E and R buttons. Note that the option to hide the R buttons does not include the R button on the track header title. It hides the plugin automation recording R buttons inside the chain panels.
Similar to my question about the dial/fader option: Should the options to show bypass, editor, bounce and record buttons be global options in Preferences or should it be possible to configure this individually for each editor?
