Frustrated with X1

32 bit X1 255.  Been running it since it's release.  But still frustrated....

Here is the deal.  Today inexplicably I was unable to grab an automation node and move it.  No matter what I did it just won't become "clickable".  So I decided to just delete the envelope and rebuild.  No joy.  What happened to right-click and delete ? I'm missing something here clearly and the help file further befuddled me. Edit filter ??

I went to save the same project as a cwb - like I've been doing for 6 years now - and it told me it couldn't save it as such because I had an Audiosnap clip.  No I didn't !  is there any way to find the Audiosnap clip ?  Visible inspective of each track and clip revealed no transients that you would normally see with Audiosnap.

AND after minimizing and the maximizing X1 my freaking Control Bar was just a black square.

Not a happy OR productive day........

I don't know if the feature carried through to X1 but you could try right clicking on the node and reset it.

A1MixMan - thx.  I found it :)  So why did we complicate this 8.5.3
 

Bub - I'm not alone then !!!


After 6 months I'm still finding myself frustrated.

ampfixer

New frustration for me yesterday. For some unknown reason Pro channel was unavailable on a track for about an hour. To be more precise, it was greyed out and I was unable to activate any modules. This was on just 1 track and after an hour or so it became accessible again. Never had anything like this happen before. WTF !?!?

This has happened to me also. But you see, if I post or submit a bug report for everything like this that I run in to in X1, everyone would think I'm even crazier than they already do.

It's a bug fest man and I think they're in denial of it.

A1MixMan


Be sure to be in the right edit mode via the edit filter. X1 only allows you to edit the things you want so you don't edit the ones you don't want to.

It's in the drop down box for each track.

Use the smart tool. The quickest way to set the edit filter  to the correct mode is to use shift click. If you want to edit automation, position your mouse right on an automation envelope line and shift click it. The edit filter then changes to editing automation and other material is ghosted in the background. If the screen doesn't change dramatically then you're not pointing at the envelope line good enough.

yesterday i recorded a song. took me 2 hours to lay down the basics. after that i found out that in the meantime the screensets were all broken (graphic bugs) and my master bus suddenly made some babies, so that now i had 5 of them.

strange.

had to reload, so that is why i save nearly every step i make in X1.

How did you find the Audiosnap clip ?

I eneded up just bouncing EVERYTHING to clips.  Not happy.......

I am not sure how you Audiosnap individual clips in X1. That used to be possible in 8.5, but I don't think it works anymore. Looks like you can only Audiosnap the entire track, then edit the clip you want to correct.

So, in Track View, where all the control buttons are (mute, solo, etc.) there is also a wider button; a dropdown list.

Open that and you will see one of the options is Audiosnap.

You have to go through all your tracks and look whether any of them are set to Audiosnap.

I have had several strange little glitches with X1b255, usually non-repeatable so I haven't been able to put together a good bug report. Some I've experienced recently:

- Mute tool drag action on clips stopped working on certain lanes (closing and re-opening sonar fixed it)

- Several times I've had actions that did not "undo" properly (so I had to go to a recent save, luckily I've gotten into the habit of saving a LOT)

- Editing dynamic markers in staff view seemed to be an exercise in graphic glitches, snapping weirdness, and things in general not moving where they're dragged.

- I got a "poison bus" once that seemed to crash any VST I output to it. I checked carefully and there was no feedback or anything. Deleting and re-creating the bus fixed it.

And so on. I feel like there are a lot of subtle insidious bugs deep down in there that I really hope the bakers are working hard to scrub out in X1c.

And a couple annoyances that appear to be design flaws/ things overlooked, such as:

- Smart tool "hit area" for changing clip end fades overlaps the "hit area" for adjusting the ends of the clip when the fades are really short. According to the documentation (and in 8.5) you could always get to both adjustments no matter how short the fades were by moving up to the corners or along the sides.

- When freezing a track, prochannel should not be rendered completely unavailable Instead, it should be temporarily disabled, but re-enablable, just like the FX bin. (I have to assume that the workflow of write synth parts->freeze tracks->Mixdown is NOT unique to me. My work-around is to bounce to tracks but that's the exact process that freeze tracks was supposed to make easier!)

- If I have a clip/track selected off in la-la land, and then I start editing the fades on a new clip that's NOT selected, I do not want the other clip to be affected! The other selection should de-select just like every other action when you start working on a non-selected clip. The only time multiple clips should be affected is if you're working on one of the ones that's selected, not some other non-selected one. So I think this is a proper bug. (This one has really burned me several times, usually some time later when I'm listening back and suddenly all my clips have ridiculous fades on them)

I've been too busy on a project to submit reports for these, but I might get to them this week. But honestly I hope these things were relatively obvious and they're already in the works for X1c.



EDIT: And for all those chiming in on these kinds of threads with "I don't know what you're talking about works fine for me" -- this is the nature of intermittent bugs. You think you're safe from them until the worst moment :P

Gregmang

heres a new and fun one -

I expanded a folder in track view that had 3 audio tracks.  EACH track is now HUGE in terms of vertical size.  Seems "set as default height" no longer functions ?

I have seen that happen to buses, but not to tracks. I set each bus to fill the entire bus space, then I lock the height, and scroll though my buses, rather than have them all show up minimized. Sometimes they will resize on their own and show multiple ones in the window like I didn't have 'Lock Height' on and hit 'F'.

However ... I have seen track folder headers (I think that's what they are called) get resized on their own. The only way to get it to stay the normal size is to drag it and make it smaller with the mouse and then right click and tell it to 'Lock Height'.

Here's a screenshot of what I'm talking about ... look at the 'Guitars' folder ...



It stays at that size even if I hit Shift + F or F until I manually resize it.

I have a project which suddenly started to stutter and stop due to audio engine dropouts. CPU consumption graph goes into the red.

The night before, everything was fine.

I began freezing tracks, bouncing clips, removing unnecessary material and disabling effects. Nothing helped.

I have given up and begun rebuilding from a previous still-working backup.