ZynewaveCan you email me your project file, so I can see how you have set up the loop recording etc.?
For a 2 bar roll-back to work, you need to start recording at bar 3. Place your edit cursor at bar 3, start recording, and you’ll notice that the play cursor jumps back to bar 1. Also remember that you need to activate the metronome in the transport toolbar to enable the roll-back.
ZynewaveThe recording of the first note should not depend on whether looping is enabled or not. I just tried here on my system, and I can record the first note fine with looping enabled.
Be aware that if you press the key before the recording starts (or before the punch-in position if you have punch-in enabled) then the note won’t be recorded.
ZynewaveI split your posts from the 2.08 release topic into this support topic.
What kind of MIDI controller are you recording with?
If the first note wasn’t recorded, does that mean it didn’t sound in the VSTi as well?
There is a “roll back” option in the preferences/metronome page. So if you need two bars lead, you should start your recording at bar 3.
Zynewave@michi_mak wrote:
Hi, i’m playing with recording vstis right now : when i record in loop mode allways the first note will NOT be recorded – does not depend on the vsti!! – i allways start with an audiorecording and play it in loop to create beats and leads and stuff …
or am i missing something?
regards,michi
Do you mean MIDI input recording or VSTi audio bouncing? MIDI loop recording is not yet supported, so if you record MIDI input with looping enabled the notes will be overlaid onto the same sequence. One of the next releases will support MIDI loop recording using the same audio multi-take system that was introduced in this 2.08 release.
ZynewaveI’m currently doing some redesign of the piano roll editor for the 2.09 release, so this bug should be fixed in that process.
ZynewaveHi,
No plans on building an arpeggiator natively into Podium. But one of my next big feature implementations will be support for MIDI plugins (hopefully first half of 2009). Once this is done you’ll be able to use arpeggiator plugins to control your synths. I may even develop a Zynewave zArp plugin in the future, which then will provide an integrated arp editor in the Podium UI.
Frits
ZynewaveAs the texture image is tiled, it is best to use “seamless textures”:
Zynewave@Conquistador wrote:
If you use the freebie Spitfish you can see this behaviour quite easily (hopefully anyway). Simply holding down a knob and moving it around for a few sconds will cause Podiums screen to shift. Of course if one was to automate another plug for instance (cut offf on a synth) you would be holding that parameter knob much longer than a few seconds.
I downloaded Spitfish. This plugin unfortunately does not implement the proper method for keeping the host UI alive when you click and hold one of its controls. This means that e.g. the Podium play cursor stops moving as long as you hold the control. But I do not get the “not responding” message. I can click and hold the Spitfish control forever without seeing this message. I am puzzled why you get this not responding message.
ZynewaveThe “VST Plugin Folder” you select on the create new project page (which you can also set in the Preferences dialog) is stored in the Podium.ini file.
If your problem is that the folder you select is not remembered when you get a crash, then you can get around this by exiting Podium (or saving the setup manually) after you have selected the VST folder, to force Podium to save it in the setup. The next time you start up Podium the VST folder you last selected will be remembered.
Zynewave@Conquistador wrote:
I have reduced the cores to one for Podium but if I click on the screen when Podium loads a project, the screen still shifts left, for a few seconds.
I was expecting that. I was thinking more about the problems you have with plugin editors, when I suggested limiting the cores to 1. Let me know if this has changed anything.
ZynewaveOk, then I don’t understand why you want the project saved before the plugin scanning. What’s the point of saving the template project when it’s not fully created?
Zynewave@Conquistador wrote:
However…I could not access Affinity settings for any audio hosts I have…Project 5, Sonar..CD Architecht e.t.c
Can’t you open the dialog, or are the CPU check boxes just grayed out?
Maybe it has something to do with the audio/MIDI driver that you use in your hosts. Does it change anything if you disable all MIDI/audio drivers in Podium and then restart Podium?
Zynewave@aMUSEd wrote:
My main point though is the plugin scan should come after the project has been saved otherwise you can never save it if it keeps crashing on scan. Possibly what it needs is a “scan on next startup” or something or just an option to save the project before scan commences.
When you say “save the project” do you mean saving it as a template project?
Zynewave@aMUSEd wrote:
@Zynewave wrote:
@aMUSEd wrote:
I’m still seeing the brushed texture even though I set it to be off.
You can’t set it to off. If you want a blank bankground then you can create a solid colored rectangle (at least 32×32 in size) in MS paint, and use that bitmap file as the texture. Use the “dye texture” option to make it match the color scheme you use.
Oh – since this came up as a response to my request to be able to turn off the texture I assumed by making the texture grain the same colour as the background that would effectively make it disappear – I see now it’s a bit more convoluted (though why not just have an “off” I don’t know)
IMO, it will not look good with a purely blank background that has the same color as the panel color in the color scheme. The texture is painted on areas that are unclickable or that does not show content, so having those areas look identical to the tracks region etc. will add confusion I think.
Zynewave@aMUSEd wrote:
The new release seems to be crashing a lot on plugin scan which is making it very hard to create a new project. I really wonder why the process of making a project involves scanning the VST folder before the project is saved because every time I get a crash I have to start again making a new project.
I haven’t touched the plugin scanning code for a very long time. Is it your perception that the Podium scanning has become unstable, or do you think it is new plugins you have installed that could be the cause?
Are you familiar with how project templates work? If you scan your plugins once and save that project as a template, then future new projects can be created with the “Project Templates > New Project” submenu, rather than the “Create New Project” page.
On the other hand if I don’t do it at this point, if I choose to untick the scan plugins and later on do the scan using the “Import plugins from folder” and add folders one-by-one so I can rule out what is causing the crashes Podium doesn’t then sort the plugins by the folders they are in which creates a very unorganised list.
If you select multiple devices in the devices list, you can right-click and use the “Sort Alphabetically” command.