Please be a bit more specific. What is not working? Do you get errors? Is something converted incorrectly? Which source formats do not work? Do you have an example file? ...Acid4Life wrote: Mon Feb 10, 2025 2:17 am Hello!
I'm new here.
First I would like to thank you for sharing a much needed free file format converter to the world, especially for macOS. I really enjoy using it. Unfortunately , the latest ConvertWithMoss 12.1.0 seems to have broken going from a few different Source options to the Logic EXS24 Destination conversion.
I had to revert back to version 11.6.0 for Logic EXS24 conversion. I'm on macOS Sequoia using Logic Pro 11.1.2.
[FREE] ConvertWithMoss - convert from/to WAV,Bitwig,SFZ,SF2,DecentSampler,MPC/Force,Wave-/Modwave/KMP,NKI,EXS) v17.1
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
The files seem to not have any information about their note position. The algorithm takes the 1,2,3,... as the note number, which then gives you this error. Only way to fix this is to check that the numbers are unique (or add meaningful note names/numbers).Acid4Life wrote: Mon Feb 10, 2025 4:33 pm No problem. I get the same message regardless of source option or file format in mono or stereo.
1.png2.png3.png
-
- KVRer
- 18 posts since 10 Feb, 2025
Ok. Those were just test files, not my own.
What is the lowest and highest resolution supported on audio files for a conversion?
Can you please consider giving the software true dark mode instead of the blueish look?
What is the lowest and highest resolution supported on audio files for a conversion?
Can you please consider giving the software true dark mode instead of the blueish look?
-
- KVRer
- 4 posts since 8 Mar, 2024
Memorandum
To: MOSS
Subject: Request to Enable the Import of SYS "SYEX" Files Containing Montage/MODX Performances in the Yamaha ESP Plugin VSTi (THIS FILES CAN BE DOWNLOAD FROM SOIUNDMONDO)
Dear Team,
We would like to emphasize the significant benefits of incorporating the functionality to import SYS "SYEX" files containing Montage/MODX performances into the next release of the Yamaha ESP Plugin VSTi. Below, we outline the key points supporting the importance of this implementation:
Creative Continuity:
Facilitate the seamless transition of configurations created on hardware to the digital production environment.
Enable musicians to utilize custom performances from the Montage/MODX directly within the VSTi without manual recreation.
Enhanced Integration:
Promote seamless integration between hardware and software, offering a unified user experience.
Reduce technical barriers for professionals working with various Yamaha devices.
Strengthening the Yamaha Ecosystem:
Encourage users to stay within the Yamaha product ecosystem due to enhanced compatibility.
Demonstrate a commitment to technological evolution and customer satisfaction.
Productivity and Efficiency:
Save time on import processes and manual configurations, streamlining workflow.
Minimize errors that may occur when attempting to manually recreate performances.
Market Competitiveness:
Differentiate the Yamaha ESP Plugin VSTi from other products on the market, positioning it as a robust and versatile tool for musicians and producers.
Attract new customers seeking integrated solutions for hardware and software.
We are confident that including this feature will greatly benefit Yamaha’s user community, further strengthening the brand’s reputation as a leader in musical innovation. We appreciate your attention and look forward to this improvement in future updates to the Yamaha ESP Plugin VSTi.
Sincerely,
Herminio Cerqueira
To: MOSS
Subject: Request to Enable the Import of SYS "SYEX" Files Containing Montage/MODX Performances in the Yamaha ESP Plugin VSTi (THIS FILES CAN BE DOWNLOAD FROM SOIUNDMONDO)
Dear Team,
We would like to emphasize the significant benefits of incorporating the functionality to import SYS "SYEX" files containing Montage/MODX performances into the next release of the Yamaha ESP Plugin VSTi. Below, we outline the key points supporting the importance of this implementation:
Creative Continuity:
Facilitate the seamless transition of configurations created on hardware to the digital production environment.
Enable musicians to utilize custom performances from the Montage/MODX directly within the VSTi without manual recreation.
Enhanced Integration:
Promote seamless integration between hardware and software, offering a unified user experience.
Reduce technical barriers for professionals working with various Yamaha devices.
Strengthening the Yamaha Ecosystem:
Encourage users to stay within the Yamaha product ecosystem due to enhanced compatibility.
Demonstrate a commitment to technological evolution and customer satisfaction.
Productivity and Efficiency:
Save time on import processes and manual configurations, streamlining workflow.
Minimize errors that may occur when attempting to manually recreate performances.
Market Competitiveness:
Differentiate the Yamaha ESP Plugin VSTi from other products on the market, positioning it as a robust and versatile tool for musicians and producers.
Attract new customers seeking integrated solutions for hardware and software.
We are confident that including this feature will greatly benefit Yamaha’s user community, further strengthening the brand’s reputation as a leader in musical innovation. We appreciate your attention and look forward to this improvement in future updates to the Yamaha ESP Plugin VSTi.
Sincerely,
Herminio Cerqueira
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
There is no limitation from my side (there might some in the used libraries). Conversions are only applied if the destination format has a limitation (e.g. SF2 supports only 16 and 24bit data).Acid4Life wrote: Thu Feb 13, 2025 1:36 pm Ok. Those were just test files, not my own.
What is the lowest and highest resolution supported on audio files for a conversion?
I am not a designer and this is so far as good as it gets.Acid4Life wrote: Thu Feb 13, 2025 1:36 pm Can you please consider giving the software true dark mode instead of the blueish look?
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Not sure why you are posting this here.HCMC wrote: Mon Feb 17, 2025 10:19 am Memorandum
To: MOSS
Subject: Request to Enable the Import of SYS "SYEX" Files Containing Montage/MODX Performances in the Yamaha ESP Plugin VSTi (THIS FILES CAN BE DOWNLOAD FROM SOIUNDMONDO)
Dear Team,
We would like to emphasize the significant benefits of incorporating the functionality to import SYS "SYEX" files containing Montage/MODX performances into the next release of the Yamaha ESP Plugin VSTi. Below, we outline the key points supporting the importance of this implementation:
...
-
- KVRian
- 1121 posts since 4 Jun, 2003 from Skanky Manc
Hello Moss,
I discovered your excellent free tool because I was looking for a way to convert some multi-samples from SFZ to Waldorf Iridium format. Thank you for making this available for free!
Whilst I got it working I found a bug (using 12.1.0) I thought you might want to be aware of.
In short, I think the "tune" opcode is implemented incorrectly and causes samples to be out of tune when opened in Iridium. Here's why:
In SFZ you might have a region like this:
Here, "tune" is +11cents, causing the pitch of this region to play 11 cents HIGHER than its root pitch.
When converted to Iridium format using ConvertWithMoss, the sample gets imported with a Pitch value of "F#/Gb3 +11.0c" (or 66.11). In Iridium-world this is used as the root note, and the +11.0c actually causes the sample to play back 11cents LOWER than the root note.
When converting from a tuning value to a root value like this, the sign (+ or -) of the tuning value needs to be reversed. So in this example, a Pitch value of "F#/Gb3 -11.0c" (or 65.89) results in the sample playing back as intended.
Would love a fix for this so I can convert all my SFZs.
I discovered your excellent free tool because I was looking for a way to convert some multi-samples from SFZ to Waldorf Iridium format. Thank you for making this available for free!
Whilst I got it working I found a bug (using 12.1.0) I thought you might want to be aware of.
In short, I think the "tune" opcode is implemented incorrectly and causes samples to be out of tune when opened in Iridium. Here's why:
In SFZ you might have a region like this:
Code: Select all
<region>
sample=sample.wav
pitch_keycenter=66
tune=11
When converted to Iridium format using ConvertWithMoss, the sample gets imported with a Pitch value of "F#/Gb3 +11.0c" (or 66.11). In Iridium-world this is used as the root note, and the +11.0c actually causes the sample to play back 11cents LOWER than the root note.
When converting from a tuning value to a root value like this, the sign (+ or -) of the tuning value needs to be reversed. So in this example, a Pitch value of "F#/Gb3 -11.0c" (or 65.89) results in the sample playing back as intended.
Would love a fix for this so I can convert all my SFZs.
-
- KVRer
- 2 posts since 17 Feb, 2025
Hello,
When I installed ConvertWithMoss a fer months ago, everything worked. However, I noticed that I cannot convert anymore since I installed the latest version 12.1.0. Whenever I click on "Convert", I see the Analyse windows and a ConvertWithMoss.log is being created in the Destination folder, but there are no conversion at all. Only the log file appears. I am using a Mac M1, with Sonoma 14.5. I switched back to a previous version like 10.6 but it still not working.
I did follow the Mac installation instructions about the security issue.
When I installed ConvertWithMoss a fer months ago, everything worked. However, I noticed that I cannot convert anymore since I installed the latest version 12.1.0. Whenever I click on "Convert", I see the Analyse windows and a ConvertWithMoss.log is being created in the Destination folder, but there are no conversion at all. Only the log file appears. I am using a Mac M1, with Sonoma 14.5. I switched back to a previous version like 10.6 but it still not working.
I did follow the Mac installation instructions about the security issue.
-
- KVRAF
- 3672 posts since 13 Jun, 2004
hi Moss,
would it be possible to convert from Orion's Sampler instrument format, *.osp, to soundfont?
i know Synapse Orion is discontinued now, so it might be too niche for you to bother with.
i asked ChickenSystems ages ago and sent them a specimen file as requested but haven't heard anything since.
the sampler is quite good for doing and re-pitching autodetected (and shifted) chops on wav files, and can export it as *.osp.
it can also import soundfonts as playback material, with instruments/presets.
i tend to use it on single imported samples, but it can do quite a bit more, making more sophisticated programs, which i've never bothered with, which may be a problem, and have been too much complexity for CS to bother with for an obscure format. but it'd be great to have SF2 export for single wav chop programs. maybe Synapse have more information they'd be willing to let you in on.
the thing is, in Orion, it's really easy to use. frustrating that those *.osp files can't be used in the outside world eg: converted from SF2 to other formats.
would it be possible to convert from Orion's Sampler instrument format, *.osp, to soundfont?
i know Synapse Orion is discontinued now, so it might be too niche for you to bother with.
i asked ChickenSystems ages ago and sent them a specimen file as requested but haven't heard anything since.
the sampler is quite good for doing and re-pitching autodetected (and shifted) chops on wav files, and can export it as *.osp.
it can also import soundfonts as playback material, with instruments/presets.
i tend to use it on single imported samples, but it can do quite a bit more, making more sophisticated programs, which i've never bothered with, which may be a problem, and have been too much complexity for CS to bother with for an obscure format. but it'd be great to have SF2 export for single wav chop programs. maybe Synapse have more information they'd be willing to let you in on.
the thing is, in Orion, it's really easy to use. frustrating that those *.osp files can't be used in the outside world eg: converted from SF2 to other formats.
-
- KVRer
- 18 posts since 10 Feb, 2025
Ok. Hopefully you, and your eyes, will see the benefit of having true dark-mode in the late nights.moss wrote: Mon Feb 17, 2025 12:03 pmThere is no limitation from my side (there might some in the used libraries). Conversions are only applied if the destination format has a limitation (e.g. SF2 supports only 16 and 24bit data).Acid4Life wrote: Thu Feb 13, 2025 1:36 pm Ok. Those were just test files, not my own.
What is the lowest and highest resolution supported on audio files for a conversion?
I am not a designer and this is so far as good as it gets.Acid4Life wrote: Thu Feb 13, 2025 1:36 pm Can you please consider giving the software true dark mode instead of the blueish look?
Can you please rename Logic EXS24 Source and Destination, to Logic Sampler EXS, or to Logic EXS instead?
Only the Sampler, old UltraBeat, Alchemy, in Logic, reads .exs files. There is no more fugly and dated EXS24 Sampler in Logic, for years now. The file format is .exs, not EXS24.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Thanks for reporting! Will be fixed in the next update!Rozzer wrote: Mon Feb 17, 2025 12:51 pm Hello Moss,
I discovered your excellent free tool because I was looking for a way to convert some multi-samples from SFZ to Waldorf Iridium format. Thank you for making this available for free!
Whilst I got it working I found a bug (using 12.1.0) I thought you might want to be aware of.
In short, I think the "tune" opcode is implemented incorrectly and causes samples to be out of tune when opened in Iridium. Here's why:
In SFZ you might have a region like this:Here, "tune" is +11cents, causing the pitch of this region to play 11 cents HIGHER than its root pitch.Code: Select all
<region> sample=sample.wav pitch_keycenter=66 tune=11
When converted to Iridium format using ConvertWithMoss, the sample gets imported with a Pitch value of "F#/Gb3 +11.0c" (or 66.11). In Iridium-world this is used as the root note, and the +11.0c actually causes the sample to play back 11cents LOWER than the root note.
When converting from a tuning value to a root value like this, the sign (+ or -) of the tuning value needs to be reversed. So in this example, a Pitch value of "F#/Gb3 -11.0c" (or 65.89) results in the sample playing back as intended.
Would love a fix for this so I can convert all my SFZs.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
Did you select the correct source format?mgamache wrote: Mon Feb 17, 2025 11:12 pm Hello,
When I installed ConvertWithMoss a fer months ago, everything worked. However, I noticed that I cannot convert anymore since I installed the latest version 12.1.0. Whenever I click on "Convert", I see the Analyse windows and a ConvertWithMoss.log is being created in the Destination folder, but there are no conversion at all. Only the log file appears. I am using a Mac M1, with Sonoma 14.5. I switched back to a previous version like 10.6 but it still not working.
I did follow the Mac installation instructions about the security issue.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
As you said, it is a bit too dead for my taste. AWave does support it, which is not that expensive.mztk wrote: Tue Feb 18, 2025 8:34 am hi Moss,
would it be possible to convert from Orion's Sampler instrument format, *.osp, to soundfont?
i know Synapse Orion is discontinued now, so it might be too niche for you to bother with.
i asked ChickenSystems ages ago and sent them a specimen file as requested but haven't heard anything since.
the sampler is quite good for doing and re-pitching autodetected (and shifted) chops on wav files, and can export it as *.osp.
it can also import soundfonts as playback material, with instruments/presets.
i tend to use it on single imported samples, but it can do quite a bit more, making more sophisticated programs, which i've never bothered with, which may be a problem, and have been too much complexity for CS to bother with for an obscure format. but it'd be great to have SF2 export for single wav chop programs. maybe Synapse have more information they'd be willing to let you in on.
the thing is, in Orion, it's really easy to use. frustrating that those *.osp files can't be used in the outside world eg: converted from SF2 to other formats.
- KVRAF
- Topic Starter
- 4868 posts since 13 May, 2004
It is actually the old original EXS24 format. The new Logic Sampler has additional features and parameters which I never tested and might not work.Acid4Life wrote: Wed Feb 19, 2025 4:17 am Can you please rename Logic EXS24 Source and Destination, to Logic Sampler EXS, or to Logic EXS instead?
Only the Sampler, old UltraBeat, Alchemy, in Logic, reads .exs files. There is no more fugly and dated EXS24 Sampler in Logic, for years now. The file format is .exs, not EXS24.
