German Fafian.
ConquistadorHi Frits,
I have a rather strange problem…when I try and quantize (1/16) Podium will save changes to some midi events and not others.
The best way I can illustrate it is when I click on a midi file and click on quantize inside it will do it but if I click on another file on the same track, it will quantize that as well. Fine so far.
However I am hearing timing issues with the first midi file, so I have to quantize that again! Go back to the other file and click on quantize inside and the notes move again suggesting they too somehow slipped out of the quantize values of 1/16th, which has not been touched through out this project.
If 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?
If so why is it that the two midi events that I am quantizing with quantize inside constantly require re quantizing?
I think even the quantize start and end options are affected by this as well but not 100% sure.
2. FR, really…I like to work with no more than 8 bars visible on the arrange page so that the markers do not overlap. Whenever I save all changes in Podium it resizes my project view so that the entire project is in view. Nice in theory to get an overview but not if you do not want that at that time or work that way. Of course the markers have all overlapped as well by this time.
Every time I have to resize the arrange view to about 8 bars that are visible but this happens every time I re open a project.
If you wish I can send you the project file for problem one. I assume you can easily replicate problem 2.
Cheers. 😉
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.
Conquistador@Zynewave wrote:
If 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.
It is a copy of a sequence, but I don’t think it’s a phantom copy. Either way why would quantising phantom copies align notes differently? 😕
How would such a process be useful or beneficial?
I used Console on the track but then I tried another synth, EVM Neutron (Free) and the same thing happened.
I am sending over the file now. Thanks.
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.
Conquistador@Zynewave wrote:
Either 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.
Agreed. 😉 I thought there some other reasons other than those you mentioned above.
Hopefully you can replicate the quantize problem.
Thanks
ConquistadorJust got this message…
Your message did not reach some or all of the intended recipients.
Subject: Quantize issue.
Sent: 28/05/2005 15:58
The following recipient(s) could not be reached:
‘info@zynewave.com‘ on 28/05/2005 15:58
550 must be authenticated
I will try sending it again. Failing that I wll use an alternative email address.
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.
Conquistador@Zynewave wrote:
Got 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.
The misalignment when corrected still brings up this problem… the notes when quantized in the first event will somehow cause the second phantom copy to lose its quantization state.
Try it yourself and see. The clone phantom sequence seems to indeed separate the connection between the events but why would a quantized midi event when copied not produce another fully quantized event?
Sorry Frits, I don’t mean to go round in circles but I am just trying to get my head around the Podium approach to quantizing copies of files that are linked and why it produces different results even when the events are properly aligned. I have just tried it. 😕
Another issue I noticed is that when the project is closed and re opened it loses the quantised state. Please try this as well.
Thanks
ZynewaveThe 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?
ConquistadorOk…your detailed explanations about phantom copies has really helped. Having used other hosts sometimes you expect a simple copy and paste to work just like other hosts.
Some hosts I think give you the option of creating a linked copy of a clip when you try to copy it. My expectation was that Podium was simply copying my cilp and not linking it. As I said earlier I am trying to understand the way Podium operates as well as the different terminolgy used in Podium.
So far so good anyway, and thanks for your efforts. I have decided to simplify this problem and delete any links to the original file and quantize the original again, double check the alignment and crop the sequence ( what specifically does the crop feature do, a type of trimming of the event?) this approach seems to have cleared up the midi timing issue.
I guess if I had only ever used Podium as a sequencer that would have made the learning process much easier for me. 😉
But for that to happen you would have had to leave your job at TC Electronics alot earlier to finish Podium around 2001 / 2002!
Saving arrangement zoom settings is on the plan.
Glad to hear it and looking forward to it.
By the way I was puzzled as to how to save changes to a plug ins exisitng preset. But you simply click on the New button in the preset area and make your changes on the plug in ! This is really well done.
It’s actually quite odd because I tried Podium about 6 – 9 months ago for the first time and gave up because I just could not get a sound out of it!
There was even a thread on KVR with some existing Podium users supporting your cause but many like me really wanted to use it but could not understand how after 30 minutes of trying or longer we could not get a beep out of Podium, really! I will find the thread if you want.
Anyway about 4 months ago or so I read the superb reviews of Podium on KVR and one reviewer actually posted a link to his own self made quickstart. So I thought with all these glowing reviews let me try this again and use his quick start.
I think even that failed because somewhere in the quickstart he forgot to mention that you cannot access a plug in interface without hitting play first or something along those lines so I was well and truly stuck. I simply hit the play button and noticed the E button appear and thought finally!
So here I am today!
Anyway keep it going Frits. 8)
Thanks 🙂
Zynewavewhat specifically does the crop feature do, a type of trimming of the event?
It is similar to the crop commands you find in graphics editors. It deletes everything outside the range of the sequence shown in the sequence event.
I will find the thread if you want.
I have read all user comments on KVR regarding Podium. What’s interesting is that whenever these threads appear, they are actually creating more traffic to zynewave.com than e.g. a Podium news item on the KVR main page can generate.
ConquistadorThanks for the ‘crop’ explanation.
I have read all user comments on KVR regarding Podium. What’s interesting is that whenever these threads appear, they are actually creating more traffic to zynewave.com than e.g. a Podium news item on the KVR main page can generate.
Ironic indeed and very funny. 🙂
German Fafian@Conquistador wrote:
Thanks for the ‘crop’ explanation.
I have read all user comments on KVR regarding Podium. What’s interesting is that whenever these threads appear, they are actually creating more traffic to zynewave.com than e.g. a Podium news item on the KVR main page can generate.
Ironic indeed and very funny. 🙂
Well. I came in for a comment about Podium I read in KVR. 😀
Haven´t left since 😉