1. BTD issues?
2. Stuck notes?
3. Hang or crash on quit?
4. CPU spikes?
5. Other? (please describe)
Part 2 of the $64k question:
What problems are there you've had which remain?
Inquiring Hobbits want to know!

Moderator: James Steele
Are you sure you are starting the playback on exactly the top of a measure or beat? If you start, say at 03/01/xxx - any x being anything but a zero) then the countoff will behave in an odd manner).tommymandel wrote:Did 5.01. I hit MIDI record with Click on and 1 bar of countoff,and the Location display displayed some bizarre asymmetrical negative (ok) location, and the click sped up for the 1st measure, then righted itself for the 2nd measure and on. (MAS, Digi Core Audio Driver, audio click, routed thru 002R outs 7 & 8, MOTU Click and MPC Clicks.) I turned OFF Countoff, and the click was perfect. (i just had to start playing at measure 2.) I will try again this morning after trashing my preferences. No stuck notes yet!
Sure thing, Timeline. I know Shooshie is busy collecting data for some issues, but that started right before or right around 5.0 was released. Seems that those who participated so far in those polls have both 4.6x and 5.x. I really want to see more specifically (in one place) what issues were resolved with 5.x before deciding when the best time might be to update. Overall, things sound positive, so I may order 5.x next week just to have it ready to go.Timeline wrote:Thanls for posting this Frodo...
Will watch with interest!
Audio dropout after recording-- is this immediately "right after" recording only? It could be that some background processing is still at work, depending on how large a chunk the recorded audio was. Assuming that this ocurred in 5.0 for you, did it occur with 4.6x as well?bradswan wrote:I had the same thing happen with the MIDI click on the first project I opened with 5.01. Unfortunately 5.01 does not address audio drop out when hitting play after recording.
Although the bells and whistles are nice my wish is for DP to be a rock solid, CPU efficient, audio-MIDI DAW first and foremost.
I've been trashing Prefs a lot lately. This is a common fix and old files do get corrupted eventually-- but the frequency of having to trash the Prefs has me wondering what the cause of the corruption might be that such a corruption can happen so often and so easily. Suspcions of bad HD sectors prompted the purchase of a new HD, but the issue still occurs...tommymandel wrote:After trashing prefs, and rebooting, the click is working fine in 5.01.
This sounds great!! The nice thing about this is that it gives the user a chance to also reset start button to the new start time. I would otherwise just put in the location data right in the start window, but it's too small to read on the fly. I have been manually hitting "pause"-- or 2 on they keypad-- lately, but this new feature seems like it will make this process a bit easier to navigate.tommymandel wrote:I found a new 'feature'. Tell me if you like it:
Since 5.01, when you are playing a sequence, and you type in a locate point, (Decimal Point key on numeric keypad, then a number, then Enter) it goes to the locate point, and immediately goes into PAUSE, rather than continue play at the new location. This is true even if you hit Return, rather than Enter, and also if you cursor and drag over the actual measure number in the Transport Window.
Perhaps it's in the interest of cleaner MIDI, but I wonder if there's a pref to toggle this feature on and off?
And this is new, if I'm not mistaken?