Hi Frits,
@Zynewave wrote:
- Bounce enabling a track will create a dedicated bounce track in the effect chain, instead of enabling bounce mode on an existing effect track. The bounce track will show up with a “Bounce” button in the chain, which can be clicked to open the bounce menu. The bounce extraction point can be set by dragging the bounce track up or down in the chain.
Just got a chance to try the new bounce behaviour and I have to say it’s a joy to work with. Such an improvement since I made my “How to Bounce” video! 8)
I really love the fact that you can choose to record live audio and/or the MIDI input when working with VSTi’s now.
The only thing I still find confusing is the behaviour after bounce. If I enable Realtime Bounce (my preferred bounce method when jamming with VSTi’s) then enter Record, the audio file is displayed while recording – but disappears when I press Stop. I think this is very confusing behaviour, and the first couple of times I tried it I thought I had done something wrong. It took me a few goes before I found out I had to enable the playback of bounced audio after recording in order to view/listen to the bounced track.
Could this behaviour be changed (even if it’s something that can be enabled by preference) so that the audio is displayed and plays back automatically after creating a bounced recording?
Cheers,
Malcolm.
It looks like timestretching is already under-way, and I already have a license, so I’ll just post my two remaining feature requests:
1. Ctrl+click to select multiple tracks – for grouping, deleting, copying, adjusting volume, etc, etc …
2. The ability to record the output of tracks, in real-time, without the current, somewhat convoluted, bounce system.
🙂
@Zynewave wrote:
Those that haven’t tried the beta versions can get an idea of the note map feature from the new YouTube video I’ve just uploaded:
That is a great usability improvement when working with GPO 4. Great stuff Frits. 🙂
@thcilnnahoj wrote:
Hmm, I’d rather use the mouse (with the current modifier keys, or just the navigator) instead of having both hands on the keyboard to do these things.
I don’t see myself using any of those shortcuts, to be honest.
Same here.
The list of shortcuts
http://www.zynewave.com/wiki/doku.php?id=guide:key_shortcuts
is getting really long, but there’s no editor for them. I’d really like the option to be able to map the shortcuts to the keys of my choosing, especially if the list is going to continue to grow.
Cheers,
Malcolm.
@Zynewave wrote:
@confusador wrote:
ok, that all makes sense. is there a thread somewhere about how to show the hidden track and draw the event to enable realtime bounce?
1/ Enable the “realtime record bouncing” mode on the group track.
2/ Right-click the empty “effect” button on the track header or the inspector, and select “options > hide track lane”. That should reveal the hidden bounce track with the “B” button on the track header.
3/ Draw the sound event on this track.
4/ Hide the bounce track lane again, to tidy up.
5/ Select “Arm bounce recording” from the bounce menu.
6/ Enable record mode in the transport toolbar.
7/ Start playback.Step 2 to 4 will not be needed once I implement the automatic creation of the sound event.
I look forward to seeing this implemented. I just tried the above procedure with Stylus RMX and it took me about an hour to setup (with trial and error).
@Zynewave wrote:
is it possible once you’ve drawn the events for the realtime bounce recordings to save the whole setup as a track or track group template?
It should be. If you enable the copy events option when saving the group track as a template.
I also tried this with Stylus RMX. When I created a new arrangement and then created a new track with the template it imported the Stylus RMX instance and events correctly, but when I made a recording it linked the WAV files to the arrangement that contained the original instance of Stylus. I assume I’d need to create new events with each instance to avoid this problem.
Ideally I’d like Podium to function like a *tape deck, so that whenever I see an audio signal in the mixer I can record that signal to WAV by simply arming the track and pressing the main record button.
Cheers,
Malcolm.
*that which came before DAWs, see history, see analog, …. 🙂
It’s a bit convoluted. You can’t just right-click on the Piano Roll and select “Drum Map”, unfortunately.
The Drum Map editor view is tied to a setting in the Preset. To enable the Drum Map editor view, right-click on a Preset and select “Properties”. On the right-hand side of the properties window, select the “Use preset as a drum kit” option.
You’ll then be prompted to create a generic drum map for the preset, which can be a good or bad thing depending on whether the VSTi conforms to general MIDI drum mapping.
Click “OK”, then create a segment on the track that contains your VSTi, and open the editor. You should then see the list of drum map names down the left-hand side of the editor.
Cheers,
Malcolm.
A user on the Camel Audio forum had a similar problem with Reaper last year, which they solved by rescanning:
http://www.kvraudio.com/forum/viewtopic.php?t=270077
Which version of Alchemy are you using?
@Zynewave wrote:
• Added a plugin option selector to the Create New Project page. The first time you create a new project you have the option to build the plugin database. In the following new projects you can select between: “load plugin database”, “rebuild plugin database” and “update plugin database”.
Superb! =D>
This works like a dream, and removes the waiting-for-scanning that used to slow down the Project creation before.
Great effort Frits! 🙂
Hi Frits,
@Zynewave wrote:
Scanning of each plugin produces the various device mapping, device definition, preset and parameter objects. To be able to skip rescanning plugins in case of a crash, then it’s necessary to save the project template file after each scanned plugin.
Why does the plugin database need to be part of the POD file, and therefore part of the template?
Reaper scans for new plugins each time you start it up (by default, but it can be configured to only scan on command) and writes the list of plugins to an ini file in an Application Data folder. You can then create as many Project files (equivalent to Podium projects) as you want without having to rescan the plugin database.
Is there some architectural reason the database can’t be separated from the POD file?
Cheers,
Malcolm.
@abducted wrote:
hello,
could someone please tell me why I can’t record vsti automation anymore?Before, I could tweak any knob on my midi ontroller and the vsti parameter was recorded. Now I can only record pitch bend and modulation .
P.S. : when I tweak a knob directly on a vsti displayed on the screen, it is recorded but when I tweak it from my midi controller it is not recorded (although the knob is moving on the vsti)
I just tested this with 2.27 beta 7 and the Camel Audio Camel Space effect (as an effect on the same track as an instance of Alchemy).
When I tried the same test in another host, all MIDI data I sent from my controller was recorded, the UI movements were recorded and played back, and the MIDI Learn function worked as expected.
I’m not sure which part of this is/isn’t broken, as Podium doesn’t record all MIDI data by default, so I don’t know how much of this is by design and how much might be operator error. 😕
Cheers,
Malcolm.
@Zynewave wrote:
The template file seems ok to me. It imports like shown in the screenshot of your previous post. Can you give me more details about what is not working?
The VSTi does not load as part of the template. All of the tracks do, but no device. Isn’t the device definition meant to be saved as part of the template?
Cheers,
Malcolm.
+10 to separating the plugin database from the Project/Arrangement management.
I would use the Project function a lot more if I didn’t have to do a full VST scan each time I create a new Project. At the moment I have lots of Arrangements, but only one Project per Podium release.
Cheers,
Malcolm.
Hi Frits,
I have emailed you a copy of the template file.
Cheers,
Malcolm.