skulkrusha

Members
  • Content Count

    163
  • Joined

  • Last visited

Everything posted by skulkrusha

  1. Someone correct me if I'm wrong, but you can save FST files in the demo, but not FLPs. I do remember doing it myself, but it might have been in version 3 rather than 4. Apply samples to your MIDIs? I'm not really sure what you want, here ... You can drag and drop samples onto the MIDI Out channels from the sidebar, although it might not sound too good. You can also do this with almost anything else in the sidebar. Finally, have a look under Projects>Tutorials>VST and DX instruments, which explains how to control VSTi and DXi from MIDI Out channels. I'd warn you, however, if you're taking someone else's MIDI and just putting your own instruments on top to pass it off as a remix, it's known as "MIDI ripping" here and it's akin to plagiarism.
  2. I've found it works just fine if you set the instruments using the MIDI Out channels, even without using Fruity LSD. If that isn't working, make absolutely sure there's no automation that could possibly be causing the channels to revert to the piano patch (particularly if you're importing an external MIDI file, since FL regards all patch numbers as automation information). If it still doesn't work, your problem is beyond me.
  3. Just link them all to the same controller. Make sure you've unchecked the "remove conflicts" box. FST files are just Fruity save states. They just save the current state of whatever thing you're using, handy if you want to copy settings of one thing to a different project. Anyway, you can make these by clicking in the top left-hand box in any box and selecting "save state as ..." or file>save state as. STFU RTFM
  4. This only happens on MIDI Out/Fruity LSD and not the standard or external plugins? Is this "delay" still present after you export the MIDI? If you've done anything to the MIDI settings in the system settings screen, reset everything in there. Turn off everything, set the outputs and inputs to none or generic controller, reset all the port numbers and MIDI channels, and set output board mapping to Microsoft MIDI Mapper. Also, try changing the buffer length under audio settings. What you've described could also be the result of other software you're running outside FL at the same time accepting FL's MIDI signals, so if you've got anything else running that could be doing it, try turning it off. Otherwise, I don't know. Care to share what you've already tried? Your speaker set up, perhaps?
  5. A very high standard mix, making use of a good range of effects and some pretty good drum programming. This manages to avoid being overly repetative and remain interesting, which is always good, although I would have liked to have seen it being a little more adventurous (a drum break here and there wouldn't have been out of place). Otherwise, a pretty good listen overall.
  6. I'll assume you're talking about external plugins ... I don't know, give me a clue. What do you mean, exactly? The wrapper has nothing in it after you've loaded a plugin? The channel properties box doesn't open the "plugin" tab? Something else?
  7. Takuyuni: I believe you're referring to the soundfont player. Sample = an audio clip. Soundfont: You can buy the XXL version of FL at the moment which is the Producer edition with all the full versions of the plugins (you don't pay for what you already have, though, so if you've already got the Fruityloops edition with, say, the full version of the Soundfont Player and DX10, you wouldn't pay for those plugins and you'd only pay the upgrade price for Producer edition. Not sure if it's still on, but there was a special offer of 40% off the total price on that package). The price depends on what you already have, though. Peng: This thread has been around for years, and those threads have been purged since then. There's a "getting started" guide on the FL Studio website under "downloads".
  8. You want to sample from CDs or MP3s? It's not really FL related, but any wave editor can do it. You should ask that sort of question in the sample/soundfont request thread, I guess. There's also a sticky for this subject ... In a nutshell, clipping is where the audio input signal is too loud for the output, and the sound distorts (if it's particularly bad it can wreck your speakers, too). It's called "clipping" because of the characteristic sharp truncation of the audio waveform. So, there's two ways of recognising it, either audible distortion or by looking at the waveform. Oh, and a compressor is not the clipping cure-all. It has its uses, but it can make clipping a lot worse. Read the "solution for clipping" thread, there's a bunch of handy hints in it.
  9. You want to automate the tempo. Look up "automation" in the help file.
  10. Oooh, I didn't know that. Thanks for sharing, I'll stick it in the FAQ Sounds like your speakers are outputting in mono. That's not a bug, it's your computer/speakers. Alternatively, if that doesn't happen all the time, some effects can cause the sound to be output in mono regardless of the panning of the generator channel ... Do you have the producer edition? If so, are you panning in the mixer? (Edit: Never mind, you use an old version of FL. This doesn't apply to you) Once again, I suspect this isn't FL's fault. If I remember correctly, you use an old version of FL, so I don't know if this is the case, but are you placing the pattern for the automation in the playlist? I've also noticed that some third-party plugins don't respond all that well to FL's automation, although that might not apply to this. You should also make sure that you've definately got an automation pattern (check Current Project>Automation in the sidebar). This has been answered several times, actually. If your MIDI Out channels are set to the correct instruments, make absolutely sure there's no automation causing the channels to revert to the piano setting (Current Project>Automation in the sidebar). If this doesn't work, run the FL diagnostic tool to see if anything's wrong (Help>FL Diagnostic Tool). If your keyboard has a MIDI output port on the back and you've got the USB-MIDI cable, you can send MIDI to anything on your computer that'll accept it. MIDI isn't sound; it's a protocol which allows MIDI enabled devices and instruments to communicate with each other. You can record MIDI data with FL, which is explained in the help file under "Live Recording", but you cannot record audio through MIDI. To record audio, you'll have to hook up your keyboard to a line in on your computer with some sort of audio cable and record the audio that way. I have no idea what you mean by "overlay it to a soundfont", but from your second post ... You want to record it as a soundfont? Firstly, FL can't do that, and I'm almost certain you want to sample your keyboard. I answered that question on the previous page.
  11. Yeah, but you need a soundcard with ASIO inputs. If you have that, you can route that input into FL's mixer (the "in" dropdown box at the bottom of the mixer; if you have any experience with routing vocoder channels this should be second nature to you), then you can record audio from that input using FL's disk record function. You'll need the Producer edition to do all this.
  12. I don't know if that's normal, but try downloading from there when internet traffic is lower. It could be just that their servers are experiencing a lot of load. FAQ is still being worked on. I'm one of the two or three people who are meant to be working on it ... I'm at the stage of categorizing the questions and answers, so hopefully it won't be long before it's all finished. I might post the raw archive later, but it's kind of messy to look through right now. We don't mind answering your questions, just try not to ask questions we already answered on the previous page There's a plugin which specifically does that, but I forget what it's called or where I saw it ... Anyway, muting the channel seems to do the same thing, although it's not dynamic. I've seen something called "FX Freeze", which wasn't what I was thinking of, but it seems to do more or less the same thing as what this other plugin does. It's on KVR. You need to get a utility called SfPack (it's free and you should be able to find it on Google), then use it to decompress the .sfpack file. You'll then get the SF2 file from that, which you can use normally.
  13. Yeah, they have to process your order before they can send it to you. It wouldn't be any good for them if you sent them bad credit card details and they'd already given you the product. No, they send you a username and password (I recommend you print that out and keep it in a safe place) which you put into a section of the FL Studio website. After you've done that, you start the download of your registry key from their site. As soon as you've got your username and password, you can access the site as a user.
  14. I don't know what you mean by "won't make sounds". When you load them into sampler channels and write patterns for them, they won't fire when you hit play? The files themselves could be corrupt, try reinstalling the program or downloading it again. While it might not have anything to do with your problem, a lot of FL's included samples are encoded with a 32-bit float bit depth. This doesn't mean much outside of FL or CoolEdit/Adobe Audition (it's just for editing purposes), but a lot of media players will choke on them. You might, then, have some problems with those particular samples. Of course, corrupt files probably won't play anywhere, so this might be besides the point.
  15. It's a rather (in)famous orchestral soundfont. Should be on Darkesword's soundfont website.
  16. First, MIDI isn't audio; it's a standard that allows MIDI devices to communicate with each other. Presumably you want the GM MIDI sounds to be rendered. Load up a Fruity LSD in an FX channel in the mixer (doesn't matter which channel, although if there's any effects after the LSD, it'll render with those effects), and change the port number in the top right corner of the LSD to the same as your MIDI Out channels. MasamunE: That "clip" you're talking about is probably a result of you cutting and cropping it. You could get rid of it with some use of FL's built-in volume envelope. Under the INS tab of the sampler channel, either click the LED at the top left of the volume envelope or adjust one of the controls to turn it on. I suggest changing the attack slightly, but don't make it too slow. I suggest using reverb on just about everything, as it really does make it sound more natural, but not too much. You can kill a good mix with too much reverb. Basically, changing the sampler's pitch will change the speed it's played at. Not sure what else you really want. Search function is under the OCR logo. Click the link that says "Search". The "official" OCR FL FAQ should be finished sometime this year, if I can get my arse into gear
  17. You might want to ask that in either Synthesis 101 or VST/DX Requests; it's not really FL-specific.
  18. Yep, the lower the bars, the lower the tempo. You can go from 10 to 999 on that. Also, it says on the hint bar (under File, Edit etc.) what the value being changed to is. There's a whole section in the help file dedicated to improving CPU and memory performance under the "Troubleshooting" section, if you want a look. Another way to improve performance is to get an APG soundcard, rather than the onboard sound. FL will utilize whatever DirectSound or ASIO drivers that are on it, and reduce some of the strain on your system.
  19. MasamunE: That was a long post, and I'm not really sure what you're asking. All I can really tell from what you've said is that you're using a LOT of resources with the amount of soundfonts you're using and by cloning channels so much. The patterns that are automated are listed under "Current project>Automation" in the sidebar. I'm not sure what else you really want (I don't work with 3D animation programs so I don't know what you mean by "keyframes").
  20. Hmm, so how am I supposed to handle clipping? First you say to level it so the loudest peak reaches +0dB max, but then you say doing that kills a lot of a song's dynamics. I think he's talking about using a compressor to keep outputs at 0db. You can in fact lose dynamics by lowering the volume too much.
  21. Fixed it; presumably Lycos runs on Apache, and links are case sensitive. Anyway, nothing looks wrong from the screenshot ... This is only happening when you export the MIDI? The only thing that I can think of is that there's some automation doing it. If that's not it, I have no idea. If we could see the FLP file, we might be able to better help you.
  22. Some very nice piano work from Dhsu. I take my metaphorical hat off to you A very mature level of arrangement and performance is shown here, and it makes for a very listenable piece indeed. I look forward to your work in future. As for the noise in the background, I can hear it too, but only if I turn my headphones up really loud. It's probably just background noise, and I'm guessing the reason it keeps on coming in and out would be if Dhsu used a compressor at all (might be wrong, though, in which case I have no idea). Not very much can be done about it unless he records it again.
  23. 1. It's not impossible to search, use the "Search" link at the bottom right of the the OCR logo. 2. You want the samples and sounfont request thread, anyway. Try to keep discussion in this thread FL-centric. 3. Using different colors in the piano roll will have no effect on the performance of any of FL's generators. Nice FLP. Exporting as a zipped loop includes all the samples you used (there's a few samples missing, which you have to provide in order for anyone to hear the completed song).
  24. Montblanc: Set the "PORT" display-thing at the top-right corner of the wrapper window that the plugin is in to whatever port you like. Then load up MIDI Outs and set all of them to that same port. Then assign them to the channels you've set in that plugin. Calabrel: Check to see if there's any automation that's making the channels revert back (it's under Current Project>Automation in the side bar, and it'll normally be under "initiallized controls" in this case). Once you've found the event(s) that are causing this, right click on the automation event, select "edit events", then in the new window that pops up, press ctrl+A (select all) and hit delete. No more automation!
  25. siiiiiiigh ... I just finished archiving the relevant posts from pages 45 to 90. Are you there, Mythril? How're you going?