search

polyend / TrackerBetaTesting

Beta firmware and reporting. For official releases go to https://polyend.com/downloads/
250 stars 24 forks source link

1.5.0 Multiple crashes with 48 slice chopped sample #1424

Open bambrose opened 2 years ago

bambrose commented 2 years ago

As the title says : I have a project with one instrument containing a sample comprised of 48 slices via sample playback menu option. It just crashes periodically. Sometimes when playing the slices in (to record a pattern), and sometimes just when the sample is playing. It is not debilitating enough to abando, but oftne enough (four or five crashes last night to warrant comment.

It freezes (i.e. no sound, screen remains static and buttons un-responsive)

Steps to reproduce.. Have a project with 8 tracks all playing, one track with a sample chopped into 48 slices, with roll fx on some slices. My 'layman instinct' tells me i am '"asking too much of the processor" and it "overloads" but as it's just a hunch that's probably bollocks.. but that's what it "feels like"

bambrose commented 2 years ago

project can be resurrected easily enough. it is saved.. so unplug power and reboot and continue

static-noise-PT commented 2 years ago

Hey, I was just about to file in the same issue. Just started to get into 1.5, especially building instruments. I observed that the bigger the file size is which is chopped into 48 slices the more likely the Tracker is about to crash. It seems if the file is using more than ~15% of the memory the instability issue occurs.

static-noise-PT commented 2 years ago

In addition I observed that the Pads went black for a couple of seconds when using an instrument with 48 slices. Happens in any situation. Pads went black ... 1,2,3 ... Pads are lit again. Happens here and there. Only with a lot of slices. Can't say the actual count.

Jacknametrouble commented 2 years ago

Check how it behaves on an alternative powering source. Please attach a video of the mentioned issue. Thank you.

bambrose commented 2 years ago

It’s too difficult to catch in video. It happens maybe once an hour. And I don’t have a video device that can run for that long.

The power unit I’m using is the same I’ve been using for this tracker for about a year and I’ve only just started seeing this behaviour on this last project where I had this 48 slide sample.

On that basis I’m pretty convinced it’s not related to the power structure. If I can isolate and video I will, and if I can get any closer to identifying the specific issue I’ll post as well

Jacknametrouble commented 2 years ago

Check other powering sources too, please.

bambrose commented 2 years ago

Will do

On Tue, 8 Mar 2022 at 09:44, Jacek @.***> wrote:

Check other powering sources too, please.

— Reply to this email directly, view it on GitHub https://github.com/polyend/TrackerBetaTesting/issues/1424#issuecomment-1061589417, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSBZTRI63RIM3S2F4UKZJ3U64ORBANCNFSM5QC7E2UA . You are receiving this because you authored the thread.Message ID: @.***>

-- Great Expectations Set Dec. Art Director

static-noise-PT commented 2 years ago

Check how it behaves on an alternative powering source. Please attach a video of the mentioned issue. Thank you.

Works almost fine via the included adapter straight into the socket, yet sometimes there is a short "going dark", maybe a second probably less. The behavior I described earlier the Tracker was powered via my Laptop (all USB saving modes disabled win10).