ZynewaveThanks for the mp3s. I actually think the Podium mp3 sound “fatter” 😛
When I load my z3ta+ demo on a new track and call up the “031 stella c2 (velo)” preset, and play on my midi keyboard, it sounds exactly like your Podium mp3. Some things you could check: Verify that you don’t have several z3ta+.dll files installed. Maybe Sonar uses a different version than the one found by Podium. Also check if the MIDI file you imported into Sonar created parameter automation tracks as well. I tried modifying some of the filter parameters and oversampling setting in z3ta+ but I could not get near the sound of your sonar mp3. Changing the samplerate in the project did not affect the sound much either.
Otherwise I don’t know why there is this difference. Try playing this z3ta+ preset in some of your other hosts, to determine if it is only Podium that produces a different sound.
ZynewaveIt’s too far away for me to put a deadline on it. Features such as timestretching, Rewire, a couple more zPlugins etc. is something I’m going to work on before looking at OSC support.
ZynewaveI can send over the midi sequence that I used as well as my project file.
Yes please, and an mp3 of the wrong/correct sound would be useful as well.
Zynewave@acousmod wrote:
There is also a bug : when I resize an event, the length of the fade out changes !
It is shorter when the event is long and longer when it is short 😯
For example :
– the event is 60 seconds long
– I make a 10 seconds fade out
– I shorten the event to 20 seconds by dragging the right handle
– the fade is longer on the timeline (about 15 seconds)
– the numeric fade value is always 10 seconds but it lasts more
Or try to drag the right handle of an event : the fade out becomes shorter and disapears.
On the other hand, the fade in is stable.
I’ve checked your project file, and the problem happens because you play a 44k1 sound file in an 48k arrangement. One of the next major things I am going to look at is sample rate conversion. The implementation of this feature will fix issues like this one. You sent me a project a while back where you had a problem with curve sequences that did not align when being merged. This turned out to be a similar problem where the curve sequence used a different time resolution than the arrangement. This could have happened if you dragged the curve sequence object between arrangements that used different time resolutions.
So my advise for now is to make sure your sounds are the same samplerate as the arrangement. I’ll solve the time format issues when I start on SRC/timestretching.
Zynewave@acousmod wrote:
I like the simplicity of the double click to open the fade editor, but it would be even more easy and intuitive to be able to double click directly on the fade zone instead of only the little handles.
If we double click somewhere between the fades it is the sound editor window, and if we click inside a fade it is the fade editor which opens.
If the fade out starts immediately after the fade-in you would not be able to double-click to open the sound editor.
Zynewave@acousmod wrote:
Do you have any tempo changes on the timeline?
Absolutely not.
Cannot you reproduce it ?
No. Please email me your project file.
Do you mean that it will use more CPU while editing (which I understand and is not a problem) or while playing (which would be strange and annoying) ?
It will require more CPU power to draw the graphics. So zooming may become slower if the waveform should be scaled to the fade spline curves. A linear fade in/out is easy to implement and will not use much CPU power.
Zynewave@Max wrote:
1. Fade in/out curve can be edited with a mouse, but curve graphs is not updated in realtime when changing time/curve parameters – need to click on the graph to see curve changes. That’s wrong IMO.
The curve is updated as soon as you tab away from the value input field. You can also click and drag horizontally in the upper and lower halfs of the curve graphs to edit the curve values.
ZynewaveI tried various things while recording and I have found a bug which most likely is the one you have noticed. The problem is connected with the auto-extension of recorded note sequences. I’m guessing that the implementation of this feature from 1.71 has caused the bug to appear:
Sound and sequence events that are moved during playback will start playing immediately and no longer requires playback to be restarted.
I’ll trace the bug tomorrow, and hopefully release a bug-fix version later this week.
ZynewaveThere is a little problem when splitting an event which has some fades settings : the begining of the second part have the same fades as the first part and the end of the firts one the same as the second one.
It is a really annoying behaviour…
Perhaps is this made on purpose ?
If you think that it can be useful in some case, could you make it an option please ?
Currently when splitting an event, the two new events are assigned the same fade-in/out settings as the original event. Would you prefer that a split should always set fade-in/out to zero, or would you want the possibility to define the default fade times for splitting?
There is also a bug : when I resize an event, the length of the fade out changes !
Do you have any tempo changes on the timeline?
can you make the lines visible also when the mouse is not over the events ?
The fade curve or the vertical fade-in/out handle lines?
can you allow to drag also the vertical lines (not only the fade handles), like for the level line ?
I have not done this, because I think it can make it difficult to drag the event. If the event is zoomed in at about 10-20 pixels width, the drag handles will cover the entire area and you will not be able to click at the middle of the event to drag it.
A question : the fade edition actually doesn’t allow to draw an “inverse S curve”.
In other words, the top part of the curve cannot be negative, and the bottom part cannot be positive.
It is sometimes useful.
This would require an additional 4 coordinate parameters in the fade properties. I did not add these because I wanted to keep the fade-in/out editing simple.
And I suppose that the drawn amplitude will reflect the fades and levels settings in a future version ?
Would it be sufficient if the waveform within the fade-in/out range is scaled linearly nomatter the shape of the fade curve? If the waveform should reflect the spline fade-in/out it will require a substantial amount of CPU to draw.
Zynewave@Podianer wrote:
I had this when Playing Halion. Some notes are delayed or eaten up, thus resulting in a awkward sound.. Same happens when playing The Grand..
Did the Podium CPU indicator flash red when the mistimed notes occurred?
ZynewaveBut what do you think about an option in the preferences to automatically select the track when selecting a clip ?
That may be a solution, but it should be optional. Auto-selection of a track would mean the track inspector would be updated, and if you use the MIDI input focus track option the instrument played may change. Not always desirable if you have selected an instrument track for monitoring, and want to adjust events on other tracks.
It is hard to make more intuitive to use, and it works the same for multiple selection.
Do the hosts you mention have a ‘focus track’ feature? If you select multiple events on multiple tracks, do all the tracks then get selected?
Zynewavebut the monitored sound is awkward..
Define ‘awkward’, please.
ZynewaveHi francois. I moved your post from the 1.72 release topic because I needed to lock it for the next release.
there is a little problem since version 171 , in midi recording
I need more info, because between 1.70 and 1.71 I haven’t touched any code that should influence the MIDI response.
the note echoed(the sound) is not correct, some time delayed, while the event recorded on the track seems to be ok.
Is the problem only that the notes are sometimes delayed?
Does this happen no matter what VSTi/external MIDI synth you are playing?
I am using WinXP now.
Does 1.70 work ok on your new WinXP installation?
I assume that you are still using ASIO4All. Check that the buffer settings are like they used to be on your older Windows installation.
ZynewavePodium 1.73 is released. This has the basic fade-in/out capabilities that have been discussed in this topic. This is just the first step, but I release it so that you can try it out and give feedback on problems or ideas you may have. I will continue working on e.g. automatic crossfades, applying fade edits to all events in a multiple selection, fade curve defaults etc.
Zynewave