GithubHelp home page GithubHelp logo

Comments (8)

git-moss avatar git-moss commented on August 23, 2024

Seems the WAV file is broken or damaged. I also noted that a few of the files in the MPC library have such an issue.
To fix this try to open the file in an audio editor and save it again.

from convertwithmoss.

sequoi avatar sequoi commented on August 23, 2024

Hello, Mister Moss. Thank you for your kind response.

No, if you mean by the source files being damaged then files are not damaged in any case. Not mine or anyone else's.

I mean I just tried to convert a "commercial" MPC library into Bitwig with the same outcome.

What I am pointing out is this:

  1. I doubt a commercial library would deliver broken or damaged samples.
  2. when I copy samples from those libraries delivered with MPC format and place them into some folder on my computer - the same Bitwig is seeing those same samples in the browser just fine and can load them in a session (or sampler) just fine. So source samples seems to work just fine.

Manually loading those samples is fine by Bitwig. They seem to be broken only after conversion.

Also converting the same source samples from MPC into SFZ format with your converter and loading SFZ in Bitwig is working. It seems that just Bitwig file conversion is not working because only that format is giving me an error. Ironically it's the only output format (Bitwig that is) in which I am interested.

I checked that. I also tried to install 5.0 and it's the same outcome. Let me know if you can advise me on trying anything else.

from convertwithmoss.

git-moss avatar git-moss commented on August 23, 2024

That's strange since the files should only be zipped and not altered. But could be that mono to stereo file conversion is involved.
Could you send me one example source file?

from convertwithmoss.

sequoi avatar sequoi commented on August 23, 2024

Sure. Here is a small file.

Folder "MPC-Source" contains an XPM file and a sample taken from my AKAI Force. I can read it on my MPC Live or AKAI Force or MPC Software just fine. Also pointing Bitwig to that folder - you can see that the sample file can be loaded normally in Bitwig just fine - so pre conversion source is readable.

The folder "Bitwig-destination" contains the result of conversion with your converter. It can not be loaded in Bitwig.

If I (for example) try to use the "MPC-Source" folder and convert it to SFZ - that SFZ can be loaded fine in Bitwig.

As I said, only the Bitwig native file format, generated by your converter, seems to be having issues
conversion.zip
.

from convertwithmoss.

git-moss avatar git-moss commented on August 23, 2024

As I assumed the original WAV file has an incorrect header. That is what Wavelab reports:
Screenshot 2022-07-06 114821
Many programs simply carry on but Bitwig seems not to accept it. Simply resaving the file should fix it. E.g. you can use Reaper for doing this in a batch if it concerns many files.

from convertwithmoss.

sequoi avatar sequoi commented on August 23, 2024

That's interesting. You are on to something but I beg to differ. Allow me to explain myself.

I did what you asked me. Resaved sample in a different editor. And now conversion works fine.

However, your error is revealed only in Wavelab and not everywhere else.

I tried Audition, Izotope RX, Presonus, Live, Cubase, Reason, and FL Studio. So a sample is loaded across numerous DAW applications and audio editors. No error whatsoever. I tried to load a sample on my old and trusty AKAI S6000 hardware, no error message.

In fact, what is an interesting fact is that the pre-conversion sample is loading just fine even in Bitwig itself.

What is even more interesting is that the same pre-converted sample (supposedly with bad headers) can be manually loaded in Bitwig Sampler, saved as a Bitwig Sampler file, through the very same Bitwig, and this very same supposedly buggy sample is loading later in Bitwig sampler just fine. When saved in the very same format your converter is saving to.

So when I save this very same supposedly bad sample in Bitwig itself, as Bitwig Sampler preset - it is loading fine.

It looks like the sample is supposedly damaged or that the supposed error is revealed only after it goes through your own conversion tool and is saved as a Bitwig Sampler format file.

Even your SFZ tool outputs the same file and it's working.

Note that I fully understand this is free software and is supported by you in goodwill.

I am not complaining about your effort. I am explaining that it seems very irrational for me to accept that samples are wrong while in fact

a: the very same sample is working on countless audio editors and DAWs,
b: in fact it's even working in Bitwig itself and when saved from Bitwig in the very same format that you're trying to generate - it is working fine

Sorry but it sounds like your converter and its Bitwig output is the one to be blamed for the error.

I think you could work on the output format because not everyone has access to commercial batch converters and people should not pay for additional DAW apps only to be able to use your converter. And besides that, I tried to convert samples from different vendors such as AKAI itself, mpc-samples, E-lab, Wave-Alchemy and so on.

It really seems hard to accept that all these sample vendors are wrong when Wavelab is correct.

Thanks for your time. Much appreciated.

from convertwithmoss.

git-moss avatar git-moss commented on August 23, 2024

OK, I will try again:

  1. The file is broken, that is a fact.
  2. Many applications simply ignore it and carry on. Bitwig does that too when you only load the sample. But the multisample loader works differently, somehow they decided they need to check the header, maybe because they look for the root note or range.

The output of ConvertWithMoss still writes the same content of the file. You can test that yourself:

  1. Drag the file into Bitwig -> Sampler work fine
  2. Right click on the waveform and choose "Convert to Multisample"
  3. Store the multisample
  4. Reload the multisample -> you get the same error

You can now ask for two things:

  1. Ask Bitwig to ignore the error when loading multisamples as well
  2. Ask me to fix broken WAV files during the conversion

I already decided against 2) since this would mean to parse the wave-forms and check each value, which would slow down the conversion process hugely. Furthermore, it can be easily fixed by batch-resaving all files.

I also converted the whole MPC library in the past to multisamples and I noticed this issue on only a few files, mainly drum samples. So, yes Akai has some broken files in the library.

from convertwithmoss.

sequoi avatar sequoi commented on August 23, 2024

I'll try again as well.

  1. I realized that the file is indeed "broken". That's why I said that when I resaved it with a batch converter as per your instruction - your converter indeed worked.

  2. You are completely missing a point. No one is debating that the file may have some metadata error. What I am saying is:

  • All vendors seem to have such errors in their libraries. Not just AKAI. I've run and wasted a lot of time with this today and this is not AKAI-related. It seems the error is so mandatory that it is slipping into libraries provided by the largest online shops.

The error may be real but it's so mandatory that no one cares for it, thus it's working in every DAW or audio editor in existence. It is even ignored by Bitwig itself.

I am unsure what you mean by multisample or which version you are working at, as I said I can load a supposedly broken sample in Bitwig and save it in Bitwig natural Sampler format and it's working fine. Yes, even multi-samples.

It only seems to be affecting your own converter. Even when there is a single sample (not a multisample patch). I would accept this issue as a nonsolvable issue but your own converter spits out SFZ files which are then normally read in Bitwig.

What I am failing at is probably a language barrier and not direct whining or critics of your work. I am not saying you are incompetent or something like that. English is not my native so perhaps I am sounding harsh? This is not what I wanted.

You need to realize that it is very unlikely that people will use your converter to convert 3 or 4 samples. They will want to use it to convert thousands of samples in one go.

In the end, it doesn't matter, I am not here to upset you. I wanted to report my findings because I didn't see anything like that reported on KVR on both threads (old one and new one). My work is not dependent on this converter thus I merely wanted to report this to you.

I sincerely wish you the best.

from convertwithmoss.

Related Issues (20)

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.