Questions about Stems files in Traktor Pro 4

124»

Comments

  • Didier Malenfant
    Didier Malenfant Member Posts: 36 Helper

    Unfortunately this only selects files added to the library as stems and not the ones created inside Traktor.

    I guess NI got caught by their own issue of not marking stem files created in the app in the database apart from checking the hashed value exists in the stem folder. Most likely forgot to update the smart playlists code so that it does that too.

    Would have probably been better to just add a <STEM> entry in the database even to the files created inside Traktor and that way everything else would have worked the same as regular stem files.

  • Hirschie
    Hirschie Member Posts: 22 Helper

    I have testet it now. Yes it only shows up my NUO-Stems imported as mp4 to the database. the inside traktor created stems are missing. it seems they have forget this already.

  • bizniz
    bizniz Member Posts: 14 Member

    My workaround is :

    I right-click and enable lock every stem I make, that's going into a smartlist with locked tracks

  • dannys1
    dannys1 Member Posts: 18 Member

    It's not substantial though, you THINK it is, but it isn't at all. Which is why the worlds best audio professionals on £30,000 rigs can't accurately tell the difference. In the greatest respect you have neither better ears or better audio equipment than them.

    I have £2000 pair of Sennheiser HD-800s with a £4000 Violectric Amp coming out out UADs best DACs and no one is able to reliably pick which is which in an A/B

    Also you're not getting 1300Kbps with lossless, the kbps is irrelevant, it's just effectively a real time zip file that reduces the size of a wav or aiff.

    Of course if you think you have magic ears you can prove it by doing a blind A/B test here, do the long test and see if you can get anything better than basically guessing each time.

    http://abx.digitalfeed.net/faac.320.html

  • Transmission.today
    Transmission.today Member Posts: 9 Newcomer

    My ears can tell the difference, no question about that. It's not about having an expensive rig; you can easily hear the difference between FLAC and 320kbps. The richness, detail, and clarity are just on another level with FLAC, and it's noticeable to anyone who listens closely.

  • Transmission.today
    Transmission.today Member Posts: 9 Newcomer

    Again, I think you’re not really aware of how much flexibility you lose when working with a compressed file. Just like editing a RAW file in Lightroom or Photoshop gives you far more control than a JPEG, FLAC does the same for audio. FLAC is lossless, so it preserves every detail in the original recording, allowing you to hear the full depth and richness of the sound. MP3s, like JPEGs, compress the data and limit what you can hear. The difference may seem subtle, but for those who value quality, it's undeniable.

  • DJ Bobby Tables
    DJ Bobby Tables Member Posts: 22 Helper

    I noticed that the track entry in the NML file does change when a stem is generated. The flags attribute has 64 added. Also, I think that the hash for the stem file name is calculated from the AudioId but traktor probably only checks for the stem file when the flag is set.

  • Didier Malenfant
    Didier Malenfant Member Posts: 36 Helper

    Great catch! I updated Traktor Buddy to make use of this. From the module you can now call Track.isStem() to know if the track is a stem (generated by Traktor or added to the collection by you) and from the command line I've added the —only option which lets you do this:

    tktbud --only=stems tag add Type:Stem MyPlaylist

    which will add the tag Type:Stem to any stem files found in the playlist MyPlaylist. You can then use this tag in a smart playlist in Traktor.

    (side-note, if you're going to experiment with tktbud, it does make backups of the collection before making any changes but still use the —test option first to make sure you understand what you are doing).

This discussion has been closed.
Back To Top