the Node size is scalable in 2308
In version 2308 you can change the size of the node that the envelopes use. It’s in the Preferrence > Appearance > volume Envelope/ranges dialog box. The default is 3, just put in the size you would like to use in the box. Makes it much easier to edit envelopes on a monitor with high setting. A small change but it really is helping me - much easier to see the nodes. 
Hi bax3:
I downloaded the build but I always do that…
As it’s downloading I go the check what’s changed…
However, this time I didn’t or overlooked going there…
Is this change something you discovered by accident?
Anyway, it doesn’t matter again…
I can use any feature like that for helping me GRAB-and-SEE things on the timeline…
Maybe, Flavio can add a “Skin” colour change to the feature…
Reason 
?
Make it some obnoctious colour so it can be GRABBED as easy as seeing IT…
Make it stick out like a sore thumb…
Well…
Just an idea…
Bill…
well done BAX took some finding didnt it ? -
Dr J
Well, actully, it’s a feature I requested and Flavio had emailed that it was coming. Made Bill and me happy anyhow. And it works great!
Bax
i spent ages looking for it, and yes its a vast improvement -
well done -
Dr J
That is a neat feature but kinda’ useless if the volume envelopes are messed up when you mix down anyways 
When’s THAT going to get fixed?
Yeah, I guess it would be. Are you saying you are having a problem with the envelope not being applied correctly during mixdown?
there seems to be a problem there - i have reported it to Flavio who cannot replicate it -
two things - one - with a track fader in lowest position db range may start to shows -330db -
two - when using fader automation in RECORD mode there is a point when the fader is taken down that the envelope drops instantly to zero and raises back up instantly leaving the bottom 1/3rd of the envelope uncontrolable -
i reset prefs to default and it worked for a while - but now its back -
looked for another reason and have found cure (for how long i dont know)
PREFS / appearance / volume envelope range - set upper level range to +10db set lower range to -15db - other box’s are -20 > 18. -20 > 18, -20 > 10 - now the envelope is fully controlable -
DR J
Yes. My latest mixdown doesn’t appear to properly compensate for plugins latency on the volume envelopes. As a result all my boosts and cuts using the volume evolutions were offset by like half a second. I tried a mix without EZ Drummer thinking it may be the cause of the problem but it still occured. I’ve yet to strip it down to basics to see when it begins to occur but someone else mentioned they were having the same difficulties on mixdown when I first posted about it. I’ve contacted Flavio but haven’t gotten a response yet. You can listen to www.myspace.com/offormerfame Never Intended to hear it. When the guitars kick in heavy there’s a delay in the volume. Then when they’re staccato you can hear the guitar buzz I “cut out” using the envelopes. The mix posted is actually compensated for a little bit. i took the mix back in and redrew envelopes to try and fix the swells but they’re still there. Also, my drum track using EZ Drummer slowly drifts out of sync in the song.
I tried freezing all the tracks but then the tracks with the most processing actually began to speed up and were no longer in sync. “n” kinda’ ruined my song lol
Something this node thing may help is that everytime I went to grab a node I ended up doing a highlight on the track. It’d take me literally like 10 times to move the nodes most of the time.
when you firstloaded in EZ Drummer did you see a yellowish coloured POPUP box saying that for this VSTi you have to set the DSP thread priority to 1 ? -
Dr J
no. in addition I took ez drummer out eventually and had the same problems.
I don’t know what your computer setup is. I have a dual processor and that may be a help on this kind of thing because of the Multithread. Be that as it may, I thinnk the problem mnay be in the Ntrack setup ypuu are using. Open Settings Options and look about a third down the page. Find the box labled DSP thread prioity: try clicking the 2 settng. If you have Multithread (dual core or 2X) click the Multithread Audio Processing, and then check the Compensate plugins latency.
I hope this helps.
Bax
I’ve already moved up the thread priority but haven’t checked it out with the mix. I already had multithread and plugin latency checked. My computer is a dual core Pentium D 3.0 GHz processor, 3 GB DDR2 667 RAM, ATI X1900 Video Card, 300 GB HD partitioned into 2 drives, 1 XP PRO and 1 Data drive, 2 10K RPM Raptor drives in a Striped RAID for audio.
Sure doesn’t look like you don’t have enough computer. Maybe that number setting is the key - here’s hopin’
Bax
yep, hence my confusion. This pc really shoulda’ been able to handle what I was throwing at it pretty well. but it didn’t. I have a sneaking suspicion that I need to pull a stick of RAM out. There are 3 1GB modules in it but the board is Dual Channel compatible. Which means for dual channel I need 2 or 4 sticks. I’m wondering if having 3 is causing a detrimental bottleneck since it’s not running in dual channel mode, or maybe it’s trying and failing. I don’t really know.
Quote:
My latest mixdown doesn't appear to properly compensate for plugins latency on the volume envelopes.
That's a long standing known issue and isn't system specific. It's very easy to repro when using SIR or any plug-in that causes the need for a lot of compensation. I've mentioned is quite a few times in posts.
yeah you brought it up in my other post. I e-mailed flavio but haven’t heard anything. My PC doesn’t seem to be able to handle than many plugins either though. The CPU usage was huge on my mix. I had 22 tracks but I used to do that on my XP Athlon 2800+ and 1 GB RAM with an 80GB drive. It’d be close to peaking but this new computer crapped out pretty quickly. I think I had less effects too. It’s a new image on the drives but I might switch to xp64 and add some more RAM. I haven’t tweaked XP for the best results yet either, but I still expected more out of my pc. even after I yanked ez drummer the cpu usage was still past 100% on the relative setting. I was using a few compressor plugins by Modern and I had autotune going (which is pretty heavy). I added a couple of “groups” which seemed to increase the demand pretty drastically. I had frozen the autotune channel because it had the most effects and I was able to work from there. I haven’t done conclusive testing, but it just seemed to not do as well as my previous setup.
Yeah, something is wrong there. I have done mixes with a Pen 4 3.2 and I run as many as 36 tracks with Ntrack effects (not other folks plug-ins) and the CPU didn’t pull more than 40% tips.
Is is possable you have something running in the background that you don’t know about? I don’t think the 64 will help with this problem - at least not until you are able to find the root cause. I don’t usually do a bunch of “tweeking” either - just don’t run the internet or Norton or anything but the Ntrack. Do you get the same results if you have no plug-ins running? If you do, then there is something wrong.
download this app “CPUmon” - it will show dual core CPU use and menory use - will help you see whats happening -
http://www.den4b.com/downloads.php?project=CPUMon
Dr J