ZynewaveThe volume value of audio events is often hard to read because the first number is partially hidden by the handle.
I’m not sure what you mean here. Could you post/email a small screenshot showing the problem?
ZynewaveIs Timestretching back on the menu now?
It hasn’t returned to the top of the priority list yet. The timestretching was sidetracked by the mixer improvements leading from discussions on this forum. I still have some ideas for improving the mixer/track management, which I want to carry through. The control surface support is not finished either.
ZynewaveThe realtime bounce should work. There have been a discussion before about problems with offline rendering of the Emulator X:
ZynewaveWith this new support for control surfaces, is there a way to attach a MIDI CC to a mixer fader ?
No. That will come later.
ZynewaveWe already have a dropdown menu for choosing mappings within the mixer. Will this be also available in the right-click menu of the tracks in the arrangement window?
Yes. The recently implemented mixer mouse-over highlighting and popup menus will migrate to the track inspector and track headers later on.
Pressing ctrl + a selects the whole sound file, without the need to manually draw the segment with the mouse.
Ctrl+A will select all events, which for sounds is limited to marker events. You can use the ‘J’ key to select the sound as a segment.
ZynewaveI tested with the 2.1.2 demo version and can confirm the bug. Running the debugger I found that the plugin crashes when it processes a set of MIDI reset control change messages that Podium sends when unmuting the track. I’ve sent an email to IK Multimedia about this. I’ll post again if I get a reply from them.
ZynewaveZynewaveZynewaveWill this be in the next demo realease?
Yes.
Is is possible to try a current demo and still have the CM version installed?
I recommend that you uninstall one before installing the other. It should be quick to reinstall the CM version.
Is there an option to make the buttons bigger or to enable tooltips on those track buttons?
The BSMRX track buttons cannot be resized. Later on I’m going to implement mouse-over highlighting of the buttons, like I did recently with the mixer buttons. The tooltips will appear if you hover over the track buttons in the track inspector. All the track buttons have key shortcuts.
ZynewaveUnfortunately though, they have removed the standard MCU and now currently only offer the PRO-version.
I purchased my MCU (non-PRO) from a German shop that still had a batch on stock. I think you should be able to find shops that are selling the older model cheap. I paid 800 Euros (ex. VAT) for mine. I bought the older model because I prefer the dark/round button design over the new white/square button design.
ZynewaveI’ll keep looking for other options as far as hardware control goes.
Keep me posted of what you find out. The only surface I know so far will work with Podium, apart from the Mackie products, is the Behringer BCF2000. Why is the BCF2000 not an option for you?
ZynewaveI glanced at the AlphaTrack MIDI documentation, and it seems it only supports HUI emulation mode. So the current Podium Mackie Control support will not work with the AlphaTrack.
ZynewaveI don’t know. The last time I tested with Waves plugins was a Diamond demo bundle downloaded September 2004. Since then they apparently require an iLok to even try demo versions, so I can’t test this myself. I don’t want to risk messing up my development PC by plugging an iLok into it. I’ve heard too many horror stories.
Since you mention three specific versions, are there any other Waveshell versions that work? What are the two plugins that are working, and are they part of a bundle with other plugins that are not working?
ZynewaveWhat I really want is an easy interactive way to figure out not only BPM (that’s not too bad as it is really) but also time signature and on what beat my guitar idea starts on. The best way I can think of would be a way to comprehensively experiment with MIDI tempo realtime against prerecorded audio. There are countless tools to mangle and chop audio to fit a MIDI tempo, but it seems little is available to manipulate MIDI tempo into fitting with audio.
A function to automatically extract time signature from an audio recording requires some clever DSP coding. At the moment I don’t have time to implement this. However I have now added a simple function that can help set up a tempo map that matches an audio recording:
Right clicking the tempo lane shows a new “match tempo to cursor” command. This command will adjust the tempo of the last tempo event prior to the play cursor position.
The procedure for tempo mapping an audio recording will thus be:
Align the sound event so that the first bar/beat in the recording is on a bar/beat grid line. If this position is not at the start of the recording, then also insert a tempo event at the first bar/beat position. Now move the play cursor to the next noticeable bar/beat position in the recording, right click the tempo lane and select the “match tempo to cursor” command. The tempo event prior to the play cursor is now adjusted so that the play cursor is aligned on a bar/beat grid line. The editor quantize value determines the snap resolution used by the match tempo command.
You now have a tempo indication of the recording. If this tempo is general for the song, and you had a pause before the recording started, you could replace the default tempo event at the start of the arrangement with this tempo, and then realign the sound event to the new bar/beat grid positions.
If there are tempo changes within the recording, you can repeat this procedure from start to end of the recording. Find the next position where the tempo is changing, insert a tempo event at this position, move the play cursor to the next bar/beat position in the recording, and use the “match tempo to cursor” command.
ZynewaveThe Windows task manager possibly measures over longer periods, and so short spikes are evened out.
I consider the Podium CPU indicator both as a measure for general CPU load, as well as a warning indicator of how close you are to overloading. I think it is important to show the spikes, because if they happen to go to 100%, you will get audio dropouts. Other hosts may have less sensitive CPU indicators, but you then risk getting unexpected audio dropouts at a lower CPU percentage. I’ve seen posts on kvr where people state that for some hosts they can only reliably utilize up to ~60% before they start getting audio dropouts.