ZynewaveRegarding the statement above…if we want to will we still be able to?
Yes. Pressing the H key (or using the menu) will still toggle display of the mixer strip for the track.
What purpose will the Send button (under the Pan button) on the left of the screen serve now, possibly to hide / show the new send locations?
It shows/hides the send dials on the bus send headers. Hiding these can save some space when you are not adjusting send levels.
Will it be possible to hide / show all track headers?
The “compact headers” option is still available in the mixer view menu.
In the image above… your have “Voxengo SP” (instead os Voxengo Span) and “Classic Master Li” which sounds like some sort of kung fu grand master or something fighting off 10 men all by himself (instead of displaying the full name Classic Master Limiter).
Of course being able to extend the width of these strips would be an option but…if that is a problem at least a tool tip could appear when the mouse cursor hovers over a name in the track header. This could show the full track name.
Tooltip popup of the full name of the track and any objects assigned to it, is already on the plan. That’s why I’m moving the bypass/edit buttons from the right edge to the left edge of the strip. The tooltip popup will thus not obscure the buttons.
Since the last screenshot, I’ve attached arrows to the top of the headers, similar to the arrows in the tracks region. I’ve also moved the input and latency rows down at the bottom of the mixer, which further emphasizes the bottom to top signal flow.
ZynewaveThe latest mixer redesign (coming up in 1.86):
This shows the new extended track headers in the mixer. They now contain controls for mappings, presets and send dials. This is more space efficient for the bus send and effect insert tracks. There is no longer any need to show the mixer strip for these tracks, unless you want to check the meter of the track output.
I’m considering moving the map, preset and param rows on the mixer strips up to the mixer header as well.
Thoughts?
ZynewaveMidi Time Code is on the list already, but my question is: “How soon?”
That’s difficult to say. I’ll probably look at it when I begin implementation of control surface support. Hopefully within this year.
the dragging/exporting of midi sequence events to the list at the right, which should save that parts as midi files
I’ll keep that in mind.
Zynewavei would like to be able to change the name of a project by right clicking in the project list , actually the only options are open and remove
The project name is stored in the project file, so renaming the file is not enough. You’ll need to open the project, edit the name in the project properties dialog, and then resave.
ZynewaveFinally, how easy is it to “copy,” “ghost,” or whatever the term is, a MIDI clip throughout the next x# measures or so? In creating a (rock) drum part, for example – with the Drum Editor – it makes more sense productively to just create one measure if the next 15 are all the same and then just copy them forward, if you know what I mean.
The quickest way to do this: Select the one-measure sequence event in the arrangement editor, and press the Insert key for each “phantom” copy you want to append. If you want to paste a large number of copies, you can hold the Insert key and let auto-repeating kick in.
ZynewaveDo you simply drag another one from the map onto another track?
That’s what you do in the case of insert mappings. With global plugins (i.e. plugins that have multiple mappings for a single instance), you need to create a set of mappings for each instance you want to use. Right-click the folder or any of the mappings for the plugin in the project start page device list, and select “New Instance”.
is the “track” NOT the whole horizontal strip?
A Podium “track” has a dual purpose. It can function as a standard track with a track “lane”, but also works as a modular connection of the MIDI/audio flow. Inserting tracks without a track lane is mostly used to set up a chain of bus sends/plugins.
ZynewaveZynewaveI’ve had McAfee On access statistics window open and guess what…
Everytime a spike occured On Access scanner changed it’s last file scanned and upped it’s total number of files scanned.
I have a very string feeling that this is the cause.
I think you’re right. It’s most likely the scanner file access that temporarily blocks the Podium audio thread.
Zynewave“Sensible” in what way?
You describe some of the problems in your post. I’m guessing that what you really want numbers for, is track lanes and not tracks in general. Since you can show/hide the track lane with a shortcut, how should this affect the numbering of the tracks? Should the track numbers be assigned to a track when created, or should it automatically adjust according to changes in the track hierarchy?
ZynewaveIt’s tricky to make a sensible numbering due to the hierarchic organisation of the tracks.
Personally I dislike using numbers to identify tracks, but I know some prefer to have numbered tracks. I’d rather organize tracks under group tracks to get a better overview in arrangements with a large number of tracks.
ZynewaveTried dropping latency in drivers down to 4ms.
Seemed to make no difference on spikes or on avg of CPU monitor
Do the spikes occur less frequently, if you increase the latency/buffer size?
Do the spikes occur more often if you move the mouse or press any keys?
BTW: Are onaccess virus scanners known to cause issues?
Not that I’m aware of. But try to temporarily disable it, to see if this has an effect.
After you have had a few spikes, go to the report page in the interfaces dialog, and save a report. Paste the report here or email it to me.
ZynewaveI’ll consider hiding the gain/pan dials in the mixer, instead of just dimming them. I’ve also forgotten to indicate dimmed state of the recently implemented gain faders, so hiding the faders seems like the least confusing solution.
ZynewaveWhy, if a track is designated at a Bounce Track, do adjustments to the level sliders for the track have no effect on the output level of the track (containing the bounced audio)?
Bounce recording captures the output of the track, after all processing is applied. This includes level/pan processing. Level has to be processed before the bounce capture because otherwise level/pan automation child tracks (which become muted when bounce is enabled) would not be processed. This question has come up quite often, so I may decide to change this behaviour. To adjust the gain output of a bounced group track, you can add a parent audio enabled track.
why, after Bouncing to a track, do the plugin’s of the Child Tracks remain active, but the tracks are muted?
If by “active” you mean loaded in memory, then you have the “unload plugin…” option in the track properties. This option is off by default, because some plugins take a lot of time loading (e.g. sample set based plugins). So if your workflow involves frequent toggling of bounce mode, you would often prefer that the plugins are always loaded.
ZynewaveIs it true that if plug ins are not used in my arrangement then they don’t affect anything I have lots of plig ins in my folder but very few loaded.
Plugins not loaded in an arrangement have no effect on performance.
Make sure you are using ASIO drivers and not Wave drivers. Try adjusting the buffer size to see how this affects the spikes.
Does the spikes occur with a steady fixed interval?
Also try disabling the plugin multiprocessing option in the preferences dialog. Plugins that have problems with multiprocessing may cause CPU spikes.
ZynewaveThe email address is listed at the bottom right corner of the home page.