I've gone through your blog post detailing some of the new features and i can tell that there's a lot of cool things in there now that i've wanted for a long time! i had grown a bit tired of lsdj after a few years being blocked into a specific mindset. feeling like i've hit the wall of what i can do (i know it's never true it was just my perception) but there's a lot of cool stuff now ti reignite my excitement and discover new sounds!

also i'm glad i discovered your blog coz there's a lot of fun reads in there! thank you again defensem3ch

defensem3ch wrote:

that being said let me list some features that will help you kind of get started right away:

all the L commands are now different, so that L01 is the fastest and LFF is the slowest (inverted from how v4 worked)

the next most immediate change is the "PITCH" feature in pulse and wave - if you press A+Up, you can choose "drum" and this emulates the pitch slides for kicks. i don't recommend making a kick with "FAST" pitch although you definitely can if you want to. the transpose feature is also useful for kicks since if you turn it off, you can use the chain transpose column on phrases with kicks and bass and the kicks won't change pitch! i made a kick drum tutorial video here (in v6 it was called P/L/V but in v7+ it's just called PITCH) https://www.youtube.com/watch?v=8ihMjHn90zY

in v7/8, table AUTOMATE is now called STEP and is selected by pressing A+Left/Right where it says PLAY next to TABLE

there's a new feature called CMD/RATE (it was called FX/SPEED at the time i wrote the blog) that controls the rate of C commands (and P commands which also work in the noise channel along with C)

the screen navigation has changed - there are only 2 rows, and each row remembers where you left off when you switch between them. the exceptions for this are that going upwards from a wave instrument still takes you to the synth screen, and going upwards from a G command still take you to the groove screen.

i also wrote a tech blog covering some more of the changes in v7: https://chiptuneswin.com/blog/intense-t … -features/

i'm trying to think of the major ones but it's kind of hard to remember since there are so many. feel free to message me on any platform including here if you want to have a chat, i'm happy to help!

Thank you very much for that detailed reply! I really appreciate it. I’ll download the latest version and flash it tonight and start discovering what’s new.

The last version of lsdj i ever used was 4.x.x i saw that there was lots of new developments for lsdj in the last few years and that's awesome... but since 4.x.x i have no idea now what are the new things introduced and new features...

reading the changelog is a long and tedious process since most things are bug fixes and it's hard to discern which is new features and which are just bug fixes...

i downloaded the latest manual version but the last updated one is for version 6.8.5 but lsdj now has reached 8.1

was wondering if there's somewhere where i can have a more upper level view of the new features that were introduced to lsdj (like short resume of features added only)

if not then i guess i have no choice but to read the entire changelog and filter out all the new features indicated in there... perhaps in my endeavour i could make my own resume of features.

thanks...

sorry for the questions, i've been away from chiptunes for years now and i'm getting back into it and i wanna catch up on all the developments

hi, this is a quick question i had, would it be possible to do the prosound mod (pre-pot) and keep the headphone amp signal functional so when i wanna just use my headphones for composing?

I was wondering if the headphone amp circuitry being still intact would affect the output of the line level or as long as i dont have a headphone plugged in i can run a line out?

normally it would be line out for shows/live PA, headphones for composition.

also since the headphone amp circuit is noisy and not that great... would it be better to make anther DIY headphone amp circuit instead? has anyone done this before?

thanks

5

(22 replies, posted in LittleGPTracker)

BLEO wrote:

OK, two ideas:

1) Which build of piggy are you using? From that log, it looks like debian? There's a specific pi build here at the bottom with the ghettos (ALWAYS use the ghettos): http://littlegptracker.com/download.php
2) That being said, once you use the ghettos, different sound libs need to be installed.

sudo apt-get install libasound2-plugins:i386

And maybe you'll have to remove the ":i386" again, maybe not! This is what got it working for me on debian but I've never tried on a pi...


no i'm using the lgpt.rpi-exe

I've already installed those libraries though... it only worked when i removed the :i386 otherwise it wasn't retrievable.

6

(22 replies, posted in LittleGPTracker)

i think i need to figure out how i can change lgpt to play using either the usb audio interface or using pulse .....

I'm not sure how i can do that.. i dont really know all the of the config options.

EDIT:

Here is the lgpt log file:

[CONFIG] Got config path=/home/pi/lgpt_DEB/bin/config.xml
[-D-] Audio
[CONFIG] Got value for AUDIOBUFFERSIZE=512
[AUDIO] Audio object initialised with
[AUDIO] Api:
[AUDIO] Device:
[AUDIO] Buffer size:512
[AUDIO] Pre Buffer Count:2
[AUDIO] Current API: Linux ALSA
[AUDIO] Found device hw:bcm2835 ALSA,0
[AUDIO] Found device hw:bcm2835 ALSA,1
[AUDIO] Found device
[AUDIO] Selecting: hw:bcm2835 ALSA,0
[DISPLAY] Using driver x11. Screen (1920,1080) Bpp:32
[CONFIG] Got value for SCREENMULT=4
[DISPLAY] Creating SDL Window (1280,960)
[DISPLAY] Preparing fonts
[DISPLAY] Preparing font cache
[DISPLAY] Preparing full font cache
[MIDI] 2 input port(s)
[MIDI]  Midi Through:0
[MIDI]  AudioBox USB:0
[MIDI] 2 output port(s)
[MIDI]  Midi Through:0
[MIDI]  AudioBox USB:0
[MAPPING] No (bad?) mapping file (bin:mapping.xml)
[-D-] Mapping config
[MAPPING] Attached /event/a to key:0:a
[MAPPING] Attached /event/b to key:0:s
[MAPPING] Attached /event/left to key:0:left
[MAPPING] Attached /event/right to key:0:right
[MAPPING] Attached /event/up to key:0:up
[MAPPING] Attached /event/down to key:0:down
[MAPPING] Attached /event/lshoulder to key:0:right ctrl
[MAPPING] Attached /event/rshoulder to key:0:left ctrl
[MAPPING] Attached /event/start to key:0:space
[*ERROR*] Only 8/16 bit supported
[*ERROR*] Failed to load samples kick-thump.wav
[*ERROR*] Only 8/16 bit supported
[*ERROR*] Failed to load samples kick-tape.wav
[AUDIO] RTAudio device hw:bcm2835 ALSA,0 successfully open - buffer=512
[-D-] Out initialized

7

(22 replies, posted in LittleGPTracker)

I installed MilkyTracker on the pi to test the audio quality while playback and it's much cleaner! it seems like only lgpt has issues....

When i ran milkytracker from the cli it said

SDL: using audio driver: pulse

Meanwhile when i run lgpt it says:
RtApiAlsa::getDeviceInfo: snd_pcm_open error for device (hw:0,1), Device or resource busy

but it still plays audio but has the shitty sound.

8

(22 replies, posted in LittleGPTracker)

herr_prof wrote:

Are you running piggy from the command line or from the desktop? Did you run apt-get update?

Cant compare two different apps, linux succckkks

Id suggest

-Disable booting to the Desktop but rather to the command prompt
- making sure everything is updated
- instal alsa tools if you havent
- boot the pi with the usb soundcard installed, dont add it
- and show us the config

yeah! good call on the CLI instead of the DE, worked like a charm.
I made a script to run lgpt on startup and now it works great...

However... the audio properties are still the same...

crackling frequently sometimes even slight hiccups in the timing of the sequence...

as for the audio soundcard i'm using a Presonus audiobox USB (only thing i have) it's supposed to be bus powered though...

i can't seem to get any audio out of it however... it still is stuck on the analog output.

9

(22 replies, posted in LittleGPTracker)

herr_prof wrote:

Can you post your config.xml? maybe you have bad syntax in there.

What usb sound card? Some cheap ones are SOFTWARE ONES that force the udnerpwoered pi to do some rendering, the crackling is related to cpu load.

Will do that once I get home but the thing is, when I’m watching YouTube or something the sound is excellent. It’s only when I’m on LGPT that it crackles and pops even though the CPU LOAD shown on top in raspbian is very very low

10

(22 replies, posted in LittleGPTracker)

herr_prof wrote:

-use a usb sound card
- add the fullscreen arg to the comfig.xml

the fullscreen thing doesn't work even as an argument, but added the screen multiplier and it makes it bigger so that's a fix.

however the audio is still an issue, i tried with a usb soundcard but it doesn't really work still...

11

(22 replies, posted in LittleGPTracker)

i managed to get lgpt running on raspbian now but i can't seem to make it fullscreen (it says to add the -fullscreen flag next to the excution command which doesn't seem to work for me)

also my audio is really distorted from both HDMI and analog outputs... I tried installing those libjack0:i386 packages but on rpi it doesn't find it, not sure what else i need to change/install/fix to get the sound to come out nicely without distortion...

im not a super expert with linux and especially when it comes to audio interfaces like pulse audio and alsa and all that jazz im very ignorant.

would love some help :3

UPDATE:

i managed to install those packages by removing the ":i386" end of it and it worked but there was no difference in the audio... i started messing around with the config.xml file and added a buffer of 512 for the audio and that seems to have helped but still sound distorts if rpi is set at loud volume or if there's a lot of stuff going on in the song (using the 10k demo as a test song)


once i manage to get those fixed ideally id love to manage to find a way to get the lgpt program to work on start;up without any other desktop environment elements as if it's trully just running natively (no task bar or menus or window top bar)

i'm not really sure how to do any of those things on rpi since the wiki seems to be pretty light on rpi specific explanations


perhaps once i get everything going (if ever) i could maybe update the wiki to help out more rpi bravehearts

12

(22 replies, posted in LittleGPTracker)

herr_prof wrote:

Ive not had the money to burn, but there are lots of DIY rasberry pi handhelds you can buy now that are prebuilt. You could probably configure that to autoboot lgpt, and use any usb midi device as brady mentioned. If you are handy with linux.

Yeah ive been looking at stuff like the gameboy zero project and considering hacking my own variation of it with the parts i already have just to avoid spending some unnecesary cash.

i think the most complicated part will be to convert the buttons into keyboard presses... i shoudl test out lgpt on linux/rpi before i get into this whole ordeal i guess

13

(22 replies, posted in LittleGPTracker)

Hey guys,

It's been a long time since i've touched any chipmusic gear but im finally back at it and i was curious about the state of LGPT in 2019...

I'm managed to get my PSP 1001 running again and surprisingly still works well with LGPT but the lack of midi really makes it hard to try and use it live with any other gear (ideally with a couple of gameboys running LSDJ synced with MIDI)

So i was wondering what would be the best device to buy that would have an easy way to sync over MIDI with lsdj gameboys (DMG gameboys)

I was thinking of building my own raspberry Pi based LGPT device but a project like that would still get quite complicated and not very gig friendly with all the wires and stuff...

14

(4 replies, posted in General Discussion)

come to Montreal instead wink

I care!

16

(39 replies, posted in Nintendo Handhelds)

So im reviving this very old thread because ive been using nanoloop recently and loving it so much i want to start using it as my core component in my setup....

I have both an SP 100 and a DS Lite. i lvoe the sound on the DS lite. i got a chance to use it at a show the other day and it was kicking hard as balls.

there is however an issue that i ran into that for me is a complete dealbreaker for using the DS unfortunately.

when running on DS lite... the tempo of nanoloop is not accurate. ive done some tests @ 120bpm and after around 60 bars the tempo was behind by a 1/16th note. which is extremely drastic and unacceptable...

I know that you can't sync the DS to anything but i was at least hoping i could manually beatmatch with my other gear but if there's gonna be some drift like this it's gonna be pratically impossible to use with other gear.

so for anyone who's planning on using DS with other gear, don't. or at least do some tests about tempo drifts before you do.

I really like the DS sound and screen and buttons but ..... it's just not usable.

Does anyone else notice this? maybe it's just my DS? i used to think that because DS is more advanced (pun not intended) it would be even more acurate... but my SP was solid over 200 bars.