Coder Social home page Coder Social logo

trackerbetatesting's People

Contributors

ambv avatar jacknametrouble avatar piotr3500 avatar shuler323 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

trackerbetatesting's Issues

Quantise the transport of external sequencers

There are very few pieces of equipment that allow you to have control over the quantised start/stop of midi connected sequencers.
It would be a very handy feature to implement that from a second midi based performance screen or include a transport parameter from the midi selection (and possibly have shift and shuffle parameters on the FX lane) that would allow it to be achieved from within a track from the pattern screen.

For example you could add the midi out start/stop parameter on the first step of a track, which could work via the same method as pattern + arrow to sync the start.

[1.1.14] Caps Lock Cosmetic Issue

When you select the song/project naming tab and press Caps Lock, the letters on the keyboard don't change to Caps but remain in lowercase, so you don't know what you are typing.

[1.1.14] LFO sync reset issue

How to replicate:

  • I'm putting a Saw LFO on the cutoff of a sample, for 8 steps to emulate kick/sidechain ducking behaviour.
  • it all goes smooth for the first 35-37steps, then the LFO gets reset and so the 8 steps saw LFO is sounding like it has the phase switched for another 35-37steps, then again the LFO resets and it sounds good again, then again after 35-37steps LFO reset, again phase switched on LFO and sounding wrong again.

It happens in every project with 128 steps per pattern.
To replicate put a note on every step 128 steps long. Add low pass - saw LFO or rev saw - 8 step speed. (edited)

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Don't know,
Does this bug happen in every project? - Every project,

[1.1.14] Consistent crackling present in stereo exports.

There is a subtle but consistent crackling present in stereo exports that were not present in the v1.1.0 firmware.

It is happening in the change from pattern 11 to pattern 12 when playing the track on the tracker in "song" mode too.

Project + workspace + reference mix
https://drive.google.com/file/d/1eWon0KE-C96qqOgdq0vOoh5xquGP9td7/view?usp=sharing

  • How often does this bug happen? (every time, often, "it only happened once") - always,

  • Does this bug happen in previous firmware versions? - wasn't happening on the v1.1.0 (I jumped straight from 1.1.0 to 1.1.14),

  • Does this bug happen in every project? - on the several ones I've tried,

PageUp / PageDown For Key Scrolling

In older software such as impulse tracker I could navigate much faster especially for longer patterns using a pgup/pgdn type key command that could skip. The skip function is great but currently only works when entering a note. Unless I am mistaken with the current interface we don't have a means to navigate quickly when in note entry mode for example (we cant turn wheel to move quickly, it changes note information). If we could have a command hotkey to navigate quickly up or down a page would be a welcome addition to the current navigation.

Add solo tracks to the performance page

Self explanatory really. In the same manner as mutes. Not sure how this could be worked in.....maybe a rolling shift function.
EG: on the performance page - default is track/pattern - press shift to display track/mutes - press shift again to display track/solo - press shift again to return to default track/pattern

[1.1.14] Tracker as MIDI slave to Seq gets out of sync and freeze

The Seq is a master clock. On the video, we can hear the progressive shift between the two Kick and at the end, the tracker stop and freeze. I have to unplug tracker for turn it off. When the clock is internal there is no problem.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Hard to say,
Does this bug happen in every project? - Doesn't matter,

Equalizer in Sample Editor

We really need a basic EQ in the sample editor, to roll-off unwanted frequencies and make adjustments to the samples for better mixing. The filters are nice but having the ability to resample with eq processing, would result to much better production quality.

Scramble Command

A cool addition in the "Fill" menu would be a "Scramble" row or whole pattern command, meaning it would allow you to scramble the recorded notes of a pattern into new randomized positions, in the same pattern.

The command could also make you select if you want to Scramble only the notes, only FX1, only FX 2 or all ;)

[1.1.14] No audio detected in sample recorder

When entering the sample recorder page, there's no signal on anything, even when audio is set to coming into the unit or switching to the radio, I have to exit the page and enter it again for it to kick in. Also, sometimes switching between sources, line-in, radio etc. It cuts out and there's no audio detected.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Don't know,
Does this bug happen in every project? - Yes,

[1.1.14] Recorded sample volume level is very low

When sampling, set a good gain level and it sounds appropriate. After saving the sample, the level drops so much that it cannot be heard. Playing around with sampling the radio and the record level was at the higher end of the yellow and during monitoring, sounded fine. After saving, it's impossible to hear it unless cranking up the system volume a lot.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Yes,
Does this bug happen in every project? - Yes,

1.1.14 Mute states after solo/unsolo

If you have a mute group set up, then solo a track, the Tracker defaults to all tracks active after unsolo. It seems to reset all applied mutes to active.

Does this bug happen every time or just once? All the time
Does this bug happen in previous firmware versions? Yes
Does this bug happen in every project? Yes
[https://www.dropbox.com/s/ve0yq80djzd8d97/Solo%20and%20mute%20groups.mp4?dl=0]

[1.1.14] Copy/paste between pattern tracks and from pattern to pattern sometimes do not work.

Strange behaviour of the copy/paste function since the last update > Sometimes it just stops working for a time, and it seems to start working again if I try to copy something from another track.

Additional questions to answer:
Does this bug happen every time or just once? - Happens from time to time,
Does this bug happen in previous firmware versions? - Didn't try,
Does this bug happen in every project? - Don't know,

[v1.1.15] Sample preview + arrows not working anymore.

Hi, sorry you had trouble!

Steps to reproduce

Hi Guys, I loved in previous versions, we could continually hold down the "preview" button and cursor down using the direction arrows to preview each sample when auditioning samples to load. However, in the latest version, we can't seem to be able to do this. Cheers

Other important information

  • How often does this bug happen? (every time, often, "it only happened once")
    Every time
  • Does this bug happen in previous firmware versions?
    No
  • Does this bug happen in every project?
    Yes

[1.1.14] Bit Depth not audible

The Bit Depth in Master section is not audible unless you re-arrange the value.

How to replicate:

Save a song with Bit Depth at Value "10".
Turn off and then on the Tracker.
Load / Play song.
Bit Depth is not audible, you have to re-adjust the Bit Depth to listen to the effect.

[1.1.14] Selecting (popup) & playing instruments from external controller bug

Selecting (popup) & playing instruments from an external controller when Tracker is a MIDI slave is causing the popup list to disappear.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Don't know,
Does this bug happen in every project? - Yes,

Limiter Out / Master Out per project

There could be a "Limiter out" volume, that could be saved within the project. Or it would be useful to re-enable saving the master volume per project, as it was in past firmwares. When preparing a live set, you don't want to adjust the master volume each time you load a new project / track.

[1.1.14] Project save text edit issue

Go to Sample Loader > delete some instruments > Save project as > the edited marked text is masked

Additional questions to answer:
Does this bug happen every time or just once?
Does this bug happen in previous firmware versions?
Does this bug happen in every project?

[1.1.14] Tracker MIDI over USB out of sync

Hi. I'm currently working on a project using the tracker connected to Garageband via USB on an iPad Pro with a SATECHI USB-C adapter. I've set all the MIDI-settings on the tracker/config/MIDI to USB where applicable. I immediately noticed after 2-3 bars of playing the Garageband-project on my iPad, the tempo eventually got misaligned. To be sure this wasn't just an issue with the iPad, I tried flashing the tracker back to v1.1.0. and the BPM-problem does not occur

Additional questions to answer:
Does this bug happen every time or just once? - as described,
Does this bug happen in previous firmware versions? - Not present on 1.1.0
Does this bug happen in every project? - not relevant,

[1.1.14] Position FX command doesn't work with loops and reverse playback

See attached video.

  1. First it shows the entire sample in Pattern 1.
  2. Then it shows proper position selection with the p command in Pattern 2.
  3. Then still in Pattern 2 it shows the p command not working when the sample playback is set to loop forward instead of single shot. That's problem 1.
  4. Then in Pattern 3 it shows the p command behaves erratically when r<<< is used:
  • it does not change the starting position of reverse playback;
  • but it does affect the duration of playback (note the sample being cut sooner when p greater than zero is selected).
    That's problem 2 which is a specific case of FX1 and FX2 not working in tandem.

Attachments and links

Other important information

  • How often does this bug happen? (every time, often, "it only happened once")
    every time

  • Does this bug happen in previous firmware versions?
    yes, tested since at least 1.1.5

  • Does this bug happen in every project?
    yes

[1.1.14] Jog-wheel use while booting freeze instrument

Toggle on the Tracker and immediately turn the jog-wheel to permanently freeze the unit.
This happens when turned on for the first time, after a reset it won't happen, you need to take out the USB cable to reproduce.

Additional questions to answer:
Does this bug happen every time or just once? - Yes,
Does this bug happen in previous firmware versions? - Yes, starting from 1.1.0
Does this bug happen in every project? - Not relevant,

[1.1.14] render song audio low

Wav. file from rendered song is low volume. If dropped directly to SoundCloud the wav is nearly inaudible, even when tracks are mixed to the ceiling in the tracker.

Additional questions to answer:
Does this bug happen every time or just once?
Every time.

Does this bug happen in previous firmware versions?
I went from factory firmware to 1.1.14, so I don’t know.

Does this bug happen in every project?
3/3 so far.

New Fill Type: "Find/Replace"

I Love Polyend Tracker!

Thank you all for your hard work making this device. I LOVE it! I searched for the following feature, but could not find it in Github. I understand you all have much bigger fish to fry at the moment, but I wanted to write this idea down. Now, on to my feature request:

New "Fill Type": Find and Replace

"find and replace" for some values. I specifically would like something in the instrument lane but could see it being useful in other areas as well. Sometimes I realize I want to use a different instrument for a rhythm part after I've written lot's of notes using multiple instruments into the track.

Why not go to sample loader and replace the sample there?

That would work if I had not already written other patterns using that instrument, but unless I want to replace that reference for all patterns I will have to change the instrument number manually for all steps within that pattern. This isn't a big deal for 16 step patterns, but when you have 128 step patterns, this can be more tedious.

Why not just use the "fill" command we have so generously provided?

Fill is great! but one great strength of the tracker is the ability to address multiple instruments on the same track. So if I wanted to use a slightly softer Kick for this pattern, and already have my kick part written out in a track with hi-hats, snares, and clever household noises, it can take a bit to go replace that one sample.

Example:

For this example, instruments 1-5 are single shot rhythm samples, while instruments 6 & 7 are melodic. FX lanes are omitted.

pattern 1:

I have a pattern with a rhythm part written into track 1, and I like it. Great!

Track 01 Track 02
C1 01 #C4 07
C1 03 #G4 07
C1 02 #C4 07
C1 01 #D4 07
C1 04 #C4 07
C1 03 #C4 07
C1 01 #C4 07
C1 03 #C4 07
pattern 2:

Now I have copied that pattern, and added a counter-melody to Track 03, but now I would like to use a kick drum with a different sonic character. Maybe instrument 01 is an acoustic kick, but now I'd like to do a lo-fi 8-bit drum that's already loaded in instrument slot 05. It would be cool if I could do the following from the "pattern" view:

  1. Click the "fill" context button
  2. Leave "Scale" blank
  3. Choose "Instrument" on the "Where?" sub-menu
  4. Choose "find/replace" in the "fill type" sub-menu
  5. Use the pads or jog wheel to enter: 01 in the first "find" field
  6. Use the pads or the job wheel to enter 05 in the "replace" field and click "Fill"

And then... viola! All my references to inst. 01 on that track are now references to inst. 05

Track 01 Track 02 Track 03
C1 05 #C4 07 #F4 06
C1 03 #G4 07 #D4 06
C1 02 #C4 07 #F4 06
C1 05 #D4 07 #G4 06
C1 04 #C4 07 #D4 06
C1 03 #C4 07 #C4 06
C1 05 #C4 07 #C5 06
C1 03 #C4 07 #C6 06

Conclusion

Thank you very much for your time!

[1.1.14] Delete & Save problem

If you delete files from the instruments using the Sample Loader and then save the project, the deleted files return when you reopen the project later. For example, to keep the above project simple to share with you, I deleted all of the samples using the Sample Loader except for Instrument 1. But I reopen the project (in both 1.1.12 and 1.1.14) all of the slots I deleted are still present. Not a big deal, but something I did notice.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Don't know,
Does this bug happen in every project? - Every project,

Sample End - FX Command

It could be the reverse of the position command; meaning it would trim a sample (much like shortening the decay).
Very useful for many applications.

Tempo FX Command - Value Resolution

It would be useful if the Tempo FX command had 1-step value resolution, meaning it would allow all tempo values to be entered with better detail (11,12,13,14,15, 123, 311 etc)

Sample / Instrument Capacity

It would be nice if the sample / instrument capacity was not fixed at 48 but could be dynamically dependent on the general sample pool size (for example I would like to load 100 very small samples, or 100 wavetables etc).

Chord / Arp FX command

I am sure you guys have already thought about that, the Chord / Arp FX command inspired from LSDJ, would make a great addition for us oldschool chiptuners.

5gPyNA4

Sample Cut By

How about adding on Instrument Automation page 2/2 the command "Cut by"?

The "Cut by" command could be used for gain staging (for envelope timing you can use the same steps from your LFO enu, 1/64, 1/48 etc), using an amount value, and you simply enter which instrument cuts the one you have selected.
Apart form the creative sequencing, that way you could use a kick to gain stage / parallel compress a bass and many other creative uses of course. I think it's also an efficient way to produce more clean tracks on the Tracker.

[1.1.14] Pattern divider has 15 steps max

Previously it was 16 steps, now it's 15 steps only.

Additional questions to answer:
Does this bug happen every time or just once? - Yes,
Does this bug happen in previous firmware versions? - No,
Does this bug happen in every project? - Not relevant,

[1.1.14] CUT and FAD + RV1 = Bug

at 150 BPM if I put a CUT or FAD directly after a note with an rV1 effect, the volume goes up all at once for that track. But at 130 BPM it doesn’t do it.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? = Don't know,
Does this bug happen in every project? = Yes,

[1.1.14] Tracks manually recorded to DAW (Tracker as a MIDI slave) drifts from each other.

While recording a new track to disk, track after track.

Here is the setup: Use Live 10 for master clock/ transport > the Tracker via USB, I solo one track, record it, then go on to the next track on another channel etc.

The problem is the Tracker since to drive in time so none of the Track is correctly synced, and it seems that it keeps drifting as after I recorded four of the channels I now have to edit every bar so they sync up.

I just tried exporting the stems out of the Tracker and none of them is correctly synced when put in a DAW.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - It was working way better on the last firmware I've been using (v1.1.12).
Does this bug happen in every project? - On the ones I've tried,

[1.1.4] SD content sorting

File system order of display conventions is odd if your file/sample starts with a number.
Currently, samples 1 to 9 do not display in numeric order.
The file systems displays 1, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 2, 20, 21 etc.

Solution:
Make numbers 1 to 9 display first in numerical order.

[1.1.14] WT Smoother freezing the instrument

I noticed the WT - Smoother function causes the machine freezing with some samples.

Additional questions to answer:
Does this bug happen every time or just once? - happened a few times already,
Does this bug happen in previous firmware versions? - It seems happening too much often with the latest firmware update,
Does this bug happen in every project? - happens in the attached project, https://drive.google.com/file/d/1Kv2_8fJ3fXAU91-vjpYFrt5C0uMmB8Nc/view?usp=sharing

Hex display of pattern position

Decimal positions

Currently pattern positions are decimal and indexing starts at 1:
tracker-current-status-no-hex

Hexadecimal positions

I'd like to propose a traditional hexadecimal position numbering with indexes starting at 0:
tracker-hex

Advantages

The most important advantage of this design is that when using 4/4 meter, all beats are on power-of-two values. In the screenshot you see beats of the first bar on 00, 04, 08, 0C. What would be the second bar? 10, 14, 18, 1C. Third bar? 20, 24, 28, 2C. Fourth bar? 30, 34, 38, 3C. And so on. As you can see, there's a pattern. Bars start at 00, 10, 20, 30, and so on. Divisions inside bars have predictable values.

Compare this with the current situation: first bar beats are 1, 5, 9, 13. Can you guess what the second bar beats will be? 17, 21, 25, 29. Third is 33, 37, 41, 45. Fourth is 49, 53, 57, 61. Hard to predict, no discernible pattern.

The hexadecimal notation is natural for existing users of tracker software.

Implementation

  • The feature would be toggleable in Config.
  • The feature is global (per device, not per project).
  • This feature request only discusses hexadecimal pattern position.
  • For consistency it would make sense to also make pattern numbers themselves hexadecimal, too.
  • All other numeric values in the Tracker software, in particular instrument indexes, FX values, and automation, would stay decimal, displayed as is today.
  • The change would require display of pattern positions and pattern numbers to be consistently hexadecimal on all screens, including button labels on the bottom part of the screen.
  • Leading zeroes are displayed to help users tell that the hexadecimal mode is enabled.

[1.1.14] Sample pool indicator is showing wrong values

Sample pool indicator is showing wrong values when copying or replacing large files and then browsing files on the left side of the sample loader.

Additional questions to answer:
Does this bug happen every time or just once? - Always,
Does this bug happen in previous firmware versions? - Don't know,
Does this bug happen in every project? - Yes,

[1.1.14] Live rec on external MIDI bug

The tracker will not record information when Live record mode active (with regards to the failure to record any info when in live rec mode; it works sometimes when you step out and back into that mode. Very random).

1.1.14 Save mute states per pattern

Would be a handy feature if we could save mute states on a per pattern basis instead of global. Then when we are adding slots/patterns in song mode, each pattern would include its own mute states.

[1.1.14] Tracker lag on an advanced project (buffer issue?)

The Tracker seems to lag for a small instant when you have busy pattern sequencing and lots of FX (is this a buffer issue?)

Additional questions to answer:
Does this bug happen every time or just once? Always,
Does this bug happen in previous firmware versions? Didn't try,
Does this bug happen in every project? - on an advanced one only, with all the tracks loaded with steps & various fx

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.