Zynewave's Forum Page

@Markus wrote:

Hi guys

I’m back! Like it or not 😮

Podium has take some rly nice steps while i’m was away. I read that Frits is now focusing on inspector. So here is one idea to develop it to even better!

Pls let me know what you guys think 8)

I’m planning to do some more work on the inspector in the coming releases. This will include a redesigned group panel which may be a solution for your “FX slot” in the screenshot. Hopefully I’ll complete the inspector changes before the end of 2009.

@Malcolm Jacobson wrote:

@Zynewave wrote:

I can add a “clone and crop sound event” command, which will reduce two steps to one. Which additional steps do you want automated?

The “export to sound file” part.

How about replacing all 4 steps with a “convert event to audio file” option?

I’m a bit reluctant to add an “export” command to the edit menu (or the event right-click menu), as I don’t think it belongs there. How about if I add “Export Sound Event To Sound File…” to the sound editor file menu. This will do an export limited to the range of the clicked event. The range is highlighted with a lighter background in the sound editor. This bypasses the need to do the clone and crop edits. What you need to do is select one of the events (in your first screenshot), and then use the file menu in the sound editor. Does that count as one or two steps? 😉

@Malcolm Jacobson wrote:

@Zynewave wrote:

Is there a reason why you want to use bounce for your export? In your screenshot you have no effects on the track, and there doesn’t seem to be fade-in/out on the individual events, so the bounced audio will be identical to the source audio.

No, I don’t want/need to use bounce for this process. I should have used a separate file for that image. The track I dragged onto the arrangement had “bounce” in the file name, from when it was originally bounced. Sorry to add to the confusion.

I didn’t mean why your sound event is named “bounce”. I meant why you want to bounce the track at all, since the result of the bounce rendering will be the same as the events you have placed on the track?

@Zynewave wrote:

If you just want to export the clips, you could use the “clone phantom sequence” and then “crop unique sequence” on each clip. Then you don’t need to do any edits in the sound editor, but just use the “export to sound file” command in the sound editor file menu.

OK, I tried that. It’s an improvement, but it’s still 4 steps per event. Another editor I use can accomplish this in one step by simply right-clicking on the event and selecting “glue” (an unfortunately named option but it does the job). Is it possible to get something like this in Podium?

I can add a “clone and crop sound event” command, which will reduce two steps to one. Which additional steps do you want automated?

@Conquistador wrote:

Why? The right click menu is more accessible for bounce options than before but I think more options are needed. That will make it even longer :-k

What are these additional options?

a. Render and replace file within Punch in range: That may likely solve Malcoms issue and make bounce files shorter, side stepping the need to crop files after a bounce.

b. Stereo to Mono Bounce Option. (Podium really needs a mono switch on each track as well IMO).

c. Multitrack bouncing:
1. Multitrack bounce (Ignore track FX)
2. Multitrack bounce (Ignore master FX)

d. Replace track events: Or bounce in place. This will overwrite any audio on the track being bounced…not just within the Punch in range as suggested in Point a.

e. Track file convert: When you want to Render a track you should have the file convert options pop up. As of the current beta you only get that when you export the file AFAICT.

As you can see that will lengthen the right click menu but in a dialog box (with drop downs) it will be far easier to navigate than even the existing options in 2.22 beta2.

I’m sorry, but I don’t understand the intended use of most of these suggestions. I’m trying to simplify things, and keep the options to a minimum. I’d like to keep the bounce setup separate from options that deal with file export. That’s what the new “export to sound file” dialog is intended for.

The screenshot you show and some of your suggestions are a mixture of bounce options and file export options. The bounce feature in Podium is a way to reduce the CPU usage in the engine, and so bounced audio is an exact copy of the audio extracted from the engine at the bounce point. If you want to manipulate the bounced audio, then you do that by moving the bounced audio to a new track and do your edits there.

@thcilnnahoj wrote:

– You may want to adjust the default size of the editor window (if not related to screen size) or horizontal size of the piano keys, as the new linked velocity buttons don’t fit anymore.

Done.

– A minor inconsistency concerning the MIDI/note editor. The EE (embedded editor) will in some rare cases copy the velocity region height from the SWE (separate window editor), though they’re fine with having different region heights most of the time. Here’s one way to reproduce this:

Switch to the ‘Editor’ profile > select a MIDI sequence > in the EE, set height of velocity region with the drag-handle > double-click a MIDI sequence to bring up the SWE and leave it there (it should have a different velocity region height) > click on a sound or curve sequence, so the EE switches to a different editor > select a MIDI sequence again > the EE should have assumed the velocity region height from the SWE.
…That’s a mouthful! :-#

That’s because they are using the same editor profile. Besides the settings you find in the region dialogs, the profile also logs the “last used” size of resizable panels. So if you have two editors open showing the same profile, the last resize action will determine the size used the next time the editor is opened.