PSPSeq on TA-082 & 1.5 fw? Which firmware is best?
finagle
Can I upgrade it to the latest 3.90-m33-2 firmware and then install
PSPSeq? OR should I install it on 1.5? Any performance advantages
between either firmware as far as PSPSeq goes? (I'm actually a noob to
all this until yesterday when I started reading up on it. But this is
based on my assumption that since I'm running 1.5, I don't have to
worry about downgrading or anything like that and I can just install
custom m33 firmware on top of it, right?)
And are there any issues with running PSPSeq on a PSP with TA-082
motherboard (other than not being able to downgrade past a certain
firmware, which doesn't apply to me since I have 1.5)?
Thanks!
Ethan Bordeaux
i use 1.5, phat, and a non-TA082 for writing the program. i'd say
download PSPSeq 2.10 and try running what's in the 1.5 directory to
see if it works. as for upgrading to 3.90 m33-2, i think someone
reported a problem with that firmware but i'm not positive. there are
apparently people using 3.71 with success. check this out:
http://groups.google.com/group/pspseq/browse_thread/thread/f1dcc20bddb7f39e#
the key thing is to use the eLoader. also there are definitely people
on 3.40 and 3.52 custom FW:
http://groups.google.com/group/pspseq/browse_thread/thread/564b7c17c312ccce#
but i don't know the motherboard story for them. sorry i can't answer
this question definitively. the firmware question is something i'm
pretty unknowledgeable about and is definitely the worst thing about
PSP homebrew. alas.
finagle
V2. Then I installed PSPSeq dragging the 1.5 folder into GAME150. And
it works just fine! When you go to the game memory stick menu PSPSeq
icon shows up along with the Corrupted Data icon which is a minor
annoyance but I understand that this is normal behavior and should
stay there for everything to work.
On Feb 22, 5:17 pm, "Ethan Bordeaux" <ethan.borde...@gmail.com> wrote:
> hi - welcome to the list! :)
>
> i use 1.5, phat, and a non-TA082 for writing the program. i'd say
> download PSPSeq 2.10 and try running what's in the 1.5 directory to
> see if it works. as for upgrading to 3.90 m33-2, i think someone
> reported a problem with that firmware but i'm not positive. there are
> apparently people using 3.71 with success. check this out:
>
> the key thing is to use the eLoader. also there are definitely people
> on 3.40 and 3.52 custom FW:
>
> but i don't know the motherboard story for them. sorry i can't answer
> this question definitively. the firmware question is something i'm
> pretty unknowledgeable about and is definitely the worst thing about
> PSP homebrew. alas.
>
H- Seiken
finagle
itself of course, but the folders inside them.
Ethan Bordeaux
actually have to upgrade and use my PSP for (gasp) games as well. :)
one thing i'd recommend you try before giving PSPSeq the total a-ok is
recording a song to WAV. i think that has been a problem for some
people with new custom FW - it should record but i think it may also
crash afterwards. but if that's the only problem it's far from the
end of the world.
finagle
gave me this error:
ERR: NEED 704656 BYTES, FOUND -237502464
On Feb 24, 9:51 am, "Ethan Bordeaux" <ethan.borde...@gmail.com> wrote:
> aw man that's awesome news! with patapon being released i may
> actually have to upgrade and use my PSP for (gasp) games as well. :)
>
> one thing i'd recommend you try before giving PSPSeq the total a-ok is
> recording a song to WAV. i think that has been a problem for some
> people with new custom FW - it should record but i think it may also
> crash afterwards. but if that's the only problem it's far from the
> end of the world.
>
Ethan Bordeaux
could you try another test for me - create a synth which has wav file
playback and load in a WAV file (or load a song which has wav files in
it (03DNB.SEQ in the files section is a good example). does that
work? also, try bringing up the about box (SYSYTEM->ABOUT). there
are a couple places i make a low level PSP system call. maybe that's
not functional (or functioning the same way) as it does on 1.5
firmware.
and actually -237502464 is an interesting number in hex - it is
F1D80000. way too round to be a coincidence. hmm.
there's a chance i could do a special build that doesn't perform that
memory available check but you could very well hang (or worse?) if you
accidentally try and write more data than you have room for.
Ethan Bordeaux
memory stick?
Ethan Bordeaux
stick that could explain this. the way i wrote the program i think it
only will work properly if you have less than 2GB of memory available.
can anyone out there confirm? have any of you used a memory stick
with >2GB available and successfully written WAV files to it?
if this really is the issue, the really dumb fix is to fill up 1/2
your memory stick with fun stuff so less than 2GB is avaialble or use
a smaller stick for PSPSeq.
On Sun, Feb 24, 2008 at 6:14 PM, Ethan Bordeaux
finagle
Duo and it is currently mostly empty. I'll try to fill up half of it
and test again, as well as the other tests you mentioned.
On Feb 24, 3:31 pm, "Ethan Bordeaux" <ethan.borde...@gmail.com> wrote:
> sorry for all the messages but if you have a mostly empty 4GB memory
> stick that could explain this. the way i wrote the program i think it
> only will work properly if you have less than 2GB of memory available.
> can anyone out there confirm? have any of you used a memory stick
> with >2GB available and successfully written WAV files to it?
>
> if this really is the issue, the really dumb fix is to fill up 1/2
> your memory stick with fun stuff so less than 2GB is avaialble or use
> a smaller stick for PSPSeq.
>
> On Sun, Feb 24, 2008 at 6:14 PM, Ethan Bordeaux
>
> > one other thing - how much memory do you really have available on your
> > memory stick?
>
> > On Sun, Feb 24, 2008 at 5:59 PM, Ethan Bordeaux
> > <ethan.borde...@gmail.com> wrote:
> > > how interesting! that's a pretty buried in there error message.
> > > could you try another test for me - create a synth which has wav file
> > > playback and load in a WAV file (or load a song which has wav files in
> > > it (03DNB.SEQ in the files section is a good example). does that
> > > work? also, try bringing up the about box (SYSYTEM->ABOUT). there
> > > are a couple places i make a low level PSP system call. maybe that's
> > > not functional (or functioning the same way) as it does on 1.5
> > > firmware.
>
> > > and actually -237502464 is an interesting number in hex - it is
> > > F1D80000. way too round to be a coincidence. hmm.
>
> > > there's a chance i could do a special build that doesn't perform that
> > > memory available check but you could very well hang (or worse?) if you
> > > accidentally try and write more data than you have room for.
>
finagle
under System shows up just fine. I also tried adding and deleting wav
synths and that seems to work fine as well. I'll test the 2GB memory
issue when I can get to it.
By the way, I have to say, I love the interface on PSPSeq. Quite
genius, methinks. I love the 64 steps, the minimalist aesthetic, and
the color scheme. Thanks for making this.
Ethan Bordeaux
plans to do a 3.00 release but that's many months away. i may make a
mini-release and post it on the PSPSeq board. along with this fix i
might try and add in a bugfix/feature related to setting volume in
non-triggered tracks (if you don't know what that means don't sweat
it).
Ethan Bordeaux
> genius, methinks. I love the 64 steps, the minimalist aesthetic, and
> the color scheme. Thanks for making this.
cool. :) this is the first GUI i ever made so it was a huge learning
experience. i want to do a big rev of the interface (mostly to make
it faster to edit synths) but i'm happy you're digging what's there.
since it sounds like you're new to the program the biggest piece of
advice i can offer is to read and learn all the shortcuts in the quick
reference sheet. a lot of people didn't realize there were so many
control options/rates for setting synth values and other little
features that are hidden behind key combos.
have fun, ask questions, and post some SEQs when you've made 'em!