#LMMS does not see certain audio files

1 messages · Page 1 of 1 (latest)

lilac sapphire
#

Consolidating into this post. cc @unique fractal

I am trying to load a song into LMMS to use as a reference track. The song is just over 4 minutes long. LMMS does not "see" the song file in the sidebar or any load dialog windows.

Additionally:

  • it is not the file type. I have properly converted the source file and now have it in flac, opus, m4a, mp3, ogg, and wav. Of the filetypes 1.2.2 LMMS supports, it sees none of them.
  • it is not permissions/DRM. I have successfully loaded all of the converted sound files in FL studio with no problems. I have then rendered WAV and OGG files from FL. LMMS does not see them either.
  • it is not worn bits. scandisk/chkdsk/s.m.a.r.t. report zero problems with any of the drives on my pc.
  • the files work as expected in all programs except for LMMS, which doesn't acknowledge they exist.
  • LMMS can see and load longer and larger audio files just fine.

I sent Roxas the files and he re-rendered them in audacity and was able to load them fine on his 1.2.2 LMMS copy. He sent his rendered OGG file to me, my LMMS doesn't see it.

I sent Lost the files. He can load them fine.

I have LMMS 0.4.15, 1.2.0-rc6, 1.2.1, 1.2.2, 1.3.0-alpha.102+g89fc6c960, and 1.3.0-alpha.1.227+g2baa23ee1 installed on my machine in parallel folders, as I have done for the entirety of my LMMS usage over the years. None of them can see the audio files in question, but can load and see other audio files just fine.

unique fractal
#

LMMS does not "see" the song file in the sidebar or any load dialog windows.
Hmm... almost sounds like a rogue file name or extension. Can you go to cmd and type dir in the directory that the file is in? Does it list normal or with some oddball characters?

unkempt coyote
#

I’m wondering if are you keeping all these samples in the same path and I’d have you tried moving them to a different path

#

There might be some length/character issue as tread suggests

lyric birch
#

moving them to a different path
Precisely!
Folder-naming ao folder rights could be the thing to focus.
NB I cant find any info on OS?

lilac sapphire
#

OS is in the tags...

There are other audio files in the same folder that show up and work fine. Some of the files (the ones re-rendered with FL) are in a completely different directory with names straight from FL's save box - no funky text characters with them. No change vs the original files, which do have kanji in them (which would be problematic if that was the hang up)

#

Additionally I have run LMMS in administrative mode and put overrides on some of the files making them fully public files on the machine, no dice.

I did notice windows had a blurb about files being from the internet and an unblock button, but that made no change when used, nor would it affect the files I created with FL or Roxas's audacity copies

unique fractal
#

Curious, what did CMD say about the directory, nothing fishy?

#

Do you by chance have a backup software running on this folder, like OneCloud or Google Drive?

#

It can have a 0KB link to the file and toss it into the cloud.

lilac sapphire
# unique fractal Curious, what did CMD say about the directory, nothing fishy?
10/20/2023  11:52 PM    <DIR>          .
10/20/2023  11:52 PM    <DIR>          ..
07/05/2014  11:05 PM           978,480 173838__rocknessmonster89__tom-high.wav
03/05/2018  07:47 PM           354,272 345733__noahpardo__deep-growl-1.wav
12/10/2014  04:03 PM        14,529,042 AM1_Blackbirds_Rain_At_Dusk.wav
10/19/2023  12:02 AM         3,342,037 Amateras Records - Crisis.ogg
10/19/2023  11:21 PM        12,957,617 Amateras_Records_-_Crisis Roxas.ogg
10/19/2023  01:23 PM         3,971,218 Crisis FL - Attr Stripped.ogg
10/19/2023  01:23 PM         3,971,218 Crisis FL.ogg
10/19/2023  01:20 PM         4,048,773 Crisis YT Rip.m4a
06/26/2023  01:46 AM    <DIR>          D
06/26/2023  01:46 AM    <DIR>          Luminesce Remix
03/10/2021  11:34 PM         3,023,966 rev piano bassline.wav
06/26/2023  01:46 AM    <DIR>          SAR
06/26/2023  01:46 AM    <DIR>          Spek vs Hai 01
04/10/2022  01:09 PM         2,116,702 tosk V.wav
10/18/2023  11:24 PM        29,698,562 東方ボーカルAmateras Records - 幻象Crisis.flac
10/19/2023  01:15 PM        12,150,896 東方ボーカルAmateras Records - 幻象Crisis.wav

No cloud on this folder

#

Just noticed there was additional output at the top, but it's just ID stuff about the drive, volume, etc. No errors or anything weird

lilac sapphire
#

The Amateras Records track

unique fractal
#

Ok, that would have been my first guess. Does it show up if you change its name to something simpler like file1.wav

lilac sapphire
#

No. Nor do the ones with FL in the name - those are completely fresh local re-renders using FL

unique fractal
#

Ok. That's odd. The only thing they seem to have in common is that they have newer dates. If you copy one of the other files with a newer timestamp does the newer modified copy break too?

#

Also, the file is there and has content, right? Like, Audacity can see it, just LMMS cannot, right?

lilac sapphire
#

I need medical attention after the facepalm I just delivered.

#

Buckled up, this is full stupid hours

unique fractal
#

I'm eager to know

#

Wrong driver letter is my guess

#

Oh the suspense

lilac sapphire
#

Yes but not for the right reasons.

On this desktop I have two NVMe drives. One is staying as the OS should I end up selling the desktop, and the second drive was being used as the bigass thumb drive to carry all media and otherwise to my laptop, which has a free NVMe slot.

When I moved my Music Production folder in documents to the new drive, it (as should have been expected) broke every single file path in every single project, and that is a colossal pain. So I just copied that one folder back to the C: drive so LMMS would be happy.

I then stopped using this desktop for I want to say 4 months? Completely forgot what I had been in the middle of when it was last set up.

So this whole time I was saving these files to the D: Production folder, not the identical copy that LMMS is pointed at on the C: drive. OOF. Where do I turn in my power user card, this one stings

unique fractal
#

Ah.

#

You should use mklink it can make a symbol link to fix your projects.

#

Then you can have your drive and use it too.

lilac sapphire
#

between you and me, when I release my upcoming full length album Continuum, I will be archiving all of my LMMS projects and starting over with a completely new slate with new environment architecture and everything. I can't keep piling stuff on the shitty file organization system I used a decade+ ago when I started

unique fractal
#

Did I say mklink, I meant del /S

unkempt coyote
#

Wait so you weren’t loading the sample itself, you were loading a project with it

#

But also LMMS definitely needs scanning+ relative paths, it would help immensely with this stuff

lilac sapphire
unkempt coyote
#

Yeah but… you told me you tried to open the sample by double clicking on the sample track pattern
That time was definitely a user issue cycloy

#

(Unless LMMS opened up the sample folder)

lilac sapphire
#

Doubling clicking the empty sample track pattern, which opens a load dialog window... pointed at the wrong directory

#

If I didn't have all the important folders saved in the load dialog window's sidebar and I had to manually navigate to the folder myself, I would have (hopefully lmao) caught this much, much sooner.

#

This was able to happen because no sidebar or load window at any point showed drive labels, the production folder was a perfect 1:1 copy in both locations because I quit using the computer and forgot to delete the extra copy.

A perfect storm

#

That time was definitely a user issue
This whole thing was a big skill issue 😩

unique fractal
#

I've done tech support for > 20 years and I have the following phrase that I say out loud...

"I think I'm going crazy, but I'm not going crazy."

It's a small simple phrase, but it's something that I have to use to talk myself down. A friendly reminder that the computer will do as it's told. The computer is not magic.

#

I once troubleshot an app crash that was caused by a Windows 7 "run in compatibly mode" flag that was in the user's registry from a previous version of the app install, but the same path (e.g. C:\Program Files\myapp\myapp.exe) so any shortcuts would use the compatibility flag despite them being disabled in the Properties menu. Apparently Windows renamed but never remapped this compatibility flag in the upgrade to Windows 8. It took 4 days to find and delete this registry entry, I had to make a copy of the PC and work on it in a VM to not disrupt the user. I was the 3rd person in IT to look at it.