sam ci have and use Neb 3 with Podium………..it is one fantastic plug in!
sam cFrits, that is really cool you went to all of the trouble!
Thanks!
sam cFrits, after spending a few days with 1.96 I think you did a great job with the track inspector and tying everything in.
sam c@Zynewave wrote:
What I described was a suggestion of how it could be implemented. Currently it is only the timesig/tempo that is shown in the transport toolbar. This field could be widened to show timesig/tempo on the bottom line of the field, and marker name on the top line.
i see what you are suggesting. i would agree that any live marker visual would be a good idea.
thanks
sam c@Zynewave wrote:
@sam c wrote:
frits, the diamond bundle you are demoing must be 5.0 or 5.2. as i said, there is no problem there. it is new plugs that are 5.7 and higher.
SAW, reaper and tracktion are accepting these new plugs. both saw and reaper developers also do not have ilock. i only mention this to indicate there must be a way to overcome this…….i hope.
do you want a copy of my waveshell 5.7 and 5.9.5?
I’ll have a look at the waveshell technology once the 1.96 release is done. If it is not too timedemanding, I’ll try to add native support for the waveshell.
I doubt that having just the 5.7 waveshell will help me, and I also fear it could corrupt something if I try to mix a regular waveshell dll with the Diamond demo plugins.
thanks.
sam c@Zynewave wrote:
having the marker change name as the play cursor passes it? it really makes sense.
I don’t agree. The marker name and the time signature/tempo text on the lane below were intended as visual clues to the zoomed time range, like the bar/beat and time labels on the timeline ruler. In the case of the timesig/tempo you have an indicator in the transport toolbar to show what is active at the play cursor. If you want an indication of the active marker at the play cursor, then this could be shown next to the tempo indicator in the transport toolbar.
thanks for the response. i guess we don’t agree. i don’t understand how your suggestion works. i look at the bar/beat in the transport toolbar but it does not indicate verse. if i look at the tempo indicator i do not see verse 1 or 2, etc.
i also noticed that if the engine is not running and i move the time line…. the marker name changes at the left time sig/bpm each time the marker passes. this is the way i think the marker should work?
imho, there is no visual for the marker changes, there are just markers.
sam cFrits, do you have time to please respond?
thanks
sam c@Conquistador wrote:
I totally agree with the idea. I think you FR’d this before. No harm in mentioning it again of course. 🙂
yes, i did ask before. i am just hoping for a direct answer to both of these questions………
sam cany thoughts Frits?
also, what about the track cursor & marker, any comments there?
thanks
sam cfrits, the diamond bundle you are demoing must be 5.0 or 5.2. as i said, there is no problem there. it is new plugs that are 5.7 and higher.
SAW, reaper and tracktion are accepting these new plugs. both saw and reaper developers also do not have ilock. i only mention this to indicate there must be a way to overcome this…….i hope.
do you want a copy of my waveshell 5.7 and 5.9.5?
sam c@estwing wrote:
hi Sam
I always seem to have empty space within the inspector so why does it need more screen? but if you open zReverb for example you can maybe see where Frits is coming from.
M
mart
certainly these things get pretty subjective. personally, i think podium coud benefit more from other improvements.
frits has his plans and it is his design………..but, he is hoping to sell it to folks like us………..
sam cthe plugs that podium will not recognize are ….Waves API and SSL for example. Waveshell 5.7 and 5.95. everything above 5.2 podium simply cannot load. it seems the other programs i have don’t treat the recent releases any different?
sam c@Zynewave wrote:
I hope you see that the inspector now uses the maximum available height of the window, instead of the limited space within the tracks region. This was a necessary design change, as the space requirements of the inspector has grown with new features being added over the years.
yes, i do see. but i used the view to keep the inspector managable. i prefer to hide things when i am not using them and i think the inspector was set up well for that. just my opinion.
sam cnow that i have had a chance to really look at the beta for the track inspector i am not sure i see exactly why the tab is better than an arrow?
another tab up top seems like more clutter than an arrrow to hide or open the track inspector. am i missing something?
fwiw i prefer to keep it like it is……or have an option.
sam cFrits, I copied the project to a different drive, deleted it on the current drive, reloaded it and no problems. Who knows, huh?