ZynewaveZynewaveThe sequence events on the tracks are like ‘windows’ onto the underlying sequence. The second sequence event in your project is not placed on a grid line and also the ‘window’ start offset into the sequence is not on a grid line. You must at some point have dragged the sequence start without having snap activated. Snapping the sequence event position in the arrangement editor still misaligns the note events inside because the sequence start offset is not on a grid line.
You can verify this by opening the editor window in turn for the two events. Even though the two sequence events show the same area of the sequence, the grid lines in the editor are different for the two events. To solve this, use the ‘clone phantom sequence’ on the second event to make it unique, and then use the ‘crop unique sequence’ menu to get rid of everything outside the extent of the sequence event.
I hope this doesn’t add to the confusion ❓
Another issue I noticed is that when the project is closed and re opened it loses the quantised state. Please try this as well.
What do you mean with quantized state?
ZynewaveGot the project. The quantization problem was indeed the situation I described with phantom copies. The two sequence events you have on the track are referencing the same sequence. This is indicated by the circled ‘+’ icon shown after the sequence name on the event. The two events show almost the same part of the sequence but is slightly misaligned.
If you want the two sequence events to be unique, then use the ‘clone phantom sequence’ context menu on one of the events.
ZynewaveEither way why would quantising phantom copies align notes differently?
The quantization of events inside sequences always follows the bar/beat alignment of the arrangement. If you e.g. are using bar quantization and one phantom copy is placed in a 4/4 part of the song and the other is placed in a 3/4 part, then the bar sizes/quantization is different. Also, If using e.g. 1/16 quantization, and the start of the two phantom sequences are not placed exactly on 1/16, then the quantization will be different depending on which phantom sequence you apply the quantize to.
ZynewaveIf you quantize midi notes, and should you for whatever reason click on them to quantize again with the same value the notes should not move…correct?
Correct. However, if you put a phantom copy of the sequence on a different time position, quantizing either of the two phantom sequence events may align the note events inside differently.
But I assume your two MIDI sequences are unique, so it could be a bug. Please send me the project file.
Saving arrangement zoom settings is on the plan.
ZynewaveI did not manage to recreate the bug on my system, but I looked through the code and found a timing-related problem with the panel animation that could be the cause of this bug. Fix will be in 1.33. If you encounter this bug again, please let me know.
ZynewaveHow/where do I find that file?
Use the ‘save color setup’ in the setup menu.
ZynewaveOnly issue is that I cannot drag a midi file from RMX to a track in Podium.
That is correct. It will be possible as soon as I implement dragging of files from Windows explorer onto tracks in Podium.
ZynewaveDo you understand something ???
Not much I’m afraid. The two project files you linked seemed ok to me. The changes I’ve made for releases 1.30 to 1.32, should have no influence on this. Could you email me the project saved with 1.31 that was causing the problems?
ZynewaveThanks for your comments,
The incomplete guide is indeed what is holding me back from promoting Podium. Once it is done, I’ll probably start out by putting Podium on download.com, buy banner-advertisements on e.g. kvr, approach music magazines for reviews etc.
I have no plans at all of getting Podium into a box and onto shelves in stores. That may still be a huge market but I believe that online sale of software is the way to go. As a one-man company I certainly never will have the resources to market and sell Podium as a boxed product.
Frits
ZynewaveI’ll start experimenting with inlining the sequence/sound editor windows. I don’t think it will be like the new list page. Rather I will try to put it into the arrangement editor as a new region type. Similar to how the mixer region works. But I may change my mind.
ZynewaveI wonder if Podium can operate as a multithreaded application? Maybe the gui split that Frits spoke of earlier in this thread falls into that category.
There are plenty of threads in Podium. The audio processing is one thread only, so that is why it cannot be split to multiple processors. There are other things in the engine that runs in separate threads, so that will benefit from multiple processors also. The GUI is also a separate thread.
ZynewaveZynewaveZynewaveI have not yet had the chance to test Podium on dual CPU systems, or on the Windows64 beta OS.
When running on dual CPU-systems, the engine (and thus all plugin processing) will only utilize one CPU. The Podium UI will however be able to run on the second CPU, so you can consume close to 100% on the engine CPU without causing the UI to get sluggish.
The Podium application uses only standard Windows functions, and the installer is using the Microsoft Windows Installer database, so there should be no problems running it on the new 64-bit OS.