Multiple Issues With Kingston

Typically I've been waiting a patch or two before I install but this time I jumped on the Kingston Update. It seemed to be working fine for the first several days but the last two days I've had strange things happening. I won't mention them all here, just the main ones.

1) I cloned an audio track with six lanes of audio clips. The track was comp'd with all clips, (muted and not), still present. The cloned track ended up having 12-14 lanes with the audio clips scattered onto various lanes. I undid the clone, redid it and all was OK. Anyone seen this? This is not a biggie but strange.

2) I was comping a guitar track with three lanes. All went well until I selected the clip gain filter. Sometimes the envelopes worked, (I could edit), other times they wouldn't work at all, (adjusting the gain, placing nodes etc).  Note: There has been an ongoing issue with editing clip envelopes for some time now, very frustrating. Sometimes editing works, sometimes it doesn't, (using the smart tool). Also, they don't change color when you change the filter back to 'clips', (from red to black), and closing the take lanes and reopening most times seems to fix that. (In previous updates, that process seemed to bog down, it didn't respond quickly.  Kingston seems to have fixed that).

Anyway, in this particular case the track seemed to just lock up, nothing worked. Everything else in Sonar seemed to work, just not this track. It wouldn't let me do anything to that track! I went to another track and edited, no problems. Shut down Sonar, no dice. Reboot the computer, nothing! Unfortunately, when I went back to that project last night I forgot to check that track and I ended up rolling back, (see below), so I don't know if the issue still existed. Anyone ever seen this one?

3) Last night I was working on two acoustic guitar tracks, (same project as above), that summed to a bus. When I mix I'm soloing buses all the time but when I solo'd the acoustic guitar bus this time, Sonar locked up. Shut down, reopen Sonar and tried again, same thing. The song is playing along, I hit the solo button on that buss, instant lock up! I'm thinking it might be a plugin. Removed the last plugin I had added, same thing. I tried this several times and finally solo'd a different, non related bus. Sonar locked up! I rolled back to JP and everything seems fine now. Anyone seen this, or anything like it?

4) When I'm comping and splitting clips, I seem to be getting very small slices of clip at the joints. Not on all splits but enough to make comping a real pain! Some of them you can see, others are so small that you have to drag the edge to find it. (I know they are there because when I "delete empty lanes", they don't delete!). Is this a known Kingston issue or am I doing something wrong? I have zero crossings shut off. Anyone seen this one?

Questions not necessarily related to the above issues:
 
When I rolled back to JP I used the CCC but it re-downloaded the files from Cake instead of using the saved files on my computer. I thought that was the reason for saving the update files to your HD.  Rolling back is supposed to be fast and easy but obviously, in this case, it's not.

I've had this next issue off and on for some time. While I'm trying to comp or, edit in Melodyne, the auto save is constantly saving! I have it set to 50 changes or five minutes but it saves every two to three changes! What a royal pain in the butt! What am I doing wrong here?

I've been having a number of other issues but this is enough for one day. Any comments, suggestions or help is greatly appreciated!

Thank You!  (Moderators: If I need to break this into several posts, I will)

Paul
 
 

Resonant Serpent
I've had the solo lock up happen on two projects now. I had to reboot to get it to stop both times.
 
I also had a beginner project with two audio clips that were edited, and I couldn't get the automation nodes to move on the second clip. When I played the project, the automation, or the audio would cut out. This was on a freshly booted computer and Sonar was the first project I ran. I turned off my faderport, and it would then play back, but still couldn't edit the nodes properly. They made massive jumps, and I had to right-click each node to edit. Rebooted the computer, and it was the same thing. Tried it again the next day, and it ran fine. Once I hooked the faderport back up, the behavior became laggy again. On Win7 pro with Kingston.

Before you get into the realms of optimization, I would recommend reinstalling/updating the software:
http://www.presonus.com/support/downloads/FaderPort
 
... and then trying the faderport in a USB 2 slot rather than USB 3 (if you are using one).


After this (assuming it makes no difference) I would recommend your own new thread, showing your full hardware/software specs as this appears unrelated to the OP. Thanks.

>> 4) When I'm comping and splitting clips, I seem to be getting very small slices of clip at the joints.
 
Yes, I have this and I am still in Hopkinton.
 
Sometimes (most times) everything is fine, then for no reason that I can discern, where clips overlap (I have auto crossfade on), I get the crossfade areas turn into little clips.
 
I have yet to find a way to reproduce this.

Paul G

jpetersen
>> 4) When I'm comping and splitting clips, I seem to be getting very small slices of clip at the joints.
 
Yes, I have this and I am still in Hopkinton.
 
Sometimes (most times) everything is fine, then for no reason that I can discern, where clips overlap (I have auto crossfade on), I get the crossfade areas turn into little clips.
 
I have yet to find a way to reproduce this.

Yes it does appear to be random and very frustrating.
 
Thanks.

I've seen this.  I've gotten pretty use to hunting for this after doing a lot of edits involving the in-track clip fade in/fade out's and cross fades. I just kept assuming I had mis-clicked something along the way. Now maybe they were real bugs.

I also always thought I'd hit some hotkey to cause this.
 
Despite the fact there are no repeatable steps, I think I
will open a bug report. This is not the first thread where
this issue is discussed.
 
Edit: Done. [CWBRN-42298]

.

Thanks to everyone who has commented.  The moderators have suggested that I split this post into separate-issue threads.  They are going to lock this thread and I'll re-post the issues individually.  Please continue to post so we can narrow this down.
 
Paul

slumbermachine
I've seen this.  I've gotten pretty use to hunting for this after doing a lot of edits involving the in-track clip fade in/fade out's and cross fades. I just kept assuming I had mis-clicked something along the way. Now maybe they were real bugs.

Thanks Steve.  We can continue this discussion in the new post.


Paul