ZynewaveI assumed having a parameter ‘inside’ a track allowed you to view parameter curves and midi data on the same track, which is cool. But I there doesnt seem to be any way of created new midi data in that track. The curve editor is always displayed.
Parameter sequences cannot be overlaid onto other audio/note sequences. Tracks with parameters assigned are reserved for curve sequences.
Also, Im assuming that if you want more than one parameter for a track…child tracks have to be used.
Correct,
…Which begs the question…why have a parameter ‘inside’ a track anyway. Why not just stick to child tracks.
If you e.g. have an audio enabled group track, you may want to automate the level as the only parameter, in which case you can assign the level parameter directly on the group track.
But you’re right, it is recommended to stick to using child tracks for parameters.
ZynewaveHi planist,
Is there a REAL GAPLESS Audio Engine like Ableton LIVE?
Without being absolutely sure what you mean with gapless, I would say yes; There are no cases where the audio engine is stopped in order to perform edits. Plugins and external hardware can be inserted on tracks while playback is going on. etc.
What features are missing yet, that you know from other Sequencers?
Check out the Future Development topic to see what features are missing.
Frits
ZynewaveI discovered something else (real problem i think):
Oooh, that was a good one. I have just fixed it. Fix will be available in 1.02.
ZynewaveYes, that’s how I intended it to work 😉
How is Podium to know that you didn’t want it to look like this? Maybe you deleted track B because you wanted to insert/move some other track there. It could be a nuisance if Podium were to try to intelligently reorder the indentation.
ZynewaveAt some point I intend to implement an archive function in the Project Wizard. After finalizing a project you would use this to pack the project and all referenced audio files together in a zip file.
Including wave files into the Project file is also something I considered a couple of years ago, but I decided against it. It would not be an efficient means of storage for the everyday work on a project. On the plan is an option to create sub folders for each arrangement within a project, to keep audio files for each arrangement separate.
ZynewaveOk, I just experienced a Battery crash. I did it by entering the options dialog while the arrangement was playing. Debugging info told me that Battery made an illegal action in the sample processing function. Could you try to disable monitoring of the arrangement before opening the options dialog, and let me know if this allows you to work with Battery without crashes.
ZynewaveWould the movement be “snap to grid”? Today when I change note lenghts there´s no snap to grid.
If the quantize snap is enabled, then resizing notes with the mouse will snap to grid. Or do you mean something else?
ZynewaveI managed to bring up the options dialog inside Podium once….then changed it. But the i pressed play, and Podium reported an error in a dialog box….except this time it looked like a Podium defined error.
What sort of error? Was it the dialog saying that the plugin had performed an illegal action, and that you should save the project and restart Podium?
ZynewaveThe last demo of Battery that I tried, did not allow setting the output configurations.
I assumed you meant the crash occurs if you try to change the output configuration, or does it crash even before the options dialog appears?
ZynewaveZynewaveWhat version of Battery are you using?
From the NI website I found this in the 1.0.1 patch info:
Under certain conditions BATTERY crashed FruityLoops. Fixed.
Could be the same that causes Podium to crash.
If you change the output configurations in Battery using another VST host, will Battery then import properly in Podium afterwards?
ZynewaveYes!, instant crash, fortunately, when I run it in debug mode.
Apparently it’s a long time since I tried using the MIDI metronome 😳
Fix will be available in 1.02
Thanks for the help.
ZynewaveOk, that is very helpful. I’ll look into it tomorrow.
Have you enabled any MIDI output interfaces in the interfaces dialog?
ZynewaveI assume it’s the audio processing of the metronome that crashes. Just to make sure; could you try to disable the ‘output to audio interface’ option, and see if this crashes?
If not, then enable the audio output and disable ‘output to MIDI interface’. Crash?
If it crashes, then try to set the base channel back to 1 and disable ‘stereo’. Crash?
Sorry for all the trouble, but these tests will help me to narrow down the area of the code where the crash occurs.
ZynewaveDoes the metronome work (outputs sound) up until the crash? Is there any sound distortion at the moment the crash happens? Have you changed the default configuration for the metronome in the preferences dialog?