The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Prophet => Sequential Prophet X => Topic started by: Lady Gaia on April 14, 2019, 06:58:56 PM
-
I'm delighted to announce that PXToolkit, my sample preparation utility for the Prophet X, is now available to anyone interested in working with the beta. It should be in good shape but doubtless a few issues will get identified and shaken out over the weeks to come. Many thanks to the alpha testers who have provided feedback in its earlier state.
Here's a quick overview of what you can expect from the app:
* Per-key sample mapping, fine tuned in cent increments
* Automatic sample key and loop detection from .wav metadata
* Up to 20 velocity layers per key
* Up to 20 round-robin samples per velocity layer
* Undo/redo support
* macOS and Windows support
... and in video form:
https://www.youtube.com/watch?v=BLiOVXwReQI&feature=youtu.be (https://www.youtube.com/watch?v=BLiOVXwReQI&feature=youtu.be)
There's a dedicated page with download links here (http://www.thinkersnacks.com/px-toolkit.html). Enjoy, and don't hestitate to get in touch with any bug reports or questions. Before the obvious one gets asked: yes, the application is completely free for personal use.
-
fantastic ... nice work, thank you so much !
-
Again, LadyGaia you're the One !!!!!!!!!
-
I discovered an unfortunate bug that crept into the 0.7.5 beta build. Instruments built with single-digit index numbers weren't getting padded to two digits (eg: they'd come out as "2. Instrument|Name.zip" rather than "02. Instrument|Name.zip".) This unfortunate regression has been addressed with 0.7.6 which can be downloaded here (http://www.thinkersnacks.com/px-toolkit.html).
Apologies for the inconveniences. That's why it's a beta...
-
WOW, this is amazing.
I'm delighted to announce that PXToolkit, my sample preparation utility for the Prophet X, is now available to anyone interested in working with the beta. It should be in good shape but doubtless a few issues will get identified and shaken out over the weeks to come. Many thanks to the alpha testers who have provided feedback in its earlier state.
Here's a quick overview of what you can expect from the app:
* Per-key sample mapping, fine tuned in cent increments
* Automatic sample key and loop detection from .wav metadata
* Up to 20 velocity layers per key
* Up to 20 round-robin samples per velocity layer
* Undo/redo support
* macOS and Windows support
... and in video form:
https://www.youtube.com/watch?v=BLiOVXwReQI&feature=youtu.be (https://www.youtube.com/watch?v=BLiOVXwReQI&feature=youtu.be)
There's a dedicated page with download links here (http://www.thinkersnacks.com/px-toolkit.html). Enjoy, and don't hestitate to get in touch with any bug reports or questions. Before the obvious one gets asked: yes, the application is completely free for personal use.
-
WOW, this is amazing.
Glad to hear it looks appealing. I’m looking forward to hearing from people who are putting it to good use, even if it’s just with bug reports or suggestions.
-
Version 0.7.7 is up, and I’d recommend Windows users in particular pick this one up. Although alpha testers reported success building and installing archives from Windows, it definitely wasn’t doing so exactly as intended. That oversight has been corrected.
Everyone also gets better feedback when entering invalid export details (like an instrument index of 1.) I’ve added warnings for marginal cases where what has been entered is legal but perhaps not entirely desirable (such as an instrument name that isn’t likely to fit on the Prophet X display.)
-
Available for download (http://www.thinkersnacks.com/px-toolkit.html) from the usual location. Unlike recent releases which have been largely bug fixes, this wraps up the feature work I had planned for v1.0. If any obvious omissions come up I might add something small, but for the next week or two I'll be focused on any bugs that get reported.
The major addition here is documented as follows:
Dragging Samples and Regions
Samples displayed for the currently selected regions can be dragged individually from the detail display on the right. Just start dragging and the sample will be represented by a small icon that can be dropped anywhere in the canvas. Regions containing either single samples or round-robin collections can also be dragged as a group.
Dropped samples follow behavior very similar to sample files when initially dropped: they'll divide existing velocity ranges by default, or add to existing regions if the shift key is held. Unlike new samples being added, however, the origin key for the sample is selected based on where the cursor is using the following logic:
- When dropped between the lower and upper bounds of an existing key span, the key associated with all other samples in that span will be chosen. (This makes it much easier to split multi-key regions into velocity layers than it would be otherwise!)
- When dropped in a gap between existing key spans the exact key it is dropped over will be chosen as the origin key for that span.
-
Oh My ... downloading now ...
-
Oh My ... downloading now ...
Let me know what you think. There have been a few minor updates since I last posted here, to version 0.8.5. Most notably this adds the ability to preview samples from within the PXToolkit app. From the README:
Previewing Samples
Any attached MIDI controller can be used to play the current arrangement of samples. Samples will play at full volume until the corresponding key is released, at which point it will fade out rapidly. Velocity will be used to select the appropriate region, and round-robin alternatives will be selected among randomly. Stuck notes can be cured by sending "all notes off", or by clicking on any other window (PXToolkit releases its connection to MIDI inputs immediately when it loses focus along with silencing all audio playback.)
Samples can be also previewed when a single region is selected on the canvas or a sample is selected in the detail region on the right. Press the space bar or select the Edit > Play Sample menu item to get a two-second preview as a brief reminder of the mapped sound. When multiple samples are assigned in round-robin fashion, one of the samples will be selected at random.
The sample will be played back at its natural pitch, looped if appropriate, and adjusted for any tuning correction specified (remember that a +100 cent tuning indicates that the samples must be pitched down a semitone at playback, as the value indicates how far out of tune the original sample was recorded.)
-
How far can you stretch a sample across the keybed? I noticed in the official sample mapping program you could only do a specific portion of the keybed. It would be nice if you could just import a sample on to middle C and stretch it across the whole keyboard. I know the PX can do this with Sample Stretch but it would be nice to be able to just have this option in the mapping program too. I would say the same thing for looping but I know that’s likely problematic.
-
How far can you stretch a sample across the keybed? I noticed in the official sample mapping program you could only do a specific portion of the keybed. It would be nice if you could just import a sample on to middle C and stretch it across the whole keyboard.
PXToolkit will do exactly that. The first sample added stretches to fill all available space, and subsequent additions negotiate with their neighbors to minimize pitch shifting by placing the boundary as close the the midpoint between the two as possible. Of course everything can be tweaked manually from that starting point.
... not that I'd recommend stretching samples that far in general. I haven't done deep investigations of the Prophet X pitch shifting strategy, but some basic spectrum analysis showed clear signs of aliasing creeping in when transposing material up more than two octaves (and no, that's not surprising, as high quality sample rate conversion is computationally intensive. To get it mathematically "right" involves a summed series weighting the value of every single sample to produce each and every interpolated sample, which is insane enough that everyone takes some kind of shortcut.)
I would say the same thing for looping but I know that’s likely problematic.
Loops shouldn't be an issue. They're specified in a sample-accurate fashion in metadata, and presuming the transposition algorithm isn't broken it should just treat the end and the start of the loop as if they were a contiguous series of samples.
-
How far can you stretch a sample across the keybed? I noticed in the official sample mapping program you could only do a specific portion of the keybed. It would be nice if you could just import a sample on to middle C and stretch it across the whole keyboard.
PXToolkit will do exactly that. The first sample added stretches to fill all available space, and subsequent additions negotiate with their neighbors to minimize pitch shifting by placing the boundary as close the the midpoint between the two as possible. Of course everything can be tweaked manually from that starting point.
... not that I'd recommend stretching samples that far in general. I haven't done deep investigations of the Prophet X pitch shifting strategy, but some basic spectrum analysis showed clear signs of aliasing creeping in when transposing material up more than two octaves (and no, that's not surprising, as high quality sample rate conversion is computationally intensive. To get it mathematically "right" involves a summed series weighting the value of every single sample to produce each and every interpolated sample, which is insane enough that everyone takes some kind of shortcut.)
I would say the same thing for looping but I know that’s likely problematic.
Loops shouldn't be an issue. They're specified in a sample-accurate fashion in metadata, and presuming the transposition algorithm isn't broken it should just treat the end and the start of the loop as if they were a contiguous series of samples.
You recommended Sample Robot correct? Will it export the files in the correct format for the PX?
-
You recommended Sample Robot correct? Will it export the files in the correct format for the PX?
SampleRobot was a great help when putting together the VCO Pack. After I got the initial recordings from @blewis and @Alan I did a fair bit of sample trimming, gain adjustment, and all the looping with SampleRobot. It bulk exports .wav files at whatever sample rate and bit depth you specify, with all the metadata PXToolkit needs to pick up the loops and place the samples on the right keys.
In practice you can use anything that produces 16-bit LPCM 48kHz .wav files with loop information embedded in the standard "smpl" section of the file. PXToolkit will also rely on information about the original pitch from "inst" or "smpl" sections, but if it's absent it will try to guess the correct pitch based on the filename (eg: "Piano c#3.wav" will be imported where you'd think it should be.) When you export the final .zip PXToolkit will strip out everything unnecessary to ensure that the Prophet X gets exactly what it's looking for.
-
Thanks so much for doing this LG—your software is definitely better than the fare from 8DIO. Personally, I'd be embarrassed to release something so basic and poorly designed.
I've managed to get a reasonable workflow going, by
Autosampling in MainStage—the auto looping is superb. This is how you create professional software! It's a pity Apple dropped Redmatica's options for sample output.
Batch processing and sample/bit change (EQ, Normalise etc.) to WAVs in Izotope RX
Having to add manually to the USB dongle, remembering which folder names to create and not being able to organise and delete samples via a proper app—I felt like I'd gone back FORTRAN programming or sampling on my Mirage.
Software is supposed to make things easier, not harder. The annoying thing is that there's plenty of software that shows how to do this properly and 8DIO are a sampling company!
Stephen
-
Does anyone have any idea why renaming files on the USB should cause them not to load? I wanted to change the numbers (01,02) around. I renamed 12 files but about a third now refuse to load. I've checked and the spacing etc is the same on all the files.
Stephen
-
The contents of the zip files make reference to the file’s name. Lady Gaia had a rename utility that you have to use. You can’t just edit the file name or the data will be incoherent.
-
Thanks so much for doing this LG
Thank you for letting me know you’ve found it useful! That’s definitely what I had hoped for in taking on the project. I’ve loved watching a healthy community grow up around this instrument as I see so much potential in it.
As noted above, there’s a utility on my site for renumbering Prophet X instrument archives (http://www.thinkersnacks.com/px-renumber.html). It’s command-line only at this point, but it’s fairly straightforward to use if you’re comfortable in Terminal.app on macOS or the Windows command prompt.
-
Thanks LG et al. That’s great! Dave Smith really needs to hire you.
Stephen
-
That works great, thanks.
With the rename, what would be nice is if you could take in a list of original filenames and batch process these using px-renumber.
Stephen
-
That works great, thanks.
With the rename, what would be nice is if you could take in a list of original filenames and batch process these using px-renumber.
I've seen enough feedback from some who aren't comfortable with the command-line that I'll probably opt to rework it with a friendly UI eventually before adding anything to the current functionality. It's not an immediate priority, but the name "PXToolkit" was chosen to cover a range of possible features beyond importing samples. Archive renumbering is certainly on the list of possibilities.
-
Thanks again—renaming 20 files nearly killed me :)
I'll take a little more care the next session ...
Stephen
-
I think I didn't a bad thing. What does this error mean?
(https://i.imgur.com/FCYJkbM.png?1)
(Windows 10)
-
I think I did a bad thing. What does this error mean?
It either means that the file 21.wav isn’t a well-formed .wav file, or that PXToolkit doesn’t understand some infrequently used aspect of the .wav file specification. If you can upload 21.wav somewhere like DropBox and PM me a link to it I’ll dig into the file to figure out which is the case.
(If I had to guess, I’d say the file is longer than necessary and just has a bunch of zero byte padding at the end. The duplicate “chunk” identifier is probably 00 00 00 00. I realize this is more me talking to myself than anything. Users shouldn’t have to know anything about the file format, but the error messages are there to help diagnose situations like this.)
-
I've been trying to figure out what best tools I can use on Windoze or Linux to manipulate the wav file headers/trailers to insert the correct pitch data. Having the root pitch of the sample inside the meta-data will make life a lot easier importing the sample. Only filename conventions do not seem to work very well.
Does anyone have any tips here, what best tools to use (preferably Linux command line for batch processing)?
-
I leave the Linux and Windows tools question open to others, since macOS is my home turf.
Regarding the inference of root pitch from filename, though, that should be pretty reliable. I'll only use it if there isn't authoritative metadata in the .wav, but I'll recognize a pretty wide range of formats. What I'm looking for is:
* A delimiter (can be a space, dash, period, underscore, tilde, plus sign, or any kind of opening parenthesis/bracket/brace)
* Followed by a letter from A to G (lower case is also acceptable)
* Optionally followed by # or b
* Followed by an octave integer (anything from -2 to 8 )
* Followed by another delimiter (like the opening delimiter but with closing bracket/brace/parenthesis)
So it should be pretty flexible. The one limitations that leap to mind are that you can't embed extra or other unrelated characters in the middle of the note name, you can't use a + in front of the octave, and it won't recognize H as a valid note. I couldn't come up with a reasonable heuristic for what B should mean that isn't ambiguous once you recognize H as a possibility.
-
This is a quality piece of work. Easy to use, solid, does what you need... many thanks from many people!
DSI should license this from you and just ship it with every PX. Well done, Madame, well done!
-
I leave the Linux and Windows tools question open to others, since macOS is my home turf.
Regarding the inference of root pitch from filename, though, that should be pretty reliable. I'll only use it if there isn't authoritative metadata in the .wav, but I'll recognize a pretty wide range of formats. What I'm looking for is:
* A delimiter (can be a space, dash, period, underscore, tilde, plus sign, or any kind of opening parenthesis/bracket/brace)
* Followed by a letter from A to G (lower case is also acceptable)
* Optionally followed by # or b
* Followed by an octave integer (anything from -2 to 8 )
* Followed by another delimiter (like the opening delimiter but with closing bracket/brace/parenthesis)
So it should be pretty flexible. The one limitations that leap to mind are that you can't embed extra or other unrelated characters in the middle of the note name, you can't use a + in front of the octave, and it won't recognize H as a valid note. I couldn't come up with a reasonable heuristic for what B should mean that isn't ambiguous once you recognize H as a possibility.
Thanks Lady Gaia. The issue might be because of the first delimiter, there is none before the note name. By the way, neither your PXToolkit nor the 8Dio tool work on these filenames. They both behave the same and assign wav files in alphabetical order to the keys. Filenames are:
A#2.wav
A2.wav
A#3.wav
A3.wav
A#4.wav
A4.wav
B2.wav
B3.wav
and so on.
Perhaps i should try to put a character + delimiter (underscore) in front of the note, something like:
fred_A#2.wav
Obviously I can drag the filenames myself, but being a lazy person, I'd prefer to script it.
-
I've heard from a few folks who were using earlier versions of PXToolkit without being aware of updates, so as of last night's 0.9.0 release, PXToolkit will automatically check and provide a reminder when there's a newer version available.
Thanks Lady Gaia. The issue might be because of the first delimiter, there is none before the note name.
That's not a naming scheme I had considered as I assumed something would always precede the note name, but it's easy enough to fix. As of 0.9.1, which is already available, the opening delimiter will no longer be necessary if the first character of the filename is the start of the note name (and the closing delimiter could already be omitted if the note name is immediately followed by the .wav extension.)
It meant wading back into regular expression land but only briefly, so no lasting harm was done. Would you believe "^(?:.*[-. ~+_({<\[])?([a-gA-G][#b]?(?:-[12]|[0-8]))(?:[-. ~+_)}>\]].*)?$" describes files that match the range of naming schemes I recognize? Yikes.
Version 0.9.1 also attempts to ignore cases where there's unnecessary padding at the end of a .wav file. This should take care of Perilous's case above, but I'd appreciate confirmation from anyone who saw similar symptoms.
-
I've heard from a few folks who were using earlier versions of PXToolkit without being aware of updates, so as of last night's 0.9.0 release, PXToolkit will automatically check and provide a reminder when there's a newer version available.
Thanks Lady Gaia. The issue might be because of the first delimiter, there is none before the note name.
That's not a naming scheme I had considered as I assumed something would always precede the note name, but it's easy enough to fix. As of 0.9.1, which is already available, the opening delimiter will no longer be necessary if the first character of the filename is the start of the note name (and the closing delimiter could already be omitted if the note name is immediately followed by the .wav extension.)
It meant wading back into regular expression land but only briefly, so no lasting harm was done. Would you believe "^(?:.*[-. ~+_({<\[])?([a-gA-G][#b]?(?:-[12]|[0-8]))(?:[-. ~+_)}>\]].*)?$" describes files that match the range of naming schemes I recognize? Yikes.
Version 0.9.1 also attempts to ignore cases where there's unnecessary padding at the end of a .wav file. This should take care of Perilous's case above, but I'd appreciate confirmation from anyone who saw similar symptoms.
Ha ha very funny, I love regular expressions when I can get them to work for me...... I've done a lot of sysadmin style automation using good ol' Perl in my days. Switching more to Python and Ansible (not really a scripting language, but still very cool) nowadays.
I figured putting the filenames in a sample voice named directory structure, was enough for me to recognize what I was working on. Also makes it quite easy to archive the samples using tar or 7zip and sent them around my computer systems.
Still it would be great to be able to hack the audio meta data. I have downloaded a trial version of Sample Robot, but at the moment I don't have the time to get a degree in astrophysics to understand even the interface.
I will be testing your new version later tonight. Don't require a degree for that ;-). Thanks for keeping the interface simple and clear, but complex enough to quickly do the most important task of mapping the samples.
-
It either means that the file 21.wav isn’t a well-formed .wav file, or that PXToolkit doesn’t understand some infrequently used aspect of the .wav file specification. If you can upload 21.wav somewhere like DropBox and PM me a link to it I’ll dig into the file to figure out which is the case.
Thanks, LG! I hope to have the files uploaded soon. I am using an old outdated wave editor to trim a large wav. into samples. It works with the 8dio utility but I still get the same error even with the latest version of PXToolKit. I would send one of those newfangled PMs but it appears I must first brush up on my DSI/Sequential history.
-
I really think the loop parameter in the Prophet X should just be available in the mapping software and you can create loop points and specify what samples you want to be automatically looped by default.
-
Thanks, LG! I hope to have the files uploaded soon. I am using an old outdated wave editor to trim a large wav. into samples. It works with the 8dio utility but I still get the same error even with the latest version of PXToolKit.
Hmmm. I'll be happy to help you get to the bottom of this. I'll PM you a link to a shared folder on DropBox where you can upload the problematic file (unfortunately you will need to create an account there to use it, but they're free.)
Ha ha very funny, I love regular expressions when I can get them to work for me...... I've done a lot of sysadmin style automation using good ol' Perl in my days. Switching more to Python and Ansible (not really a scripting language, but still very cool) nowadays.
Most of my work is in native languages, but for PXToolkit I wanted something that would give me a quick way to reach both macOS and Windows users. Would you believe the whole thing is written in TypeScript?
Still it would be great to be able to hack the audio meta data. I have downloaded a trial version of Sample Robot, but at the moment I don't have the time to get a degree in astrophysics to understand even the interface.
SampleRobot definitely has that classic engineer-designed user interface but it's quite capable once you get past the quirky character. I find it invaluable for trimming, looping, and normalizing samples.
I will be testing your new version later tonight. Don't require a degree for that ;-). Thanks for keeping the interface simple and clear, but complex enough to quickly do the most important task of mapping the samples.
I'm glad it's hitting the right sweet spot for you. The art of designing something usable is a tricky one and can be rather subjective, so I'm never sure until someone else tries to use one of my designs. I'm still struggling to figure out how best to expose the one esoteric feature the Prophet X enables that I haven't incorporated yet, precisely because it's not something I think needs to be prominent: you can specify on a per-sample basis how stereo samples should be collapsed to mono when it's required - either by summing both channels or just using the left or right channel on their own. Right now PXToolkit just marks everything as collapsing by summing the two channels.
I'll keep tinkering with ideas, because I really don't want to clutter things in the process for a feature many won't need to worry about.
I really think the loop parameter in the Prophet X should just be available in the mapping software and you can create loop points and specify what samples you want to be automatically looped by default.
Samples with loops already defined are already mapped correctly. Defining new loop points requires a very different user interface as you really need to see the waveform to make decent sample-accurate decisions. I've debated whether to tackle that project eventually or not but it definitely isn't my immediate goal as it would increase the scope significantly and start looking more like a viable commercial product. It makes sense to treat sample format and rate conversion, trimming, normalizing, looping, etc. as a whole family of related problems. For now my personal tool of choice in that space is SampleRobot.
-
Thanks Lady Gaia, you nailed the regular expression on the head! It works perfectly now, samples are properly assigned, even with the quirky filenames I have used. Good job.
-
Hmmm. I'll be happy to help you get to the bottom of this. I'll PM you a link to a shared folder on DropBox where you can upload the problematic file (unfortunately you will need to create an account there to use it, but they're free.)
Thanks. It's not one problematic file, it's each and every one. DropBox is also problematic.
I can try this: https://drive.google.com/open?id=157R1BVNKt2WhKxXNfCBuUJg98flddGui
I'm using an old wave editor to chop up the long .wav into its own separate file for each note.
This old program is likely the culprit. The only output settings I have is PCM Uncompressed, and I think it's supposed to be 44100 Hz, 24 Bits, Stereo, if I don't have my head screwed on backwards (which has been the case all week). The master file that I'm chopping from actually imports perfectly fine.
-
Version 0.9.5 of PXToolkit is now available. It includes a number of small improvements, including compatibility with technically invalid .wav files along the lines of the example @Perilous kindly provided (though as always they'll need to be 48kHz 16-bit for use with the Prophet X.)
This release also adds support for the only Prophet X user instrument feature I'm aware of that was not previously supported. The included README describes the new Advanced Sample Features context menu as follows:
Several esoteric features relating to samples are now available on a context menu. Right-click (or control-click on macOS) on either an individual sample to modify an individual sample, or anywhere in the canvas to affect all samples in currently selected regions. The context menu offers the following advanced options:
If one or more selected samples are looped, the menu will show the item "Use Sample Loop." Toggling this allows the loop described in .wav metadata to be ignored when the instrument is exported.
If one or more selected samples are in stereo, the menu will show four options for controlling how sound is collapsed to mono in 16-voice mode. Four options are available: summing both left and right channels, using only the left channel, only the right channel, or defaulting to whatever mode has been selected for the instrument as a whole, as described below.
The final section of the menu allows the default mono collapse mode to be selected. These options will be displayed no matter what is currently selected, and affect all stereo samples that do not have an explicit mode selected.
A checkmark will appear beside the currently selected mode in each case. When two or more samples are selected it's possible that multiple modes are active. This is reflected by three dots beside the modes that aren't uniformly applied. Selecting a new mode will cause all selected sample to change to the same value.
The sample detail list will reflect new states as follows:
* Samples with loops that have been disabled will display "Loop Disabled" instead of "Looped"
* Stereo samples that aren't using the instrument-wide default mode for collapsing to mono will display "(( Stereo ))", "(( Stereo", or "Stereo ))" to reflect using both channels, just the left channel, or just the right channel respectively.
-
Thanks. It's not one problematic file, it's each and every one. DropBox is also problematic.
I can try this: https://drive.google.com/open?id=157R1BVNKt2WhKxXNfCBuUJg98flddGui
I'm using an old wave editor to chop up the long .wav into its own separate file for each note.
This old program is likely the culprit.
That was very helpful. Thank you! The file is indeed technically invalid, but I've included changes that will allow files with this particular flaw to be recognized by PXToolkit.
The only output settings I have is PCM Uncompressed, and I think it's supposed to be 44100 Hz, 24 Bits, Stereo, if I don't have my head screwed on backwards (which has been the case all week). The master file that I'm chopping from actually imports perfectly fine.
This particular file, however, is 44.1kHz 24-bit as you noted, and the Prophet X only supports 48kHz 16-bit samples, either in mono or stereo. PCM Uncompressed is also required, so you're okay on that front. With a tool of a vintage that produces this particular kind of quirky .wav file, you're almost certainly better off not having it do any sample rate conversion in any case, and even bit-rate changes may not be optimal. Since the full file imports without issues, the original must already be 48kHz 16-bit, so just stick with that format and you should be good to go!
-
Thank you again, Lady Gaia ... fantastic work. Very appreciated.
-
That was very helpful. Thank you! The file is indeed technically invalid, but I've included changes that will allow files with this particular flaw to be recognized by PXToolkit.
That's really cool. It works now! Thanks a lot. I was going to ask what do folks use for slicing and dicing when I remembered I already have Audacity installed. Derp. I guess my first reaction was to use the quirky wave editor because the chopping process is quicker. Thanks again for your marvelous support.
-
Just a heads up that beta version 0.9.8 of PX Toolkit is up on ThinkerSnacks (http://www.thinkersnacks.com/px-toolkit.html) - It still reads "beta 0.9.7" under the download button, but the file you download will be 0.9.8. I don't know all the specifics of the newest version other than Lady Gaia went to the trouble to update the app so we can now drag 44.1k files into the GUI! Hot damn!
-
Ah yes, in the rush to get the build out before catching a morning flight I wound up taking one shortcut. Everything had already been staged to update the site with a post-beta 1.0 when I return, so I didn’t have time to get the minor version bump reflected on the web site.
Thanks to Armen for inspiring this latest change. PXToolkit should now accept any sample rate, not just 44.1 and 48kHz, but the Prophet X’s native 48kHz is still the ideal.
Get any last-minute but reports in now, folks! I’d like to make sure the official release version is in great shape.
-
Ah yes, in the rush to get the build out before catching a morning flight I wound up taking one shortcut. Everything had already been staged to update the site with a post-beta 1.0 when I return, so I didn’t have time to get the minor version bump reflected on the web site.
Thanks to Armen for inspiring this latest change. PXToolkit should now accept any sample rate, not just 44.1 and 48kHz, but the Prophet X’s native 48kHz is still the ideal.
Get any last-minute but reports in now, folks! I’d like to make sure the official release version is in great shape.
You're welcome! So it sounds like bit rates other than 16-bit will work too?
Bug report:
I'm on Mac OS 10.13.6.
After launching PX Toolkit and loading a .pxinstrument file, upon opening a second .pxinstrument file, no audio is heard and the piano keys of the GUI on the 2nd file do not show that they are being triggered (they don't turn blue). Highlighting the 1st file window, then going back to the 2nd file window fixes this. However, if I have closed the first file, THEN load another file, this issue occurs. At that point, relaunching PX Toolkit is necessary. So as long as that first loaded .pxinstrument file stays open, you can load multiple .pxinstrument but need to highlight (touch one of the other windows with your mouse) another PX Toolkit open file window to hear audio.
-
So it sounds like bit rates other than 16-bit will work too?
I’m afraid not. The particular white lie I’m using to trick the Prophet X plays into its inherent pitch shifting abilities. Changing bit depth is a different story altogether. Not all that tricky, really, but I’d want to research dithering options and it all starts to sound more like a sample editing utility.
Bug report
Something to look into when I’m back to the studio. I suspect I know what’s happening but it’ll take a little research to be certain. Switching to another app and back should also solve the problem, as PXToolkit releases its hold on MIDI resources when switching to other apps.
-
Version 0.9.9 went up tonight with fixes for the MIDI issue ArmenJC reported above, corrected naming for categories 12 and 16, and a few other minor changes documented in the README. If I don't hear anything further I'll go ahead and bump it to v1.0 this weekend.
Thanks to everyone who jumped in to try out the beta release, whether or not you found issues to report.
-
Version 0.9.9 went up tonight with fixes for the MIDI issue ArmenJC reported above, corrected naming for categories 12 and 16, and a few other minor changes documented in the README. If I don't hear anything further I'll go ahead and bump it to v1.0 this weekend.
Thanks to everyone who jumped in to try out the beta release, whether or not you found issues to report.
Thanks again for your work !
-
Thanks to all you of who tried the beta releases out, and especially to everyone who reported bugs or otherwise offered suggestions for improvement. I've started a new thread (https://forum.sequential.com/index.php/topic,3632.0.html) celebrating the arrival of version 1.0.0 that will take over where this thread left off. Hopefully those reluctant to install something pre-release will feel comfortable joining in.
Happy music making, everyone.