I am using X2 on Win 8 Enterprise X64 (Release to Manufacturing version).
I have had some goofy things happen with quick groups.
- add solo and mute to the same group... in the track view (not the inspector) clicking the solo toggles both, but clicking the Mute messes it up. In other words, I couldn't get things unmuted.
- I used quick groups to add the Channel Strip Emulator to 15 tracks (this worked... from console view, dragged across all the tracks and used a single one of the Pro Channels, holding down control key to add to all).
- Odd behavior as I started to convert them all to N Type. If you have two Console emulators in a quick group and one is S-Type and one is N-Type and you control click the S-Type to make it N-Type the N-Type moves over by one to become A-Type. This does not happen if one is A and one is N and you switch the N to A since the A has no where to move to the right. If they are the same, both N and you ctrl click A, they shift together.
Since there is a difference between Channel and Bus Console Emulators, I would prefer if that difference came first in the label so you could see the useful information upfront instead of a truncation of Console Emu... I know it's a console emulator... ha ha I don't know if I added Channel or Bus.
I absolutely love the full screen mode (F11).
I use a relatively old and cheap laptop which I got more than 5 years ago with Vista (I think anyway... round about there). It has 4GB RAM and the processor was slick for it's day. Processor and Memory get a 6.4 on Windows experience index for Windows 8. I've disabled the graphics Display Adapter and gone with Windows default to solve a DPC latency issue, so the Graphics Sub-score is 3.3.
I use a Line 6 tiny interface when traveling and an M-Audio Fasttrack Ultra at home. Nothing fancy and it's all working great. I've had one crash since upgrading and that was in a project I upgraded. I have had no issues with projects that started as X2.
Between X2 and Win 8, I'm definitely happier. Things are snappier. All is well.
On a side note, there's a loose screw between the chair and the keyboard that causes a problem (me). My work process follows this way... I work and work on my mix. I bounce, I listen, I mute the bounce, I listen to the tracks, I fix things, I delete the bounced mix, I bounce, I normalize, I multiband compression (lighter than light), I might use the channel tools to bring the louder side more center to balance the left and right channels, I normalize, boost11 to 1 DB or so, add clip fading > select the track, export > post for my friends > send out the link and race off to my day job
(did you see my screw up?)
Yep, I exported a muted clip. I do it all the time. Sometimes I burn the muted clip to CD haha.
I know it isn't a software bug, but it would save me some blank CDs if the software could advise after the export that all exported bits were 0 equivalent (I say equivalent b/c I don't think floats represent 0s precisely). I realize it wouldn't know until the export was done (maybe automation unmutes things), but after the export, it could advise me.
Thanks for listening.