ZynewaveThanks for the detailed description. I’m thinking that the problem is related to the way that Podium measures the CPU usage. That’s the “Performancecounter: …” line in your interface reports.
Does your AMD machine have multiple AMD processors, as opposed to a single dual-core CPU?
Is your machine a laptop? Or more specifically, does your AMD chip use speed-switching depending on power usage etc.?
Can you try to see if the problem also exists when using a different driver than ASIO4ALL? If you don’t have another ASIO driver, then try the normal wave driver.
The next Podium 2.10 release has a new option that will ignore plugin bypassing in case of CPU overload detection. That may help in your case, if the problem is with the CPU usage measurements, and not actual CPU spikes.
ZynewaveMaybe you have a plugin in the master chain that cannot be loaded. Check if there are any red icons next to plugins in the devices list on the project page.
ZynewaveCreate a new project with your new sound card, and save it as a project template. Load your old project and use the “Project Templates > Load Device Setup” submenu to replace your old device setup with your new setup. You may need to select a different master output mapping, if your monitors are connected to different channels on your new soundcard.
ZynewaveBeta3 is up.
I’ve added a “scale name” text field to the tempo event properties dialog. This enables you to e.g. shorten the default “A Minor” to “Am”, or to select custom scale and set up an exotic scale with the proper name (for example “C Mela Dhirasankarabharana” 😮 ).
ZynewaveHi Daniel,
@DanielK wrote:
1. CPU meter seems to go crazy (red bar all the time and negative CPU usage is reported from time to time) when more than 1 core is used (my cpu is AMD 3200+ dual core), this also causes the audio to dropdown every few seconds, regardless of ASIO buffer size. Once affinity is set to just 1 core it works just fine.
Please describe the appearance of “negative CPU usage”. Can you post a screenshot?
Instead of limiting the processor affinity to one core, try disabling the “plugin multiprocessing” option in preferences. Does this also work to get rid of the spikes? If so, try with a new arrangement using other plugins. The spikes may be caused by a plugin that is not coded to be multiprocessing compatible.
2. I can’t seem to be able to layer multiple VSTi’s together using the same sequence “track”. Is it possible to achieve in Podium? Any workaround?
Not on a single track. You can set up multiple tracks with VSTis, and then make phantom copies of the sequences on the tracks. Changing the note sequence in one track will then automatically be reflected in the other tracks.
I’m going away for the weekend, so I won’t be able to respond to your reply until monday night.
Zynewave“add” is short for “add to selection”. It will select events on the key you press, but not reset selection of other events.
Zynewave@Pigini wrote:
@Zynewave wrote:
Any other uses for scales?
Yes, lots. What level of depth are you planning on?
A programmable variations generator, a master editor?
Thanks for the suggestions, but I’m afraid that is going to take a huge amount of time to implement. For this release I’ll settle with using scales as a visual guide in the piano roll.
Zynewave@Pigini wrote:
@Zynewave wrote:
@adlaius wrote:
I have two requests that are almost certainly too far afield, but hey, why not? First, Hermode Tuning would be awesome. Some (few) instruments have it already, but Logic is the only sequencer (thus far) to offer it. Huge, fantastic feature, and offering it in a DAW vs. a VSTi gives added advantages (offline processing for bouncing to perfect harmonic tuning).
Also, what about native microtonal support a la Scala? A good number of popular synths (Albino, Alpha, Cameleon5000, Dimension Pro, z3ta+, and others) can load Scala tuning files; having host support would be really great.
Hermode tuning and microtonality need to be supported by the instrument plugin. MIDI notes sent from the host are integer numbers representing keys, so the host cannot adjust these for different tunings. I don’t know how Logic implements this. Perhaps it just works with their own instruments, or maybe there is something in the OSX AudioUnit plugin protocol that supports tuning setup from the host.
The universal way of using nonstandard tunings works with pitchbend events, if I remember correctly.
Pitchbend messages apply to all notes/chords playing on a MIDI channel, so it won’t work for adjusting the tuning of individual notes.
Zynewave@LiquidProj3ct wrote:
1. The button’s caption should be the scale’s name [C Major, A Minor, F Major] instead scale number [Scale 1, Scale 2…], it would be more easy to the sight.
Done.
2. And I think there is a bug. Just create any emply arrangement and write the seven notes of a simple C Major, select them and look for matching scale. When you choose any of them, the scale isn’t applied, and it creates an
event in the time line, without any information of the choosen scale.
Fixed.
3. I don’t see the point: why must we select notes before find the scale? It would be more easy and workflowable import a MIDI file and look for the scale without select all the notes whenever exist at least three notes in the selected clip.
You may have recorded a note sequence or manually entered a note sequence in the editor, without knowing what scale it is. The FMS command can be used as an analysis tool for any selection of notes, with the option to apply the found scale to the arrangement. You may also have scale changes in the middle of a sequence, in which case it would yield incorrect results if the FMS command analyzed all notes in the sequence.
ZynewaveAh yes, the “navigator” region 🙂
I’ve been tempted to start implementation of this feature, but at the moment I feel there are more important features that needs to be implemented first.
ZynewaveZynewave@UncleAge wrote:
@Zynewave wrote:
because you can have several editors, and several piano roll regions.
Please explain what you mean by several piano roll regions.
In the default Podium.ini setup you have two piano roll editors. One for the embedded, and one for the separate window. So in that case you have two sets of piano roll configurations. You can add any number of customized piano roll editors that you can switch between with the editor view menu. You can even add more than one piano roll region within a single editor, if you can find a use for that. So a single piano roll properties page in a preferences dialog will not do. You need to select which editor profile you want to edit, and which region within the editor profile you want to edit.
Zynewave@adlaius wrote:
I have two requests that are almost certainly too far afield, but hey, why not? First, Hermode Tuning would be awesome. Some (few) instruments have it already, but Logic is the only sequencer (thus far) to offer it. Huge, fantastic feature, and offering it in a DAW vs. a VSTi gives added advantages (offline processing for bouncing to perfect harmonic tuning).
Also, what about native microtonal support a la Scala? A good number of popular synths (Albino, Alpha, Cameleon5000, Dimension Pro, z3ta+, and others) can load Scala tuning files; having host support would be really great.
Hermode tuning and microtonality need to be supported by the instrument plugin. MIDI notes sent from the host are integer numbers representing keys, so the host cannot adjust these for different tunings. I don’t know how Logic implements this. Perhaps it just works with their own instruments, or maybe there is something in the OSX AudioUnit plugin protocol that supports tuning setup from the host.
Zynewave@UncleAge wrote:
@Zynewave wrote:
Beta2:*snip*
Changelog:
A new “find matching scale” command is included in the piano roll edit menu and context menu, if at least three different notes are selected. The command will present a dialog showing best scale matches, with options for applying the scale to a tempo event in the arrangement.
FMS = Find Matching Scale
I have a clip 4-bars long and a note at the start of each bar. If I select all notes and follow the FMS process a tempo marker is added at the start of the clip. However, if I only select the notes at bars 3 & 4 and do the same FMS process the tempo marker is still placed at the beginning of the clip and not in the timline at the first selected note.
Is this intentional?
Yes. Podium searches backwards for an existing scale-enabled tempo event from the start of the first note. If none is found, it scale-enables the very first tempo event.
I think it would be very annoying if new scale tempo events were added each time you use FMS for a different selection of notes.
If you know you have a scale change at e.g. bar 9, then add a scale-enabled tempo event at bar 9, and using FMS on notes after bar 9 will then change the scale at bar 9 instead of the one at bar 1.
ZynewaveSome of the setup dialogs can be consolidated into one preferences dialog, as you suggest.
And now there is a new one that we get with the right click on the piano roll.
That’s the “piano roll region properties” dialog, and it has always existed but had to be accessed through the editor profile setup. It was just expanded in 2.09, and a shortcut link was added to the menu.
The editor setup dialogs cannot be included into the single global preferences dialog, because you can have several editors, and several piano roll regions. But it would be possible to consolidate all the individual region properties dialogs into one “editor properties” dialog.